When booting fails we will be immediately be back into the menu, so the error message can't be seen. Also, boot in verbose mode since in interactive mode the last bit of performance is not that necessary. Signed-off-by: Sascha Hauer <s.hauer@xxxxxxxxxxxxxx> --- defaultenv-2/menu/menu/boot-menu-add-entry | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/defaultenv-2/menu/menu/boot-menu-add-entry b/defaultenv-2/menu/menu/boot-menu-add-entry index 7e1d9c6..f06c524 100644 --- a/defaultenv-2/menu/menu/boot-menu-add-entry +++ b/defaultenv-2/menu/menu/boot-menu-add-entry @@ -1,5 +1,5 @@ #!/bin/sh -menu -e -a -m boot -c "boot $1" -d "Boot: ${GREEN}$2${NC}" +menu -e -a -m boot -c "boot -v $1; echo; readline \"press enter to continue\" a " -d "Boot: ${GREEN}$2${NC}" menu -e -a -m boot_entries_edit -c "$global.editcmd /env/boot/$1" -d "${GREEN}$2${NC}" menu -e -a -m boot_entries_remove -c "rm /env/boot/$1" -d "${GREEN}$2${NC}" -- 1.7.10.4 _______________________________________________ barebox mailing list barebox@xxxxxxxxxxxxxxxxxxx http://lists.infradead.org/mailman/listinfo/barebox