On Wed, Nov 05, 2003 at 08:39:17PM +0200, Micha Feigin wrote: > On Tue, 2003-11-04 at 13:17, Magnus von Koeller wrote: > > On Tuesday 04 November 2003 12:07, Ducrot Bruno wrote: > > > > Yeah, could you send these? My stuff somehow doesn't work. I use > > > > this: echo 0:600000:600000:powersave > /proc/cpufreq > > > > > > You are using a user space daemon which change the frequency on the > > > fly. > > > > You're right, this was due to cpufreqd changing it back. If I disable > > that, it stays at the 600Mhz-600Mhz range. But still, /proc/cpuinfo > > always gives > > cpu MHz : 1294.774 > > > > So, it's not working, is it? > > This looks like its not working for some reason although 600Mhz-600Mhz > and 600Mhz-1300Mhz should be the same when you are using powersave. With > power save you are supposed to always get the lower frequency (at list > on my laptop).
I use in a script something like: echo 0%100%powersave and echo 0%100%performance (with the same script, I enable/disable laptop-mode, amongst other things) and all that is done via acpid. > Could you post the output of dmesg? It is supposed to have near the top > information about the cpufreq data detected. For example on mine: > (this is after a patch to fix a bug with the voltage scaling not being > read correctly on powernow so that I will also get voltage scaling at > the lower frequencies). > I doubt speedstep-centrino will dump the states. -- Ducrot Bruno -- Which is worse: ignorance or apathy? -- Don't know. Don't care.
