#47 kpowersave-0.7.3 wrongly displays 2 batteries


Since updating kpowersave from 0.6.2 to 0.7.3 it displays two batteries instead of just one. (There is only one battery in my laptop.)
The remaining capacity of the second battery never changes, but is differs depending on what the battery capacity is when I do a reboot.

Please tell me what additional information could be useful for you.


  • Marc van der Wal

    Logged In: YES
    Originator: NO

    I had the same problem until I looked exactly at what happened.

    Since 0.7.3, kpowersave uses hal to search for batteries in the system. Since Linux 2.6.24 (or something like that), the acpi state files are being moved to /sys instead of /proc, so the battery info can be accessed in two ways. By default, the status report is activated in both sysfs and proc, so that screws up HAL (or maybe the way it's called isn't correct).

    The sysfs way being experimental and buggy, that explains the second meter not to change. The /proc one being stable and tested, that's your first battery correctly being polled.

    To fix that, I recompiled my kernel (I'm on Gentoo) and told Linux not to use the sysfs method. After that, it only displayed one battery. I have this:

    Kernel configuration
    Power management options --->
    [*] ACPI (Advanced Configuration and Power Interface) Support --->
    [*] Deprecated /proc/acpi files
    [*] Deprecated power /proc/acpi folders
    [ ] Future power /sys interface
    [*] Deprecated /proc/acpi/event support
    [ Other stuff ]

    Hope that helps :-)


  • Danny Al-Gaaf

    Danny Al-Gaaf - 2008-06-04
    • status: open --> closed-works-for-me
  • Danny Al-Gaaf

    Danny Al-Gaaf - 2008-06-04

    Logged In: YES
    Originator: NO

    That was a HAL bug and's fixed since end of January 2008 in git and should be part of latest released hal v0.5.11. I close this bug now


Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

JavaScript is required for this form.

No, thanks