View Single Post
Posts: 455 | Thanked: 278 times | Joined on Dec 2009 @ Oregon, USA
#120
Originally Posted by titan View Post
thanks for testing! it is possible that the Frequency monitoring applications are confused by the more than 5 levels available in the new kernel...
I've just uploaded cpufrequtils to extras-devel. could you please show me the output of cpufreq-info ? thanks a lot!
Here's the results (max scaling still set to 800Mhz)
Code:
cpufrequtils 006: cpufreq-info (C) Dominik Brodowski 2004-2009
Report errors and bugs to cpufreq@vger.kernel.org, please.
analyzing CPU 0:
  driver: omap
  CPUs which run at the same hardware frequency: 0
  CPUs which need to have their frequency coordinated by software: 0
  maximum transition latency: 0.00 ms.
  hardware limits: 250 MHz - 1000 MHz
  available frequency steps: 1000 MHz, 900 MHz, 850 MHz, 800 MHz, 750 MHz, 700 MHz, 600 MHz, 550 MHz, 500 MHz, 250 MHz
  available cpufreq governors: ondemand, userspace
  current policy: frequency should be within 250 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: 1000 MHz:0.00%, 900 MHz:0.00%, 850 MHz:0.00%, 800 MHz:13.93%, 750 MHz:0.19%, 700 MHz:0.47%, 600 MHz:16.40%, 550 MHz:0.51%, 500 MHz:68.50%, 250 MHz:0.00%  (623)
I'm a bit worried that it never seems to go into any pstate lower than 500mhz.. The other 'overclocking' kernels included scaling down to 125mhz.

Installing your cpufreq-utils package does not automatically enable the cpufreq daemon, does it?