U-Boot for Nokia RX-51 with BootMenu (updated version 2012.10-rc3-1) - Page 26 - maemo.org

Active Topics

The N900 is now 15 years old! (7)
to Nokia N900 by Danct12 - 1 day, 14 hrs ago
Sailfish OS for the Motorola Moto G7 Power (XT1955-5) - (ocean) (4)
to SailfishOS by Maemish - 2 days, 10 hrs ago
F(x)tec Pro1x (QWERTY) for sale (0)
to Buy & Sell by aln00000 - 4 days, 19 hrs ago
more...

Page 26 of 85

Thread Tools

J4ZZ	2012-05-03 , 17:21
Posts: 539 \| Thanked: 518 times \| Joined on May 2010 @ nanaurbusiness	#251

Pali is there anything else I can try to get power-kernel booting?
Omap1 and Omap1-fb are booting just fine so why kernel-power50 does not I don't get it? On page 1 flocke had the same problem, but somehow it was working later.

Edit: Somehow kernel-power50 is finally booting. But I'm not sure what exactly fixed it. I re-ran FSCK on MyDocs, renamed REUSEATAGS to USEATAGS and ran u-boot-update-bootmenu again.

Regards,

J4ZZ

__________________

N900 ~ $ make me a sandwich
-bash: no, make it yourself
N900 ~ $ sudo make me a sandwich
-bash: ok then...

Last edited by J4ZZ; 2012-05-05 at 20:31.

Quote & Reply |

bcunha	2012-05-05 , 22:08
Posts: 5 \| Thanked: 0 times \| Joined on Apr 2012	#252

I'd like some help here. I've managed to flash the power kernel with the u-boot, and successfully load it. I've then proceeded to burn a Meego image into the SD card. When I select "external SD card" from the boot menu, it recognizes the meego kernel, and begins boot, but then a white strip is painted across the screen and 10-15s afterwards the phone reboots. The same behavior happens when I try to boot Nemo from the external card.

I don't know what I'm doing wrong... I must have forgotten something, but I don't know what it is...

Quote & Reply |

drucula	2012-05-05 , 22:44
Posts: 34 \| Thanked: 44 times \| Joined on Sep 2010 @ Israel	#253

Originally Posted by bcunha

I'd like some help here. I've managed to flash the power kernel with the u-boot, and successfully load it. I've then proceeded to burn a Meego image into the SD card. When I select "external SD card" from the boot menu, it recognizes the meego kernel, and begins boot, but then a white strip is painted across the screen and 10-15s afterwards the phone reboots. The same behavior happens when I try to boot Nemo from the external card.

I don't know what I'm doing wrong... I must have forgotten something, but I don't know what it is...

I'm experiencing the same problem.

Quote & Reply |

ivyking	2012-05-06 , 19:55
Posts: 237 \| Thanked: 274 times \| Joined on Jul 2010	#254

Originally Posted by bcunha

I'd like some help here. I've managed to flash the power kernel with the u-boot, and successfully load it. I've then proceeded to burn a Meego image into the SD card. When I select "external SD card" from the boot menu, it recognizes the meego kernel, and begins boot, but then a white strip is painted across the screen and 10-15s afterwards the phone reboots. The same behavior happens when I try to boot Nemo from the external card.

I don't know what I'm doing wrong... I must have forgotten something, but I don't know what it is...

I have been having the same problem while trying to boot directly this way, but the system booted fine after creating the appropriate item file and updating the menu.

[Edit]

Originally Posted by bcunha

Thanks for the reply. I've tried creating an .item file at /etc/multiboot.d/ pointing to the uImage at the external SD card. The u-boot updater simply ignores it. Could you please post your .item file here?

you are placing the item file in a wrong directory(it should be placed in /etc/bootmenu.d/), please re-read the first post carefully before going further.

if you are going to boot nemo make sure you use u-boot version built on the 4th of May or later.

I found that reading /usr/bin/u-boot-update-bootmenu is very useful for learning how the item file parameters should be filled.

example .item file:

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

please note that if you are going to boot from an external loaction(other than nand) using a ready made uImage, ITEM_DEVICE and ITEM_FSTYPE actually refer to where the uImage is located whether or not it is the same partition you intend to boot from..

you specify the root device (the partition you want to boot from) along with other kernel parameters using ITEM_CMDLINE.

also for some reason, if the target kernel requires nolo atags and ITEM_REUSEATAGS is used instead of ITEM_USEATAGS, the target system won't boot (this even happens with KP when booting maemo).

Last edited by ivyking; 2012-05-07 at 06:52.

Quote & Reply |

The Following 5 Users Say Thank You to ivyking For This Useful Post:
bcunha, drucula, Estel, MaddogG, Sourav.dubey

bcunha	2012-05-06 , 22:57
Posts: 5 \| Thanked: 0 times \| Joined on Apr 2012	#255

Thanks for the reply. I've tried creating an .item file at /etc/multiboot.d/ pointing to the uImage at the external SD card. The u-boot updater simply ignores it. Could you please post your .item file here?

Quote & Reply |

	MaddogG	2012-05-07 , 21:35
	Posts: 234 \| Thanked: 175 times \| Joined on Jun 2010 @ Genova (Italy)	#256

@Pali

I could not create "bootmenu.scr" file, so I investigated a bit and I think I found a little bug in u-boot-update-bootmenu script.
In fact, if file "BOOTMENU_CMD.default" is never created, the script will surely fail at lines 269, and file "bootmenu.scr" will never be generated.
I think this happens if you don't set any default entry (you don't create the symlink "bootmenu.item" in /etc/default/).
Maybe you should check if this file exist before line 269:

Code:

if test -f "$BOOTMENU_CMD.default"; then
cat "$BOOTMENU_CMD.default" "$BOOTMENU_CMD" > "$BOOTMENU_CMD.new"
mv "$BOOTMENU_CMD.new" "$BOOTMENU_CMD"
fi

I included command

Code:

mv "$BOOTMENU_CMD.new" "$BOOTMENU_CMD"

in the "if" statement because, at line 255, you delete the file "BOOTMENU_CMD.new", so if file "BOOTMENU_CMD.default" doesn't exist, file "BOOTMENU_CMD.new" is not created and this command fails, too.

I hope I explained myself...

What do you think?

__________________
Some say the world will end in fire; some say in segfaults...

Quote & Reply |

The Following 7 Users Say Thank You to MaddogG For This Useful Post:
Estel, ivyking, kowalski, lokimotive, misiak, pali, Sourav.dubey

drucula	2012-05-07 , 21:54
Posts: 34 \| Thanked: 44 times \| Joined on Sep 2010 @ Israel	#257

Originally Posted by bcunha

Thanks for the reply. I've tried creating an .item file at /etc/multiboot.d/ pointing to the uImage at the external SD card. The u-boot updater simply ignores it. Could you please post your .item file here?

ivyking is right. Nemo is now booting properly using the following .item in /etc/bootmenu.d/:

Code:

ITEM_NAME="Nemo"
ITEM_KERNEL="uImage"
ITEM_DEVICE="${EXT_CARD}p3"
ITEM_FSTYPE="vfat"
ITEM_CMDLINE="root=/dev/mmcblk0p1 rootwait ro console=ttyO2,115200n8 console=tty0 omapfb.vram=0:2M,1:2M,2:2M mtdoops.mtddev=2 quiet"
ITEM_USEATAG=1

Quote & Reply |

The Following 5 Users Say Thank You to drucula For This Useful Post:
bcunha, fw190, ivyking, MaddogG, Sourav.dubey

scoobydoo	2012-05-08 , 07:20
Posts: 101 \| Thanked: 47 times \| Joined on Aug 2010 @ somerset	#258

how can i extract nitdroid rc7 kernel on device as no pc at present cheers

Quote & Reply |

	sifo	2012-05-09 , 17:48
	Posts: 1,359 \| Thanked: 1,292 times \| Joined on Oct 2011 @ Tartus.Syria	#259

hi friends just questions as we know that u-boot loads and multiboot flash
but if i installed multiboot and choose kp50 and boot but i didnt open the keyboard anytime so in short does multiboot flash if i didnt open the keyboard and change the kernel does it flash ?
thanks in advance.

__________________
[ N900-Crack ] [ The Purge ] [ New Smiles ] [ New icons ] [ ? ]
" Hey ! I've just met you and this is crazy, so install cssu maybe ? "
Please help out keeping Maemo.org alive, and consider donating.
https://www.facebook.com/ZoRk7

Quote & Reply |

pali	2012-05-10 , 07:33
Posts: 2,154 \| Thanked: 8,464 times \| Joined on May 2010	#260

Originally Posted by MaddogG

@Pali

I could not create "bootmenu.scr" file, so I investigated a bit and I think I found a little bug in u-boot-update-bootmenu script.
In fact, if file "BOOTMENU_CMD.default" is never created, the script will surely fail at lines 269, and file "bootmenu.scr" will never be generated.
I think this happens if you don't set any default entry (you don't create the symlink "bootmenu.item" in /etc/default/).
Maybe you should check if this file exist before line 269:
Code:
if test -f "$BOOTMENU_CMD.default"; then
cat "$BOOTMENU_CMD.default" "$BOOTMENU_CMD" > "$BOOTMENU_CMD.new"
mv "$BOOTMENU_CMD.new" "$BOOTMENU_CMD"
fi
I included command
Code:
mv "$BOOTMENU_CMD.new" "$BOOTMENU_CMD"
in the "if" statement because, at line 255, you delete the file "BOOTMENU_CMD.new", so if file "BOOTMENU_CMD.default" doesn't exist, file "BOOTMENU_CMD.new" is not created and this command fails, too.

I hope I explained myself...

What do you think?

do you have free space on rootfs? try to reboot device