| The Following User Says Thank You to Stiki For This Useful Post: | ||
|
|
2010-04-13
, 16:20
|
|
Posts: 149 |
Thanked: 140 times |
Joined on Sep 2009
@ YUL
|
#2632
|
It has nothing with overclocking, it is a bug.
Try this - http://talk.maemo.org/showpost.php?p...3&postcount=62
|
|
2010-04-13
, 16:28
|
|
Posts: 53 |
Thanked: 8 times |
Joined on Apr 2010
@ Switzerland
|
#2633
|
the customizable voltage kernel is ready:
online tweaking of voltages is done withCode: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
The meaning of the voltages (first column):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
I have verified that the customized voltages are actually used.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
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
|
|
2010-04-13
, 16:33
|
|
Posts: 22 |
Thanked: 4 times |
Joined on Jun 2009
|
#2634
|
1) for 125Mhz you need to set 124999. but I don't recommend 125 anyway.
2) videos work perfect for me (ideal kernel settings). do they play if you flash the stock kernel?
|
|
2010-04-13
, 16:41
|
|
Posts: 61 |
Thanked: 21 times |
Joined on Jan 2010
|
#2635
|
please let me know whether the upgrade worked fine
or whether you had problems. I'm waiting for your feedback before I promote it to testing.
|
|
2010-04-13
, 17:00
|
|
Posts: 946 |
Thanked: 1,650 times |
Joined on Oct 2009
@ Germany
|
#2636
|
I had your ideal kernel installed, updated throught HAM. Result: Reboot loop![]()
Strange fact, Ihad to reflash the entire PR1.1.1 fiasco image since reflashing only the kernel didn't fix it.
| The Following User Says Thank You to titan For This Useful Post: | ||
|
|
2010-04-13
, 17:02
|
|
Posts: 946 |
Thanked: 1,650 times |
Joined on Oct 2009
@ Germany
|
#2637
|
Thanks Titan for the great work
Will you make an xlv package of your kernel maemo22 on your repository ? or the only solution is the "/etc/event.d/kernel-maemo " script?
thx
|
|
2010-04-13
, 17:05
|
|
Posts: 1 |
Thanked: 0 times |
Joined on Feb 2010
@ Texas
|
#2638
|
Flashing from N900 xterminal: (no need for PC): (source)
* do a backup, have a pc nearby and know you are able to flash the n900 with flasher-3.5 - just in case
0. Launch xterminal app then type sudo gainroot (need rootsh installed)
1. type "softupd -vv -s --local" (thats double v)
2. open new terminal
3. type "flasher --local -f -k <kernel_zimage_file_with_path>"
4. you see the flashing (takes some time)
5. type "sync" to save changes
6. type "reboot" and enter to restart
7. Test out your phone as usual. (Apps, browser, camera, phone etc etc)
8. If any abnormal events occur frequently (crash, hang, screen corruption etc), turn it off, flash it to a slower kernel and test again.
I do have rootsh installed by the way. Once I get to the step where you have to enter command "flasher --local -f -k <kernel_zimage_file_with_path>" it tells me that the path doesn't exist. Am I supposed to have the < or > on either end, or am I supposed to have the file stored on an SD card? I have put the file directly in the root of the device, and not in any folders at all. I can see the file when I go to file manager and click on the directory that first comes up "Nokia N900." I am new to the Maemo software, especially when it comes to anything with Linux. But I have been reading a lot trying to soak in as much as I can. Anyway, I MUST be typing in the file path incorrectly. That's the only thing that I can think of. If you need more info from me please reply. I really would like to OC my N900 to see the difference.
Also, I can't remember where I downloaded the file from as I am not home right now on my personal laptop. But the file name that I downloaded is "zImage-850mhz-450dsp" with no extension on the end of it. My N900 says the file type is unknown. Could someone give me an example of how it should be typed with my file name that I downloaded. I really would love it if someone had a video posted up somewhere going through the steps on how to do it through the xterminal. That would be great! If not, I look forward to anyone's help. Thanks.
|
|
2010-04-13
, 17:29
|
|
Posts: 61 |
Thanked: 21 times |
Joined on Jan 2010
|
#2639
|
weird! I guess it is related to the different modules directory (-xlv) in the experimental kernels. It would be really interesting to see the output if you upgrade via apt-get
and then to check the /lib/modules directory.
I hope it doesn't affect people who only installed kernels from extras*
|
|
2010-04-13
, 17:46
|
|
Posts: 44 |
Thanked: 5 times |
Joined on Apr 2010
|
#2640
|
![]() |
| Thread Tools | |
|
Will you make an xlv package of your kernel maemo22 on your repository ? or the only solution is the "/etc/event.d/kernel-maemo " script?
thx