On Sun 2008-07-13 22:22:06, Henrique de Moraes Holschuh wrote: > On Sun, 13 Jul 2008, Andi Kleen wrote: > > It probably switches to protected mode. I noticed this on my old > > Fujitsu laptop when I tried to make the S3 wakeup run in the s2ram x86 emulator > > and found it entered protected mode at some point, which x86emu > > didn't support. > > > > I guess Lenovo is doing the same. > > > > And that protected mode code relies on some GDT values that have been > > loaded earlier when the BIOS also went into protected mode. > > > > It seems the BIOS programmers really don't like real mode anymore. > > Somehow understandable. > > If it were just Lenovo, it shouldn't be too difficult to get them to fix the > BIOS. But since other vendors have the same problem, that won't fly as a > solution. With all the BIOSes in field, practically impossible to update? (My x60 has no CDrom..) No, I don't think we can expect fix from BIOS vendors. Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html -- 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