Bugzilla – Bug 134240
no suspend to RAM after close LID
Last modified: 2005-11-24 11:35:32 UTC
When I close the Display LID then turns the Notebook not in suspend to RAM mode, how definied in the corresponding YAST Modul. Manually switch to this mode works well, also suspend to disk works ( manually ) After closing the LID the system doesnt show any actions. The logfile in /var/log/acpid shows an action: [Thu Nov 17 20:04:38 2005] notifying client 6656[0:0] [Thu Nov 17 20:04:38 2005] notifying client 6815[0:0] [Thu Nov 17 20:04:38 2005] notifying client 6825[0:0] [Thu Nov 17 20:04:38 2005] completed event "ibm/hotkey HKEY 00000080 00005002" System is a IBM T41 , Kernel is 2.6.13-15-default.
Holger, might this be the wrong event? On a T41p I see no event in /var/log/message during lid-close, but that might be a local problem.
It seems that the ibm_acpi module hides the real acpi events on you machine and the powersave daemon cannot handle the ibm specific "hotkey..." events except the sleep button. The only feature the ibm_acpi module provides at the moment is setting the brightness of the display. But I noticed that on an t41p, this works also without the ibm_acpi module. So please remove the module from /var/lib/acpi/laptop_modules (don't remove the file!), restart the laptop and check whether the lid close works as ecpected. If not, please attach the output of /var/log/acpid again.
after removing the ibm_acpi module from /var/lib/acpi/laptop_modules how described I'v seen no changes, but in /var/log/acpid were no more actions logged like "...hotkey...value". I have found a solution, which I should see before I send a bugreport: in the grub - configuration I've added as kernel parameter acpi=on. Note: this entry is not needed on other of my machines such several toshiba laptops, and wasn't required on SuSE 9.3. However, perhaps is it an ibm specific acpi problem. You can close my request.
This is very strange, I have never seen acpi=on needed, since it is activated as default. That parameter is only needed for very old BIOS (<2000) which cause normally ACPI to be deactivated. I'll close this bug but recommend to update your BIOS. (It might even be aq newer BIOS with a wrong creation date - I have seen such BIOS :( )