How do I load speedstep-ich before acpi during boot?
Thanks,
paul

I could be wrong, but I don't think you can. Processor throttling AFAIK depends on ACPI.

I have acpid running. I also have a bunch of files listed here:
/sys/devices/system/cpu/cpu0/cpufreq

affected_cpus scaling_available_governors scaling_max_freq
cpuinfo_max_freq scaling_cur_freq scaling_min_freq
cpuinfo_min_freq scaling_driver scaling_setspeed
scaling_available_frequencies scaling_governor stats

When I type echo 1867000 > scaling_setspeed it doenst change the speed listed in scaling_setspeed. I dotn know why its working. What else do I need running.

[root@blueox cpufreq]# cat scaling_driver
acpi-cpufreq
[root@blueox cpufreq]# cat scaling_available_frequencies
3200000 2933000 2667000 2400000 2133000 1867000

For boot I have acpi=on under kernel parameters and also I added these two lines to /etc/rc.local
/sbin/modprobe speedstep-lib
/sbin/modprobe acpi_cpufreq

What else am I missing. Any help would be greatly appreciated. This is giving me grey hair....

thanks,
Paul

whats the output of
cat scaling_available_governors
and
cat scaling_governor
the 'userspace' governor is ideally what you're looking for.

Here's how I do it:
**CAUTION - this is ugly and only here for reference.....Your mileage may (and likely will) vary***

I have an early P4-m that supports speedstep-ich at 1200000 and 1600000 only
At boot i have a script that echo userspace> /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor. I call it from the correct run level in rc.d (3 in my case)
The above is because I set the default governor to performance when i built the kernel, and never bothered to find the correct way to fix it
I can then use another script that echo 1600000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_setspeed
or
echo 1600000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_setspeed

these scripts can be launched anyway you like...icon, taskbar button, hotkey, etc.


EDIT- almost forgot.....BS from U of FLA here in 90 (EE)...go Gators

Heres the output:

[lumbrjackedpcj@blueox cpufreq]$ cat scaling_available_governors
ondemand userspace performance
[lumbrjackedpcj@blueox cpufreq]$ cat scaling_governor
userspace
[lumbrjackedpcj@blueox cpufreq]# cat scaling_driver
acpi-cpufreq


I also compiled speedstep-ich as a module but when I try to start it at a prompt i get this error:
[root@blueox cpufreq]# /sbin/modprobe speedstep-ich
FATAL: Error inserting speedstep_ich (/lib/modules/2.6.11.6/kernel/arch/i386/kernel/cpu/cpufreq/speedstep-ich.ko): No such device

Now do I just need acpi-cpufreq or speedstep-ich for my processor(538 prescott)? I think Ill start over and compile exactly what I need for my processor, get rid of p4-clockmod. Ive never been so confused about all this power management stuff.

THanks,
Paul

p.s. you wouldnt beleive all the construction going on in gainesville. actually this august my aparment is going to be torn down and a condo being built on the corner of university and 13th. its crazy how its changing so fast. ton of bars left so thats good at least

Try unloading P4 clockmod module before loading ich module. If P4 clockmod is built into your kernel, then yes, I would recommend rebuilding it (the kernel) using only enhanced speedstep and speedstep-ich drivers. Also be sure to select all of the power/performance states you think you will need, as well as choosing the default you'd like. MAKE SURE TO INCLUDE THE CPU FREQ TABLE HELPERS (better safe than sorry), and read all the documentation on Relaxed speedstep capability checks to see if they may be required.

Choosing userspace and powersave states is highly recommended if you plan on automatically switching states when AC power is connected/disconnected. The problems are surely in your kernel, as you can see by my ugly and dirty fix above it's fairly easy to switch on the fly once it's set up correctly.