svn commit: r351831 - in head: . stand/efi/boot1 stand/efi/gptboot tools/build/mk

Rebecca Cran bcran at freebsd.org
Thu Sep 5 23:49:11 UTC 2019


On 2019-09-05 02:41, Niclas Zeising wrote:

> mount -t msdosfs /dev/ada0p1 /mnt # (if that's the ESP, check with gpart
> list)
> cp /boot/loader.efi /mnt/EFI/FreeBSD/loader.efi
> umount /mnt
> 
> This works if proper EFI boot variables have been set up.  This can be
> done with, it's only needed the first time, or if they are somehow
> overwritten.
> 
> efibootmgr --create --activate --label FreeBSD --loader
> /dev/ada0p1:/EFI/FreeBSD/loader.efi
> 
> Once again, check that /dev/ada0p1 is the ESP.
> You can check your efi boot variables with efibootmgr -v

Or, if you prefer not to rely on EFI boot variables (for example, Linux
GRUB EFI updates seem to reset them, deleting the FreeBSD entries), you
can also copy loader.efi into /mnt/EFI/BOOT/BOOTx64.efi (replace
BOOTx64.efi with BOOTarm.efi for ARM, and BOOTaa64.efi for AARCH64).

EFI\BOOT\BOOTx64.efi is the default place where UEFI system firmware
looks to run a bootloader from, given no EFI boot variables. I think
it's only supposed to be for removable media, but I've not come across
any that differentiate between fixed and removable.

-- 
Rebecca Cran

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <http://lists.freebsd.org/pipermail/svn-src-head/attachments/20190905/058f7437/attachment.sig>


More information about the svn-src-head mailing list