Overclock the N900? - Page 352 - maemo.org

Active Topics

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

Page 352 of 536

352

Thread Tools

sierrafoxtrot	2010-05-09 , 12:52
Posts: 78 \| Thanked: 53 times \| Joined on Nov 2009	#3511

hi, after updating power kernel settings from 0.6 to 0.7 i've noticed

dmesg | grep "error"

returns

[2.733581] onenand_bbt_wait: ecc error = 0x2222, controller error 0x2400
[2.759307] onenand_bbt_wait: ecc error = 0x2222, controller error 0x2400

that's to do with the nand right? is this serious? reflash?

phone seems to be okay so far tho ...

EDIT: hm. problems booting, sometimes it doesn't boot properly (gets to the first set of five flashing dots but not the next) and requires a couple of power key presses before it boots to the pin code entry screen

also, i'm using the old (pre-0.6) method of configuring power settings ie, i haven't done anything since updating to 0.6 and 0.7 ie i have not done what titan has described in this post

http://talk.maemo.org/showpost.php?p...postcount=3412

i've just left my kernel settings from before

Last edited by sierrafoxtrot; 2010-05-09 at 13:00.

Quote & Reply |

titan	2010-05-09 , 13:07
Posts: 946 \| Thanked: 1,650 times \| Joined on Oct 2009 @ Germany	#3512

the upgrade was certainly not the reason for the ECC errors.
It could be due to too low voltage levels?

I highly recommend upgrading the config:
load the old and save it with kernel-config in the new format.

Originally Posted by sierrafoxtrot

hi, after updating power kernel settings from 0.6 to 0.7 i've noticed
dmesg | grep "error"
returns
[2.733581] onenand_bbt_wait: ecc error = 0x2222, controller error 0x2400
[2.759307] onenand_bbt_wait: ecc error = 0x2222, controller error 0x2400
that's to do with the nand right? is this serious? reflash?
phone seems to be okay so far tho ...
EDIT: hm. problems booting, sometimes it doesn't boot properly (gets to the first set of five flashing dots but not the next) and requires a couple of power key presses before it boots to the pin code entry screen
also, i'm using the old (pre-0.6) method of configuring power settings ie, i haven't done anything since updating to 0.6 and 0.7 ie i have not done what titan has described in this post
http://talk.maemo.org/showpost.php?p...postcount=3412
i've just left my kernel settings from before

Quote & Reply |

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

gabby131	2010-05-09 , 13:13
Posts: 1,729 \| Thanked: 388 times \| Joined on Jan 2010 @ Canada	#3513

Originally Posted by AlMehdi

No, only if you set the voltage to low.

oh.......coz my camera shuts down in video mode with titan's oc kernels (ulv). this was my first time recording a vid using my n900 so i just notice it. so LV kernel should work right?

EDIT: oops! problem solved! reboot brings everything back to default, so i just need to reboot to use Video Cam after OC.

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-09 at 14:07.

Quote & Reply |

sierrafoxtrot	2010-05-09 , 13:48
Posts: 78 \| Thanked: 53 times \| Joined on Nov 2009	#3514

@titan

I've run (as root)

kernel-config save myconfig

and i can see that it's created

/home/user/.kernel/myconfig

however i still get the onenand_bbt_wait errors (only at boot time), are there any old files i should clean up or does you script already delete the old config files?

i'm not sure it's the voltage because i was running your ideal kernel settings for several weeks with no apparent errors ...

Quote & Reply |

adalal	2010-05-09 , 14:03
Posts: 100 \| Thanked: 19 times \| Joined on Jan 2010	#3515

i just upgraded from maemo24 to maemo25, i dont see kernel-config command anywhere on my system :S help

Quote & Reply |

geneven	2010-05-09 , 14:07
Posts: 5,795 \| Thanked: 3,151 times \| Joined on Feb 2007 @ Agoura Hills Calif	#3516

Originally Posted by adalal

i just upgraded from maemo24 to maemo25, i dont see kernel-config command anywhere on my system :S help

Become root and try again.

Quote & Reply |

adalal	2010-05-09 , 14:10
Posts: 100 \| Thanked: 19 times \| Joined on Jan 2010	#3517

i tried ssh-ing into the system as root, and it's still not under /usr/sbin/

Quote & Reply |

Jokah	2010-05-09 , 14:34
Posts: 53 \| Thanked: 8 times \| Joined on Apr 2010 @ Switzerland	#3518

I have errors too checking my dmesg

[ 2.660278] Scanning device for bad blocks
[ 2.679565] onenand_bbt_wait: ecc error = 0x2222, controller error 0x2400
[ 2.679595] Bad eraseblock 337 at 0x02a20000
[ 2.710601] onenand_bbt_wait: ecc error = 0x2222, controller error 0x2400
[ 2.710632] Bad eraseblock 882 at 0x06e40000
[ 2.743316] onenand_bbt_wait: ecc error = 0x2222, controller error 0x2400
[ 2.743377] Bad eraseblock 1457 at 0x0b620000
[ 2.745361] onenand_bbt_wait: ecc error = 0x2222, controller error 0x2400
[ 2.745391] Bad eraseblock 1492 at 0x0ba80000

what are those related and how to fix?

Quote & Reply |

geneven	2010-05-09 , 14:59
Posts: 5,795 \| Thanked: 3,151 times \| Joined on Feb 2007 @ Agoura Hills Calif	#3519

Originally Posted by adalal

i tried ssh-ing into the system as root, and it's still not under /usr/sbin/

It is on my system, so you must not have installed correctly somehow.

Quote & Reply |

titan	2010-05-09 , 16:07
Posts: 946 \| Thanked: 1,650 times \| Joined on Oct 2009 @ Germany	#3520

Originally Posted by Jokah

I have errors too checking my dmesg
what are those related and how to fix?

those seem to normal bad blocks which occur on NAND flash and are automatically corrected (like bad sectors on harddisk).
it should be fine if you have less than 20 of them
(see bold lines below from my log)

Code:

[  925.998352] Scanning device for bad blocks
[  926.022369] onenand_bbt_wait: ecc error = 0x2222, controller error 0x2400
[  926.022430] Bad eraseblock 421 at 0x034a0000
[  926.028961] onenand_bbt_wait: ecc error = 0x2222, controller error 0x2400
[  926.028991] Bad eraseblock 536 at 0x04300000
[  926.114837] Creating 6 MTD partitions on "omap2-onenand":
[  926.114868] 0x00000000-0x00020000 : "bootloader"
[  926.115264] 0x00020000-0x00080000 : "config"
[  926.115509] 0x00080000-0x000c0000 : "log"
[  926.118041] mtdoops: Attached to MTD device 2
[  926.118072] 0x000c0000-0x002c0000 : "kernel"
[  926.118347] 0x002c0000-0x004c0000 : "initfs"
[  926.118621] 0x004c0000-0x10000000 : "rootfs"
[  926.120697] UBI: attaching mtd5 to ubi0
[  926.120758] UBI: physical eraseblock size:   131072 bytes (128 KiB)
[  926.120788] UBI: logical eraseblock size:    129024 bytes
[  926.120819] UBI: smallest flash I/O unit:    2048
[  926.120849] UBI: sub-page size:              512
[  926.120880] UBI: VID header offset:          512 (aligned 512)
[  926.120910] UBI: data offset:                2048
[  926.254974] UBI: attached mtd5 to ubi0
[  926.255035] UBI: MTD device name:            "rootfs"
[  926.255065] UBI: MTD device size:            251 MiB
[  926.255096] UBI: number of good PEBs:        2008
[  926.255126] UBI: number of bad PEBs:         2
[  926.255157] UBI: max. allowed volumes:       128
[  926.255187] UBI: wear-leveling threshold:    4096
[  926.255218] UBI: number of internal volumes: 1
[  926.255249] UBI: number of user volumes:     1
[  926.255279] UBI: available PEBs:             0
[  926.255310] UBI: total number of reserved PEBs: 2008
[  926.255340] UBI: number of PEBs reserved for bad PEB handling: 20
[  926.255371] UBI: max/mean erase counter: 164/68
[  926.255401] UBI: image sequence number: 12