Darklord318

Hi everyone, I am developing an industrial system using a Raspberry Pi 5 (Raspberry Pi OS Bookworm). Because it is deployed in an environment with abrupt power cutoffs, I am facing an issue where the default pink and white splash screen randomly reappears during boot, overriding my configuration. Here is what I have already implemented to prevent this: Disabled Splash Screen: Added disable_splash=1 to /boot/firmware/config.txt. Read-Only File System: Enabled the native Overlay File System via raspi-config to protect the boot and root partitions from corruption. Industrial Hardware: Tested with high-end storage to rule out basic SD card degradation. The Problem: The system boots cleanly with no display text or logo for several cycles. However, after a few abrupt hardware power cutoffs, the pink and white splash screen unexpectedly pops back up during boot. Since the Overlay FS is active, config.txt should theoretically be protected from corruption or modification. My Questions: Does the Raspberry Pi 5 EEPROM/bootloader force the fallback splash screen if it detects an improper shutdown flag, completely bypassing the config.txt directive? Is there a specific EEPROM configuration parameter (via sudo rpi-eeprom-config -e) that permanently disables this splash image at the firmware level, rather than relying on the OS partition? Are there any known bugs with the Raspberry Pi 5 firmware where an unclean power-off resets certain video/boot states? Any insights into the Pi 5 bootloader behavior regarding dirty shutdowns would be greatly appreciated. Thanks!