Active Topics
-
Is there a section to talk about Java ME? Apps, etc. (7)
to General by teroyk - 16 hrs, 2 mins ago - more...
| The Following User Says Thank You to Nobless For This Useful Post: | ||
 |
|
2012-07-16
, 16:31
|
|
Posts: 4,118 |
Thanked: 8,901 times |
Joined on Aug 2010
@ Ruhrgebiet, Germany
|
#372
|
Then I think I do not have an idea anymore.
Or maybe one try: boot with keyboard out, select u-boot console and type run attachboot. But I guess this will produce the same error
Or maybe one try: boot with keyboard out, select u-boot console and type run attachboot. But I guess this will produce the same error
| The Following User Says Thank You to peterleinchen For This Useful Post: | ||
ty for helping
|
|
2012-07-16
, 17:51
|
|
Posts: 804 |
Thanked: 1,598 times |
Joined on Feb 2010
@ Gdynia, Poland
|
#374
|
Well, according to http://talk.maemo.org/showpost.php?p...0&postcount=23 the 2104 hw revision is a bit problematic. This with addition to the fact that new u-boot has some important change in atags reading/setting (at least as far as i understood after reading last few pages quickly) may be the reason for your help.
Pali, could you comment on that? It looks Nobless has N900 with hw rev 2104 which cannot be booted with new u-boot. May it be a release blocker?
Nobless, could you boot your N900 by loading kernel from flasher via usb and try to read atags? Here is instruction how to do that once you successfully boot your n900 using flasher - it is important that you do this using flasher and not load kernel by old, working u-boot. If it's indeed a problem with u-boot, this may help solve it not only for you, but for many other 2104 owners.
Pali, could you comment on that? It looks Nobless has N900 with hw rev 2104 which cannot be booted with new u-boot. May it be a release blocker?
Nobless, could you boot your N900 by loading kernel from flasher via usb and try to read atags? Here is instruction how to do that once you successfully boot your n900 using flasher - it is important that you do this using flasher and not load kernel by old, working u-boot. If it's indeed a problem with u-boot, this may help solve it not only for you, but for many other 2104 owners.
| The Following 3 Users Say Thank You to misiak For This Useful Post: | ||
 |
|
2012-07-16
, 19:22
|
|
Posts: 101 |
Thanked: 73 times |
Joined on Oct 2011
@ Lithuania
|
#376
|
very very sorry! just rechecked HW revision with
Typed a mistake in the older post.
The HW revision is 2204 not 2104! Long time ago I checked the revision so similars numbers of misled me.. Still need a dump of readed atags ?
Last edited by Nobless; 2012-07-16 at 19:33.
cat /peroc/cpuinfo
The HW revision is 2204 not 2104! Long time ago I checked the revision so similars numbers of misled me..
Still need a dump of readed atags ?
Originally Posted by pali
works nicely when kernel flashed via USB! that means mine rootfs is not corrupted. So the problem related to something else ?
just edit /sbin/preinit and add line "modprobe fbcon" before condition if exists file /bootmenu.sh
please note, that framebuffer module (fbcon) and also /sbin/preinit are stored in rootfs. If rootfs is corrupted no framebuffer output!
Last edited by Nobless; 2012-07-16 at 19:33.
| The Following User Says Thank You to Nobless For This Useful Post: | ||
|
|
2012-07-18
, 10:40
|
|
Posts: 101 |
Thanked: 73 times |
Joined on Oct 2011
@ Lithuania
|
#379
|
any news here ? 
|
|
2012-07-18
, 11:13
|
|
Posts: 1,397 |
Thanked: 2,126 times |
Joined on Nov 2009
@ Dublin, Ireland
|
#380
|
Please, could anyone point me to any tutorial or how-to, about migrating from an already existing multiboot installation (with Nitdroid and backupmenu) to an uboot/bootmenu based one?
Or do I need to first uninstall all the stuff (Nitdroid, backupmenu, KP, multiboot) and start over?
Or do I need to first uninstall all the stuff (Nitdroid, backupmenu, KP, multiboot) and start over?
| The Following User Says Thank You to ivgalvez For This Useful Post: | ||
Yes i have one inside, i do what u sad and the same error occurs.