On Sat, 12 Jan 2019 at 07:55, Stefan Bethke <stb at lassitu.de> wrote: [...]> The UEFI man page has a good explanation of which files are involved in booting: > https://www.freebsd.org/cgi/man.cgi?query=uefi&sektion=8&manpath=freebsd-release-ports > > I mounted the ESP and copied /boot/boot1.efi to /boot/efi/EFI/BOOT/BOOTX64.EFI. Surprisingly, the new boot1.efi is much smaller than what I had before (according to the timestamp from November), but using that, booting seems to be restored. > > # grep efi /etc/fstab > /dev/ada0p2 /boot/efi msdos rw,noauto 0 0 > # mount /boot/efi > # ls -l /boot/efi/EFI/BOOT/BOOTX64.EFI /boot/efi/EFI/BOOT/bak/BOOTX64.EFI > -rwxr-xr-x 1 root wheel 81920 Jan 11 18:43 /boot/efi/EFI/BOOT/BOOTX64.EFI* > -rwxr-xr-x 1 root wheel 410112 Nov 25 16:27 /boot/efi/EFI/BOOT/bak/BOOTX64.EFI*While the uefi(8) man page suggests that boot1.efi should be used, loader.efi can also substituted. I believe the release images use loader.efi instead of boot1.efi, as it's slightly more efficient. Cheers. -- Jonathan Chen <jonc at chen.org.nz>
On Fri, Jan 11, 2019 at 1:15 PM Jonathan Chen <jonc at chen.org.nz> wrote:> > On Sat, 12 Jan 2019 at 07:55, Stefan Bethke <stb at lassitu.de> wrote: > [...] > > The UEFI man page has a good explanation of which files are involved in booting: > > https://www.freebsd.org/cgi/man.cgi?query=uefi&sektion=8&manpath=freebsd-release-ports > > > > I mounted the ESP and copied /boot/boot1.efi to /boot/efi/EFI/BOOT/BOOTX64.EFI. Surprisingly, the new boot1.efi is much smaller than what I had before (according to the timestamp from November), but using that, booting seems to be restored. > > > > # grep efi /etc/fstab > > /dev/ada0p2 /boot/efi msdos rw,noauto 0 0 > > # mount /boot/efi > > # ls -l /boot/efi/EFI/BOOT/BOOTX64.EFI /boot/efi/EFI/BOOT/bak/BOOTX64.EFI > > -rwxr-xr-x 1 root wheel 81920 Jan 11 18:43 /boot/efi/EFI/BOOT/BOOTX64.EFI* > > -rwxr-xr-x 1 root wheel 410112 Nov 25 16:27 /boot/efi/EFI/BOOT/bak/BOOTX64.EFI* > > While the uefi(8) man page suggests that boot1.efi should be used, > loader.efi can also substituted. I believe the release images use > loader.efi instead of boot1.efi, as it's slightly more efficient. >Indeed, boot1.efi is a hack that's going to get kicked out of the tree in due time.
On Fri, Jan 11, 2019 at 12:17 PM Jonathan Chen <jonc at chen.org.nz> wrote:> On Sat, 12 Jan 2019 at 07:55, Stefan Bethke <stb at lassitu.de> wrote: > [...] > > The UEFI man page has a good explanation of which files are involved in > booting: > > > https://www.freebsd.org/cgi/man.cgi?query=uefi&sektion=8&manpath=freebsd-release-ports > > > > I mounted the ESP and copied /boot/boot1.efi to > /boot/efi/EFI/BOOT/BOOTX64.EFI. Surprisingly, the new boot1.efi is much > smaller than what I had before (according to the timestamp from November), > but using that, booting seems to be restored. > > > > # grep efi /etc/fstab > > /dev/ada0p2 /boot/efi msdos rw,noauto 0 0 > > # mount /boot/efi > > # ls -l /boot/efi/EFI/BOOT/BOOTX64.EFI /boot/efi/EFI/BOOT/bak/BOOTX64.EFI > > -rwxr-xr-x 1 root wheel 81920 Jan 11 18:43 > /boot/efi/EFI/BOOT/BOOTX64.EFI* > > -rwxr-xr-x 1 root wheel 410112 Nov 25 16:27 > /boot/efi/EFI/BOOT/bak/BOOTX64.EFI* > > While the uefi(8) man page suggests that boot1.efi should be used, > loader.efi can also substituted. I believe the release images use > loader.efi instead of boot1.efi, as it's slightly more efficient. >We should change that... boot1.efi has transitioned to 'legacy applications only' and we should recommend loader.efi only. Warner