Re: RPI4-4Gb Boot fails from SD card (both my build AND the official 14.3 build)

Mark Millard <[email protected]>
Newsgroups gmane.os.freebsd.devel.arm
Message-ID <[email protected]>
On Jul 27, 2025, at 10:39, Bakul Shah <[email protected]> wrote:

> Some more info in case it helps....
> 
> I rebooted the pi4 running freebsd into raspbian (on an sdcard) and see this:
> 
> # rpi-eeprom-config
> [all]
> BOOT_UART=0
> WAKE_ON_GPIO=1
> POWER_OFF_ON_HALT=0
> SDRAM_BANKLOW=3
> 
> [all]
> BOOT_ORDER=0xf41
> 
> # rpi-eeprom-update
> *** UPDATE AVAILABLE ***
> 
> Run "sudo rpi-eeprom-update -a" to install this update now.
> 
> To configure the bootloader update policy run "sudo raspi-config"
> 
> BOOTLOADER: update available
>    CURRENT: Tue Feb 11 05:00:13 PM UTC 2025 (1739293213)
>     LATEST: Thu Jul 17 08:26:45 AM UTC 2025 (1752740805)
>    RELEASE: latest (/usr/lib/firmware/raspberrypi/bootloader-2711/latest)
>             Use raspi-config to change the release.

FYI: "latest"for RELEASE means "latest Beta", also called
beta and stable by the RPi* folks.

The non-Beta is called "default", also called critical.

>   VL805_FW: Dedicated VL805 EEPROM
>      VL805: up to date
>    CURRENT: 000138c0
>     LATEST: 000138c0
> 
> # cat /proc/cpuinfo | tail -3
> Revision        : c03111
> Serial          : 10000000eda244df
> Model           : Raspberry Pi 4 Model B Rev 1.1
> 
> So this is a working setup and firmware version. I am not going to update it to the latest as something may break!
> 
> Note that 
>     https://github.com/raspberrypi/rpi-eeprom/tree/master/firmware-2711/old/stable
> has all the images so you can experiment. My freebsd pi4 has pieeprom-2025-02-11.bin, while the raspbian pi4 is running the latest.
> 
> From freebsd:
> 
> # cksum /boot/efi/u-boot.bin
> 1050247439 630976 /boot/efi/u-boot.bin
> 
> Note sure where this came from. Probably some freebsd snapshot image.

===
Mark Millard
marklmi at yahoo.com
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.