Re: Loader needs to be updated message

From: void <void_at_f-m.fm>
Date: Sat, 07 Sep 2024 13:19:24 UTC
hello again,

On Fri, Sep 06, 2024 at 03:13:59PM -0700, Mark Millard wrote:
>
>What shows if you do the likes of (showing an amd64 context example):
>
># ls -lah /boot/efi/efi/*/*
>-r-xr-xr-x  1 root wheel  643K Aug 24 05:32 /boot/efi/efi/BOOT/bootx64.efi
>-rwxr-xr-x  1 root wheel  643K Aug 24 05:32 /boot/efi/efi/FREEBSD/loader.efi
>
>If one is old, then it is probably the one actually being used.
>(The name bootx64.efi is amd64 specific: other platforms use
>other names.)
>
>In such a case, you might need something like:
>
># cp -a /boot/loader.efi /boot/efi/efi/BOOT/bootx64.efi

I have the same issue in a completely different context:

1. amd64 not arm64
2. a vm running in bhyve, not baremetal
3. the host is 15.0-CURRENT #0 n270917-5dbf886104b4 amd64 1500019 1500019 zfs-on-root
    built July 4th.
4. the guest is 13.4-STABLE stable/13-n258323-e7b4f6e0c064 amd64 1304500 1304500 zfs-on-root

5. on the guest :- % gpart list | grep -Ew '(Name|efi)'
                    1. Name: vtbd0p1
                    2. Name: vtbd0p2
                    3. Name: vtbd0p3
                    1. Name: vtbd0

on the guest, there is no ESP in this case, no bootx64.efi, /boot/efi is empty

After source building to latest stable in the usual way, same error message 'loader needs updating'.

Any ideas?
--