g-p-m requires twiddling in gconf-editor to for cpufreq to be operable on some machines
Bug #229672 reported by
Daniel Gimpelevich
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gnome-power-manager (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
powernowd (Ubuntu) |
Invalid
|
Undecided
|
Hanno Stock (hefe_bia) |
Bug Description
Binary package hint: gnome-power-manager
The default cpufreq policy for gnome-power-manager (8.04) in gconf is "ondemand" for both AC and battery, even on machines where the cpufreq driver does not support the ondemand governor. The GUI option to change the policy is missing, as if cpufreq were not supported at all. On login, g-p-m tries to change the governor to "ondemand" anyway, causing the "performance" governor to be used. Once both policies are changed from "ondemand" to "nothing" in gconf-editor, the patch that fixes Bug #229027 makes frequency scaling work correctly.
To post a comment you must log in.
See also Bug #223812. Powernowd and g-p-m conflict.
The missing GUI option is another thing, so I am leaving this open for g-p-m.