Bug#475097: powersaved: Thinkpad T60: Fn+F4 no longer suspends-to-ram machine
There appears to have been some progress on this bug. powersaved now responds to Fn+F4. It seems to get the event from HAL (when I stop hal, powersaved no longer responds). Wow, is the future really here?? No, things are still badly broken: - Fn+F4 suspends to disk, not ram. - Fn+F12 does nothing. - In /etc/powersave/events, there appears to be only one event (EVENT_BUTTON_SLEEP) we can respond to. - Have they never heard of separate sleep and hibernate buttons? - Where are the events even documented? (nowhere!) - In /etc/powersave/events, the possible actions appear to be suspend_to_disk and suspend_to_ram. - Have they never heard of the most useful hybrid (aka s2both) mode? - Is there any setting to use hybrid mode for suspend? (no, it goes through HAL, and HAL offers no such configurability) - Digging through powersave_manual.txt.gz reveals several instances of the string novell, which pretty much explains all of the above. Andrew -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#475097: powersaved: Thinkpad T60: Fn+F4 no longer suspends-to-ram machine
On Wed, 9 Apr 2008, Michael Biebl wrote: Sven-Haegar Koch schrieb: Package: powersaved Version: 0.15.20-2 Severity: normal Until the powersaved update of today pressing Fn+F4 on my Thinkpad T60 started suspend to ram, which worked without problems. Now when pressing it I only get some logs from acpid into syslog, nothing from powersaved anymore: (/etc/powersave/common DEBUG=31) Apr 9 01:11:06 aurora acpid: received event ibm/hotkey HKEY 0080 1004 Apr 9 01:11:06 aurora acpid: notifying client 4028[0:0] Apr 9 01:11:06 aurora acpid: notifying client 27786[115:122] Apr 9 01:11:06 aurora acpid: notifying client 4596[0:0] Apr 9 01:11:06 aurora acpid: notifying client 718[0:0] Apr 9 01:11:06 aurora acpid: executing action /etc/acpi/sleepbtn.sh Apr 9 01:11:06 aurora acpid: action exited with status 0 Apr 9 01:11:06 aurora acpid: completed event ibm/hotkey HKEY 0080 1004 Is that really all? No other logs of powersaved e.g. when it starts. I'm wondering if the debug log is working at all. There are log messages at the start of powesaved: Apr 10 20:59:24 aurora powersaved: Starting powersaved with ACPI support Apr 10 20:59:24 aurora acpid: client connected from 20760[0:0] Apr 10 20:59:24 aurora acpid: 1 client rule loaded Do you get any messages in the syslog, if you run powersaved -v31 -f /var/run/acpid.socket This generates way more logging than only having DEBUG=31 in /etc/powersave/common: Apr 10 21:02:36 aurora powersaved[21167]: Info (readConfigFile:127) Empty value in file /etc/powersave/common line 67, key 'NOTIFY_METHOD' Apr 10 21:02:36 aurora powersaved[21167]: Info (readConfigFile:127) Empty value in file /etc/powersave/common line 78, key 'BOOT_LOADER' Apr 10 21:02:36 aurora powersaved[21167]: Info (readConfigFile:127) Empty value in file /etc/powersave/common line 90, key 'POLLING_INTERVAL' Apr 10 21:02:36 aurora powersaved[21167]: Info (readConfigFile:127) Empty value in file /etc/powersave/common line 101, key 'SCREENSAVER_DPMS_OFF' Apr 10 21:02:36 aurora powersaved[21167]: Info (readConfigFile:127) Empty value in file /etc/powersave/common line 113, key 'SCREENSAVER_BLANKONLY' Apr 10 21:02:36 aurora powersaved[21167]: Info (readConfigFile:127) Empty value in file /etc/powersave/common line 125, key 'POWERBTN_DELAY' Apr 10 21:02:36 aurora powersaved[21167]: Info (readConfigFile:127) Empty value in file /etc/powersave/thermal line 18, key 'ENABLE_THERMAL_MANAGEMENT' Apr 10 21:02:36 aurora powersaved[21167]: Info (readConfigFile:127) Empty value in file /etc/powersave/thermal line 36, key 'THERMAL_POLLING_FREQUENCY' Apr 10 21:02:36 aurora powersaved[21167]: Info (readConfigFile:127) Empty value in file /etc/powersave/cpufreq line 14, key 'CPUFREQ_CONTROL' Apr 10 21:02:36 aurora powersaved[21167]: Info (readConfigFile:127) Empty value in file /etc/powersave/cpufreq line 22, key 'MAX_CPUS_ONLINE' Apr 10 21:02:36 aurora powersaved[21167]: Debug (PS_Config:36) Init power management interface Apr 10 21:02:36 aurora powersaved[21167]: Debug (SchemeConfig:33) SchemeConfig Constructor Apr 10 21:02:36 aurora powersaved[21167]: Info (initSchemes:212) Scheme scheme_powersave found. Apr 10 21:02:36 aurora powersaved[21167]: Info (initSchemes:184) Default Battery scheme is scheme_performance Apr 10 21:02:36 aurora powersaved[21167]: Info (initSchemes:188) Default AC scheme is scheme_performance Apr 10 21:02:36 aurora powersaved[21167]: Debug (PS_Config:36) Init power management interface Apr 10 21:02:36 aurora powersaved[21167]: Debug (SchemeConfig:33) SchemeConfig Constructor Apr 10 21:02:36 aurora powersaved[21167]: Info (initSchemes:212) Scheme scheme_performance found. Apr 10 21:02:36 aurora powersaved[21167]: Info (readConfigFile:127) Empty value in file /etc/powersave//scheme_powersave line 176, key 'MAX_CPUS_ONLINE' Apr 10 21:02:36 aurora powersaved[21167]: Info (readConfigFile:127) Empty value in file /etc/powersave//scheme_performance line 175, key 'MAX_CPUS_ONLINE' Apr 10 21:02:36 aurora powersaved[21167]: Info (openSystemConnection:252) dbus_bus_get(): Success. Apr 10 21:02:36 aurora powersaved[21167]: Info (openSystemConnection:277) Successfully acquired the interface org.freedesktop.Policy.Power Apr 10 21:02:36 aurora powersaved[21167]: Debug (PM_Interface:59) Constructor PM_Interface Apr 10 21:02:36 aurora powersaved[21167]: Info (Brightness:40) No Laptop Panels found Apr 10 21:02:36 aurora powersaved[21167]: Debug (ACPI_Interface:48) Constructor ACPI_Interface Apr 10 21:02:36 aurora powersaved[21167]: Info (setBatteryAlarm:304) set alarms: rem_Perc_all: 33, want alarm at: 12, divisor: 0.00 Apr 10 21:02:36 aurora powersaved[21167]: DIAG (setBatteryAlarm:338) Battery 0, remaining: 14210, last full: 42780, set alarm to: 5167 Apr 10 21:02:36 aurora powersaved[21167]: Info (setBatteryAlarm_:261) Alarm set to 12% Apr 10 21:02:36 aurora powersaved[21167]: DIAG (ACPI_Interface:53)
Bug#475097: powersaved: Thinkpad T60: Fn+F4 no longer suspends-to-ram machine
Sven-Haegar Koch schrieb: Package: powersaved Version: 0.15.20-2 Severity: normal Until the powersaved update of today pressing Fn+F4 on my Thinkpad T60 started suspend to ram, which worked without problems. Now when pressing it I only get some logs from acpid into syslog, nothing from powersaved anymore: (/etc/powersave/common DEBUG=31) Apr 9 01:11:06 aurora acpid: received event ibm/hotkey HKEY 0080 1004 Apr 9 01:11:06 aurora acpid: notifying client 4028[0:0] Apr 9 01:11:06 aurora acpid: notifying client 27786[115:122] Apr 9 01:11:06 aurora acpid: notifying client 4596[0:0] Apr 9 01:11:06 aurora acpid: notifying client 718[0:0] Apr 9 01:11:06 aurora acpid: executing action /etc/acpi/sleepbtn.sh Apr 9 01:11:06 aurora acpid: action exited with status 0 Apr 9 01:11:06 aurora acpid: completed event ibm/hotkey HKEY 0080 1004 Is that really all? No other logs of powersaved e.g. when it starts. I'm wondering if the debug log is working at all. Do you get any messages in the syslog, if you run powersaved -v31 -f /var/run/acpid.socket I do not use kde or gnome (I use Windowmaker), so no powermanagement tool from these is running. Executing powersave -u as root still works, it suspends and locks the xscreensaver on resume. powersaved -u does not react on events itself. It simply sends a Suspend() or Hibernate() request to hal. But it's good to know, that that works. The NEWS.Debian file tells me that powersaved no longer does suspend-things, but installing pm-utils did not fix the problem either, and I was not able to find a place to look for further config-changes I might have to do now to get my laptop back into a usable state. Interesting enough, you should already have pm-utils installed, as hal depends on it. It's strange that you had to manually install it. Could you please run the hal daemon in debug mode, and check if it forwards the button presses to powersaved: hald --daemon=no --verbose=yes Cheers, Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#475097: powersaved: Thinkpad T60: Fn+F4 no longer suspends-to-ram machine
Package: powersaved Version: 0.15.20-2 Severity: normal Until the powersaved update of today pressing Fn+F4 on my Thinkpad T60 started suspend to ram, which worked without problems. Now when pressing it I only get some logs from acpid into syslog, nothing from powersaved anymore: (/etc/powersave/common DEBUG=31) Apr 9 01:11:06 aurora acpid: received event ibm/hotkey HKEY 0080 1004 Apr 9 01:11:06 aurora acpid: notifying client 4028[0:0] Apr 9 01:11:06 aurora acpid: notifying client 27786[115:122] Apr 9 01:11:06 aurora acpid: notifying client 4596[0:0] Apr 9 01:11:06 aurora acpid: notifying client 718[0:0] Apr 9 01:11:06 aurora acpid: executing action /etc/acpi/sleepbtn.sh Apr 9 01:11:06 aurora acpid: action exited with status 0 Apr 9 01:11:06 aurora acpid: completed event ibm/hotkey HKEY 0080 1004 I do not use kde or gnome (I use Windowmaker), so no powermanagement tool from these is running. Executing powersave -u as root still works, it suspends and locks the xscreensaver on resume. The NEWS.Debian file tells me that powersaved no longer does suspend-things, but installing pm-utils did not fix the problem either, and I was not able to find a place to look for further config-changes I might have to do now to get my laptop back into a usable state. Have a nice evening, Haegar ps: The former version of powersaved logged: Apr 8 18:40:44 aurora powersave-hotkey_handler[22962]: DIAG: Process script for event other ID 196 Apr 8 18:40:44 aurora powersave-hotkey_handler[22962]: INFO: Event: OTHER occured. Apr 8 18:40:44 aurora powersave-hotkey_handler[22962]: INFO: Parameters: Event - other; Current Active Scheme: scheme_performance - ACPI event line: ibm/hotkey HKEY 0080 1004 Apr 8 18:40:44 aurora powersave-thinkpad_acpi_events[22962]: DIAG: Process script for event other ID 196 Apr 8 18:40:44 aurora powersave-thinkpad_acpi_events[22962]: INFO: Event: OTHER occured. Apr 8 18:40:44 aurora powersave-thinkpad_acpi_events[22962]: INFO: Parameters: Event - other; Current Active Scheme: scheme_performance - ACPI event line: ibm/hotkey HKEY 0080 1004 Apr 8 18:40:44 aurora powersave-thinkpad_acpi_events[22962]: INFO: Custom event script for ThinkPad ibm_acpi driver Apr 8 18:40:44 aurora powersave-prepare_suspend_to_ram[22978]: DIAG: Process script for event global.suspend2ram ID 197 Apr 8 18:40:44 aurora powersave-thinkpad_acpi_events[22962]: INFO: Fn+F4 hotkey: keycode 128 serial 4100. action: suspend-to-ram Apr 8 18:40:44 aurora powersave-thinkpad_acpi_events[22962]: DIAG: script_return() invoked: event_id: 196, request: 0, text: thinkpad_acpi_events finished Apr 8 18:40:44 aurora powersave-prepare_suspend_to_ram[22978]: INFO: Event: GLOBAL_SUSPEND2RAM occured. Apr 8 18:40:44 aurora powersave-prepare_suspend_to_ram[22978]: INFO: Parameters: Event - global.suspend2ram; Current Active Scheme: scheme_performance - ACPI event line: empty Apr 8 18:40:44 aurora powersave-prepare_suspend_to_ram[22978]: DIAG: script_return() invoked: event_id: 197, request: 4, text: 0 Apr 8 18:40:44 aurora powersave-prepare_suspend_to_ram[22978]: DIAG: script_return() invoked: event_id: 197, request: 4, text: 20|stopping services Apr 8 18:40:44 aurora powersave-prepare_suspend_to_ram[22978]: DIAG: script_return() invoked: event_id: 197, request: 4, text: 20|stopping service: irda Apr 8 18:40:44 aurora powersave-prepare_suspend_to_ram[22978]: DIAG: Service irda stopped Apr 8 18:40:44 aurora powersave-prepare_suspend_to_ram[22978]: DIAG: script_return() invoked: event_id: 197, request: 4, text: 20|stopping service: eatmemory Apr 8 18:40:46 aurora powersave-prepare_suspend_to_ram[22978]: DIAG: Service eatmemory stopped Apr 8 18:40:46 aurora powersave-prepare_suspend_to_ram[22978]: DIAG: script_return() invoked: event_id: 197, request: 4, text: 40|unloading modules Apr 8 18:40:46 aurora powersave-prepare_suspend_to_ram[22978]: DIAG: script_return() invoked: event_id: 197, request: 4, text: 40|unloading module: usb_storage Apr 8 18:40:46 aurora powersave-prepare_suspend_to_ram[22978]: DIAG: script_return() invoked: event_id: 197, request: 4, text: 40|unloading module: uhci_hcd Apr 8 18:40:46 aurora powersave-prepare_suspend_to_ram[22978]: DIAG: Modules unloaded Apr 8 18:40:46 aurora powersave-prepare_suspend_to_ram[22978]: DIAG: script_return() invoked: event_id: 197, request: 4, text: 50 Apr 8 18:40:46 aurora powersave-prepare_suspend_to_ram[22978]: DIAG: script_return() invoked: event_id: 197, request: 4, text: 60|syncing file systems Apr 8 18:40:46 aurora powersave-prepare_suspend_to_ram[22978]: DIAG: script_return() invoked: event_id: 197, request: 4, text: 101 Apr 8 18:40:46 aurora powersave-prepare_suspend_to_ram[22978]: DIAG: script_return() invoked: event_id: 197, request: 0, text: prepare_sleep finished successfully for global.suspend2ram ...and resume abot 1 hour later... -- System Information: Debian Release:
