From: Matthew G. <mj...@sr...> - 2003-03-02 18:48:44
|
Having upgraded my BIOS to the latest available from IBM, I've very nearly got working ACPI. 1) S1 usually works correctly, but the backlight doesn't get switched off. Is there any trivial way of dealing with this? 2) S3 suspends and resumes. On resume, the backlight comes back on the machine is responsive from the network. The keyboard and mouse don't work, though - if I use modular input drivers, a rmmod i8042 && modprobe i8042 brings things back to life. Switching on the Toshiba keyboard kicking code doesn't result in any change in behaviour. The symptoms are that no input results in an increase in interrupts until I reload the module. The other problem is that the screen doesn't come back. The backlight comes on but no text appears. This is the case with both vesafb and vgacon - sometimes (but not predictably) a small amount of text is printed, but it looks like it's left over from lilo or something. The screen seems to be in 640x480 text mode, rather than the 800x600 it should be in when I'm using the VESA driver. Killing X and restarting it results in X starting up, but I can't switch back to a text console (they're just garbage). Passing acpi_sleep=s3_bios or s3_mode doesn't seem to make any difference. 3) S4 with SWSUSP sometimes works, but usually I hit the BUG() in ide-disk that others have reported. Is there any understanding behind why that one's happening? It certainly seems a lot better than things have been before now. -- Matthew Garrett | mj...@sr... |