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). 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). powernow: AMD K7 CPU detected. powernow: PowerNOW! Technology present. Can scale: frequency and voltage. powernow: Found PSB header at c00f74d0 powernow: Table version: 0x12 powernow: Flags: 0x0 (Mobile voltage regulator) powernow: Settling Time: 100 microseconds. powernow: Has 28 PST tables. (Only dumping ones relevant to this CPU). powernow: PST:26 (@c00f76ac) powernow: cpuid: 0x780 fsb: 100 maxFID: 0x14 startvid: 0xe powernow: FID: 0x4 (5.0x [500MHz]) VID: 0x1b (1.000V) powernow: FID: 0x8 (7.0x [700MHz]) VID: 0x13 (1.200V) powernow: FID: 0xc (9.0x [900MHz]) VID: 0xe (1.300V) powernow: FID: 0x0 (11.0x [1100MHz]) VID: 0xe (1.300V) powernow: FID: 0x14 (13.0x [1300MHz]) VID: 0xe (1.300V) -- Micha Feigin [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
