From nobody Sat Aug 03 14:28:30 2024 X-Original-To: freebsd-arm@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4WblRz0drKz5SWs9 for ; Sat, 03 Aug 2024 14:28:31 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (www.zefox.net [50.1.20.27]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "generic", Issuer "generic" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4WblRy22lYz4HX3 for ; Sat, 3 Aug 2024 14:28:30 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Authentication-Results: mx1.freebsd.org; none Received: from www.zefox.net (localhost [127.0.0.1]) by www.zefox.net (8.17.1/8.17.1) with ESMTPS id 473ESVXl063836 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Sat, 3 Aug 2024 07:28:31 -0700 (PDT) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.17.1/8.17.1/Submit) id 473ESVNT063835; Sat, 3 Aug 2024 07:28:31 -0700 (PDT) (envelope-from fbsd) Date: Sat, 3 Aug 2024 07:28:30 -0700 From: bob prohaska To: Mark Millard Cc: freebsd-arm@freebsd.org Subject: Re: BOOT LOADER IS TOO OLD. PLEASE UPGRADE. Message-ID: References: List-Id: Porting FreeBSD to ARM processors List-Archive: https://lists.freebsd.org/archives/freebsd-arm List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-arm@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:7065, ipnet:50.1.16.0/20, country:US] X-Rspamd-Queue-Id: 4WblRy22lYz4HX3 On Fri, Aug 02, 2024 at 11:08:36PM -0700, Mark Millard wrote: > > > On Aug 2, 2024, at 21:59, bob prohaska wrote: > > > On Fri, Aug 02, 2024 at 09:02:46PM -0700, Mark Millard wrote: > >> On Aug 2, 2024, at 19:19, bob prohaska 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