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: 151 | Thanked: 82 times | Joined on Sep 2008
#3531
Originally Posted by kennibal View Post
I'm just new here..

I've updated the Enhance Linux Kernel to Maemo27 for my N900.

If I may ask, is it ok to overclock this device to the ideal 500-850mhz here in the Philippines were the temperature ranges from 35-38 degs Celsius?

By the way, I also installed the leaked PR1.2 previously.

Thanks!

I'm using Enhanced Linux Kernel 2.6.28.10power27
(PR1.2-leaked) with ideal settings.
Temp ranges between 25-33 degs C.

All is well.
 
giecsar's Avatar
Posts: 91 | Thanked: 34 times | Joined on Apr 2010 @ Italy
#3532
Hi everyone, I bought my N900 a few days ago, and do not want to overclock it (yet), but I would like to know what is the command to lower the idle frequency from 250MHz, to say, 125MHz. Thanks in advance.
 
CarstenDutch's Avatar
Posts: 147 | Thanked: 78 times | Joined on Dec 2009 @ Netherlands
#3533
I have got a problem now which i had not with the maemo25 kernel and custom config.

Updated to maemo27 Kernel and got a problem,

# kernel configuration file generated by /usr/sbin/kernel-config
MINFREQ=125
MAXFREQ=600
FREQS="0:22,90 125:23,90 250:28,180 500:29,360 550:32,400 600:33,430"
SMARTREFLEX_VDD1=0
SMARTREFLEX_VDD2=0
IGNORE_NICE_LOAD=1
UP_THRESHOLD=75
SAMPLING_RATE=150000

Up on booting the device will play arround 2 seconds bootvideo and quit playing and goes directly to dashboard, also media section won't play media... media not supported??

I guess the voltage config is to low for this kernel? It was running stable with maemo25 did many testing.

dmesg log,
WMD_DEH_NOTIFY: ********** DEVICE EXCEPTION **********
WMD_DEH_NOTIFY: DSP_SYSERROR, errInfo = 0x102

Last edited by CarstenDutch; 2010-05-09 at 22:15.
 
Posts: 1,427 | Thanked: 2,077 times | Joined on Aug 2009 @ Sydney
#3534
UPDATE
- I have updated my guide with latest info from titan's latest kernel and settings.
- Have included some simple commands for both loading ideal and starving profile.

I have just upgraded to maemo27 kernel and latest settings.
Have loaded the new profiles and made new profiles off them.
Have setup the default profile at bootup to be 'starving' default.
Looking good. No issues yet even at 1.1Ghz as before.

Awesome work titan! thank you.
 

The Following 4 Users Say Thank You to jakiman For This Useful Post:
CarstenDutch's Avatar
Posts: 147 | Thanked: 78 times | Joined on Dec 2009 @ Netherlands
#3535
I was looking into the problem and find something strange when i had the maemo25 kernel running.
I saw that it was most of the time working on 550mhz and not 599 that much.
Now i saw that something was changed from the 599 to 600mhz in the maemo27 kernel now working most of time 600mhz (don't know if the mhz change was only visual or other...) so i upped the voltage by 1 point 600:34,430 and that affected the dsp thats why i got the dsp error and media lock-up.

Device is running great now.
 
Posts: 1,729 | Thanked: 388 times | Joined on Jan 2010 @ Canada
#3536
Originally Posted by titan View Post
?? I uploaded and successfully downloaded v27+0.7 today and you can see the files here
http://repository.maemo.org/extras-d.../kernel-power/
http://repository.maemo.org/extras-d...ower-settings/
the latest versions after maemo25 gives me an "Incompatible Application Package". what can i do? do i need to uninstall previuos kernels?

UPDATE: oops, apt-get update is al it needs, thanks
__________________
if i did help you, just click "Thanks" on the lower right of my post. thanks!

"The best way to break a Spell is to prevent it from being cast in the first place"

N900: 1000/1150mhz; sampling_rate 15; up_threshold 150000;

Last edited by gabby131; 2010-05-10 at 03:26.
 
Posts: 1,729 | Thanked: 388 times | Joined on Jan 2010 @ Canada
#3537
awright awesome! the 599 is now read as 600mhz......kinda got me confused if im on ulv or the default kernel (reboot).

but the starving settings is not so compatible with my device. always reboot after changing the max freqs (even in xterm). im sticking with ulv, i guess
__________________
if i did help you, just click "Thanks" on the lower right of my post. thanks!

"The best way to break a Spell is to prevent it from being cast in the first place"

N900: 1000/1150mhz; sampling_rate 15; up_threshold 150000;
 

The Following User Says Thank You to gabby131 For This Useful Post:
CarstenDutch's Avatar
Posts: 147 | Thanked: 78 times | Joined on Dec 2009 @ Netherlands
#3538
Originally Posted by gabby131 View Post
awright awesome! the 599 is now read as 600mhz......kinda got me confused if im on ulv or the default kernel (reboot).

but the starving settings is not so compatible with my device. always reboot after changing the max freqs (even in xterm). im sticking with ulv, i guess
I had this problem too, just make it 600:35,430 to make it run. with 600:34,430 i had artifacts and litle bit of hickup sometimes in video.
I'am still testing this setup with other frequencies too. and look at video's for artifacts and then test every frequency on locked speed.

I believe that the starving config is not realy wel suited for most! there must be something related too the 599/600 change with the maemo27 kernel i needed too move up the voltage for the cpu600/430dsp range.
 
Posts: 38 | Thanked: 13 times | Joined on Oct 2009
#3539
Updated script to switch profiles based on temperature

What it does -
Probes the temperature every 30 seconds
If the temperature is higher then 45 degrees, switches to the deafult profile (safety measure).
If the temperature is 40-45 degrees, runs on ideal config, with max =850
If the device is cold, starvs the CPU and let it run till 900MHZ.


#!/bin/sh
set old=""
set limits=""
set oldlimits=""
while test 2 -gt 1;
do
modprobe bq27x00_battery
read tmpr </sys/class/power_supply/bq27200-0/temp
if test $tmpr -gt 45;
then new="default";
limits="250 600";
else
if test $tmpr -gt 40;
then
new="ideal";
limits="500 850";
else
new="starving";
limits="500 900"
fi
fi
if test $old!=$new;
then
/usr/sbin/kernel-config load $new;
/usr/sbin/kernel-config limits $limits;
else if test $limits!=$oldlimits
/usr/sbin/kernel-config limits $limits;
fi
fi
old=$new
oldlimits=$limits
sleep 30
done

Last edited by sdpkom; 2010-05-10 at 10:37.
 

The Following 2 Users Say Thank You to sdpkom For This Useful Post:
Posts: 1,729 | Thanked: 388 times | Joined on Jan 2010 @ Canada
#3540
Originally Posted by CarstenDutch View Post
I had this problem too, just make it 600:35,430 to make it run. with 600:34,430 i had artifacts and litle bit of hickup sometimes in video.
I'am still testing this setup with other frequencies too. and look at video's for artifacts and then test every frequency on locked speed.

I believe that the starving config is not realy wel suited for most! there must be something related too the 599/600 change with the maemo27 kernel i needed too move up the voltage for the cpu600/430dsp range.
i read on a thread (i think it was the "saving battery, undervoltage kernels") that the developer of the starving itself stated that there is no guarantee for the starving kernel to work to all devices.

i am aware of it since i read it, but still want to try when its available.

unfortunately, no luck, im sticking with low voltages of titan.

thanks to titan

EDIT: i can chhoose to tweak the settings but i chose not to, i want the kernels the way they are when i installed them, and based on past my experience touching the pmconfig. by usig the ulv and ideal kernels @1ghz, my device has less time producing heat. and only up to 25°c (its a bit cold here, thats why its low) even if using game emus.
__________________
if i did help you, just click "Thanks" on the lower right of my post. thanks!

"The best way to break a Spell is to prevent it from being cast in the first place"

N900: 1000/1150mhz; sampling_rate 15; up_threshold 150000;

Last edited by gabby131; 2010-05-10 at 11:32.
 
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

Thread Tools

 
Forum Jump


All times are GMT. The time now is 22:02.