Date: Mon, 10 Oct 2022 22:08:47 -0600 From: Warner Losh <imp@bsdimp.com> To: Mark Millard <marklmi@yahoo.com> Cc: freebsd-arm <freebsd-arm@freebsd.org>, bob prohaska <fbsd@www.zefox.net> Subject: Re: FYI: FreeBSD-14.0-CURRENT-arm-armv7-GENERICSD-20220930-42dc8696df5-258315.img is broken for RPi2 v1.1 (so: armv7) Message-ID: <CANCZdfoJ=E=ef86PRaYsvgXWLAu=AdbN%2B_kiv0vPhKVksqPY%2Bg@mail.gmail.com> In-Reply-To: <D9B791B7-106A-402E-AD8C-F811EB315560@yahoo.com> References: <6B46F46A-2CAF-42C9-9A04-63567D7DB9B2@yahoo.com> <D9B791B7-106A-402E-AD8C-F811EB315560@yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--0000000000008feced05eaba6f70 Content-Type: text/plain; charset="UTF-8" On Mon, Oct 10, 2022, 10:00 PM Mark Millard <marklmi@yahoo.com> wrote: > [Summary: it looks to be FreeBSD main's EFI loader that is > at issue for armv7 RPi2B v1.1 booting not working.] > > On 2022-Oct-10, at 20:04, Mark Millard <marklmi@yahoo.com> wrote: > > > I put: > > > > FreeBSD-14.0-CURRENT-arm-armv7-GENERICSD-20220930-42dc8696df5-258315.img > > > > on a microsd card via dd and tried to boot a RPi2 v1.1. it > > hung up after: > > > > Using DTB provided by EFI at 0x7ef6000. > > Kernel entry at 0x36a00200... > > Kernel args: (null) > > > > (A "-" might show in the next line.) > > > > So I tried: > > > > FreeBSD-13.1-STABLE-arm-armv7-GENERICSD-20221007-d497b97e902-252653.img > > > > on the microsd card instead. It worked just fine. (Thus the > > RPi2B v1.1 is not broken.) > > > > I did this experiment because recent testing for other > > reasons of somewhat older main vintages that I'd built > > also showed such failures. This test shows official > > builds also have the problem. > > > > I've no clue how long this issue has been around. It > > been a very long time since the RPi2B v1.1 had been > > powered on. > > > > > > Note: The arm-armv7-GENERICSD images include the RPi2B > > v1.1 related RPi* firmware and u-boot, in addition to > > an installed FreeBSD EFI loader and a kernel and a > > world. Historically it was supposed to just work for > > RPi2B v1.1's. > > I mounted the main [so: 14] media to /mnt and > copied /mnt/EFI/BOOT/bootarm.efi to > /boot/msdos/EFI/BOOT/bootarm.efi . > > The result makes the 13.1-STABLE media fail in > the same sort of manor as 14-CURRENT did. > > So I tried an experiment going in the other > direction: copying 13.1-STABLE's > EFI/BOOT/bootarm.efi into a main [so: 14] > context that had been failing to boot. > It then boots fine. > > main's armv7 EFI/BOOT/bootarm.efi is broken, at > least for RPi2B v1.1 systems. > Can you write a brief summary so I can recreate? And are you sure it's a booting issue and not a console issue? I can't make heads or tails of this whole thread. I need something simple, that's like 5 steps with version numbers. Warner === > Mark Millard > marklmi at yahoo.com > > > --0000000000008feced05eaba6f70 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div dir=3D"auto"><div><br><br><div class=3D"gmail_quote"><div dir=3D"ltr" = class=3D"gmail_attr">On Mon, Oct 10, 2022, 10:00 PM Mark Millard <<a hre= f=3D"mailto:marklmi@yahoo.com">marklmi@yahoo.com</a>> wrote:<br></div><b= lockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px = #ccc solid;padding-left:1ex">[Summary: it looks to be FreeBSD main's EF= I loader that is<br> at issue for armv7 RPi2B v1.1 booting not working.]<br> <br> On 2022-Oct-10, at 20:04, Mark Millard <<a href=3D"mailto:marklmi@yahoo.= com" target=3D"_blank" rel=3D"noreferrer">marklmi@yahoo.com</a>> wrote:<= br> <br> > I put:<br> > <br> > FreeBSD-14.0-CURRENT-arm-armv7-GENERICSD-20220930-42dc8696df5-258315.i= mg<br> > <br> > on a microsd card via dd and tried to boot a RPi2 v1.1. it<br> > hung up after:<br> > <br> > Using DTB provided by EFI at 0x7ef6000.<br> > Kernel entry at 0x36a00200...<br> > Kernel args: (null)<br> > <br> > (A "-" might show in the next line.)<br> > <br> > So I tried:<br> > <br> > FreeBSD-13.1-STABLE-arm-armv7-GENERICSD-20221007-d497b97e902-252653.im= g<br> > <br> > on the microsd card instead. It worked just fine. (Thus the<br> > RPi2B v1.1 is not broken.)<br> > <br> > I did this experiment because recent testing for other<br> > reasons of somewhat older main vintages that I'd built<br> > also showed such failures. This test shows official<br> > builds also have the problem.<br> > <br> > I've no clue how long this issue has been around. It<br> > been a very long time since the RPi2B v1.1 had been<br> > powered on.<br> > <br> > <br> > Note: The arm-armv7-GENERICSD images include the RPi2B<br> > v1.1 related RPi* firmware and u-boot, in addition to<br> > an installed FreeBSD EFI loader and a kernel and a<br> > world. Historically it was supposed to just work for<br> > RPi2B v1.1's. <br> <br> I mounted the main [so: 14] media to /mnt and<br> copied /mnt/EFI/BOOT/bootarm.efi to<br> /boot/msdos/EFI/BOOT/bootarm.efi .<br> <br> The result makes the 13.1-STABLE media fail in<br> the same sort of manor as 14-CURRENT did.<br> <br> So I tried an experiment going in the other<br> direction: copying 13.1-STABLE's<br> EFI/BOOT/bootarm.efi into a main [so: 14]<br> context that had been failing to boot.<br> It then boots fine.<br> <br> main's armv7 EFI/BOOT/bootarm.efi is broken, at<br> least for RPi2B v1.1 systems.<br></blockquote></div></div><div dir=3D"auto"= ><br></div><div dir=3D"auto">Can you write a brief summary so I can recreat= e?</div><div dir=3D"auto"><br></div><div dir=3D"auto">And are you sure it&#= 39;s a booting issue and not a console issue?</div><div dir=3D"auto"><br></= div><div dir=3D"auto">I can't make heads or tails of this whole thread.= I need something simple, that's like 5 steps with version numbers.</di= v><div dir=3D"auto"><br></div><div dir=3D"auto">Warner</div><div dir=3D"aut= o"><br></div><div dir=3D"auto"><br></div><div dir=3D"auto"><div class=3D"gm= ail_quote"><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;bor= der-left:1px #ccc solid;padding-left:1ex"> =3D=3D=3D<br> Mark Millard<br> marklmi at <a href=3D"http://yahoo.com" rel=3D"noreferrer noreferrer" targe= t=3D"_blank">yahoo.com</a><br> <br> <br> </blockquote></div></div></div> --0000000000008feced05eaba6f70--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CANCZdfoJ=E=ef86PRaYsvgXWLAu=AdbN%2B_kiv0vPhKVksqPY%2Bg>