|
Bugzilla – Full Text Bug Listing |
| Summary: | EVENT_BATTERY_WARNING and EVENT_BATTERY_LOW (notify) and EVENT_BATTERY_CRITICAL (wm_shutdown) are not processed | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 10.2 | Reporter: | Forgotten User cwt8EEdsgo <forgotten_cwt8EEdsgo> |
| Component: | SaX2 | Assignee: | Danny Al-Gaaf <dalgaaf> |
| Status: | RESOLVED DUPLICATE | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Major | ||
| Priority: | P2 - High | CC: | jcnengel |
| Version: | Final | ||
| Target Milestone: | --- | ||
| Hardware: | i686 | ||
| OS: | SUSE Other | ||
| Whiteboard: | |||
| Found By: | Other | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: |
dmesg output
acpidump output Acer Aspire acpidump Acer Aspire 3623 tail /var/log/acpid Acer Aspire cat /proc/interrupts |
||
|
Description
Forgotten User cwt8EEdsgo
2006-12-15 22:14:51 UTC
I can confirm that behaviour also on an ASUS machine. Maybe there is a missing link somewhere... Do a tail -f /var/log/acpid if you plug/unplug the AC or lid or sleep button, do you see ACPI events generated there? What does cat /proc/interrupts say? Do you have acpi line there, is it increasing if you do above? If interrupts and events are generated it should be a userspace problem, otherwise a kernel... Can you also attach dmesg and acpidump output, just for reference, maybe there already is a hint... /var/log/acpid shows the events generated by (un)plugging the cable and opening/closing the lid. So does /proc/interrupts counting the lines. But this is not true for the special keys of the ASUS laptop which were supposed to generate ACPI events as well. The brightness of the display nevertheless can be changed via these keys although this seems not to be recognized by the os. Created attachment 110995 [details]
dmesg output
Created attachment 110996 [details]
acpidump output
Oh, I forgot to mention that the sleep button event is also listed in /var/log/acpid although not handled by powersaved. powersaved does no longer handle acpi events, if a power management desktop applet (such as kpowersave) is active. Kpowersave however is still missing the functionality to handle these events, there is a bug for this and there will be an online update soon to fix that. You can use gnome-power-manager until then. This is probably a duplicate of bug 221715 Created attachment 111003 [details]
Acer Aspire acpidump
Created attachment 111004 [details]
Acer Aspire 3623 tail /var/log/acpid
Created attachment 111005 [details]
Acer Aspire cat /proc/interrupts
I don't use any power management desktop applet (I'm using IceWM 1.2.29). Only battery events don't work - when I press power button then system shutdown is started. On FreshMeat I have founded this: http://freshmeat.net/projects/acpi4asus acpi4asus is a Linux kernel module and user-space daemon that handles special keys, LEDs, and extra ACPI features found on Asus laptops. It has been reported to work on Asus A1X/D1/L1X/L2X/L3X/M2X/S1X, but other models should also be supported. The amount of ACPI interrupts compared to timer interrupts is quite high... 9: 378103 IO-APIC-level acpi But acpi events reach userspace (cmp. comment #9), kernel seem to work. Seife (comment #7), does this mean not only lid events are not processed, but also critical battery state events are not processed anymore? Last one is only for gnome-power-manager or also for kpowersave, whatabout running without X-server? Renaming bug and reassign whether this is already known. Danny can you confirm that this is the problem and possibly mark this as a duplicate or handle this, pls. > Seife (comment #7), does this mean not only lid events are not processed, but > also critical battery state events are not processed anymore? The (running as root) powersave daemon is the default policy manager which cares for those events until you start a desktop policy manager (like kpowersave, gnome-power-manager), which then takes over all those responsibilities. As soon as the desktop policy manager is started, powersaved does nothing with regard to acpi events. > Last one is only for gnome-power-manager or also for kpowersave, whatabout > running without X-server? Not supported on notebooks. This is already fixed for KPowersave. Close as duplicate of bug #221715 *** This bug has been marked as a duplicate of bug 221715 *** |