[hardy] Regression: powernowd no longer works with some chipsets
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gnome-power-manager (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
powernowd (Ubuntu) |
Fix Released
|
High
|
Unassigned |
Bug Description
Binary package hint: powernowd
Description: Ubuntu 8.04
Release: 8.04
powernowd:
Installiert:
Updated description:
Powernowd (the package) does not work with chipsets where the ondemand governor fails. This is because now the powernowd init script only actually loads powernowd (the daemon) if the ondemand governor is not present.
Also gnome-power-manager now conflicts with powernowd as it also enables the ondemand governor by default.
Original description of the bug:
In gutsy I added cpufreq-nforce2 to my modules list and then powernowd nicely scaled the frequency on my Athlon XP 2400+. Now I upgraded to hardy and frequency scaling does no longer work.
However if I do the following, it works again (until next reboot):
sudo /etc/init.
sudo powernowd -q
If I do an 'sudo /etc/init.
"Apr 28 20:10:29 HANNO kernel: [10637.446135] ondemand governor failed, too long transition latency of HW, fallback to performance governor"
It seems that the init script loads the ondemand governor instead of userspace governor. How can I prevent this from happening?
Related branches
description: | updated |
Changed in powernowd: | |
importance: | Undecided → High |
status: | Confirmed → Triaged |
I think I found a solution...