Date: Fri, 2 Aug 2024 22:34:08 -0600 From: Warner Losh <imp@bsdimp.com> To: Kyle Evans <kevans@freebsd.org> Cc: freebsd-arm@freebsd.org Subject: Re: BOOT LOADER IS TOO OLD. PLEASE UPGRADE. Message-ID: <CANCZdfoffX7iNyRY=TpUCyuy9K4AkvP4QSJJpvxUaKOND0BvZQ@mail.gmail.com> In-Reply-To: <7d7b0e67-0426-49e3-88ee-8a7e89883342@FreeBSD.org> References: <Zq2Tn6XycReuifF6@www.zefox.net> <CANCZdfp8yQ_yUS-vPwSbFNJQVDq5N8fXx_HWiTEodRDvmYqd5Q@mail.gmail.com> <7d7b0e67-0426-49e3-88ee-8a7e89883342@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--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 <kevans@freebsd.org> wro= te: > On 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:fbsd@www.zefox.net>> 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 <div dir=3D"ltr"><div dir=3D"ltr"><br></div><br><div class=3D"gmail_quote">= <div dir=3D"ltr" class=3D"gmail_attr">On Fri, Aug 2, 2024 at 10:28=E2=80=AF= PM Kyle Evans <<a href=3D"mailto:kevans@freebsd.org">kevans@freebsd.org<= /a>> wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0= px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">O= n 8/2/24 22:08, Warner Losh wrote:<br> > <br> > <br> > On Fri, Aug 2, 2024, 8:52=E2=80=AFPM bob prohaska <<a href=3D"mailt= o:fbsd@www.zefox.net" target=3D"_blank">fbsd@www.zefox.net</a> <br> > <mailto:<a href=3D"mailto:fbsd@www.zefox.net" target=3D"_blank">fbs= d@www.zefox.net</a>>> wrote:<br> > <br> >=C2=A0 =C2=A0 =C2=A0After a build/install of -current on a Raspberry Pi= 2 (so, armv7) the<br> >=C2=A0 =C2=A0 =C2=A0console output reported:<br> > <br> >=C2=A0 =C2=A0 =C2=A0***************************************************= *******************<br> >=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 *****<br> >=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 *****<br> >=C2=A0 =C2=A0 =C2=A0***************************************************= *******************<br> >=C2=A0 =C2=A0 =C2=A0***************************************************= *******************<br> > <br> >=C2=A0 =C2=A0 =C2=A0The statement is likely true, but it's a bit ha= rd to guess exactly<br> >=C2=A0 =C2=A0 =C2=A0what needs upgrading. The boot process succeeded. I= s it wiser to<br> >=C2=A0 =C2=A0 =C2=A0heed the command, or leave well enough alone? AFAIK= there's no<br> >=C2=A0 =C2=A0 =C2=A0firmware to upgrade on the Pi2.<br> > <br> > <br> > loader.efi in the ESP in this case. In almost every case, really, but = we <br> > can't tell in lua AFAICT what is out of date without some more lua= <br> > bindings..<br> > <br> <br> I'm enjoying the irony in that we can fix this, but you'd have a lo= ader <br> too old to be able to tell you which loader binary is too old.<br></blockqu= ote><div><br></div><div>It's not lost on me...</div><div><br></div><div= >I could say 'loader' vs 'loader.efi'=C2=A0 but not the pat= h to the boot loader</div><div>which isn't completely helpful.</div><di= v><br></div><div>We set boot and loader env vars based on where we came fro= m, but</div><div>they are EFI variables, which we don't have lua bindin= gs too in the</div><div>old loader. There's a command to examine variab= les, but not something</div><div>we can leverage that I can see..</div><div= ><br></div><div>Warner <br></div></div></div> --0000000000000f4a0e061ebff548--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CANCZdfoffX7iNyRY=TpUCyuy9K4AkvP4QSJJpvxUaKOND0BvZQ>