Reply
Thread Tools
Posts: 139 | Thanked: 97 times | Joined on Nov 2010 @ United States
#21
I've installed the tools and flasher packages, as well as the sample images + configs, and I don't see them in my boot menu. Instead I am offered to boot from Internal Flash, eMMC, SD, etc.

Here is the output of the u-boot-update-bootmenu script:

# u-boot-update-bootmenu
Adding bootmenu entry for: Maemo 5 (Internal Nand)

Configuration file: /etc/bootmenu.d/01-Maemo-kernel-power-2.6.28.10-power49.item
Generating u-boot image for kernel zImage-2.6.28.10-power49...
Adding bootmenu entry for: Maemo kernel-power 2.6.28.10-power49

Configuration file: /etc/bootmenu.d/10-Maemo5-2.6.28-omap1-fb.item
Generating u-boot image for kernel zImage-2.6.28-omap1-fb...
Adding bootmenu entry for: Maemo 5 with 2.6.28-omap1-fb

Configuration file: /etc/bootmenu.d/10-Maemo5-2.6.28-omap1.item
Generating u-boot image for kernel zImage-2.6.28-omap1...
Adding bootmenu entry for: Maemo 5 with 2.6.28-omap1

Configuration file: /etc/bootmenu.d/20-Maemo5-kernel-power-2.6.28.10-power49+pre50.item
Generating u-boot image for kernel zImage-2.6.28.10-power49+pre50...
Adding bootmenu entry for: Maemo 5 with kernel-power 2.6.28.10-power49+pre50

Configuration file: /etc/bootmenu.d/20-Maemo5-kernel-power-2.6.28.10-power49.item
Generating u-boot image for kernel zImage-2.6.28.10-power49...
Adding bootmenu entry for: Maemo 5 with kernel-power 2.6.28.10-power49

Configuration file: /etc/bootmenu.d/80-U-Boot-2011.12-1+zImage-2.6.28-omap1.item
Generating u-boot image for kernel u-boot-2011.12-1+zImage-2.6.28-omap1.bin...
Adding bootmenu entry for: U-Boot 2011.12-1 with zImage 2.6.28-omap1

Configuration file: /etc/bootmenu.d/80-U-Boot-2011.12-1.item
Generating u-boot image for kernel u-boot-2011.12-1.bin...
Adding bootmenu entry for: U-Boot 2011.12-1

Configuration file: /etc/bootmenu.d/backupmenu.item
cannot open /dev/null
another udev daemon already running
After the script has finished running, my screen backlight turns up, and starting a new X-Terminal window fails with message:

CAL ERROR: open(/dev/mtd1): No such file or directory
mesg: /dev/pts/1: No such file or directory
 
Posts: 2,153 | Thanked: 8,462 times | Joined on May 2010
#22
Originally Posted by flocke000 View Post
When I use your kernel images from the first post everything works fine, maybe I made a mistake before.

And would it be possible to use another dir for the config files?
Now if you have bootmenu installed along with u-boot you get the same menu items twice while booting.
And if you have the backupmenu entry in the dir the 'u-boot-update-bootmenu' command fails.
I have patches for fanoush bootmenu, which will ignore configs with kernels (fanoush bootmenu does not support booting kernels...)

Config file must have only variables with ITEM_ prefix. It is same in fanoush bootmenu.

Should I add some shell checking if config file has only variables? It will decreate bootmenu speed... But I think it is not needed...
 

The Following 3 Users Say Thank You to pali For This Useful Post:
Posts: 2,153 | Thanked: 8,462 times | Joined on May 2010
#23
Originally Posted by AndrewX192 View Post
I've installed the tools and flasher packages, as well as the sample images + configs, and I don't see them in my boot menu. Instead I am offered to boot from Internal Flash, eMMC, SD, etc.

Here is the output of the u-boot-update-bootmenu script:



After the script has finished running, my screen backlight turns up, and starting a new X-Terminal window fails with message:
WTF, what you are doing? Config file must have only ITEM_ variables assing as written in first post!!
 

The Following 3 Users Say Thank You to pali For This Useful Post:
flocke000's Avatar
Posts: 16 | Thanked: 13 times | Joined on May 2011 @ Magdeburg, Germany
#24
Yeah that's what happend on my device too.
Move the 'backupmenu.item' out of the /etc/bootmenu.d, run 'u-boot-update-bootmenu' and move it back.
 
Posts: 362 | Thanked: 426 times | Joined on Nov 2010 @ Italy, Lombardia
#25
Originally Posted by pali View Post
Try again, I updated u-boot-tools package
Unfortunately since some hours I have a N900 which no boot anymore (reboot loop) and I am trying to recover it without full reflash.

I have executed :
  • dpkg -i u-boot-tools (installed but not configured)
  • dpkg -i u-boot-flasher (install failed)
  • cd / && tar -xf /home/user/u-boot-images.tar.gz
  • u-boot-update-bootmenu
  • dpkg -i kernel-power-modules_2.6.28-10power49+pre50_armel.deb (which has removed power kernel v49 modules)
  • flashed manually new kernel
  • rebooted

Then phone has never completed boot process.

Tried many kernels but at some point it always reboots with all kernels (stock and power v50).
Tried RD mode and Kernel with FB but no results

Fortunately multiboot menu is still operative and I can launch backupmenu and its ssh shell, the problem is to find out what is the problem that causes reboot

Last edited by Fabry; 2012-01-15 at 23:38.
 

The Following User Says Thank You to Fabry For This Useful Post:
Estel's Avatar
Posts: 5,028 | Thanked: 8,613 times | Joined on Mar 2011
#26
Originally Posted by pali View Post
Should I add some shell checking if config file has only variables? It will decreate bootmenu speed... But I think it is not needed...
Absolutely agree with you. It;s already not noob-proof thing, so I think we can ommit things like this - everyone is responsible to check for typos/plain wrong content, before proceeding.

/Estel
__________________
N900's aluminum backcover / body replacement
-
N900's HDMI-Out
-
Camera cover MOD
-
Measure battery's real capacity on-device
-
TrueCrypt 7.1 | ereswap | bnf
-
Hardware's mods research is costly. To support my work, please consider donating. Thank You!
 
Posts: 139 | Thanked: 97 times | Joined on Nov 2010 @ United States
#27
Originally Posted by pali View Post
WTF, what you are doing? Config file must have only ITEM_ variables assing as written in first post!!
Thanks! I'm not sure how that backupmenu.item file got in there.

For future thread readers, be sure to move backupmenu.item out of /etc/bootmenu.d/ before running u-boot-update-bootmenu.
 

The Following 2 Users Say Thank You to AndrewX192 For This Useful Post:
Posts: 362 | Thanked: 426 times | Joined on Nov 2010 @ Italy, Lombardia
#28
Originally Posted by Fabry View Post
Unfortunately since some hours I have a N900 which no boot anymore (reboot loop) and I am trying to recover it without full reflash.

Then phone has never completed boot process.

Tried many kernels but at some point it always reboots with all kernels (stock and power v50).
Tried RD mode and Kernel with FB but no results

Fortunately multiboot menu is still operative and I can launch backupmenu and its ssh shell, the problem is to find out what is the problem that causes reboot
Ok some hours needed but now phone is alive again.

Stock kernel can't work anymore (reboot loop), probably because I have updated dsp libs with N9 version.

Kernel v49 did not work because modules directory was not present (as I known)
Kernel v50 did not work because multiboot had replaced it with v49 at each boot tried with manually flashed v50 kernel

Solution: Manually install modules directory for kernel v49
 

The Following User Says Thank You to Fabry For This Useful Post:
Posts: 1,225 | Thanked: 1,905 times | Joined on Feb 2011 @ Quezon City, Philippines
#29
Originally Posted by AndrewX192 View Post
I've installed the tools and flasher packages, as well as the sample images + configs, and I don't see them in my boot menu. Instead I am offered to boot from Internal Flash, eMMC, SD, etc.
I have this problem, but I don't have backupmenu item installed.
I updated to the newest tools and flasher, I don't get to see my menu.

How do I diagnose this? /home file system is ext4, if it's important.
__________________
N9 PR 1.3 Open Mode + kernel-plus for Harmattan
@kenweknot, working on Glacier for Nemo.
 
Posts: 2,153 | Thanked: 8,462 times | Joined on May 2010
#30
Originally Posted by Hurrian View Post
I have this problem, but I don't have backupmenu item installed.
I updated to the newest tools and flasher, I don't get to see my menu.

How do I diagnose this? /home file system is ext4, if it's important.
These U-Boot menu entries "Internal Nand", "Internal eMMC", "External SD card" are hardcoded into U-Boot binary and used if bootmenu script not exist (as fallback).

U-Boot bootmenu script is stored in MyDocs in file bootmenu.scr. U-Boot it load from first partition from internal mmc. So if you changed MyDocs partition number, U-Boot bootmenu will not work. Other partition on internal mmc (home, swap) has no effect for U-Boot.

Also you need to properly generate bootmenu.scr file. This file is generated by u-boot-update-bootmenu program. Do not forget to run it. Bootmenu entires is generated only if this program not failed - It must write someting like "generating bootmenu file..."
 

The Following 7 Users Say Thank You to pali For This Useful Post:
Reply

Tags
bootmenu, u-boot

Thread Tools

 
Forum Jump


All times are GMT. The time now is 20:45.