On Wed, Dec 07, 2005 at 07:01:11PM +0100, Dirk Stepan wrote: > Package: cpufrequtils > Version: 0.3-2 > > I enabled setting the governor and minimum/maximum frequency at startup > in /etc/default/cpufrequtils: > > -------- > > ENABLE="true" > GOVERNOR="ondemand" > MAX_SPEED=1800 > MIN_SPEED=800 > > --------- > > The required kernel-modules are loaded before through /etc/modules. > > I suggest delaying script execution from S20cpufrequtils to > SXXcpufrequtils, because it works when I use for example > S89cpufreqdutils. I suppose the problems occur because cpufreqd is only > started at the same time (S20cpufreqd).
Well, I don't think this is a bug. I suppose that what's happening is that cpufreqd overrides your cpufrequtils boot parameters. I don't understand the usefulness of using a deamon (cpufreqd) to set your CPUFreq policy and then trying to override its settings with something else (cpufrequtils). If you're not happy with cpufreqd settings you might want to tweak them and disable cpufrequtils boot script (or disable cpufreqd and only use cpufrequtils, but I can't see the point as cpufreqd offers an high configurability and has lots of features) :) ciao -- mattia :wq! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
