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

Active Topics

Extra softwares in Sailfish using CLI, repositories, etc (117)
to SailfishOS by nieldk - 14 hrs, 4 mins ago
Firefox with Leste (6)
to Maemo 7 / Leste by teroyk - 1 day, 10 hrs ago
more...

Page 72 of 85

Thread Tools

	Alecsandru	2013-06-25 , 21:19
	Posts: 439 \| Thanked: 282 times \| Joined on Oct 2012	#711

can you add images to boot items? like n9's ubiboot?

__________________

N900 Beast featuring :
8GB OPTFS@ext4(*performance mount options)
overclock: cpu[125 - 1,150(*VDD1)+Dsp overclock
CSSU-T latest version

Quote & Reply |

The Following User Says Thank You to Alecsandru For This Useful Post:
nokiabot

ejcrashed	2013-06-26 , 21:18
Posts: 67 \| Thanked: 88 times \| Joined on Jan 2011 @ Costa RIca	#712

Originally Posted by ejcrashed

Hi Pali, is there any way to boot a console only (aka recovery mode) kernel from SD card?

I did a mistake while doing some tinkering with my N900 and got into reboot loop, i don't wan to reflash, i just need to boot and mount rootfs so i could restore some files?

Greets.

Nevermind, got around it using nemo.

Quote & Reply |

The Following User Says Thank You to ejcrashed For This Useful Post:
nokiabot

topet2k12001	2013-07-03 , 09:09
Posts: 428 \| Thanked: 226 times \| Joined on Dec 2010 @ Philippines	#713

Originally Posted by disappear

<snip>

Install u-boot from pali;
Code:
apt-get install -y u-boot-tools u-boot-flasher
restart n900
Code:
apt-get install kernel-power-settings
I would put a note here:

There will be a pop-up notification telling you that U-Boot will be "overwritten" (i.e. Kernel Power will flash it). Do not accept it.

This will result to Kernel Power Boot Image for U-Boot to be not installed.

Open FAM and check if Kernel Power Boot Image for U-Boot is not installed. If so, install it. You will not be prompted to flash/overwrite the U-Boot Kernel

restart n900
Code:
sudo gainroot
u-boot-update-bootmenu
restart with open ukeyboard
choose kp52

If you want to installing backupmenu:
Code:
apt-get install backupmenu
restart n900,with close ukeyboard,when shows the titles of u-boot,open ukeyboard and you see how loading bootmenu,choose maemo with..

I would edit this as:

Turn off N900

Keep keyboard open

Turn on N900

U-Boot will appear. You can select a Kernel.

After selecting a Kernel, don't close the keyboard. Boot Menu (with Backupmenu inside of it) will initiate.

then advice from Pali:
Code:
root
ln -s /etc/bootmenu.d/20-Maemo5-kernel-power-2.6.28.10-power52.item /etc/default/bootmenu.item
after that the backmenu shoud properly load kp52
I think this is all,if somebody have other advice please share it

Just wanted to report that this works.

I now have:

Default kernel
Kernel Power 52
Backupmenu

...all powered by U-Boot.

My next step now is to decide which CSSU I want to install, and then NITDroid. As for Nemo...I'll probably install it just so that I can write a Wiki Page/article about U-Boot and the steps to get it working with Backupmenu.

EDIT: I have modified the quoted message from "disappear" to show how I did it (basically it's the same steps but I rephrased them to be more descriptive/newbie-friendly).

I'll write an article for this in the Wiki Pages...not sure if this should be in a new Wiki article or if this should be placed/added in an existing Wiki Page/Article...please let me know your thoughts. I will likewise make a video of it (will reflash during the weekend to start all over).

Last edited by topet2k12001; 2013-07-03 at 09:56.

Quote & Reply |

The Following 5 Users Say Thank You to topet2k12001 For This Useful Post:
disappear, Dongle Fongle, handaxe, misiak, Sourav.dubey

marmistrz	2013-07-09 , 13:46
Posts: 3,328 \| Thanked: 4,476 times \| Joined on May 2011 @ Poland	#714

Well, I put a config file for Nemo to /etc/bootmenu.d/

Code:

ITEM_NAME="Nemo"
ITEM_KERNEL="uImage"
ITEM_DEVICE="/dev/mmcblk0p6"
ITEM_FSTYPE="vfat"
ITEM_CMDLINE="root=/dev/mmcblk0p5"

But no entry is being displayed. What's more, I can't boot kernel-power now too (at first boot after installing kp there's was omap kernel and kp to choose, but now standard options (emmcboot, sdboot & etc.)). What am I doing wrong?

should u-boot-update-bootmenu be run as user or as root? Tried both, none work.

__________________
If you want to support my work, you can donate by PayPal or Flattr

Projects no longer actively developed: here

Quote & Reply |

sLumPia	2013-07-09 , 14:23
Posts: 153 \| Thanked: 81 times \| Joined on Dec 2011 @ P town	#715

ITEM_DEVICE value should be in format:
ITEM_DEVICE="${INT_CARD}pX"
or
ITEM_DEVICE="${EXT_CARD}pX"

Quote & Reply |

The Following 2 Users Say Thank You to sLumPia For This Useful Post:
marmistrz, misiak

marmistrz	2013-07-09 , 17:17
Posts: 3,328 \| Thanked: 4,476 times \| Joined on May 2011 @ Poland	#716

Originally Posted by sLumPia

ITEM_DEVICE value should be in format:
ITEM_DEVICE="${INT_CARD}pX"
or
ITEM_DEVICE="${EXT_CARD}pX"

OK, my 21-Nemo.item looks like that:

Code:

ITEM_NAME="Nemo"
ITEM_KERNEL="uImage"
ITEM_DEVICE="${INT_CARD}p6"
ITEM_FSTYPE="vfat"
ITEM_CMDLINE="root=/dev/mmcblk0p5"

But still no custom entries (including kernel-power-bootimg) show up.

__________________
If you want to support my work, you can donate by PayPal or Flattr

Projects no longer actively developed: here

Last edited by marmistrz; 2013-07-09 at 19:02.

Quote & Reply |

pali	2013-07-09 , 18:18
Posts: 2,153 \| Thanked: 8,462 times \| Joined on May 2010	#717

Originally Posted by marmistrz

...now standard options (emmcboot, sdboot & etc.)...

This looks like your first eMMC partition (MyDocs) is not valid fat, ext2 or ext4. Some Windows and Linux systems using some fat extension which is not supported by u-boot, so then u-boot cannot read bootmenu file from MyDocs.
You need to (re)format MyDocs partition from Maemo (to be sure that you use correct format) to one support filesystem (fat, ext2 or ext4).

Quote & Reply |

The Following 2 Users Say Thank You to pali For This Useful Post:
marmistrz, nokiabot

marmistrz	2013-07-09 , 18:41
Posts: 3,328 \| Thanked: 4,476 times \| Joined on May 2011 @ Poland	#718

Originally Posted by pali

This looks like your first eMMC partition (MyDocs) is not valid fat, ext2 or ext4. Some Windows and Linux systems using some fat extension which is not supported by u-boot, so then u-boot cannot read bootmenu file from MyDocs.
You need to (re)format MyDocs partition from Maemo (to be sure that you use correct format) to one support filesystem (fat, ext2 or ext4).

I was using gparted to shrink the partition. But fsck-ing the partition gives no problem. Is gparted doing some strange stuff?

__________________
If you want to support my work, you can donate by PayPal or Flattr

Projects no longer actively developed: here

Quote & Reply |

pali	2013-07-09 , 18:45
Posts: 2,153 \| Thanked: 8,462 times \| Joined on May 2010	#719

Problem is that u-boot support only subset of fat fs supported by linux and windows. gparted using dosfstools for fat support. And I think it enabled (or used) some fat extension which is not supported by u-boot.

Quote & Reply |

The Following User Says Thank You to pali For This Useful Post:
marmistrz

marmistrz	2013-07-09 , 18:49
Posts: 3,328 \| Thanked: 4,476 times \| Joined on May 2011 @ Poland	#720

Originally Posted by pali

Problem is that u-boot support only subset of fat fs supported by linux and windows. gparted using dosfstools for fat support. And I think it enabled (or used) some fat extension which is not supported by u-boot.

Thanks.
and should I run u-boot-update-bootmenu as root or as user?

__________________
If you want to support my work, you can donate by PayPal or Flattr

Projects no longer actively developed: here