Cpu Freq

Installed Suse 11.1 on a AMD 64 fx 55.When I do a cat /proc/cpuinfo I get 1200 not 2600.I had this same problem on a ubuntu install.I had to turn off CPU freq Manager.Can I do this in Suse if so how ?

Try this if you are using kde: (probably something similar in gnome)

K Menu -> Configure Desktop -> Advanced tab -> Power management

Make sure that it is set for performance when on AC power
Go to Edit Profiles

click on Performance and then the CPU and System (at the bottom)
Make sure the CPU frequency scaling policy is set to Performance, not Dynamic. I believe Dynamic (on demand) is the default here, so that may be your problem.

Reply back if you are in gnome and can’t find something similar.

Unless you’re actually noticing a slowdown where you shouldn’t, leave it be.

It will up the clockspeed when it’s needed, it does the same thing under Windows Vista (and XP if you enable a power profile and install the Cool’N’Quiet drivers).

Thanks Guys
That did it.the reason for turning off CPU Manager the Computer will lockup with the CPU freq Manager on. This has happen with Ubuntu too.I have no idea why ?

Can you file a bug report then?

The /proc/cpuinfo and kernel log info is an issue, but CPUFREQ causing lock ups is worse.

To avoid frequency scaling, add CPUFREQ=no to the boot command line, which will turn it off completely.

For anyone else stumbling into this thread as I did. As “root” execute zypper install cpufrequtils to install cpufreq tools.

The open three Konsole (Linux prompt) windows.

In Window #1, type:
watch cpufreq-info

In Window #2, type:
top

In Window #3, try commands:
cpufreq-set -g ondemand Recommended
cpufreq-set -g performance
cpufreq-set -f 1000000 Basically “Power Save Mode”
cpufreq-set -f 2600000 Depends on what cpufreq-info says is possible. This is the max setting for my Athlon X2 5200+.
cpufreq-set -f 3000000 Depends on what cpufreq-info says is possible. This is the max setting for my Athlon X2 6000+.

While watching Window #1 after excuting cpufreq-set -g ondemand in Window #3, try starting some big apps like Open-Office, or VMware, or some other CPU (as opposed to disk) intensive application. Watch as current CPU frequency in Window #1 changes CPU frequency to meet demand, and drops it back down to power saving frequencies when the CPU isn’t needed.

cpufreq-info presents information that looks like this for an AMD Athlon™ 64 X2 Dual Core Processor 6000+:

cpufrequtils 004: cpufreq-info (C) Dominik Brodowski 2004-2006
Report errors and bugs to Submitting Bug Reports - openSUSE, please.
analyzing CPU 0:
driver: powernow-k8
CPUs which need to switch frequency at the same time: 0 1
hardware limits: 1000 MHz - 3.00 GHz
available frequency steps: 3.00 GHz, 2.80 GHz, 2.60 GHz, 2.40 GHz, 2.20 GHz, 2.00 GHz, 1.80 GHz, 1000 MHz
available cpufreq governors: conservative, userspace, powersave, ondemand, performance
current policy: frequency should be within 1000 MHz and 3.00 GHz.
The governor “ondemand” may decide which speed to use
within this range.
current CPU frequency is 1000 MHz (asserted by call to hardware).
analyzing CPU 1:
driver: powernow-k8
CPUs which need to switch frequency at the same time: 0 1
hardware limits: 1000 MHz - 3.00 GHz
available frequency steps: 3.00 GHz, 2.80 GHz, 2.60 GHz, 2.40 GHz, 2.20 GHz, 2.00 GHz, 1.80 GHz, 1000 MHz
available cpufreq governors: conservative, userspace, powersave, ondemand, performance
current policy: frequency should be within 1000 MHz and 3.00 GHz.
The governor “ondemand” may decide which speed to use
within this range.
current CPU frequency is 1000 MHz (asserted by call to hardware).

Really good stuff in that last post :wink: