Date: Tue, 11 Oct 2022 09:20:29 -0700 From: Mark Millard <marklmi@yahoo.com> To: Warner Losh <imp@bsdimp.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: <5B631C27-E68C-4F38-96B5-B311110A8F86@yahoo.com> In-Reply-To: <28D78C89-E195-4EF1-BB7B-E7F75060BDC7@yahoo.com> References: <6B46F46A-2CAF-42C9-9A04-63567D7DB9B2@yahoo.com> <D9B791B7-106A-402E-AD8C-F811EB315560@yahoo.com> <CANCZdfoJ=E=ef86PRaYsvgXWLAu=AdbN%2B_kiv0vPhKVksqPY%2Bg@mail.gmail.com> <FC871551-7C49-4751-8763-2E8F82C1480A@yahoo.com> <CANCZdfoU2Ln2vqymT66Yu6ZdxSrZLAx1%2BA_hstLYSrzBmduHBw@mail.gmail.com> <28D78C89-E195-4EF1-BB7B-E7F75060BDC7@yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
[Summary: Both somewhat before and just after your ConOut commit work. I'll have to do a rough bisect with the available armv7 artifacts that are after those but before October.] On 2022-Oct-11, at 08:26, Mark Millard <marklmi@yahoo.com> wrote: > On 2022-Oct-11, at 06:17, Warner Losh <imp@bsdimp.com> wrote: > . . . >> . . . >>=20 >> 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: >>=20 >> commit df065f699f1ff819bb9607c44a6754275ab335ed >> Author: Warner Losh <imp@FreeBSD.org> >> Date: Fri Aug 26 15:46:33 2022 -0600 >>=20 >> stand: More sensible defaults when ConOut is missing >=20 > I'll look at finding and trying some artifact build to extract a > armv7 EFI loader from. Available snapshot history does not > go back that far so far as I know. >=20 > But I may not be able to look into this immediately. >=20 > In main: >=20 > commit df065f699f1ff819bb9607c44a6754275ab335ed > Author: Warner Losh <imp@FreeBSD.org> > AuthorDate: 2022-08-26 21:46:33 +0000 > Commit: Warner Losh <imp@FreeBSD.org> > CommitDate: 2022-08-27 04:17:56 +0000 >=20 > It looks like the closest prior artifact is at: >=20 > = https://artifact.ci.freebsd.org/snapshot/main/a358db5603702d5de5fd75f5bd16= bbf7c0ab673f/arm/armv7/?C=3DM&O=3DD > git: a358db560370 - main - socket(2): bring documentation up tp date = Gleb Smirnoff >=20 > with date/time: 2022-Aug-26 16:26 >=20 > So I expect to use that. Turns out that I had the time. Use of the ./boot/loader.efi from a358db560370 substituted into the failing main snapshot based microsd card worked fine for both contexts: A) Just serial console. and: B) Serial console and HDMI console at the same time. I also tried the oldest artifact build with the loader change in place: = https://artifact.ci.freebsd.org/snapshot/main/7ed3228323ef4f9e3130603ea68c= 3be9c2ed50ce/arm/armv7/ git: 7ed3228323ef - main - stand: Document that boot0 uses BIOS Warner = Losh Date/time: 2022-Aug-27 05:12 This also worked for both (A) and (B). So it looks like I'll be doing a rough bisect to find a before/after pair. It might have some elapsed time to finish. >> I think this should be backed out and we should use a different = hueristic >> when we don't know. >>=20 >> If you have RPi2B v1.1 (so: armv7) access, just try to boot: >>=20 >> = FreeBSD-14.0-CURRENT-arm-armv7-GENERICSD-20220930-42dc8696df5-258315.img >>=20 >> via serial console usage, no video connection present. (I >> did not try a video connection as that is not my type of >> context.) >=20 > Again: It turned out that serial+HDMI also shows the issue. >=20 > I also later reported that the snapshot with the date 20221007 > also shows the issue. You do not need to use the 20220930 one. >=20 >> . . . >> OK. That's a fairly clear set of instructions. I'll try to work that = into my >> schedule. >=20 =3D=3D=3D Mark Millard marklmi at yahoo.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5B631C27-E68C-4F38-96B5-B311110A8F86>