On Tuesday 02 March 2010 6:12:57 am Marko Vojinovic wrote:
On Tuesday 02 March 2010 05:42:42 am Chris Smart wrote:
> On Tue, Mar 2, 2010 at 4:22 PM, Chris Smart <mail(a)christophersmart.com>
wrote:
> > And my assumption is wrong.. I just logged in as root *GASP* and KDE
> > also reports inability to step the CPU, so I must be missing some kind
> > of package or configuration.
>
> Does anyone with a KDE install have support for CPU scaling with
> PowerDevil under System Settings?
Apparently something is broken within KDE here. I just checked, and I don't
have the support for CPU scaling. And I sort-of remember having it before
(on the same hardware). IIRC it would scale the frequency down when in
powersave mode (ie. when I run it on batteries).
Let me check...
Well, frequency scaling actually *works*, just checked by (un)plugging and
reading /proc/cpuinfo, it does scale from 1.5 GHz to 1 GHz when on
batteries. It seems that just the PowerDevil GUI is broken and doesn't
allow you to choose any settings. In systemsettings -> Advanced -> Power
Management -> Edit profiles -> CPU and System, the "CPU frequency scaling
policy" drop-down box is empty and does not provide any options to set up,
while in Capabilities tab it says that I don't have any scaling
capability.
But it does actually work, ie. it does scale the frequency when (un)plugged
or when swithcing profiles.
At least this is the situation on my machine.
HTH, :-)
Marko
I have the same issue, and I don't know what it could be (I'm on Fedora 12 64-
bit KDE4.4). I've worked around the issue using 'cpufreq' at the CLI to
manually select my governor & max CPU speed.
I'd bet that your governor is set to 'ondemand' as I believe this is the
default for all processors (for whatever reason). You can check this by
running "#cpufreq-info" at the CLI after you have installed the cpufrequtils
rpm. That command will give you a readout of everything going on such as your
CPU stepping frequencies, the current governor, the current frequency, etc.
What's weird about this issue, is that I didn't have this problem when using
this same laptop & Mandriva 2009.1-2010. On the contrary, with Mandriva my
laptop does not have a "Suspend to Disk" feature...go figure.
Andre Goree