Coreboot device (EFI): Upgrade to 24.03-RC fails efibootmgr: efi_get_variable: Bad address

mfld

>>> Removing unnecessary packages...done.

>>> Cleanup pkg cache...done.

>>> Deferring package installation scripts...done.

>>> Upgrading boot code...

System Configuration

Architecture: amd64

Boot Devices: /dev/ada0

              /dev/nda0

 Boot Method: uefi

  Filesystem: zfs

    Platform: unknown hardware

Updating boot code...

/usr/local/sbin/../libexec/install-boot.sh -b auto -d /tmp/be_mount.Sv7x -f zfs -s gpt -u nda0

gpart bootcode -b /tmp/be_mount.Sv7x/boot/pmbr -p /tmp/be_mount.Sv7x/boot/gptzfsboot -i 2 nda0

partcode written to nda0p2

bootcode written to nda0

fstyp: /dev/nda0p1: filesystem not recognized

ESP /dev/nda0p1 mounted on /tmp/stand-test.h3r0xp

Copying loader.efi to /EFI/freebsd on ESP

efibootmgr: efi_get_variable: Bad address

Creating UEFI boot entry for FreeBSD

efibootmgr: efi_get_variable: Bad address

Failed to create new boot entry

Unable to update boot code on /dev/nda0

>>> Unlocking package pkg...done.

Failed

stephenw10

What hardware is that?

There is a fix incoming though that should apply to this too: https://redmine.pfsense.org/issues/15395

mfld

@stephenw10 said in Coreboot device (EFI): Upgrade to 24.03-RC fails efibootmgr: efi_get_variable: Bad address:

What hardware is that?

There is a fix incoming though that should apply to this too: https://redmine.pfsense.org/issues/15395

Some flavor of Protectli with Coreboot and a paid TAC lite.

I just retried with the April 16 release 24.03.r.20240416.0005 and it works now! The "bad address" error is still printed in the log but it seems to ignore it and YOLO a reboot successfully.

System Configuration

Architecture: amd64
Boot Devices: /dev/ada0
              /dev/nda0
 Boot Method: uefi
  Filesystem: zfs
    Platform: unknown hardware


Updating boot code...

/usr/local/sbin/../libexec/install-boot.sh -b auto -d /tmp/be_mount.JapV -f zfs -s gpt -u nda0
gpart bootcode -b /tmp/be_mount.JapV/boot/pmbr -p /tmp/be_mount.JapV/boot/gptzfsboot -i 2 nda0
partcode written to nda0p2
bootcode written to nda0
ESP /dev/nda0p1 mounted on /tmp/stand-test.DVxRMK
260839KB space remaining on ESP: renaming old loader.efi file /etc/freebsd/loader.efi /etc/freebsd/loader-old.efi
Copying loader.efi to /EFI/freebsd on ESP
efibootmgr: efi_get_variable: Bad address
Copying bootx64.efi to /efi/boot on ESP
Unmounting and cleaning up temporary mount point
Finished updating ESP

/usr/local/sbin/../libexec/install-boot.sh -b auto -d /tmp/be_mount.JapV -f zfs -s gpt -u ada0
gpart bootcode -b /tmp/be_mount.JapV/boot/pmbr -p /tmp/be_mount.JapV/boot/gptzfsboot -i 2 ada0
partcode written to ada0p2
bootcode written to ada0
ESP /dev/ada0p1 mounted on /tmp/stand-test.dZRnnE
264784KB space remaining on ESP: renaming old bootx64.efi file /efi/boot/bootx64.efi /efi/boot/bootx64-old.efi
264784KB space remaining on ESP: renaming old loader.efi file /etc/freebsd/loader.efi /etc/freebsd/loader-old.efi
Copying loader.efi to /EFI/freebsd on ESP
efibootmgr: efi_get_variable: Bad address
Copying bootx64.efi to /efi/boot on ESP
Unmounting and cleaning up temporary mount point
Finished updating ESP

Done.
>>> Copying upgrade log...done.
>>> Unmounting upgraded boot environment...done.
>>> Activating default for the next boot only...done.
System is going to be upgraded.  Rebooting in 10 seconds.
>>> Unlocking package pkg...done.
Success

stephenw10

Ah great. Yes it was exiting out of the entire upgrade process on any error at that point before. It doesn't actually need to create a new uefi boot entry there so should be fine.
Interesting that Coreboot doesn't play nice with efibootmgr though.