Sorry for the delay in testing. This appears to work and fix the problem. --Andy On Mon, Jul 14, 2008 at 12:18 AM, H. Peter Anvin <hpa@xxxxxxxxx> wrote: > H. Peter Anvin wrote: >> >> The most likely explanation for this is that the VESA BIOS expects to be >> entered in Big Real Mode (*.limit = 0xffffffff) instead of ordinary Real >> Mode. Here is a completely untested patch which changes the segment >> descriptors to Big Real Mode instead. It would be worth testing out. >> > > ... and here is one that actually has a prayer of actually working. > > -hpa > > > --- AV & Spam Filtering by M+Guardian - Risk Free Email (TM) --- > -- 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
