Date: Tue, 28 Apr 2020 21:10:58 -0700 From: Mark Millard <marklmi@yahoo.com> To: bob prohaska <fbsd@www.zefox.net> Cc: Glen Barber <gjb@freebsd.org>, freebsd-arm@freebsd.org Subject: Re: Trouble booting the April 23 snapshot for rpi3 Message-ID: <A05B3023-8C29-45BE-8820-DC11B3B6917C@yahoo.com> In-Reply-To: <20200428214013.GB7169@www.zefox.net> References: <20200428195759.GA7169@www.zefox.net> <46FAA17D-6104-4DAC-A0AA-63ED4DDD72DC@yahoo.com> <20200428201722.GI9584@FreeBSD.org> <20200428214013.GB7169@www.zefox.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2020-Apr-28, at 14:40, bob prohaska <fbsd at www.zefox.net> wrote: > On Tue, Apr 28, 2020 at 08:17:22PM +0000, Glen Barber wrote: >> On Tue, Apr 28, 2020 at 01:11:58PM -0700, Mark Millard via = freebsd-arm wrote: >>>=20 >>>=20 >>> On 2020-Apr-28, at 12:57, bob prohaska <fbsd at www.zefox.net> = wrote: >>>=20 >>>> In trying to boot the April 23 RPI3 snapshot the machine is >>>> reporting what looks like an old problem: > [big snip] >=20 >>=20 >> It is based on the latest branch, but more specifically the port is >> built from a checkout of head from the ports tree. Looking in: http://pkg.freebsd.org/FreeBSD:13:aarch64/latest/All/ shows: u-boot-rpi3-2019.10.txz 203564 2020-Jan-03 18:32 So using "latest" need not mean recent, unfortunately. RPi4 fairs no better: u-boot-rpi4-2019.10.txz 181908 2020-Jan-01 00:47 So, unless the snapshot process built these from more recent source, the snapshot would not have Kyle's changes and the old problems would exist. Hopefully, at some point, http://pkg.freebsd.org/FreeBSD:13:aarch64/latest/All/ will get updates to these. May be the recent change to 2020.04 from 2019.10 might cause such an update to latest? > Looking back through the old thread, Kyle W. put up a patch to test, > which I didn't do. Mark M. got the patch working on a Pi4, but the > conversation ended, at least under that subject line, with no explicit > resolution. Could the problem have slipped between the chairs?=20 >=20 > With much help from Mark M. my pi3 was working by March 22nd, so the=20= > u-boot issue got fixed, in some fashion, by then. After expanding the .img on media, you could replace any old-vintage of u-boot-rpi3 materials with newer ones that you had built from source and installed in /usr/local/share/u-boot/u-boot-rpi3/ . While my context is from source based builds, not snapshots, the RPi3 is running: # uname -apKU FreeBSD Pine64P2G 13.0-CURRENT FreeBSD 13.0-CURRENT #2 r360311M: Sat Apr = 25 10:39:37 PDT 2020 = markmi@FBSDFHUGE:/usr/obj/cortexA53_clang/arm64.aarch64/usr/src/arm64.aarc= h64/sys/GENERIC-NODBG arm64 aarch64 1300092 1300092 (The media can also boot the Pine64+ 2GB --but is in the RPi3 currently.) I do warn that there is for arm64/aarch64 : https://lists.freebsd.org/pipermail/freebsd-bugs/2020-April/093970.html but no bisect has determined the failure start. (Failure is not immediate: bisect would be every slow.) =3D=3D=3D Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?A05B3023-8C29-45BE-8820-DC11B3B6917C>