From e55d6c26f37c7ce83a48c67105d136283795a856 Mon Sep 17 00:00:00 2001 From: "Jose M. Guisado" Date: Thu, 4 Feb 2021 13:41:53 +0000 Subject: #802 UEFI: Add boot entries to last boot order It's been reported that some UEFI implementations of several manufacturers do not comply with the standard and behave oddly. In this case it has been noted that when a BootEntry was created (with efibootmgr) but not added to the BootOrder this new entry did not survive a reboot. Thus, UEFI booting of a client from the ogLive menu was not possible. Adjust calling ogNvramAddEntry so that it adds the new entry to the BootOrder, but in last place so network boot, usually first option, remains in place. --- client/engine/Boot.lib | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'client/engine') diff --git a/client/engine/Boot.lib b/client/engine/Boot.lib index 383777d8..f60b9327 100755 --- a/client/engine/Boot.lib +++ b/client/engine/Boot.lib @@ -114,7 +114,7 @@ case "$TYPE" in fi # Crear orden de arranque (con unos valores por defecto). - ogNvramAddEntry $BOOTLABEL "/EFI/$BOOTLABEL/Boot/$BOOTLOADER" + ogNvramAddEntry $BOOTLABEL "/EFI/$BOOTLABEL/Boot/$BOOTLOADER" TRUE # Marcar próximo arranque y reiniciar. ogNvramSetNext "$BOOTLABEL" reboot @@ -139,7 +139,7 @@ case "$TYPE" in [ -n "$LOADER" ] || ogRaiseError $OG_ERR_NOTOS "$1 $2 ($TYPE, EFI)" || return $? # Crear orden de arranque (con unos valores por defecto). - ogNvramAddEntry $BOOTLABEL "/EFI${LOADER#*EFI}" + ogNvramAddEntry $BOOTLABEL "/EFI${LOADER#*EFI}" TRUE # Marcar próximo arranque y reiniciar. ogNvramSetNext "$BOOTLABEL" reboot -- cgit v1.2.3-18-g5258