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

Reply: John Kennedy : "Re: Failed to execute custom kernels which where build on a RPi 4 operated by 13.1-RELEASE"
In reply to: John Kennedy : "Re: Failed to execute custom kernels which where build on a RPi 4 operated by 13.1-RELEASE"
Go to: [ bottom of page ] [ top of archives ] [ this month ]

From: Dr. Rolf Jansen <freebsd-rj_at_cyclaero.com>
Date: Tue, 05 Jul 2022 02:12:38 UTC

> Am 04.07.2022 um 22:33 schrieb John Kennedy <warlock@phouka.net>:
> 
> 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.

In the serial console I see:

   U-Boot 2022.04 (Jul 01 2022 - 06:22:22 +0000)

   DRAM:  1.9 GiB
   RPI 4 Model B (0xb03115)
   Core:  196 devices, 13 uclasses, devicetree: board
   MMC:   mmc@7e300000: 3, emmc2@7e340000: 0
   Loading Environment from FAT... In:    serial
   ...

This was just, when stating 14.0-CURRENT. In the serial console I can scroll back, while on a HDMI screen this would rush away too quickly, but perhaps you would be able to take a photo, for finding out your model's revision.

> 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.

In 13.1-STABLE the RTC issue was fixed as well. If I can't built a custom kernel on 13.1-RELEASE then I will stay with 14.0-CURRENT, even if I would have preferred RELEASE, but a working RTC is more important for me.

> 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.

OK, here I just found out the build of a 14.0-CURRENT custom kernel does execute without any failure.

I forgot to mention, that I tried to get the 13.1-RELEASE custom kernels to work by installing the most recent u-boot.bin from the ports. This didn't help either.

Best regards

Rolf Jansen