From nobody Sat Aug 03 04:34:08 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 4WbVGP3TWrz5RwLC for ; Sat, 03 Aug 2024 04:34:21 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-pf1-x42c.google.com (mail-pf1-x42c.google.com [IPv6:2607:f8b0:4864:20::42c]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "WR4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4WbVGN73K6z4Qdh for ; Sat, 3 Aug 2024 04:34:20 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-pf1-x42c.google.com with SMTP id d2e1a72fcca58-70d1fb6c108so6502841b3a.3 for ; Fri, 02 Aug 2024 21:34:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20230601.gappssmtp.com; s=20230601; t=1722659659; x=1723264459; darn=freebsd.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=toFfuSfYhBz7sxV2oZwkHB3gySVbozDl6Y4GbAekNbQ=; b=M82AC529Auk7XZ8NoK02q7g7Tnebp71g3M1wpNJxi/YuA8a9DczpkVp/7Zt/N1fUtL liZ6nsu/id0Suv9ahH4QWO/GNPiIn1WxBlrBZOlANH+/zGPlVy4tN7wTh/WmWaZ4udyF GaK1Fr3Nee5zdDhVq/WVwSZELBkXxEvPR+uZ/bzqTgMIsOui0fxypb6drM3NCJziw1Xk h/jh8Ir3ntMvlmN6uaINi+F0Qgr06eF857gDbyn/ZROks0D/ARY8Mq663i0RBz8xm+t8 eDJTQO6bOS7LAjhnDV62ixRR93otfGs1zvvdvV0PPX5uD8Z/xbQDIjuiEgRFs9Dnfx7G iRbQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1722659659; x=1723264459; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=toFfuSfYhBz7sxV2oZwkHB3gySVbozDl6Y4GbAekNbQ=; b=AWN5isTsfGoyH6nTNRlHP/Vsxg3Upp5Qt5xYt0R6HgwfPA+ibU1w8k4UHu6QgKxkEQ EtXDDyTe3k2Hgtqf0Yl/0AxACvrkri0emS+QuJW0TFCot1E7VOhR4ZIY6sSAadVFyaVW XxwGQYGvOKu0xKS0NEWC0wpBpmwwpGJpc0UNdTdy4XthPhGUdVwrGwpyRivt0LCqMgaF 3EP1ivO/+98+DEKIOsX4+/cwSUfYjfpq0b7PV0DRqxrCpNVC7ybTLtzmatmEPU09tpyt NmlAT+0m76KXFUreHVEoBZc2hs/8O+wZXHefoQFApHi4zmP2DXDCl8pAWW2v8EmrK97q paBA== X-Gm-Message-State: AOJu0YzyaGkx7nh43rc2Bzh7b/5uZVriveBnKd0+3kxO0LKOu2ASi3Oo ceFw/5stj1Nz1xVhwzh7nj30N4nAHhq7Nzs/Yn0XegvypygABIaoolPTmg2eiM937LxiuJQ6NMF YquyEBjGCatMcSKZBcpLewVKkMep7d/3UTI1dDw== X-Google-Smtp-Source: AGHT+IHeQFf2JCNGp2b2vkTU0deq/EsRC3ynULBLpxGvBzKchJiAPyy20PmZ92rmMCECPEFkyWEG9Pnud7MahF6Hkz8= X-Received: by 2002:a05:6a21:609:b0:1c6:ac08:8dd2 with SMTP id adf61e73a8af0-1c6ac088f1emr1100511637.15.1722659659263; Fri, 02 Aug 2024 21:34:19 -0700 (PDT) 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 References: <7d7b0e67-0426-49e3-88ee-8a7e89883342@FreeBSD.org> In-Reply-To: <7d7b0e67-0426-49e3-88ee-8a7e89883342@FreeBSD.org> From: Warner Losh Date: Fri, 2 Aug 2024 22:34:08 -0600 Message-ID: Subject: Re: BOOT LOADER IS TOO OLD. PLEASE UPGRADE. To: Kyle Evans Cc: freebsd-arm@freebsd.org Content-Type: multipart/alternative; boundary="0000000000000f4a0e061ebff548" 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:15169, ipnet:2607:f8b0::/32, country:US] X-Rspamd-Queue-Id: 4WbVGN73K6z4Qdh --0000000000000f4a0e061ebff548 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Fri, Aug 2, 2024 at 10:28=E2=80=AFPM Kyle Evans wro= te: > On 8/2/24 22:08, Warner Losh wrote: > > > > > > On Fri, Aug 2, 2024, 8:52=E2=80=AFPM bob prohaska > > wrote: > > > > After a build/install of -current on a Raspberry Pi 2 (so, armv7) t= he > > 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. > > > > > > loader.efi in the ESP in this case. In almost every case, really, but w= e > > can't tell in lua AFAICT what is out of date without some more lua > > bindings.. > > > > I'm enjoying the irony in that we can fix this, but you'd have a loader > too old to be able to tell you which loader binary is too old. > It's not lost on me... I could say 'loader' vs 'loader.efi' but not the path to the boot loader which isn't completely helpful. We set boot and loader env vars based on where we came from, but they are EFI variables, which we don't have lua bindings too in the old loader. There's a command to examine variables, but not something we can leverage that I can see.. Warner --0000000000000f4a0e061ebff548 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


=
On Fri, Aug 2, 2024 at 10:28=E2=80=AF= PM Kyle Evans <kevans@freebsd.org<= /a>> wrote:
O= n 8/2/24 22:08, Warner Losh wrote:
>
>
> On Fri, Aug 2, 2024, 8:52=E2=80=AFPM bob prohaska <fbsd@www.zefox.net
> <mailto:fbs= d@www.zefox.net>> wrote:
>
>=C2=A0 =C2=A0 =C2=A0After a build/install of -current on a Raspberry Pi= 2 (so, armv7) the
>=C2=A0 =C2=A0 =C2=A0console output reported:
>
>=C2=A0 =C2=A0 =C2=A0***************************************************= *******************
>=C2=A0 =C2=A0 =C2=A0***************************************************= *******************
>=C2=A0 =C2=A0 =C2=A0*****=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 *****
>=C2=A0 =C2=A0 =C2=A0*****=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0BOOT = LOADER IS TOO OLD. PLEASE UPGRADE.=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 *****<= br> >=C2=A0 =C2=A0 =C2=A0*****=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 *****
>=C2=A0 =C2=A0 =C2=A0***************************************************= *******************
>=C2=A0 =C2=A0 =C2=A0***************************************************= *******************
>
>=C2=A0 =C2=A0 =C2=A0The statement is likely true, but it's a bit ha= rd to guess exactly
>=C2=A0 =C2=A0 =C2=A0what needs upgrading. The boot process succeeded. I= s it wiser to
>=C2=A0 =C2=A0 =C2=A0heed the command, or leave well enough alone? AFAIK= there's no
>=C2=A0 =C2=A0 =C2=A0firmware to upgrade on the Pi2.
>
>
> loader.efi in the ESP in this case. In almost every case, really, but = we
> can't tell in lua AFAICT what is out of date without some more lua=
> bindings..
>

I'm enjoying the irony in that we can fix this, but you'd have a lo= ader
too old to be able to tell you which loader binary is too old.

It's not lost on me...

I could say 'loader' vs 'loader.efi'=C2=A0 but not the pat= h to the boot loader
which isn't completely helpful.

We set boot and loader env vars based on where we came fro= m, but
they are EFI variables, which we don't have lua bindin= gs too in the
old loader. There's a command to examine variab= les, but not something
we can leverage that I can see..

Warner
--0000000000000f4a0e061ebff548--