You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Primarily this is an upstream bug - distro does not call efibootmgr properly to add boot entry.
It could be that distro tries to create boot entry with bootia64.efi and RDP-1430 with older UEFI / BIOS/ firmware only supports 32-bit EFI applications.
To create a boot entry using efibootmgr, we need:
Disk device with EFI partition
EFI partition number on disk - can be found automatically using bootutils scripts
Path to bootia32.efi (or bootia64.efi)
Script design:
Parameters:
Operation: add or remove
Disk device
If operation == 'add':
--32bit or --64bit - will choose .efi file
--efi_file=bootia32.efi or --efi_file=bootia64.efi (or anything else that exists)
If --efi_file is provided, --32bit and --64bit are IGNORED
If operation == 'delete':
Entry number
The text was updated successfully, but these errors were encountered:
Related to following issues:
Primarily this is an upstream bug - distro does not call efibootmgr properly to add boot entry.
It could be that distro tries to create boot entry with bootia64.efi and RDP-1430 with older UEFI / BIOS/ firmware only supports 32-bit EFI applications.
To create a boot entry using efibootmgr, we need:
Script design:
Parameters:
If --efi_file is provided, --32bit and --64bit are IGNORED
The text was updated successfully, but these errors were encountered: