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.d/powernowd stop
sudo powernowd -q
If I do an 'sudo /etc/init.d/powernowd start' when powernowd is not running I get the following message in /var/log/messages:
"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?
Binary package hint: powernowd
Description: Ubuntu 8.04 0.97-2ubuntu4
Release: 8.04
powernowd:
Installiert:
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. d/powernowd stop
sudo powernowd -q
If I do an 'sudo /etc/init. d/powernowd start' when powernowd is not running I get the following message in /var/log/messages:
"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?