Date: Sun, 18 Apr 2021 16:12:35 -0700 From: Mark Millard <marklmi@yahoo.com> To: Denis Ovsienko <denis@ovsienko.info> Cc: freebsd-arm@freebsd.org Subject: Re: RPi4B 2711ZPKFSB06C0T parts seen in the wild, 13.0-RELEASE fails to boot on them Message-ID: <9457100A-0EF8-4CCF-A068-EB1D310792B4@yahoo.com> In-Reply-To: <20210418231607.043c0ff2@basepc> References: <05740E83-5A45-4944-AC87-629D21D7F579.ref@yahoo.com> <05740E83-5A45-4944-AC87-629D21D7F579@yahoo.com> <20210418143230.573a968e@basepc> <93728D9D-9222-47A8-B6F1-DC6FCCC21915@yahoo.com> <20210418231607.043c0ff2@basepc>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2021-Apr-18, at 15:16, Denis Ovsienko <denis at ovsienko.info> wrote: > On Sun, 18 Apr 2021 13:38:07 -0700 > Mark Millard <marklmi@yahoo.com> wrote: > >> b03114 4B 1.4 2GB Sony UK > > If it helps, I have one RPI4B that reports itself as the above (2GB), > and another as d03114 (8GB). Both boot FreeBSD 13.0 from an SD card > fine. It is too late to confirm the labelling as the chips are under > heatsinks, but if anybody needs any debug information from a known-good > b03114, let me know. That does suggest 3 possibiliites: A) Differing EEPROM content versions B) Differing board/CPU revisions C) A combination of both (A) would definitely not lead to b03114 changing. So I propose another test under RaspiOS or RaspiOS64: # vcgencmd bootloader_config and/or: # rpi-eeprom-config === 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?9457100A-0EF8-4CCF-A068-EB1D310792B4>