View Single Post
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