From nobody Tue Jul 05 12:47:12 2022 X-Original-To: freebsd-arm@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id AFDDD1D050FA for ; Tue, 5 Jul 2022 12:48:41 +0000 (UTC) (envelope-from warlock@phouka1.phouka.net) Received: from phouka1.phouka.net (phouka1.phouka.net [107.170.196.116]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "phouka.net", Issuer "Go Daddy Secure Certificate Authority - G2" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4LcjCX6KXgz3GVH for ; Tue, 5 Jul 2022 12:48:40 +0000 (UTC) (envelope-from warlock@phouka1.phouka.net) Received: from phouka1.phouka.net (localhost [127.0.0.1]) by phouka1.phouka.net (8.16.1/8.16.1) with ESMTPS id 265ClClI019262 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Tue, 5 Jul 2022 05:47:12 -0700 (PDT) (envelope-from warlock@phouka1.phouka.net) Received: (from warlock@localhost) by phouka1.phouka.net (8.16.1/8.16.1/Submit) id 265ClCIG019261; Tue, 5 Jul 2022 05:47:12 -0700 (PDT) (envelope-from warlock) Date: Tue, 5 Jul 2022 05:47:12 -0700 From: John Kennedy To: Mark Millard Cc: "Dr. Rolf Jansen" , 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: References: <0A80CA1D-A3B7-4565-A059-B55FF05DE51B@yahoo.com> <531137B1-0501-47AE-BC2F-62F57067356B@yahoo.com> List-Id: Porting FreeBSD to ARM processors List-Archive: https://lists.freebsd.org/archives/freebsd-arm List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-arm@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Rspamd-Queue-Id: 4LcjCX6KXgz3GVH X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of warlock@phouka1.phouka.net has no SPF policy when checking 107.170.196.116) smtp.mailfrom=warlock@phouka1.phouka.net X-Spamd-Result: default: False [-1.79 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; TO_DN_SOME(0.00)[]; NEURAL_HAM_LONG(-1.00)[-0.999]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[phouka.net]; AUTH_NA(1.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; MID_RHS_MATCH_FROMTLD(0.00)[]; NEURAL_HAM_SHORT(-0.99)[-0.995]; MLMMJ_DEST(0.00)[freebsd-arm]; FREEMAIL_TO(0.00)[yahoo.com]; FORGED_SENDER(0.30)[warlock@phouka.net,warlock@phouka1.phouka.net]; R_SPF_NA(0.00)[no SPF record]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:14061, ipnet:107.170.192.0/18, country:US]; FROM_NEQ_ENVFROM(0.00)[warlock@phouka.net,warlock@phouka1.phouka.net]; RCVD_TLS_ALL(0.00)[]; RCVD_COUNT_TWO(0.00)[2] X-ThisMailContainsUnwantedMimeParts: N 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: 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. 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. 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.