Mattia Dongili schrieb: > On Wed, Oct 22, 2008 at 09:53:56AM +0200, Benjamin Scherrer wrote: > >> Mattia Dongili schrieb: >> >>> On Sun, Oct 19, 2008 at 02:31:01PM +0200, Benjamin Scherrer wrote: >>> >>> >>>> Package: cpufreqd >>>> Version: 2.3.3-2 >>>> Severity: important >>>> >>>> Hi, >>>> >>>> I use debian testing and just updated to cpufreq 2.3.3-3. After >>>> installing, cpufreqd won't scale my AMD Phenom 9850 (4x2.5GHz) down >>>> anymore. I use the 'ondemand' governor, and normally my CPUs are >>>> scaled down to 1.25 GHz in idle mode. >>>> Now I downgraded to 2.3.3-2, and it's working again. >>>> >>>> >>> Uhmmm, this is extermely odd. The only change in 2.3.3-3 is a one liner >>> to avoid crashing on startup. >>> Can you run cpufreqd with (stop the other instance first): >>> cpufreqd -D -V7 | tee cpufreqd.log >>> and send me the resulting logfile? >>> thanks >>> >>> >> Hi, >> >> I just found out more: >> >> If I install 2.3.3-3, unload the powernow-k8 module and reload it again >> manually, scaling is working. >> Additionally, 2.3.3-3 sets the governor to "performance" once it is >> started. If I set the governor back to "ondemand", it scales down to >> 1.25 GHz. >> But the next time I start cpufreqd (e.g. next system startup), I have to >> do the whole thing again - reload the module + set the governor to >> ondemand, otherwise it won't work. >> > > Ok, I think this is just an expectation problem. > Cpufreqd is a deamon that monitors your system and applies specific > profiles to your cpu (see /etc/cpufreqd.conf and man cpufreqd.conf). The > deafult configuration file is currently unsuitable for desktops as it > assumes you have a battery and a power supply reporting their state and > the profile is set also based on those. > So, what happens is that cpufreqd starts up and applies the "Movie > watcher" profile (the bast match for your system in its current state) > which is a performance-100%-100% profile. I guess this is not what you > want. > If you just want ondemand to be loaded then using cpufrequtils is > definitely the solution you're looking for. Cpufrequtils loads the cpu > driver on startup and sets ondemand as the governor. > > For completeness, the reason why you think cpufreqd 2.3.3-2 is working > is because it dies very early before being able to start adoing > anything. > > thoughts? Hi,
oh... I'm sorry! So I just removed cpufreqd completely and it works as I expected it... I didn't know that all I need is cpufrequtils. Ok, so you can close this report - thanks a lot for pointing me to the solution! Regards Benjamin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
