Date: Wed, 22 Mar 2023 17:16:33 +0000 From: void <void@f-m.fm> To: freebsd-arm@freebsd.org Subject: Re: FYI: upcoming 13.2-RELEASE vs. 8 GiByte RPi4B's based on U-Boot 2023.01 recently in use, given UEFI style booting Message-ID: <ZBs38XQr/MPVGNeC@int21h> In-Reply-To: <2B3378B0-A506-4A90-80D4-734AAA5EE774@yahoo.com> References: <2B3378B0-A506-4A90-80D4-734AAA5EE774.ref@yahoo.com> <2B3378B0-A506-4A90-80D4-734AAA5EE774@yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Feb 18, 2023 at 04:44:09PM -0800, Mark Millard wrote: >This is an FYI about 8 GiByte RPI4B coverage by 13.2-RELEASE. >(The existing snapshots and such show the issue now --but I'm >noting the 13.2-RELEASE consequences for as things are.) Thanks for the heads-up. I saw this only after encountering the proble; I should have looked here first ;) Can the issue be sidestepped using materials working at the moment with 13.1R-p6 ? The VC_BUILD_ID_TIME for start4.elf is Feb 25 2021. I was thinking of taking eg: FreeBSD-14.0-CURRENT-arm64-aarch64-RPI-20230316-cee09bda03c8-261544.img mounting the msdos partition with mdconfig, removing what's there and copying over the known-to-be-working contents of /boot/efi on the 13.1 system? additionally, how can I stop the msdos partition being clobbered on the working system in some future freebsd-update of the working 13.1-p6 system? --
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?ZBs38XQr/MPVGNeC>