g-p-m requires twiddling in gconf-editor to for cpufreq to be operable on some machines

Bug #229672 reported by Daniel Gimpelevich on 2008-05-12
Affects Status Importance Assigned to Milestone
gnome-power-manager (Ubuntu)
powernowd (Ubuntu)
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.

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.

Changed in powernowd:
assignee: nobody → hanno-stock
status: New → In Progress
Chris Coulson (chrisccoulson) wrote :

Thanks. Setting the gnome-power-manager task to Won't Fix, as all cpufreq code has now been removed from gnome-power-manager in Intrepid.

Changed in gnome-power-manager:
status: New → Won't Fix
Steve Langasek (vorlon) wrote :

because g-p-m in intrepid no longer changes the governor settings, there's no reason for any further changes here in powernowd.

Changed in powernowd:
status: In Progress → Invalid
Changed in gnome-power-manager:
status: Won't Fix → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers