Date: Mon, 10 Oct 2022 20:04:48 -0700 From: Mark Millard <marklmi@yahoo.com> To: freebsd-arm <freebsd-arm@freebsd.org> Cc: bob prohaska <fbsd@www.zefox.net> Subject: FYI: FreeBSD-14.0-CURRENT-arm-armv7-GENERICSD-20220930-42dc8696df5-258315.img is broken for RPi2 v1.1 (so: armv7) Message-ID: <6B46F46A-2CAF-42C9-9A04-63567D7DB9B2@yahoo.com> References: <6B46F46A-2CAF-42C9-9A04-63567D7DB9B2.ref@yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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. === Mark Millard marklmi at yahoo.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?6B46F46A-2CAF-42C9-9A04-63567D7DB9B2>