Red Hat Bugzilla – Bug 1021110
u-boot.imx does not start extlinux automatically
Last modified: 2013-10-22 01:39:54 EDT
Created attachment 813990 [details]
Add a default menu to u-boot, which executes the default 'bootcmd' command/script
Description of problem:
On my Wandboard DualLite the u-boot.imx version shows a menu and enters the commandline after a short timeout. It is needed to execute the 'boot' command to start extlinux which shows the selection of kernels installed.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. dd the u-boot.imx to the sd-card
# dd if=/usr/share/uboot-imx6dl/u-boot.imx of=/dev/mmcblk0 bs=512 seek=2
2. boot from the sd-card
U-boot enters the commandline and waits for user input.
U-boot starts extlinux, which boots the kernel after a timeout.
* I've tested the attached patch, and this works fine for me.
* The default bootcmd has been patched in the Fedora package, there is no
patch in upstream needed.
* This might be an issue on other boards as well, but I am not able to test
uboot-tools-2013.10-2.fc20 has been submitted as an update for Fedora 20.
Proposing as a blocker as i think it makes for a better user experience and violates the the following criteria,
Expected installed system boot behavior
A system installed without a graphical package set must boot to a working login prompt without any unintended user intervention, and all virtual consoles intended to provide a working login prompt must do so.
According to https://fedoraproject.org/wiki/Architectures/ARM/Supported_Platforms :
"Wandboard yes Quad works, dual and solo untested"
kinda doesn't gel with considering bugs in DualLite to be blockers?
Discussed this in 2013-10-21 Blocker Review Meeting . Rejected as a blocker issue as it does not appear to be serious enough to merit that status, but accepted as a freeze exception issue as it will improve the experience on wandboard systems and looks to be a safe fix
uboot-tools-2013.10-2.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.