I am using Raspberry Pi 5 in a production setup where the system auto-boots and launches an application. I get the red splash screen on boot in one of my raspberry pi 5 and I found the below
CURRENT: Wed Nov 5 17:37:18 UTC 2025 (1762364238)
LATEST: Mon Sep 23 13:02:56 UTC 2024 (1727096576)
RELEASE: default (/lib/firmware/raspberrypi/bootloader-2712/default)
Use raspi-config to change the release.
So I chose the default bootloader option in raspi-config and then the issue resolved. Later on going to later EEPROM version 8Dec 2025 and coming back to this version, the issue came back again.. I somehow need these messages to be avoided.
Is the “Trying SD card boot…” message an intentional diagnostic feature introduced in newer Raspberry Pi 5 EEPROM versions?
Is there any supported EEPROM configuration option to suppress or disable HDMI boot probing messages?
Why might this message appear on one Pi 5 but not another, even when both report similar bootloader versions?
CURRENT: Wed Nov 5 17:37:18 UTC 2025 (1762364238)
LATEST: Mon Sep 23 13:02:56 UTC 2024 (1727096576)
RELEASE: default (/lib/firmware/raspberrypi/bootloader-2712/default)
Use raspi-config to change the release.
So I chose the default bootloader option in raspi-config and then the issue resolved. Later on going to later EEPROM version 8Dec 2025 and coming back to this version, the issue came back again.. I somehow need these messages to be avoided.
Is the “Trying SD card boot…” message an intentional diagnostic feature introduced in newer Raspberry Pi 5 EEPROM versions?
Is there any supported EEPROM configuration option to suppress or disable HDMI boot probing messages?
Why might this message appear on one Pi 5 but not another, even when both report similar bootloader versions?
Statistics: Posted by sowmiya — Tue Dec 30, 2025 6:04 am