Re: RPI4 panic on boot with -current

On Fri, Apr 08, 2022 at 07:46:57PM -0700, Mark Millard wrote:
> On 2022-Apr-8, at 18:53, bob prohaska <fbsd@www.zefox.net> wrote:
> 
> > Might this be related to "RPi4B's got a PMIC replacement,..." reported 4/3 ?
> 
> No: See the later note about the RPi4B Revision.
> 
> > A Pi4 (mechanical disk only, no microsd) trying to boot a fresh build of 
> > -current reports:
> > 
> > Resetting system ... 
> > 
> > U-Boot 2020.10 (Mar 04 2021 - 04:32:31 +0000)
> 
> This is an old U-Boot compared to sysutils/u-boot-* .
> There may well be good reasons for using it, for all
> I know.
> 

Only the most universal reasons: Inertia and ignorance 8-)

There are many versions of u-boot for rpi boards, some of 
which are rather ambiguously named; u-boot-rpi-arm64 versus
u-boot-rp4 is a good example. It appears the pkg-descr files
have been updated since I last looked, but the descriptions
overlap and it's not obvious how to choose among them. Man
pages seem passe, is there some other guidance? 

Even if one knows which to select and build from ports the
make install command doesn't really install; the admin still
has to know what files to copy where. Your instructions for 
the task have been noted and saved, but even then it's very
easy to make mistakes that are hard to recover from.

Does pkg handle u-boot and firmware updates more automatically?
Alternatively, is it feasible to update u-boot and firmware with
an "installboot" target, either from the port directory or /usr/src?

Thanks for reading, and all your help!

bob prohaska

[big snip]