Date: Sat, 7 Sep 2024 08:20:07 -0700 From: Mark Millard <marklmi@yahoo.com> To: void <void@f-m.fm>, Current FreeBSD <freebsd-current@freebsd.org> Subject: Re: Loader needs to be updated message Message-ID: <9494862A-E445-43AC-8887-FACC84A74435@yahoo.com> References: <9494862A-E445-43AC-8887-FACC84A74435.ref@yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
void <void_at_f-m.fm> wrote on Date: Sat, 07 Sep 2024 13:19:24 UTC : > hello again, >=20 > 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 >=20 > I have the same issue in a completely different context: >=20 > 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 >=20 > 5. on the guest :- % gpart list | grep -Ew '(Name|efi)' > 1. Name: vtbd0p1 > 2. Name: vtbd0p2 > 3. Name: vtbd0p3 > 1. Name: vtbd0 >=20 > on the guest, there is no ESP in this case, no bootx64.efi, /boot/efi = is empty I'm more interested in what is there than just what is not there. May be show something analogous to: # gpart list | grep -E '(Name|type|efi|media)' 1. Name: mmcsd1s1 efimedia: HD(1,MBR,00000000,0x8000,0x3b68000) rawtype: 12 type: fat32lba 1. Name: mmcsd1 1. Name: da0p1 efimedia: HD(1,GPT,81f199f2-5eb9-11ec-b507-a0cec8d68fdc,0x28,0x82000) rawtype: c12a7328-f81f-11d2-ba4b-00a0c93ec93b label: BPIM3efi type: efi 2. Name: da0p2 efimedia: = HD(2,GPT,efa6f52d-c8ca-11ec-bb1e-03fc0558c84f,0x82800,0x366000) rawtype: 516e7cb5-6ecf-11d6-8ff8-00022d09712b type: freebsd-swap 3. Name: da0p3 efimedia: = HD(3,GPT,71abc138-db5e-11ee-bfe1-e352d1095e3c,0x6861c800,0x732800) rawtype: 516e7cb5-6ecf-11d6-8ff8-00022d09712b type: freebsd-swap 4. Name: da0p4 efimedia: = HD(4,GPT,b568945a-5eba-11ec-b507-a0cec8d68fdc,0xa1c800,0x67c00000) rawtype: 516e7cb6-6ecf-11d6-8ff8-00022d09712b type: freebsd-ufs 1. Name: da0 I'll note that on various type of systems, the (effectively) ESP need not be specifically of "type: efi", possibly some fat variant instead also works. (Of course, EFI need not be the only alternative for various type of contexts.) I'll note the /boot/efi is normally just an empty directory that is possibly used as a mount point. In some (somewhat older) configurations /boot/msdos is similarly an empty directory and possibly used as the mount point instead. > After source building to latest stable in the usual way, same error = message 'loader needs updating'. =3D=3D=3D Mark Millard marklmi at yahoo.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?9494862A-E445-43AC-8887-FACC84A74435>