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#50348 - [cpupower] Doesn't set max frequency in latest version
Attached to Project:
Community Packages
Opened by Chris Hilton (crhilton) - Thursday, 11 August 2016, 02:13 GMT
Last edited by Doug Newgard (Scimmia) - Thursday, 11 August 2016, 03:10 GMT
Opened by Chris Hilton (crhilton) - Thursday, 11 August 2016, 02:13 GMT
Last edited by Doug Newgard (Scimmia) - Thursday, 11 August 2016, 03:10 GMT
|
DetailsDescription:
Setting the max cpu frequency value from the command line, or via the configuration file with the systemd service doesn't change the maximum frequency. Additional info: * Problem is new in 4.7-1 * Downgrading to 4.6-4 fixed the issue. Steps to reproduce: sudo cpupower frequency-set -u 1.8GHz cpupower frequency-info cpupower frequency-info | grep policy I expected to see 1.8GHz as my maximum. |
This task depends upon
Closed by Doug Newgard (Scimmia)
Thursday, 11 August 2016, 03:10 GMT
Reason for closing: Duplicate
Additional comments about closing: Search for it
Thursday, 11 August 2016, 03:10 GMT
Reason for closing: Duplicate
Additional comments about closing: Search for it