Date: Tue, 11 Oct 2022 08:26:48 -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: <28D78C89-E195-4EF1-BB7B-E7F75060BDC7@yahoo.com> In-Reply-To: <CANCZdfoU2Ln2vqymT66Yu6ZdxSrZLAx1%2BA_hstLYSrzBmduHBw@mail.gmail.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>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2022-Oct-11, at 06:17, Warner Losh <imp@bsdimp.com> wrote: >=20 > 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: >=20 > . . . > > And are you sure it's a booting issue and not a console issue? >=20 > 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.) >=20 > 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. =20 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.) > . . . >=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 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. But I may not be able to look into this immediately. In main: 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 It looks like the closest prior artifact is at: = 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 with date/time: 2022-Aug-26 16:26 So I expect to use that. > 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.) Again: It turned out that serial+HDMI also shows the issue. I also later reported that the snapshot with the date 20221007 also shows the issue. You do not need to use the 20220930 one. > . . . > OK. That's a fairly clear set of instructions. I'll try to work that = into my > schedule. Thanks. =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?28D78C89-E195-4EF1-BB7B-E7F75060BDC7>