Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#12118 - [cpufreqd] looks for wrong names
Attached to Project:
Arch Linux
Opened by orbisvicis (orbisvicis) - Friday, 14 November 2008, 09:29 GMT
Last edited by Roman Kyrylych (Romashka) - Tuesday, 30 June 2009, 21:38 GMT
Opened by orbisvicis (orbisvicis) - Friday, 14 November 2008, 09:29 GMT
Last edited by Roman Kyrylych (Romashka) - Tuesday, 30 June 2009, 21:38 GMT
|
DetailsDescription:
cpufreqd -DV6 acpi_battery_update : Re-scanning available batteries get_class_device_attribute: couldn't open /sys/class/power_supply/BAT0/energy_full (No such file or directory) get_class_device_attribute: couldn't open /sys/class/power_supply/BAT0/energy_now (No such file or directory) This is because the required files are named charge_full and change_now This bug has been reported and fixed in debian http://bugs.donarmstrong.com/cgi-bin/bugreport.cgi?bug=495655 Additional info: * package version(s) * config and/or log files etc. cpufreqd 2.3.3-2 Steps to reproduce: happens without acpid running |
This task depends upon
Closed by Roman Kyrylych (Romashka)
Tuesday, 30 June 2009, 21:38 GMT
Reason for closing: None
Additional comments about closing: old, no response, seems to be working
Tuesday, 30 June 2009, 21:38 GMT
Reason for closing: None
Additional comments about closing: old, no response, seems to be working
cpufreqd now looks for energy_full then charge_full
Please close/invalid.
---
> cpufrequd might be too verbose but it actually opens charge_now and
> charge_full after failing energy_*
>
> run it with -V7 and check yourself.
yes, you are right!
get_class_device_attribute: couldn't
open /sys/class/power_supply/C1ED/energy_full (No such file or directory)
get_class_device_attribute: found charge_full -
path /sys/class/power_supply/C1ED/charge_full
get_class_device_attribute: couldn't
open /sys/class/power_supply/C1ED/energy_now (No such file or directory)
get_class_device_attribute: found charge_now -
path /sys/class/power_supply/C1ED/charge_now
looks like its working, but writing lots of error messages to my logfiles.
I changed the verbosity level from default 4 to 3 and now there are no battery
messages any more.
---
@orbisvicis - can you confirm this?