Hello, everyone, a newbie here.

Just used Application manager to update Extended kernel and install "Custom Ringtones for Your Contact", then was recommended to reboot.

Shut it off using Switching Off, then showed up the following screen w/ a penguin icon on the upper left corner:

U-Boot 2010.06-mantan (Nov 10 2010 - 13:53:03)
In: vga
Out: vga
Err: vga
Getting NOLO boot parameters ...
Die ID #0C00000400000000040382730401e00e
Booting NOLO supplied kernel ...
## Booting kernel from Legacy Image at 80538c18 ...
Image Name: kernel-power
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 1793624 Bytes = 1.7 MiB
Load Address: 80008000
Entry Point: 80008000
Verifying Checksum ... OK
Loading Kernel Image ... OK
OK
Using existing atags at 0x80000100

Starting kernel ...

This is where it stops. Take off the battery, then put it back on, power on button, it shows the aforementioned screen. A couple of times. This N900 was overclocked to 850MHz.
What should I do now? Thanks in advance!

Just reinstall Omap Kernel via flasher (on computer). Just your kernel, it will not effect anything on your N900.

I'm have not used u-boot on N900, yet. I've installed Multiboot with PR 1.3 right away.

Thanks.

I reflashed the Kenel only per the suggestion in another thread. It came back with everything intact. After rebooting, used Kernel-config to load my overclocking commands, but was told not supported. This happened once when updatin to PR 1.3 and re-installation solved it. However, this time, it is not my lucky day. After un- then re-installing Enhanced Kernel for Power Users, the device stuck at the startup again. Had to do another kernel flashing.

Word of Caution: Do not install Enhanced Kernel for Power Users at this moment.

what thread?
Having the same problem now:-)

Easy fix reflash kernel on a 32-bit OS

SERIOUSLY?!?!?
3RD ****ING THREAD~!~
http://talk.maemo.org/showthread.php?t=65420
GOD!! SEARCH!~~

Note: In my opinion, people who leave such messages should include some search tips, at a minimum. I think that people who haven't searched usually have reasons; for example

1. They have searched, but didn't understand the results they found.
2. They have searched, but didn't understand what search terms to use.
3. They naively used the giant (and useless) Search box at the top of the site rather than Power Search. Imagine, people actually use that thing! Didn't they see the warnings about it during kindergarten? All sites put useless things and display them prominently!

Ugh. I got mine apt-get updated too (including power-kernel v44 and its mate uboot) and now stuck at the uboot booting screen. Taking out the battery for a minute, putting it back and then plugging in the usb cable while holding the U key... sorry not working for me. In fact it didn't make any difference whether the U key is pressed or not. I mean the device just persist to boot in uboot no matter what.
I admit that I did see the line "use enhanced u-boot binary from package u-boot-for-power-kernel" in the changelog, but why didn't it say, or at least give a warning, about possibly actually) making the device fail to boot again?

yeah seriously.
http://talk.maemo.org/showthread.php?t=65420
http://tablets-dev.nokia.com/nokia_N900.php
http://www.torrentdownloads.net/sear...R+EMMC+MR0+ARM
http://www.youtube.com/watch?v=8eVSX...eature=related
http://www.youtube.com/watch?v=kw2ZM...eature=related
http://gathering.tweakers.net/forum/...s/1363257?data[filter_keywords]=flashen%20n900&data[boolean]=AND
http://talk.maemo.org/showpost.php?p...postcount=1835
http://www.google.be/#hl=fr&source=h...89a6a9dba1114e

without the numerous searches on this site,
so sir, plz don't assume I don't ****ing search.
It's not because I search it, that it's also solved!


in xterm on pc
flasher-3.5.exe -F RX-51_2009SE_10.2010.13-2.VANILLA_PR_EMMC_MR0_ARM.bin -f -R he gives the waring, a dos pups up
suitable device fount at bus bus-0.
Device adres, found device RX-51, hardware revision 2204
NOLO versoin 1.4.14
version of sw-release: RX-51_2009SE_20.2010.36-2_PR_MR0
booting device into flash mode;
Suitable USB device not found

oh yea I am on the same boot now.
but perhaps it helps a bit to stay cool and work together with the devs and other guys in trouble to find out the cure. I do appreciate the devs' hard work and believe they are very willing to help.