According to the kernel configuration:
Nevertheless, ondemand is the governor that is used according to the .../cpu/cpu0/cpufreq entry in /sys when the system is up and running.
Why is that?
(The kernel that I am running right now is 2.6.30.7)

Unless I'm mistaken, that kernel config entry means that the default governor in use will be determined by userspace application(s), rather than actually specifying which governor will necessarily be in use.

You should be able to set which governor is being used at any given time, by using the sysctl interface. Something like below:

shell# echo "performance" > ...<path/to>/cpu/cpu0/cpufreq/scaling_governor

..which you can do in a boot/init script, OR by using the sysctl.conf file (check around a bit for the exact syntax required for use in the sysctl.conf file for this item.

Hope this helps
Sasha

Sure, I did the echoing myself in an earlier installation in rc.local, but since I haven't done that this time, I wondered where the system does that. It is always nice to keep track on "hidden" configurations that the system does without I begging for it.

Yes, and he don't need to mess with kernel config as Slack comes correctly configured. He only need to load the modules.

Ondemand seems the safe initial choice. Most time it is just sitting on the slow speed or going full speed when demanded, but processor without multiple clocks work correctly.

Check /etc/rc.d/rc.modules. That is where the CPU frequency governor is modified during booting. Look at the end of the script.

Thank you. It seems like the script tries to load every possible driver for frequency scaling regardless if they are included or not in the kernel, maybe I should comment some of them to save some boot time?

Yes, as you see fit.

Prior to 13.0, the governor modules were listed in rc.modules but not loaded. The end-user had to uncomment the governor of choice. I prefered that approach. Before 13.0 I loaded the ondemand governor in rc.local.

In 13.0 I commented out all the options in rc.modules and still use my script snippet in rc.local. The simple reason being I run a snippet of code in rc.local to create /etc/issue, and part of the final text in /etc/issue includes the normal rated CPU speed. Loading the ondemand governor in rc.modules caused the resulting /etc/issue to always display the governed (lowest) speed rather than the normal rated speed. Purely cosmetic, but I'm the one who sees the incorrect text every day.

You are like me, don't want to see unnecessary (but harmless) messages at start up or in the logs :-)