[SOLVED] CPU frequency scaling will not load at boot

coralfang · 11-16-2010, 05:06 PM

Hello, i'm curious as to why some things are not happening at boot time (i end up having to manually load them).

In /etc/rc.d/rc.modules (near the bottom) i have set "CPUFREQ=on"
and commented out any modules not specific to my hardware.

I have left this one uncommented:

Code:

# AMD Cool&Quiet PowerNow!:
  /sbin/modprobe powernow-k8 2>/dev/null

and below the "### CPU frequency scaling policies:" i have;

Code:

  /sbin/modprobe cpufreq_ondemand 2>/dev/null

uncommented. My scaling governor is set to:

Code:

  SCALING_GOVERNOR=ondemand

Now whenever i reboot my machine `lsmod` is not showing any of either powernow-k8 or cpufreq* related modules.

I know i could use /etc/rc.d/rc.local with these:

Code:

/sbin/modprobe powernow-k8
/sbin/modprobe cpufreq_ondemand
/usr/bin/cpufreq-set -g ondemand

But seems to defeat the purpose of rc.modules, any idea why they are not being loaded at boot... ?

Code:

$ uname -a
Linux slackware 2.6.35.7 #3 SMP Mon Oct 11 01:34:00 CDT 2010 x86_64 AMD Athlon(tm) 64 X2 Dual Core Processor 5000+ AuthenticAMD GNU/Linux

with slackware64-current

Cheers.

coralfang · 11-16-2010, 05:15 PM

Well i just noticed this:

Code:

$ ls -la rc.modules*
lrwxrwxrwx 1 root root    19 Nov  9 22:18 rc.modules -> rc.modules-2.6.33.4
-rwxr-xr-x 1 root root 35412 Nov 16 23:08 rc.modules-2.6.33.4
-rwxr-xr-x 1 root root 35406 Oct 11 07:25 rc.modules-2.6.35.7

I'm pretty sure this might be why, is it safe to simply link rc.modules to the newer rc.modules-2.6.35.7 seeing as i won't be using the older kernel??

EDIT:
Well, either way it worked on boot this time after relinking:

Code:

# unlink /etc/rc.d/rc.modules
# ln -s /etc/rc.d/rc.modules-2.6.35.7 /etc/rc.d/rc.modules

T3slider · 11-16-2010, 08:32 PM

From /etc/rc.d/rc.S:

Code:

# Priority is given first to a script named "rc.modules.local", then
# to "rc.modules-$FULL_KERNEL_VERSION", and finally to the plain "rc.modules".
# Note that if /etc/rc.d/rc.modules.local is found, then that will be the ONLY
# rc.modules script the machine will run, so make sure it has everything in
# it that you need.

You could have edited rc.modules-2.6.35.7 or relinked as you have done (or created rc.modules.local).