Re: BOOT LOADER IS TOO OLD. PLEASE UPGRADE.

On Fri, Aug 2, 2024 at 10:28 PM Kyle Evans <[email protected]> wrote:

> On 8/2/24 22:08, Warner Losh wrote:
> >
> >
> > On Fri, Aug 2, 2024, 8:52 PM bob prohaska <[email protected]
> > <mailto:[email protected]>> 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.
> >
> >
> > 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 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