Re: Failed to execute custom kernels which where build on a RPi 4 operated by 13.1-RELEASE

On Mon, Jul 04, 2022 at 08:57:08PM -0300, Dr. Rolf Jansen wrote:
> On my brand new RPi 4 B (0xb03115), operated by 13.1-RELEASE, I built 2 custom kernels, with kernel configs from different sources. Building and installing went through without issues.

  I've also got a new 8G RPI4, not sure how to get the exact model
number without popping the heatsink case off.  I haven't been running
13.1-REL since they haven't been incorporating some of the changes that
are in -STABLE (although for amd64, not arm64).

> fetch https://download.freebsd.org/releases/arm64/aarch64/13.1-RELEASE/src.txz
> ... cat /usr/src/sys/arm64/conf/GENERIC-RPi4
>    include	GENERIC
>    ident	GENERIC-RPi4
>    nooptions	SOC_NVIDIA_TEGRA210

  I seeding my uboot (and ran initial bsdinstall to USB-only) from:

	FreeBSD-13.1-STABLE-arm64-aarch64-RPI-20220603-185159f77c9-250958

  I'm just building stock GENERIC:  I think I saw from another email
that you're avoid the SOC_NVIDIA_TEGRA210 (my ntpdate thread) because
it's messing with some extra stuff you're doing with your RPI.

  I'm using HDMI, vs any kind of serial console.

> When restarting with any of the new kernels, booting stalls after these messages in the serial console:
>    ...
>    sdhci_bcm0-slot0: AC12 err: 0x00000000 | Host ctl2:0x00000000
>    sdhci_bcm0-slot0: Caps:     0x00000000 | Caps2:    0x00000000
>    sdhci_bcm0-slot0: Max curr: 0x00000001 | ADMA err: 0x00000000
>    sdhci_bcm0-slot0: ADMA addr:0x00000000 | Slot int: 0x00000000
>    sdhci_bcm0-slot0: ===========================================
>    uhub0: 5 ports with 4 removable, self powered
>    mmc0: No compatible cards found on bus

  I've rebuilt mine 5 times since 06-25.  Your serial console doesn't
sync up exactly what I see in my /var/log/messages, but Mark Millard
(who I think is relying to this thread too) just did a really
interesting breakdown between uboot versions for Bob Prohaska.

  Based on some of the threads I've seen recently, I'd:

	Make sure you have a recent uboot
	Make sure you're booting the uboot you think you are
	  (sim-cards having race condition with USB, etc)
	Just try with one sim or USB and, if that works,
	  start adding on extra bits
	Try HDMI, just for the yucks