>I started installing Gentoo Linux 2006.0 with Kernel 2.6.16.x (Vanilla, >but with vesafb-tng, later also suspend2). With this Kernel, I >was never >able to power off my Notebook properply. After running `shutdown -h >now', init was called and everything went down without any problems. >Then, there was written "Power off.". However, the Notebook was never >powered off anyway. I had to do it myself every time. > >Well, this changed with Kernel 2.6.17. I'm using Kernel 2.6.17.1 with >the ACPI patchset, vesafb-tng, suspend2 and SquashFS3 now. >My actual problem is, that the Notebook powers down without any >problems, when I did not start any Desktop Environments. >But after starting any DE (I tried Fluxbox, GNOME, KDE, XFCE and >BlackBox so far), the Notebook is not powering down anymore and I have >to do it manually again. This seems very strange to me. I also disabled >any ACPI features in the DE (like a battery-applet or something like >this; Black- and FluxBox doesn't even have such) without any luck. So the latest kernel powers down properly, but only if you don't start X? With older kernels it would not power down even without X? Sounds like an issue with the video driver/BIOS. >Well, my question is, whether this could be an ACPI problem? >If yes, how >could it be fixed? I'm using a costum DSDT table already. Not, that >there were many errors or warnings I found with the INTEL(r) ACPI tool, >the only warning was about the _WAK function, which I could >remove using >a workaround in the Gentoo Forum >(http://forums.gentoo.org/viewtopic.php?t=122145). >Apart from this, the table is clean. The compiler says, that there are >36 optimizations, but I do not understand this, though. Are that >optimizations, that can be done while compiling the table to a *.hex >table? Although I'm running the new, clean table, the IASL says >everytime something about 36 optimizations. Actually, I'd prefer that you not modify your DSDT at all. Verify that you have the latest BIOS from the vendor, and if Windows can deal with it and Linux can not, then it is a Linux bug that we need to know about -- not something you want to hide by modifying the firmware. So check your BIOS. Check your video driver version, and the version of X in general. Yes, the issue is probably an interaction with ACPI, but is quite possibly a firmware or video software platform-specific issue. -Len - 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
