So i915 didn't load on 2.6.37-3, on 2.6.35-5.13 you got a crash which is bug #676963 and was fixed on 2.6.37-5.14 and 2.6.37-7 appears to work. One thing all 3 had in common is that vesafb did not get loaded at all. One small thing I noticed in the earlier dmesg's was that vesafb was trying to use 1024x768x32 on that machine's 1024x600 panel which was a problem corrected in the 0602 bios release for this machine. It would be interesting to know the results of booting 2.6.37-11-generic on your alpha 1 userspace if possible so we can rule some more potential causes out, I'm not seeing anything obvious from these logs but hopefully someone else might.
So i915 didn't load on 2.6.37-3, on 2.6.35-5.13 you got a crash which is bug #676963 and was fixed on 2.6.37-5.14 and 2.6.37-7 appears to work. One thing all 3 had in common is that vesafb did not get loaded at all. One small thing I noticed in the earlier dmesg's was that vesafb was trying to use 1024x768x32 on that machine's 1024x600 panel which was a problem corrected in the 0602 bios release for this machine. It would be interesting to know the results of booting 2.6.37-11-generic on your alpha 1 userspace if possible so we can rule some more potential causes out, I'm not seeing anything obvious from these logs but hopefully someone else might.