Re: FYI: FreeBSD-14.0-CURRENT-arm-armv7-GENERICSD-20220930-42dc8696df5-258315.img is broken for RPi2 v1.1 (so: armv7)g

On Tue, Oct 11, 2022 at 08:26:48AM -0700, Mark Millard wrote:
> On 2022-Oct-11, at 06:17, Warner Losh <imp@bsdimp.com> wrote:
> > 
> > On Mon, Oct 10, 2022 at 11:50 PM Mark Millard <marklmi@yahoo.com> wrote:
> > On 2022-Oct-10, at 21:08, Warner Losh <imp@bsdimp.com> wrote:
> > 
> > . . .
> > > And are you sure it's a booting issue and not a console issue?
> > 
> > No clue for your distinction. But, being serial console
> > based until ssh is possible for my context, I classify
> > serial-console-broken as a booting issue. (For example,
> > not being able to identify the DHCP address assigned
> > if it did make it that far.)
> > 
> > So it's not a booting issue (where the loader can't find the disk,
> > can't load the kernel or loads it such that it hangs), but a default
> > console issue. That's a lot easier for me to help solve.
>  
> I wrote separately later that I got a HDMI context set up and
> both the serial and HDMI consoles stopped, showing the same
> final text.
> 
> (I'm  not sure  that the final "-" lways shows up. But the HDMI
> and serial displays do seem to always agree about it.)
> 
> > . . .
> > 
> > The change was made in late August that I'm thinking of, so if you could find a
> > snapshot from early August July that would be a useful data point:

My Pi2B reporting 

FreeBSD www.zefox.com 14.0-CURRENT FreeBSD 14.0-CURRENT #12 main-2b766d5e5a: Mon Jul 11 01:38:59 PDT 2022     bob@www.zefox.com:/usr/obj/usr/src/arm.armv7/sys/GENERIC arm

is presently running buildworld on -current dated October 9th. If I'm 
understanding this thread correctly, running installworld will result
in an ubootable system. 

Should I refrain from running installworld for the time being?

Thanks for reading!

bob prohaska

> 
>