Help with cpufreq please

[Aleph]

If you can install the 2.6.38.8-pclos3.bfs
kernel, reboot with that kernel, be sure everything is hooked up
beforehand, only other thing to try today.   The freq's probably
need to be adjusted once we get the driver to tell us what they are.

Hi Ferdes Fides,

I installed the 2.6.38.8-pclos3.bfs kernel, reboot and nothing... cpufreq-info get the same result.
I reinstalled cpufreq and cpufrequtils and nothing...

Impossible, I think set cpufreq in my machine is not possible. What a pitty...

Thank you very much FF

[Yankee]

Impossible, I think set cpufreq in my machine is not possible. What a pitty...

Hi,

My machine uses acpi-cpufreq or P4-clockmod drivers.   I have no clue what or where
the drivers are or would be for a newer Intel Xeon quad-core.   New kernel wouldn't hurt
when one becomes available.

regards,

FF

[coffeetime]

Open Terminal [go su] and load modules one by one [after each modprobe check results with cpufreq-info]:

Code: [Select]

modprobe speedstep-centrino

Code: [Select]

modprobe p4_clockmod

Code: [Select]

modprobe powernow-k6

Code: [Select]

modprobe powernow-k7

Code: [Select]

modprobe powernow-k8

Code: [Select]

modprobe acpi-cpufreq

[Aleph]

Hi coffeetime,

something is working! 

With modprobe p4-clockmod

Code: [Select]

cpufreq-info
cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009
Report errors and bugs to cpufreq@vger.kernel.org, please.
analyzing CPU 0:
  driver: p4-clockmod
  CPUs which run at the same hardware frequency: 0
  CPUs which need to have their frequency coordinated by software: 0
  maximum transition latency: 10.00 ms.
  hardware limits: 333 MHz - 2.67 GHz
  available frequency steps: 333 MHz, 667 MHz, 1000 MHz, 1.33 GHz, 1.67 GHz, 2.00 GHz, 2.33 GHz, 2.67 GHz
  available cpufreq governors: ondemand, conservative, powersave, userspace, performance
  current policy: frequency should be within 667 MHz and 2.67 GHz.
                  The governor "performance" may decide which speed to use
                  within this range.
  current CPU frequency is 2.67 GHz (asserted by call to hardware).
analyzing CPU 1:
  driver: p4-clockmod
  CPUs which run at the same hardware frequency: 1
  CPUs which need to have their frequency coordinated by software: 1
  maximum transition latency: 10.00 ms.
  hardware limits: 333 MHz - 2.67 GHz
  available frequency steps: 333 MHz, 667 MHz, 1000 MHz, 1.33 GHz, 1.67 GHz, 2.00 GHz, 2.33 GHz, 2.67 GHz
  available cpufreq governors: ondemand, conservative, powersave, userspace, performance
  current policy: frequency should be within 667 MHz and 2.67 GHz.
                  The governor "performance" may decide which speed to use
                  within this range.
  current CPU frequency is 2.67 GHz (asserted by call to hardware).
analyzing CPU 2:
  driver: p4-clockmod
  CPUs which run at the same hardware frequency: 2
  CPUs which need to have their frequency coordinated by software: 2
  maximum transition latency: 10.00 ms.
  hardware limits: 333 MHz - 2.67 GHz
  available frequency steps: 333 MHz, 667 MHz, 1000 MHz, 1.33 GHz, 1.67 GHz, 2.00 GHz, 2.33 GHz, 2.67 GHz
  available cpufreq governors: ondemand, conservative, powersave, userspace, performance
  current policy: frequency should be within 667 MHz and 2.67 GHz.
                  The governor "performance" may decide which speed to use
                  within this range.
  current CPU frequency is 2.67 GHz (asserted by call to hardware).
analyzing CPU 3:
  driver: p4-clockmod
  CPUs which run at the same hardware frequency: 3
  CPUs which need to have their frequency coordinated by software: 3
  maximum transition latency: 10.00 ms.
  hardware limits: 333 MHz - 2.67 GHz
  available frequency steps: 333 MHz, 667 MHz, 1000 MHz, 1.33 GHz, 1.67 GHz, 2.00 GHz, 2.33 GHz, 2.67 GHz
  available cpufreq governors: ondemand, conservative, powersave, userspace, performance
  current policy: frequency should be within 667 MHz and 2.67 GHz.
                  The governor "performance" may decide which speed to use
                  within this range.
  current CPU frequency is 2.67 GHz (asserted by call to hardware).


With modprobe acpi-cpufreq Device or resource busy

Code: [Select]

FATAL: Error inserting acpi_cpufreq (/lib/modules/2.6.38.8-pclos3.bfs/kernel/arch/x86/kernel/cpu/cpufreq/acpi-cpufreq.ko.gz): Device or resource busy

With all the others, No such device:

Code: [Select]

FATAL: Error inserting powernow_k6 (/lib/modules/2.6.38.8-pclos3.bfs/kernel/arch/x86/kernel/cpu/cpufreq/powernow-k6.ko.gz): No such device

What should I do now?

Thanks!

[horusfalcon]

This may help understand the situation.  It appears your CPU is in the following family:

5100-series "Woodcrest"
Woodcrest Produced    From 2006 to 2009
Max. CPU clock rate    1600 MHz to 3000 MHz
FSB speeds    1066 MT/s to 1333 MT/s
Min. feature size    65nm
Instruction set    x86
Microarchitecture    Core
CPUID code    06Fx
Product code    80556
Cores    2
L2 cache    4 MB
Application    DP Server
Package(s)    

    LGA 771

Brand name(s)    

    Xeon 51xx

List: List of Intel Xeon microprocessors#"Woodcrest" (65 nm)

On 26 June 2006, Intel released the dual-core CPU (Xeon branded 5100 series) codenamed Woodcrest (product code 80556); it was the first Intel Core microarchitecture processor to be launched on the market. It is a server and workstation version of the Intel Core 2 processor. Intel claims that it provides an 80% boost in performance, while reducing power consumption by 20% relative to the Pentium D.

Most models have a 1333 MT/s FSB, except for the 5110 and 5120, which have a 1066 MT/s FSB. The fastest processor (5160) operates at 3.0 GHz. All Woodcrests use LGA 771 and all except two models have a TDP of 65 W. The 5160 has a TDP of 80 W and the 5148LV (2.33 GHz) has a TDP of 40 W. The previous generation Xeons had a TDP of 130 W. All models support Intel 64 (Intel's x86-64 implementation), the XD bit, and Virtualization Technology, with the "Demand Based Switching" power management option only on Dual-Core Xeon 5140 or above. Woodcrest has 4 MB of shared L2 Cache.
Model    Speed (GHz)    L2 Cache (MB)    FSB (MHz)    TDP (W)
5110    1.60    4    1066    65
5120    1.83    4    1066    65
5128    1.83    4    1066    40
5130    2.0    4    1333    65
5138    2.13    4    1066    35
5140    2.33    4    1333    65
5148    2.33    4    1333    40
5150    2.66    4    1333    65
5160    3.00    4    1333    80

More info about your processor here.

Your Woodcrest CPU has hardware-level power management (Demand-Based Switching), and may require some special steps.  Dell published this paper on the subject, tailored to an enterprise distribution (non-PCLinuxOS), but the info is probably applicable to your situation.

Good Hunting!

Later On,
D

[Aleph]

Dell published this paper on the subject, tailored to an enterprise distribution (non-PCLinuxOS), but the info is probably applicable to your situation.

Hi horusfalcon,

I will try it, but it seems to be not very easy for me...

I will tell my adventure.

Thanks!

[Aleph]

Well, I went to the BIOS and I have not a Demand-Based Power Management option

but I had the Enhanced Speedstep Techology option, was off and now is Enabled

After this the cpufreq-info report this result:

Code: [Select]

cpufreq-info
cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009
Report errors and bugs to cpufreq@vger.kernel.org, please.
analyzing CPU 0:
  driver: acpi-cpufreq
  CPUs which run at the same hardware frequency: 0
  CPUs which need to have their frequency coordinated by software: 0
  maximum transition latency: 10.0 us.
  hardware limits: 2.00 GHz - 2.67 GHz
  available frequency steps: 2.67 GHz, 2.33 GHz, 2.00 GHz
  available cpufreq governors: ondemand, conservative, powersave, userspace, performance
  current policy: frequency should be within 2.00 GHz and 2.67 GHz.
                  The governor "ondemand" may decide which speed to use
                  within this range.
  current CPU frequency is 2.67 GHz (asserted by call to hardware).
analyzing CPU 1:
  driver: acpi-cpufreq
  CPUs which run at the same hardware frequency: 1
  CPUs which need to have their frequency coordinated by software: 1
  maximum transition latency: 10.0 us.
  hardware limits: 2.00 GHz - 2.67 GHz
  available frequency steps: 2.67 GHz, 2.33 GHz, 2.00 GHz
  available cpufreq governors: ondemand, conservative, powersave, userspace, performance
  current policy: frequency should be within 2.00 GHz and 2.67 GHz.
                  The governor "ondemand" may decide which speed to use
                  within this range.
  current CPU frequency is 2.00 GHz (asserted by call to hardware).
analyzing CPU 2:
  driver: acpi-cpufreq
  CPUs which run at the same hardware frequency: 2
  CPUs which need to have their frequency coordinated by software: 2
  maximum transition latency: 10.0 us.
  hardware limits: 2.00 GHz - 2.67 GHz
  available frequency steps: 2.67 GHz, 2.33 GHz, 2.00 GHz
  available cpufreq governors: ondemand, conservative, powersave, userspace, performance
  current policy: frequency should be within 2.00 GHz and 2.67 GHz.
                  The governor "ondemand" may decide which speed to use
                  within this range.
  current CPU frequency is 2.67 GHz (asserted by call to hardware).
analyzing CPU 3:
  driver: acpi-cpufreq
  CPUs which run at the same hardware frequency: 3
  CPUs which need to have their frequency coordinated by software: 3
  maximum transition latency: 10.0 us.
  hardware limits: 2.00 GHz - 2.67 GHz
  available frequency steps: 2.67 GHz, 2.33 GHz, 2.00 GHz
  available cpufreq governors: ondemand, conservative, powersave, userspace, performance
  current policy: frequency should be within 2.00 GHz and 2.67 GHz.
                  The governor "ondemand" may decide which speed to use
                  within this range.
  current CPU frequency is 2.00 GHz (asserted by call to hardware).

and I can see at Conky that  cpufreq can change between 2000-2667 Mhz.

Should I do something more?

Thanks!

[Yankee]

cpufreq-set -c 0 -g conservative -d 667mhz -u 2670mhz
cpufreq-set -c 1 -g conservative -d 667mhz -u 2670mhz
cpufreq-set -c 2 -g conservative -d 667mhz -u 2670mhz
cpufreq-set -c 3 -g conservative -d 667mhz -u 2670mhz

The above four commands when run from terminal or placed
at the end of rc.local so they boot will run your machine at
667mhz at idle and go to full power at over 75% load.   That
ondemand thing is goofy to me.

That will show in conky as well.

Should look like this in cpufreq-info :

current policy: frequency should be within 667 mhz and 2.67 GHz.
                  The governor "conservative" may decide which speed to use
                  within this range.
  current CPU frequency is 667 mhz (asserted by call to hardware).


My only question is the best place to put modprobe p4-clockmod so
that boots OK.   There's a couple places but I don't know the best place.
Maybe the acpi-cpufreq driver I see is all that is needed.   Or turn off the
Enhanced Speedstep if we can't get conservative mode with that and
just use p4-clockmod.

One more day, almost there.

Have a good one.

FF

[Just17]

@Ferdes Fides

hardware limits: 2.00 GHz - 2.67 GHz

That appears to imply the range cannot be changed.

Can you comment please?  .....  I have a similar limitation on a PC here so am interested if it can be changed .....

Thanks

[Yankee]

@Ferdes Fides

hardware limits: 2.00 GHz - 2.67 GHz

That appears to imply the range cannot be changed.

Can you comment please?  .....  I have a similar limitation on a PC here so am interested if it can be changed .....

Thanks

Sure,

That's with the acpi-cpufreq driver that was invoked thru BIOS.
The 667mhz-2667mhz range was available with the BIOS change off and
modprob'ing the p4-clockmod driver.    Different driver, different range
available.    Reply #18 has those.

I have my machine working with the very low at idle conservative mode,
so, that's what I'm trying to do.    

FF

[Just17]

Thank you ...... IIUC, you say it is not a CPU hardware limit, but a limit of the cpufreq driver?

....  even though it is reported as a hardware limitation which is what had me concerned

[Aleph]

Thanks friends,

I tried adding to rc.local but doesn't work, still 2000-2660 Mhz

cpufreq-info

Code: [Select]

cpufreq-info
cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009
Report errors and bugs to cpufreq@vger.kernel.org, please.
analyzing CPU 0:
  driver: acpi-cpufreq
  CPUs which run at the same hardware frequency: 0
  CPUs which need to have their frequency coordinated by software: 0
  maximum transition latency: 10.0 us.
  hardware limits: 2.00 GHz - 2.67 GHz
  available frequency steps: 2.67 GHz, 2.33 GHz, 2.00 GHz
  available cpufreq governors: ondemand, conservative, powersave, userspace, performance
  current policy: frequency should be within 2.00 GHz and 2.67 GHz.
                  The governor "conservative" may decide which speed to use
                  within this range.
  current CPU frequency is 2.00 GHz (asserted by call to hardware).
analyzing CPU 1:
  driver: acpi-cpufreq
  CPUs which run at the same hardware frequency: 1
  CPUs which need to have their frequency coordinated by software: 1
  maximum transition latency: 10.0 us.
  hardware limits: 2.00 GHz - 2.67 GHz
  available frequency steps: 2.67 GHz, 2.33 GHz, 2.00 GHz
  available cpufreq governors: ondemand, conservative, powersave, userspace, performance
  current policy: frequency should be within 2.00 GHz and 2.67 GHz.
                  The governor "conservative" may decide which speed to use
                  within this range.
  current CPU frequency is 2.00 GHz (asserted by call to hardware).
analyzing CPU 2:
  driver: acpi-cpufreq
  CPUs which run at the same hardware frequency: 2
  CPUs which need to have their frequency coordinated by software: 2
  maximum transition latency: 10.0 us.
  hardware limits: 2.00 GHz - 2.67 GHz
  available frequency steps: 2.67 GHz, 2.33 GHz, 2.00 GHz
  available cpufreq governors: ondemand, conservative, powersave, userspace, performance
  current policy: frequency should be within 2.00 GHz and 2.67 GHz.
                  The governor "conservative" may decide which speed to use
                  within this range.
  current CPU frequency is 2.00 GHz (asserted by call to hardware).
analyzing CPU 3:
  driver: acpi-cpufreq
  CPUs which run at the same hardware frequency: 3
  CPUs which need to have their frequency coordinated by software: 3
  maximum transition latency: 10.0 us.
  hardware limits: 2.00 GHz - 2.67 GHz
  available frequency steps: 2.67 GHz, 2.33 GHz, 2.00 GHz
  available cpufreq governors: ondemand, conservative, powersave, userspace, performance
  current policy: frequency should be within 2.00 GHz and 2.67 GHz.
                  The governor "conservative" may decide which speed to use
                  within this range.
  current CPU frequency is 2.00 GHz (asserted by call to hardware).


rc.local

Code: [Select]

#!/bin/sh
#
### BEGIN INIT INFO
# Provides: rc.local
# X-Mandriva-Compat-Mode
# Default-Start: 2 3 4 5
# Short-Description: Local initialization script
# Description: This script will be executed *after* all the other init scripts.
#              You can put your own initialization stuff in here if you don't
#              want to do the full Sys V style init stuff.
### END INIT INFO

touch /var/lock/subsys/local

modprobe snd-usb-audio

# Fix linkage to cdrom/dvd and permissons since udev is screwed
ln -s /dev/sr0 /dev/dvd > /dev/null 2>&1
ln -s /dev/sr0 /dev/cdrom > /dev/null 2>&1
chmod 777 /dev/sr0 > /dev/null 2>&1
chown root:root /dev/sr0 > /dev/null 2>&1
chmod 777 /dev/sr1 > /dev/null 2>&1
chown root:root /dev/sr1 > /dev/null 2>&1

cpufreq-set -c 0 -g conservative -d 667mhz -u 2670mhz
cpufreq-set -c 1 -g conservative -d 667mhz -u 2670mhz
cpufreq-set -c 2 -g conservative -d 667mhz -u 2670mhz
cpufreq-set -c 3 -g conservative -d 667mhz -u 2670mhz

What should I do now? 

[Yankee]

@Aleph

What I would do to test our options.

Turn off that Enhanced Speedstep thing.

Reboot.

in root terminal :   modprobe p4-clockmod

run the 4 commands to try to get conservative mode

run cpufreq-info

post result from that

I predict we'll have a great conservative mode for you

Then we'll finalize the configuration once the above is confirmed.

If you opt for something else, that's OK too.


later,

FF


edit:   I can see it's in conservative mode OK, great.
             With the p4-clockmod driver it should idle at an
             even lower and cooler speed.   667mhz

[Aleph]

This is the output:

Code: [Select]

cpufreq-info
cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009
Report errors and bugs to cpufreq@vger.kernel.org, please.
analyzing CPU 0:
  driver: p4-clockmod
  CPUs which run at the same hardware frequency: 0
  CPUs which need to have their frequency coordinated by software: 0
  maximum transition latency: 10.00 ms.
  hardware limits: 333 MHz - 2.67 GHz
  available frequency steps: 333 MHz, 667 MHz, 1000 MHz, 1.33 GHz, 1.67 GHz, 2.00 GHz, 2.33 GHz, 2.67 GHz
  available cpufreq governors: ondemand, conservative, powersave, userspace, performance
  current policy: frequency should be within 667 MHz and 2.67 GHz.
                  The governor "performance" may decide which speed to use
                  within this range.
  current CPU frequency is 2.67 GHz (asserted by call to hardware).
analyzing CPU 1:
  driver: p4-clockmod
  CPUs which run at the same hardware frequency: 1
  CPUs which need to have their frequency coordinated by software: 1
  maximum transition latency: 10.00 ms.
  hardware limits: 333 MHz - 2.67 GHz
  available frequency steps: 333 MHz, 667 MHz, 1000 MHz, 1.33 GHz, 1.67 GHz, 2.00 GHz, 2.33 GHz, 2.67 GHz
  available cpufreq governors: ondemand, conservative, powersave, userspace, performance
  current policy: frequency should be within 667 MHz and 2.67 GHz.
                  The governor "performance" may decide which speed to use
                  within this range.
  current CPU frequency is 2.67 GHz (asserted by call to hardware).
analyzing CPU 2:
  driver: p4-clockmod
  CPUs which run at the same hardware frequency: 2
  CPUs which need to have their frequency coordinated by software: 2
  maximum transition latency: 10.00 ms.
  hardware limits: 333 MHz - 2.67 GHz
  available frequency steps: 333 MHz, 667 MHz, 1000 MHz, 1.33 GHz, 1.67 GHz, 2.00 GHz, 2.33 GHz, 2.67 GHz
  available cpufreq governors: ondemand, conservative, powersave, userspace, performance
  current policy: frequency should be within 667 MHz and 2.67 GHz.
                  The governor "performance" may decide which speed to use
                  within this range.
  current CPU frequency is 2.67 GHz (asserted by call to hardware).
analyzing CPU 3:
  driver: p4-clockmod
  CPUs which run at the same hardware frequency: 3
  CPUs which need to have their frequency coordinated by software: 3
  maximum transition latency: 10.00 ms.
  hardware limits: 333 MHz - 2.67 GHz
  available frequency steps: 333 MHz, 667 MHz, 1000 MHz, 1.33 GHz, 1.67 GHz, 2.00 GHz, 2.33 GHz, 2.67 GHz
  available cpufreq governors: ondemand, conservative, powersave, userspace, performance
  current policy: frequency should be within 667 MHz and 2.67 GHz.
                  The governor "performance" may decide which speed to use
                  within this range.
  current CPU frequency is 2.67 GHz (asserted by call to hardware).


CPU frequency is 2.67 GHz...

I don't deleted the four commands at rc.local, should I do it?

[Yankee]

 current policy: frequency should be within 667 MHz and 2.67 GHz.
                  The governor "performance" may decide which speed to use
                  within this range.
  current CPU frequency is 2.67 GHz (asserted by call to hardware).


@Aleph

Without Enhanced Speedstep,   if you ran the 4 commands for conservative
this should read:

 current policy: frequency should be within 667 MHz and 2.67 GHz.
                  The governor "conservative" may decide which speed to use
                  within this range.
  current CPU frequency is 667 MHz (asserted by call to hardware).

Can you run those four commands one more time, each one
in root terminal ?     Don't reboot or delete anything.
Don't delete anything in rc.local.
Please post back results.   Thanks for your patience also.   This is fun.