On Sun, 2007-02-25 at 11:07 +0000, Andrew Nelless wrote: > On Sat, February 24, 2007 11:30 pm, Antonino A. Daplas wrote: > > > > How about booting with just vga=normal? > > > > > > Tony > > > > That seems to work too. I've rebooted about 20 times in a row > and it hasn't done it again yet. Why would this only occur > at higher modes? > > In the 2.6.20 dmesg log it reads "Nvidia board detected. > Ignoring ACPI timer override." whereas in 2.6.21-rc1 it doesn't. > Could this be the culprit? > I don't know, probably the ACPI code can now probably detect the presence or absence of the HPET timer. Can you remove CONFIG_FB_VESA support from your kernel config but boot as if you have vesafb (ie with vga=<VESA mode number>). Your machine may boot to completion but you will have a blank screen. But you should be able to have an output in netconsole and you can start X. I wanted to know if the lockup is related to the framebuffer. Tony - To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
