Package: cpufreqd Version: 2.4.2-1 Tags: patch This bug was reported upstream by niko2gare:
http://sourceforge.net/tracker/?func=detail&aid=3172707&group_id=58904&atid=489239 2 patches were sugested by him in the same thread. The second assumes that "power_now" will be used in all future kernels and has been successfully tested by me locally: --- a/src/cpufreqd_acpi_battery.c +++ b/src/cpufreqd_acpi_battery.c @@ -36,6 +36,7 @@ #define PRESENT "present" #define STATUS "status" #define CURRENT_NOW "current_now" +#define POWER_NOW "power_now" struct battery_info { int capacity; @@ -145,9 +146,13 @@ binfo->status = get_class_device_attribute(binfo->cdev, STATUS); if (!binfo->status) return -1; - binfo->current_now = get_class_device_attribute(binfo->cdev, CURRENT_NOW); - if (!binfo->current_now) - return -1; + binfo->current_now = get_class_device_attribute(binfo->cdev, POWER_NOW); + if (!binfo->current_now) { + /* try the "current_now" name */ + binfo->current_now = get_class_device_attribute(binfo->cdev, CURRENT_NOW); + if (!binfo->current_now) + return -1; + } /* read the last full capacity, this is not going to change * very often, so no need to poke it later */ P.S.: I just noticed that the developer is the debian package maintainer as well. I'm mainly uploading the patch to bugs.debian.org for easier access for debian users of current kernels bumping into the same problem. Is there a recommended/accepted way for handling matters like this? --- System information. --- Architecture: amd64 Kernel: Linux 3.2-2.slh.4-aptosid-amd64 Debian Release: wheezy/sid 500 unstable oscar.aptosid.com 500 unstable cdn.debian.net 500 stable dl.google.com --- Package information. --- Depends (Version) | Installed ============================-+-============= libc6 (>= 2.3.2) | 2.13-25 libcpufreq0 (>= 001) | 007-2 libsensors4 (>= 1:3.0.0) | 1:3.3.1-2 libsysfs2 | 2.1.0+repack-1 lsb-base (>= 3.0) | 3.2-28.1 Recommends (Version) | Installed =========================-+-=========== acpid | 1:2.0.14-2 Suggests (Version) | Installed ===========================-+-=========== cpufrequtils | 007-2 -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
