Date: Tue, 5 Jul 2022 07:14:00 -0700 From: Mark Millard <marklmi@yahoo.com> To: John Kennedy <warlock@phouka.net> Cc: "Dr. Rolf Jansen" <freebsd-rj@cyclaero.com>, freebsd-arm@freebsd.org Subject: Re: Failed to execute custom kernels which where build on a RPi 4 operated by 13.1-RELEASE Message-ID: <F4CC3F50-828D-4F1F-BDA1-BF4940ACF0C6@yahoo.com> In-Reply-To: <YsQy0DWhOakmiII1@phouka1.phouka.net> References: <B1296677-558F-49F3-B7B7-2784ACA6612B@cyclaero.com> <0A80CA1D-A3B7-4565-A059-B55FF05DE51B@yahoo.com> <531137B1-0501-47AE-BC2F-62F57067356B@yahoo.com> <YsOsh4Wz/DmClOIg@phouka1.phouka.net> <F1A048E6-7EB2-4805-9C5E-10440C46A3AE@yahoo.com> <YsQy0DWhOakmiII1@phouka1.phouka.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2022-Jul-5, at 05:47, John Kennedy <warlock@phouka.net> wrote: > On Mon, Jul 04, 2022 at 11:41:37PM -0700, Mark Millard wrote: >> Note: I do my own builds, installs, and configuration >> experiments. Do not expect my example outputs below to >> necessarily match those for official builds. >> >> For reference from my root-on-UFS aarch64 environment that boots >> via U-Boot (not via EDK2 UEFI/ACPI): > > Gah. There is so much more out there than RPI4 now for arm64 I didn't > stop to wonder if bsdinstall set it up right. I just reformatted > /boot/efi and slapped the uboot stuff in there because that was the way > the SDcard image was set up. I left it as /boot/efi (vs /boot/msdos). > >> # sysctl hw.fdt # Likely a RPi* specific sysctl name? >> hw.fdt.serial-number: REPLACED >> hw.fdt.compatible: raspberrypi,4-model-b brcm,bcm2711 >> hw.fdt.model: Raspberry Pi 4 Model B Rev 1.4 > > # sysctl hw.fdt > hw.fdt.serial-number: <REDACTED> > hw.fdt.compatible: raspberrypi,4-model-b brcm,bcm2711 > hw.fdt.model: Raspberry Pi 4 Model B Rev 1.5 > > Aha, that is what I was looking for. Wasn't even seeing that with > hw-probe, and I wasn't going to interrupt the 12-hour llvm13 compile to > reboot and see what I could with uboot yet. I checked, and for EDK2 UEFI/ACPI the "sysctl -a" output does not report such information under any name. The sysctl hw.fdt output is empty for that type of boot context, for example. > There is this guy, Mark Millard, who writes these really good mailing > list emails that makes me paranoid about uboot version mismatches. :D > > I haven't even looked at the EEPROM firmware stuff. Rev 1.5 RPi*'s do not have many valid "default" EEPROM content alternatives yet: most are too old to be appropriate. > Reading the list, > it's all been such potential foot-cannon fodder seeing some people's > issues I just knew it would be a potential problem, but happily it just > worked as I would have hoped. > >> I boot a RaspiOS64 microsd card for the related activity. > > Yeah, I haven't been doing that. > === Mark Millard marklmi at yahoo.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?F4CC3F50-828D-4F1F-BDA1-BF4940ACF0C6>