powernowd doesn't run anymore after kernel upgrade

Bug #14129 reported by Gabriele Postorino on 2005-03-17
Affects Status Importance Assigned to Milestone
linux-source-2.6.15 (Ubuntu)
Fabio Massimo Di Nitto

Bug Description

I upgraded to 2.6.10-5 kernel in hoary and after that powernowd stopped working.
CPU frequency scaling not supported is the output of sudo /etc/init.d/powernowd
Before upgrading powernowd was working "correctly" (it only showed wrong freq
values but scaled fine)

Herman Bos (hbos) wrote :

Hi, the frequency scaling seemed to work in hoary until I reinstalled it with
the preview release.
Running kernel: Linux ki 2.6.10-4-amd64-generic #1 Thu Mar 10 02:52:25 UTC 2005
x86_64 GNU/Linux

herman@ki:/etc/init.d$ sudo ./powernowd start
 * Starting powernowd...
 * CPU frequency scaling not supported

sudo modprobe powernow-k8
sudo /etc/init.d/powernowd start
 * Starting powernowd...

And everything works agian \o/

Sorry there is something not clear to me.

Using 2.6.10-4 you have to modprobe powernow-k8.

What if you do modprobe with 2.6.10-5 ?

You can safely install the 2 kernels in parallel to test. -5 won't overwrite or
cancel -4.


Thom May (thombot) wrote :

Please confirm that the init script works correctly with an up-to-date hoary.

This bug has been marked as a duplicate of bug 14113.

Gabriele Postorino (no0tic) wrote :

Here on k7 system (hoary):
with -4 kernel all works fine
with -5 kernel powernow-k7 stopped loading automatically; modprobe loads
correctly the module (powernow_k7) and enables frequency scaling.

Herman Bos (hbos) wrote :

I confirm the problem is solved in an up to date hoary (amd64 arch).

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.