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#33483 - [cpupower] Cannot set max frequency at boot
Attached to Project:
Community Packages
Opened by Mark E. Lee (bluerider) - Sunday, 20 January 2013, 23:19 GMT
Last edited by Eric Belanger (Snowman) - Monday, 21 January 2013, 00:53 GMT
Opened by Mark E. Lee (bluerider) - Sunday, 20 January 2013, 23:19 GMT
Last edited by Eric Belanger (Snowman) - Monday, 21 January 2013, 00:53 GMT
|
DetailsDescription:
Attempting to set CPU max frequency fails at boot fails in "/etc/conf.d/cpupower". However, running the script "/usr/lib/systemd/scripts/cpupower" in user space works (with root privilege) works. Additional info: Package : cpupower 3.7-3 cat /etc/conf.d/cpupower : # Define CPUs governor # valid governors: ondemand, performance, powersave, conservative, userspace. #governor='ondemand' # Limit frequency range # Valid suffixes: Hz, kHz (default), MHz, GHz, THz #min_freq="2.25GHz" #max_freq="3GHz" max_freq="1.05GHz" # Specific frequency to be set. # Requires userspace governor to be available. # Do not set governor field if you use this one. #freq= # Utilizes cores in one processor package/socket first before processes are # scheduled to other processor packages/sockets. # See man (1) CPUPOWER-SET for additional details. #mc_scheduler= # Utilizes thread siblings of one processor core first before processes are # scheduled to other cores. See man (1) CPUPOWER-SET for additional details. #smp_scheduler= # Sets a register on supported Intel processore which allows software to convey # its policy for the relative importance of performance versus energy savings to # the processor. See man (1) CPUPOWER-SET for additional details. #perf_bias= # vim:set ts=2 sw=2 ft=sh et: Steps to reproduce: Set the max frequency in "/etc/conf.d/cpupower". Reboot, and it the output of "$ cpupower frequency-info" indicates the max frequency was not started. |
This task depends upon
Closed by Eric Belanger (Snowman)
Monday, 21 January 2013, 00:53 GMT
Reason for closing: Not a bug
Additional comments about closing: Problem was fixed by enabling cpupower.service with systemd
Monday, 21 January 2013, 00:53 GMT
Reason for closing: Not a bug
Additional comments about closing: Problem was fixed by enabling cpupower.service with systemd
Comment by Mark E. Lee (bluerider) -
Sunday, 20 January 2013, 23:50 GMT
I found out I had forgotten to enable the cpupower.service which ran the script. The cpupower max frequency set works now.