Re: New console output at boot?
- Reply: Thomas Laus : "Re: New console output at boot?"
- Reply: Warner Losh : "Re: New console output at boot?"
- In reply to: Thomas Laus : "Re: New console output at boot?"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Tue, 24 Sep 2024 17:55:40 UTC
On Tue, Sep 24, 2024, 11:47 AM Thomas Laus <lausts@acm.org> wrote: > On 9/24/24 11:04, Warner Losh wrote: > > On Sun, Sep 22, 2024 at 6:21 PM Kevin Oberman <rkoberman@gmail.com > > <mailto:rkoberman@gmail.com>> wrote: > > > > Since an update to current a couple of weeks ago, I now see several > > lines (6 or 7) early in the boot. I'm not sure whether it is from > > one of the boots or the loader, but it comes out so quickly (and so > > briefly) but it vanishes on my display before I can read it. I'm > > guessing that some part of the boot. I'm guessing it is a warning to > > update one or more of the files. > > > > I'm running main-n272093-705583b76f3f on an amd64 system with UEFI > > boot of a UFS2 file system. So far, I've seen nothing in UPDATING > > that references it. > > > > > > I'll have to look at UPDATING. > > > > tl;dr: It's telling you your loader.efi is too old and needs to be > > updated. Too old here is somewhat too strict (since > > it requires a version bump recently, not the actual commits that > > introduced the compat code that I'd like to remove). > > It's harmless, at the moment, but is warning of potential problems in > > the future, > > > I see this same issue when 'gptzfsboot' on a non UEFI system is booted > and before the startup menu is displayed and have for over a month. > I've updated my boot partition to: > > FreeBSD 15.0-CURRENT #13 1c6bb4c57 > Impossible. Gptzfsboot is an earlier phase than the new message. It can't produce a mismatch. Only loader/loader.efi vs /boot/lua/* can cause this. And usually in this setup both are updated as a pair. Warner Tom > > > > -- > Public Keys: > PGP KeyID = 0x5F22FDC1 > GnuPG KeyID = 0x620836CF > >