You are not logged in.
I tried to set up cpufreq on my desktop, never got around to it until now. I installed the cpufrequtils package, and then I put the necessary items in the modules array in rc.conf:
MODULES=(!snd_pcsp powernow-k8 cpufreq_ondemand acpi-cpufreq vboxdrv)
I entered the appropriate items in my daemons array:
DAEMONS=(syslog-ng dbus !network netfs crond sshd rpcbind nfs-common nfs-server wicd @acpid @samba @cpufreqd @alsa @cups kdm @mediatomb)
And I also edited the /etc/conf.d/cpufreq file to look like the following:
#configuration for cpufreq control
# valid governors:
# ondemand, performance, powersave,
# conservative, userspace
governor="ondemand"
# limit frequency range (optional)
# valid suffixes: Hz, kHz (default), MHz, GHz, THz
#min_freq="2.25GHz"
#max_freq="3GHz"
# use freq to set up the exact cpu frequency using it with userspace governor
#freq=
But when I run:
watch grep \"cpu MHz\" /proc/cpuinfo
It shows that my processor is running @ the full 2600mhz at all times.
If I run:
sudo cpufreq-set -g ondemand
Both cores drop to 1000mhz almost instantly and from that point on, will increase or decrease as needed. However, I have to run that command every time I boot. Is there something I've done wrong for it to not set the governer every time I boot?
Last edited by jlacroix (2011-04-07 13:49:15)
Offline
can you post the output of cpufreq-info ??
[rant] m ==> milli ; M ==> Mega. Hertz is a proper noun. Therefore: mhz is wrong, mHz is really slow (1 cycle every 1000 seconds), MHz = 1,000,000 cycles /second [/rant]
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way
Offline
Actually, I looked at my system. I remembered I put this :
cpufreq-set -c0 -g ondemand
cpufreq-set -c1 -g ondemand
into /etc/rc.local
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way
Offline
First of all you should decide what make of processor you have, since powernow-k8 is for AMD, acpi-cpufreq is for Intel. You shouldn't load both.
Then edit your /etc/conf.d/cpufreq file and add the line:
governor="ondemand"
This way your cpu will be scaled by ondemand.
PS: acpid daemon is called automatically by udev, you don't need to include it in your daemons array.
Offline
Why don't you try uncommenting the min/max values in your cpufreq file, and editing the values appropriate for your cpu into them? The wiki says scaling will occur automatically, but since that isn't happening in your case, you might try and see if it makes a difference.
Edit: ah, nevermind, siriusb has your solution. You shouldn't load both of those modules, you'll have to pick the one that is appropriate for your cpu and remove the other.
Last edited by the sad clown (2011-04-07 07:18:41)
I laugh, yet the joke is on me
Offline
PS: acpid daemon is called automatically by udev, you don't need to include it in your daemons array.
I thought it was called automatically by hal? Is it called by udev also?
Offline
@stlarch,
Thanks for correcting me, you are right.
Offline
Thanks everyone. I removed acpi-cpufreq and kept just the powernow-k8 (I have an AMD processor) but that had no effect. I already had governor="ondemand" in /etc/conf.d/cpufreq, that wasn't working either. Ewaller's solution in post #3 worked for me.
Thanks everyone!
Offline