On Tue, 2011-04-12 at 22:27 +0200, Dominik Brodowski wrote:
> Probably some other tool interfers and sets the cpufreq policy
> wrongly. Try
> the following commands (as root):
>
> $ cpufreq-set --max 2.6G
doesn't work either:
# cpufreq-set --max 2.6G
# cpufreq-info
cpufrequtils 007: cpufreq-info (C) Dominik Brodowski 2004-2009
Report errors and bugs to cpuf...@vger.kernel.org, please.
analyzing CPU 0:
driver: acpi-cpufreq
CPUs which run at the same hardware frequency: 0 1
CPUs which need to have their frequency coordinated by software: 0
maximum transition latency: 10.0 us.
hardware limits: 800 MHz - 2.53 GHz
available frequency steps: 2.53 GHz, 2.53 GHz, 1.60 GHz, 800 MHz
available cpufreq governors: userspace, powersave, conservative,
ondemand, performance
current policy: frequency should be within 800 MHz and 800 MHz.
The governor "ondemand" may decide which speed to use
within this range.
current CPU frequency is 800 MHz (asserted by call to hardware).
cpufreq stats: 2.53 GHz:0.56%, 2.53 GHz:0.12%, 1.60 GHz:0.11%, 800
MHz:99.21% (1587)
...
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
