Active Topics

 


Poll: Do you think its possible to overclock the N900?!
Poll Options
Do you think its possible to overclock the N900?!

Reply
Thread Tools
Posts: 1,255 | Thanked: 393 times | Joined on Oct 2009 @ US
#2541
Originally Posted by Lehto View Post
BTW... All my kernels are built from this source
kernel_2.6.28-20100903+0m5
I currently use a normal volt 125~800 kernel. It has been very stable, so I am wondering if any advantage in the newer kernels?

BTW, when 1.2 is finally released, will it be safe to update with the current kernel (on device now), or will I need to go to the "stock" first?

I installed my kernel using the N900's Xterm, rather than Flash 3.5. My info shows complete, where as some lost their "about" info.

Last edited by Rushmore; 2010-04-12 at 22:40.
 
Posts: 1,751 | Thanked: 844 times | Joined on Feb 2010 @ Sweden
#2542
Originally Posted by moshikko View Post
ULV & LV by titan
I discovered something about my device : using the ULV kernel it bricks when using the 850Mhz max freq but boots up normal when raising it up to 900Mhz.
been using it for almost half an hour now and it is stable.

on the other hand the LV kernel works great at any speed - so going back to the LV kernel
You should try the new XLV-kernel.
 

The Following User Says Thank You to AlMehdi For This Useful Post:
Posts: 1,751 | Thanked: 844 times | Joined on Feb 2010 @ Sweden
#2543
Originally Posted by Rushmore View Post
I currently use a normal volt 125~800 kernel. It has been very stable, so I am wondering if any advantage in the newer kernels?

BTW, when 1.2 is finally released, will it be safe to update with the current kernel, or will I need to go to the "stock" first?

I installed my kernel using the N900's Xterm, rather than Flash 3.5. My info shows complete, where as some lost their "about" info.
This howto is great in answering questions

I would recommend the lv-kernel to start with. I think it's the most stable one. If you want to save more battery you could try the xlv-kernel. Set the max_freq in /etc/pmconfig low at starters and try new mhz with the "temp command" before you settle with one permanent.

A good one for you might be setting the min_freq to 250000 and the max_freq to 810000.
 
Posts: 22 | Thanked: 15 times | Joined on Apr 2010 @ Israel
#2544
Originally Posted by AlMehdi View Post
You should try the new XLV-kernel.
I'll give it a try to see if my device can support it
I hope it can
 
Posts: 1,751 | Thanked: 844 times | Joined on Feb 2010 @ Sweden
#2545
Originally Posted by moshikko View Post
I'll give it a try to see if my device can support it
I hope it can
Start with the max_freq on 810mhz and then test the other frequencies with the "temp command". That is how i did it. I have noticed it can be unstable for me on the higher frequencies.
 
iceman600's Avatar
Posts: 324 | Thanked: 65 times | Joined on Jun 2008 @ FL
#2546
Originally Posted by rpgAmazon View Post
So hard to choose!
Today with ideal kernel, max frec=950... 2 batteries at work (8 am unplugged from car, 2:30 battery change, 7 pm plugged again)
With Lehto 125-950-500, a day without change of battery.
I can assume than user habits are delimiting battery life, anyway, nv kernel beating xlv... how is it possible? If 500 xlv=125 nv, and Lehto 950 ov> ideal 950 ov... ¿?¿?¿?¿
So again reinstaling 125-950-500... I'm getting crazy!!
ok im confused...
125-950-500 lehto meaning:
125 low
950 max
500 is what?

sorry noob
 
Posts: 171 | Thanked: 114 times | Joined on Feb 2010
#2547
Here is a script that I hacked together from the original script by rooted to measure the actual time that the CPU is running, including idle mode.

Code:
#!/bin/sh
awk '{print "\nCurrent frequency: "$1/1000" MHz\n"}' /sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq
awk '{print "Minimum frequency: "$1/1000" MHz\n"}' /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
awk '{print "Maximum frequency: "$1/1000" MHz\n"}' /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq

tis1=`awk '{SUM += $2} END {printf("%.0f",SUM/1000)}' /sys/devices/system/cpu/cpu0/cpufreq/stats/time_in_state`
idle0=`awk '{printf ("%.0f",$1/1000)}' /sys/devices/system/cpu/cpu0/cpuidle/state0/time`
idle1=`awk '{printf ("%.0f",$1/1000)}' /sys/devices/system/cpu/cpu0/cpuidle/state1/time`
idle2=`awk '{printf ("%.0f",$1/1000)}' /sys/devices/system/cpu/cpu0/cpuidle/state2/time`
idle3=`awk '{printf ("%.0f",$1/1000)}' /sys/devices/system/cpu/cpu0/cpuidle/state3/time`
totaltime=$(($idle0+$idle1+$idle2+$idle3+$tis1))
echo -e "FREQUENCY\tUSED"
awk '{printf (($1/1000)" MHz \t")};{if ($2 == 0) printf "0 %\n"; else printf ("%.3f %\n",($2/10)/"'"$totaltime"'")}' /sys/devices/system/cpu/cpu0/cpufreq/stats/time_in_state
echo ""
 
Posts: 362 | Thanked: 113 times | Joined on Feb 2010
#2548
Originally Posted by iceman600 View Post
ok im confused...
125-950-500 lehto meaning:
125 low
950 max
500 is what?

sorry noob
dsp i guess
 
Posts: 22 | Thanked: 15 times | Joined on Apr 2010 @ Israel
#2549
Originally Posted by AlMehdi View Post
Start with the max_freq on 810mhz and then test the other frequencies with the "temp command". That is how i did it. I have noticed it can be unstable for me on the higher frequencies.
ok i'm not sure about stability ( it's on for less than 5 minutes ) but the device is on and runnig
i was able to go up to 900Mhz but i don't wanna take it any higher
now i'm gonna let it run for few minutes (idle) and then use it with web, media, games etc. to see if it is stable

thanks for the advice

Update : worked great for web, games but playing video made it reboot by itself
gonna try lowering the freq and check it again

Last edited by moshikko; 2010-04-12 at 23:16.
 
Posts: 946 | Thanked: 1,650 times | Joined on Oct 2009 @ Germany
#2550
the customizable voltage kernel is ready:
Code:
wget http://maemory.com/N900/overclock/generic/kernel-maemo_2.6.28-maemo21_armel.deb 
wget http://maemory.com/N900/overclock/generic/kernel-modules-maemo_2.6.28-maemo21_armel.deb
wget http://maemory.com/N900/overclock/generic/kernel-flasher-maemo_2.6.28-maemo21_armel.deb
online tweaking of voltages is done with
Code:
# cat /sys/power/sr_vdd1_opps_vsel
30 30 38 48 54 48 60 60 60 60 60 60 60 67 72
echo "30 30 38 48 54 48 60 60 60 60 60 60 60 67 72" > /sys/power/sr_vdd1_opps_vsel
The meaning of the voltages (first column):
Code:
stock/normal kernel
30 = 0x1e = 0.975V x 0 MHz = 0
30 = 0x1e = 0.975V x 125 MHz = 119
38 = 0x26 = 1.075V x 250 MHz = 289
48 = 0x30 = 1.200V x 500 MHz = 720
54 = 0x36 = 1.275V x 550 MHz = 894
60 = 0x3c = 1.350V x 600 MHz = 1094
60 = 0x3c = 1.350V x 720 MHz = 1312
60 = 0x3c = 1.350V x 750 MHz = 1367
60 = 0x3c = 1.350V x 810 MHz = 1476
60 = 0x3c = 1.350V x 850 MHz = 1549
60 = 0x3c = 1.350V x 900 MHz = 1640
60 = 0x3c = 1.350V x 950 MHz = 1731
XLV kernel:
30 = 0x1e = 0.975V x 0 MHz = 0
20 = 0x14 = 0.850V x 125 MHz = 90
30 = 0x1e = 0.975V x 250 MHz = 238
33 = 0x21 = 1.012V x 500 MHz = 513
38 = 0x26 = 1.075V x 550 MHz = 636
38 = 0x26 = 1.075V x 600 MHz = 693
45 = 0x2d = 1.163V x 700 MHz = 946
45 = 0x2d = 1.163V x 750 MHz = 1014
48 = 0x30 = 1.200V x 810 MHz = 1166
48 = 0x30 = 1.200V x 850 MHz = 1224
54 = 0x36 = 1.275V x 900 MHz = 1463
54 = 0x36 = 1.275V x 950 MHz = 1544
60 = 0x3c = 1.350V x 1000 MHz = 1823
67 = 0x43 = 1.438V x 1100 MHz = 2273
72 = 0x48 = 1.500V x 1150 MHz = 2588
I have verified that the customized voltages are actually used.
feel free to play with it.
I'm now uploading it to extras-devel.

XLV is: "30 20 30 33 38 38 45 45 48 48 54 54 60 67 72"
ideal: 30 30 30 30 33 38 45 45 48 48 54 54 60 67 72 (first three ignored)
ULV: 25 25 25 33 38 38 45 45 48 48 54 54 60 67 72
LV: 30 30 38 48 48 54 54 54 54 54 54 54 60 67 72

Last edited by titan; 2010-04-12 at 23:35.
 

The Following 10 Users Say Thank You to titan For This Useful Post:
Reply

Tags
cooking on gas, cortex-a8, faster, first to fry it wins!, hardware, its smoking, n900, need for speed, need for weed, nos, omap, omap3, omap3430, overclock, overclocking, soc, system-on-a-chip, the dogs, this thread got good!, vtec just kicked in y0!, warranty will be void, whooplah, zoom zoom


 
Forum Jump


All times are GMT. The time now is 13:31.