Overclock the N900? - Page 163 - maemo.org

Active Topics

The N900 is now 15 years old! (8)
to Nokia N900 by whayong - 10 hrs, 7 mins ago
Sailfish OS for the Motorola Moto G7 Power (XT1955-5) - (ocean) (4)
to SailfishOS by Maemish - 5 days, 6 hrs ago
more...

Page 163 of 536

163

Thread Tools

Matan	2010-04-07 , 20:58
Posts: 1,224 \| Thanked: 1,763 times \| Joined on Jul 2007	#1621

Empirically - it seems to me that the meaning of scaling_max_frequency is:
The maximum frequency that will be used is the lowest one that is >= scaling_max_frequency.

__________________
My repository

"N900 community support for the MeeGo-Harmattan" Is the new "Mer is Fremantle for N810".

No more Nokia devices for me.

Quote & Reply |

The Following User Says Thank You to Matan For This Useful Post:
hqh

thecube	2010-04-07 , 21:02
Posts: 97 \| Thanked: 12 times \| Joined on Feb 2010	#1622

yeahh :-)

Post 600000

how can I get the current temp?

Quote & Reply |

prana	2010-04-07 , 21:03
Posts: 18 \| Thanked: 18 times \| Joined on Mar 2010	#1623

Originally Posted by jcompagner

its located in /var/log/ (syslog file)

But you have to have syslogd or sysklogd installed.

I see. I was wondering why /var/log didn't have the usual messages file or a syslog file. Thanks.

Quote & Reply |

miwalter	2010-04-07 , 21:04
Posts: 36 \| Thanked: 8 times \| Joined on Apr 2010	#1624

Originally Posted by titan

I did some tests with a kernel that has 601MHz instead 600MHz in the table of supported frequencies.
booting with 700MHz worked fine until I made a call - it switched to 600MHz ;-(

could someone with one of Lehto's kernels please report
Code:
cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
make a phone call, and report the same value after the call?
thanks!

Before a call:

Code:

Nokia-N900-51-1:~# cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq 
900000

After a call:

Code:

Nokia-N900-51-1:~# cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq 
600000

Additional info:

Code:

Nokia-N900-51-1:~# cat /sys/devices/system/cpu/cpu0/cpufreq//cpuinfo_max_freq 
930000
Nokia-N900-51-1:~# cat /sys/devices/system/cpu/cpu0/cpufreq/stats/time_in_state 
930000 127730
595000 1264
500000 20578
250000 317428
125000 11314

And a couple of seconds later:

Code:

Nokia-N900-51-1:~# cat /sys/devices/system/cpu/cpu0/cpufreq/stats/time_in_state 
930000 128530
595000 1264
500000 20578
250000 317728
125000 12292

It reports a max of 600mhz - but still uses the 930mhz.

Quote & Reply |

The Following User Says Thank You to miwalter For This Useful Post:
titan

titan	2010-04-07 , 21:05
Posts: 946 \| Thanked: 1,650 times \| Joined on Oct 2009 @ Germany	#1625

I noticed that during the call both min and max are set to 600Mhz (using console via ssh).
after the call the minimum is reset to 250MHz.
can someone confirm that during extended phonecalls, even with the stock kernel,
scaling_min_freq, scaling_max_freq and scaling_cur_freq are 600000?

it would mean that Nokia keeps your device at the dangerous 600MHz during an entire extended phone call!
Calling is overclocking!

Last edited by titan; 2010-04-07 at 21:08.

Quote & Reply |

The Following 5 Users Say Thank You to titan For This Useful Post:
hqh, miwalter, pillar, qole, UNderworld

Bernard Wei	2010-04-07 , 21:07
Posts: 36 \| Thanked: 5 times \| Joined on Dec 2009	#1626

Originally Posted by titan

another observation: The dmse daemon seems to overwrite the max. freq. in the kernel with the value
from /etc/pmconfig every hour or so.

I noticed something quite strange. I am using a kernel configured to go as low as 125 and as high as 900, with pmconfig to clock from 250 to 800.

I then set different min/max via /sys/device for testing. I set it to 250-900 for speed testing, then 125-500 for underclocking, all done via /sys/device/system/..

With the speed set at 125-500, the device mysteriously clock up to 600 during a phone call, taking neither the 500 I set or the 800 in pmconfig. Weird

Quote & Reply |

Lehto	2010-04-07 , 21:07
Posts: 126 \| Thanked: 327 times \| Joined on Nov 2009 @ Finland	#1627

Originally Posted by titan

I noticed that during the call both min and max are set to 600Mhz (using console via ssh).
after the call the minimum is reset to 250MHz.
can someone confirm that during extended phonecalls, even with the stock kernel,
scaling_min_freq, scaling_max_freq and scaling_cur_freq are 600000?

This MIGHT possibly explain the reason why one user reported that the phone calls worked more smoothly with my crude OC kernel. As for that thing the min and max will be the maximum speed during phone call (bye bye battery life!).

Quote & Reply |

The Following User Says Thank You to Lehto For This Useful Post:
miwalter

Rushmore	2010-04-07 , 21:09
Posts: 1,255 \| Thanked: 393 times \| Joined on Oct 2009 @ US	#1628

Originally Posted by egoshin

The reason is simple - battery.

Stability is too but it is not for underclocking like Droid.

Frying has nothing with it - CPU was designed by ARM and basing on common technology licensing practice I guess TI didn't change anything in it's design because ARM did all work - thermal, radio emmision, delay propogation etc. So, TI got ARM design which can run on max freq from 600MHz to 1GHz.

However, the TI production line quality limits an effective max frequency and for stable run use 600MHz. But your mileage varies...

(usual disclaimer: anything here is for education purpose only and is not intended to convince you for overclocking or doing something bad).

Battery IS the reason for the Droid clock. That being said, most report little battery impact with the 800mhz, low volt kernel after nearly several months of use. People that set the max to 1ghz and beyond are experiencing battery issues, but that is more due to hitting the operational ceiling of the chip. Hit that, and all kinds of battery, heat and lock-ups happen in an accelerated manner.

Based on mining waaay to many threads, most people that clock at 1.1 ghz or higher are having problems on Droid.

Quote & Reply |

miwalter	2010-04-07 , 21:10
Posts: 36 \| Thanked: 8 times \| Joined on Apr 2010	#1629

Originally Posted by Lehto

This MIGHT possibly explain the reason why one user reported that the phone calls worked more smoothly with my crude OC kernel. As for that thing the min and max will be the maximum speed during phone call (bye bye battery life!).

If the phone uses max mhz during calls, this would be a showstopper for me - only because of easter-holidays I'm not using the phone that much as a phone as I usualy do...