That did the trick.

[root@localhost ~]# 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: powernow-k8
CPUs which run at the same hardware frequency: 0
CPUs which need to have their frequency coordinated by software: 0
maximum transition latency: 1000 ns.
hardware limits: 550 MHz - 2.20 GHz
available frequency steps: 2.20 GHz, 1.10 GHz, 550 MHz
available cpufreq governors: ondemand, powersave, userspace, performance
current policy: frequency should be within 550 MHz and 2.20 GHz.
The governor "ondemand" may decide which speed to use
within this range.
current CPU frequency is 550 MHz (asserted by call to hardware).
analyzing CPU 1:
driver: powernow-k8
CPUs which run at the same hardware frequency: 1
CPUs which need to have their frequency coordinated by software: 1
maximum transition latency: 1000 ns.
hardware limits: 550 MHz - 2.20 GHz
available frequency steps: 2.20 GHz, 1.10 GHz, 550 MHz
available cpufreq governors: ondemand, powersave, userspace, performance
current policy: frequency should be within 550 MHz and 2.20 GHz.
The governor "ondemand" may decide which speed to use
within this range.
current CPU frequency is 550 MHz (asserted by call to hardware).
Now to figure out the next step.
