![]() |
2010-04-04
, 14:38
|
|
Posts: 664 |
Thanked: 160 times |
Joined on Jul 2008
@ Australia
|
#111
|
![]() |
2010-04-04
, 14:41
|
|
Posts: 2,473 |
Thanked: 12,265 times |
Joined on Oct 2009
@ Jerusalem, PS/IL
|
#112
|
![]() |
2010-04-04
, 14:46
|
Posts: 151 |
Thanked: 82 times |
Joined on Sep 2008
|
#113
|
He edited his post and said don't reflash, if your device is on at the moment I'd suggest reflashing the stock kernel using apt-get --reinstall install kernel kernel-flasher then reflashing the 'normal' OC'd kernel.
![]() |
2010-04-04
, 19:57
|
Posts: 310 |
Thanked: 383 times |
Joined on Jan 2010
|
#114
|
Is there a way to make it persistent so it survives reboots?
Also, compared to what I have on my phone, scaling_max_freq is currently reporting 600,000 although it's overclocked to 900Mhz (cpuinfo_max_freq)
![]() |
2010-04-05
, 10:30
|
Posts: 946 |
Thanked: 1,650 times |
Joined on Oct 2009
@ Germany
|
#115
|
echo 600000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq echo 250000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
![]() |
2010-04-05
, 13:21
|
Posts: 74 |
Thanked: 25 times |
Joined on Jan 2010
@ Hong Kong, CHINA
|
#116
|
![]() |
2010-04-05
, 13:33
|
Posts: 946 |
Thanked: 1,650 times |
Joined on Oct 2009
@ Germany
|
#117
|
wget http://maemory.com/N900/overclock/kernel-maemo_2.6.28-maemo19_armel.deb wget http://maemory.com/N900/overclock/kernel-modules-maemo_2.6.28-maemo19_armel.deb wget http://maemory.com/N900/overclock/kernel-flasher-maemo_2.6.28-maemo19_armel.deb dpkg -i kernel-m* dpkg -i kernel-flasher-maemo_2.6.28-maemo19_armel.deb reboot
![]() |
2010-04-05
, 16:34
|
Posts: 455 |
Thanked: 278 times |
Joined on Dec 2009
@ Oregon, USA
|
#118
|
The Following User Says Thank You to craftyguy For This Useful Post: | ||
![]() |
2010-04-05
, 16:58
|
Posts: 946 |
Thanked: 1,650 times |
Joined on Oct 2009
@ Germany
|
#119
|
I got around to testing it, and unless Powertop is freaking out, the results are not expected.
EDIT: I fired up Conky, and it shows an idle (min.) speed of 500 Mhz and 800Mhz under load. The min. scaling show be MUCH less.
![]() |
2010-04-05
, 17:19
|
Posts: 455 |
Thanked: 278 times |
Joined on Dec 2009
@ Oregon, USA
|
#120
|
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!
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)