I've just run into this bug, too, on my from-scratch install of Edgy on a Dell Inspiron 1300...
I similarly thought that powernowd should have been running, since I had the package installed; it took 10 minutes to figure out that the init script was silently exiting due to the "cpufreq_ondemand" module being loaded, instead of starting the daemon. This is bad behaviour. The "ondemand" governor doesn't work well on this hardware, since it causes the fan to start up and shut down every couple of minutes or so, even when the machine is entirely idle (this is probably related to bug #93404). "powernowd" is the best userspace governor for the job, and the one I *want* to use; as it stands, I had to edit the init script to inhibit the "ondemand" code. In essence, I agree with bug #94309. It is inappropriate to hook the "use ondemand if possible" code into the init script for an unrelated daemon, esp when that daemon is more suitable for certain hardware. A better fix would be to create a *new* package for that code, and keep the "powernowd" package for the powernowd daemon. If that's too hard due to packaging policies as described in that bug, at the very least, expose the current behaviour, and a switch to fix it, in an /etc/default/powernowd file. -- powernowd doesn't use /etc/default/powernowd anymore https://launchpad.net/bugs/67341 -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
