Re: BOOT LOADER IS TOO OLD. PLEASE UPGRADE.

On Fri, Aug 02, 2024 at 11:08:36PM -0700, Mark Millard wrote:
> 
> 
> On Aug 2, 2024, at 21:59, bob prohaska <fbsd@www.zefox.net> wrote:
> 
> > On Fri, Aug 02, 2024 at 09:02:46PM -0700, Mark Millard wrote:
> >> On Aug 2, 2024, at 19:19, bob prohaska <fbsd@www.zefox.net> wrote:
> >> 
> >>> After a build/install of -current on a Raspberry Pi 2 (so, armv7) the 
> >>> console output reported:
> >>> 
> >>> **********************************************************************
> >>> **********************************************************************
> >>> *****                                                            *****
> >>> *****           BOOT LOADER IS TOO OLD. PLEASE UPGRADE.          *****
> >>> *****                                                            *****
> >>> **********************************************************************
> >>> **********************************************************************
> >>> 
> >>> The statement is likely true, but it's a bit hard to guess exactly
> >>> what needs upgrading. The boot process succeeded. Is it wiser to
> >>> heed the command, or leave well enough alone? AFAIK there's no
> >>> firmware to upgrade on the Pi2.
> >> 
> >> The message is about the likes of:
> >> 
> >> RPi2 v1.1 (armv7)?   /boot/efi/EFI/BOOT/bootarm.efi
> >> RPi2 v1.2 (aarch64)? /boot/efi/EFI/BOOT/bootaa64.efi
> >> 
> >> Those are not RPi* firmware, nor armstub* , nor are they U-Boot.
> >> 
> >> They are code from FreeBSD: FreeBSD UEFI loader code. So, yes,
> >> there is new code to update to.
> >> 
> > Where can I find the newer version?  Following buildworld/kernel
> > find / -name bootarm.efi
> > locates only
> > /boot/msdos/EFI/BOOT/bootarm.efi
> > which I imagine is the obsolete version. 
> > 
> > Apologies if this is naive, something suggests it might be....
> 
> Presuming a self-hosted build was done and was installed to
> update that system, the updates could be done via:
> 
> 
> On armv7 (RPi2 v1.1 --or RPi2 v1.2 used with an armv7 kernel/world):
> 
> # cp /boot/loader.efi /boot/efi/EFI/BOOT/bootarm.efi

In this case the path turns out to be 
/boot/msdos/EFI/BOOT/bootarm.efi but the fix was otherwise trivial.
It was surprising to find the old file dated Jul 2 2020, I didn't
realize the machine has been up that long.

> 
> In other words, they are copies of the FreeBSD boot loader
> but under other path and naming conventions on the msdosfs
> that is involved.
>
 
Is there some reason installworld (or some other make target) doesn't
do this by default? The msdos filesystem is mounted and writeable any 
time the host is running.

Thank you very much!

bob prohaska