2000 posts

Using Lehto's 950/500 kernel.

Just ran the pi-calculation with 10 000 000 digits; took about 2000 seconds, and the phone got _kinda_ hot But that's to be expected, CPU = 100% and RAM = 90% for more than half an hour.

So I think it's pretty stable

I'm trying to PM you but it wont let me I have my teamviewer ID and password ready when you are.....

EDIT: this post is outdated. please goto http://wiki.maemo.org/Overclocking

I have uploaded two new low voltage kernels.
Both are the same as the maemo20 kernel in extras-devel except for the lower voltages,
i.e. they preserve your freq. limits over phone calls and don't lock to 600Mhz during phone calls.
The default limits are 250-600 MHz.
A new feature in all maemo20 kernels is the bq27x00_battery module by Matan
which gives you more info about the battery in /sys/class/power_supply/bq27200-0/

The ultralow voltage (ulv) kernel is inspired by Letho's settings.
The less extreme low voltage (lv) kernel is inspired by Matan's settings.

Download ULV:
Download LV:
Installation
replace the values (as root) for temporary change
or edit /etc/pmconfig for permanent changes of the frequencies.

To enable 125Mhz use 124999 for scaling_min_freq.
According to BlackDiamond you should
"echo 1 > /sys/devices/system/cpu/cpu0/cpufreq/ondemand/ignore_nice_load"
for 125MHz http://talk.maemo.org/showpost.php?p...&postcount=185

Also try the hint by nightfire http://talk.maemo.org/showpost.php?p...&postcount=170 for improved responsiveness.

The warning "WARNING: at /home/builder1/maemo-fremantle-armel-extras-devel/work/kernel-maemo-2.6.28/arch/arm/mach-omap2/clock34xx.c:443" some people see in dmesg indicates that we don't really know what we're doing
The same applies to the DSP settings - it is not clear whether Letho's and my kernel actually set them to >430MHz. Someone familiar with frequency selection should have a look at the code...

so far the ULV kernel works fine for me with [125,600] Mhz till 850 MHz. 900 crashed it. EDIT: I just increased the 900 voltage in an update
EDIT2: another update replaced 800 by 810MHz in ULV and LV kernels

The warning in line 443 happens at frequency 800MHz, but not at 900 or 720. It sets an undefined value to a register. The result of not setting this register correctly is increase in the electromagnetic noise that the CPU will generate, so it might result in worse reception of GSM, UMTS, BT, WiFi, etc. Maybe even interference with other devices.

Maybe trying close values to 800 (such as 810, for example) will allow for correct calculation of this register.

Did the test on 1.1ghz and mine is 79.72 1000 000 digits

I did not wanted to put it too 1.1ghz but did echo 1000000 and got 1100mhz??? with kernel zImage-800mhz-ulv-1000mhz

titan, do we really need so many steps? 100mhz steps would be better IMHO. Less latency possible per step changing. 250, 500, 600, 700, 800, 900, etc.

I'm now using Lehto's 800-1000 ULV kernel @ 1Ghz. So far very stable. But it's only been 30mins or so.
Considering mine can run stable even at 1.1Ghz (non-ulv), I guess I'm one of the lucky ones with a decent enough sample. =)

titan
I now using the ulv and works great.
800 as max is stable so far, 900 as max is unstable, like running "angry birds" sometimes crash on my n900.

AFAIK Letho's at 1GHz is using max. voltage