configure cpuspeed bluewhite64 linux
 

Hello all,

I installed Bluewhite64 linux which is basically a 64 bit port of Slackware linux on my laptop (Compaq v3133AU, AMD Turion64 x2).

Everything works fine except that the CPU is always running at 1.6GHz.

I guess the kernel is not supporting cpufreq driver and there is no cpuspeed daemon.

I am currrently trying to compile a new kernel with cpufreq module support.
Anyways, just wanted to know if somebody has experience configuring the cpufreq modules and installing/configuring the cpuspeed daemon. That way, i will save some iterations and time to solve this issue.

Thanks,
Kanwar

I'm running daemons cpufreqd and cpufrequtils with speedstep-centrino module

The daemons are enable at boot time:
1)
/etc/rc2.d/S20cpufreqd
It uses the configuration stored in /etc/default/cpufreqd

Modify your CPUFREQ_CPU_MODULE so that it points to your cpufreq module.
If set to auto, the daemon will parse /etc/cpufreqd.conf and modprobe all the necessary governor modules (cpufreq_powersave, cpufreq_performance,..).


configuring the cpufreq modules and installing/configuring the cpuspeed daemon

2)
/etc/rc2.d/S20cpufrequtils
This takes as input /etc/default/cpufrequtils conf file

This sets the governor to userspace here. If set to auto in cpufreqd, then I think this daemon is not needed.

Every poll_interval seconds, cpufreqd checks for conditions written in RULE parts which refer to PROFILE parts of /etc/cpufreqd.conf.
The conditions can be : Battery charge, CPU speed, Temperatures, presence or not of some processes,..
Then a score is established for each RULE and the winner gets its profile activated (Powersave_High, Performance Low,..)
Also cpufreqd gets acpi event through its socket. Acpid package is required to trigger event from /proc/acpi/event events.

As an example I have currently this strategy:
When battery is >70 but CPU<20, set it to 1.2Ghz (save the planet and my ears eh)
When battery is >70 and CPU>20, set it to 1.6Ghz
When battery is <70 but CPU<20, set it to 600Mhz
When battery is <70 and CPU>20, set it to 1.2Ghz
When battery is <20, set it to 600Mhz
When temperature is too important, set it to 1.2Ghz
When mplayer, xine, vlc are running, set it to 1.6Ghz

I find it very powerfull.

hello,
thanks very much..

i will try this approach once i get the new kernel running..

i guess cpufrequtils will also support AMD speed control just as it supports speedstep..

regards,
kanwar

* Cpufrequtils sets the minimal, maximal frequencies and governor ONCE, then it exits.
* Cpufreqd is a real daemon that stays and does the job explained above.