Quantcast
Channel: Raspberry Pi Forums
Viewing all articles
Browse latest Browse all 4407

Raspberry Pi OS • Running update-initramfs -u -k all stops splash screen on boot

$
0
0
Hey,

I am using Raspberry Pi 5 with the Raspberry Pi OS (64-bit) Bookworm. With a fresh installation with the Raspberry Pi Imager, the splash screen works well. But when I run

Code:

update-initramfs -u -k all
the splash screen suddenly stops working on boot, but it does work on shutdown.

The main reason I want to run

Code:

update-initramfs -u
is to replace the default splash.png file with another graphics.

Steps to reproduce:
1. Install the latest Raspberry Pi OS (64-bit) Bookworm (2024-11-19)
2. Connect a monitor to HDMI0, insert the SD card, connect to ethernet and plug in the original power supply.
3. Wait for the Pi to load, you can see the default splash screen
4. SSH into the Pi and replace the file on

Code:

/usr/share/plymouth/themes/pix/splash.png
with a different graphics.
5. Run

Code:

update-initramfs -u -k all
6. Reboot the Pi
7. The new image will be shown on shutdown
8. The Pi will boot with a black screen and the desktop will appear without the new splash screen graphics.

/boot/firmware/cmdline.txt:

Code:

console=serial0,115200 console=tty1 root=PARTUUID=xxxxxxxx-xx rootfstype=ext4 fsck.repair=yes rootwait quiet splash plymouth.ignore-serial-consoles
/boot/firmware/config.txt:

Code:

# For more options and information see# http://rptl.io/configtxt# Some settings may impact device functionality. See link above for details# Uncomment some or all of these to enable the optional hardware interfaces#dtparam=i2c_arm=on#dtparam=i2s=on#dtparam=spi=on# Enable audio (loads snd_bcm2835)dtparam=audio=on# Additional overlays and parameters are documented# /boot/firmware/overlays/README# Automatically load overlays for detected camerascamera_auto_detect=1# Automatically load overlays for detected DSI displaysdisplay_auto_detect=1# Automatically load initramfs files, if foundauto_initramfs=1# Enable DRM VC4 V3D driverdtoverlay=vc4-kms-v3dmax_framebuffers=2# Don't have the firmware create an initial video= setting in cmdline.txt.# Use the kernel's default instead.disable_fw_kms_setup=1# Run in 64-bit modearm_64bit=1# Disable compensation for displays with overscandisable_overscan=1# Run as fast as firmware / board allowsarm_boost=1[cm4]# Enable host mode on the 2711 built-in XHCI USB controller.# This line should be removed if the legacy DWC2 controller is required# (e.g. for USB device mode) or if USB support is not required.otg_mode=1[cm5]dtoverlay=dwc2,dr_mode=host[all]
Something weird that I noticed, when I run

Code:

update-initramfs -u
the updated img is

Code:

6.6.51+rpt-rpi-v8
:

Code:

update-initramfs: Generating /boot/initrd.img-6.6.51+rpt-rpi-v8'/boot/initrd.img-6.6.51+rpt-rpi-v8' -> '/boot/firmware/initramfs8'
but when I run

Code:

uname -r
the output is

Code:

6.6.51+rpt-rpi-2712
, why both img files exists?

Thanks in advance

Statistics: Posted by Shahar — Fri Feb 28, 2025 11:15 pm — Replies 0 — Views 28



Viewing all articles
Browse latest Browse all 4407

Trending Articles