Hi everyone,
I'm using Raspberry Pi OS (Bookworm) and have set up a custom Plymouth theme that displays a 300-frame image sequence as a boot animation.
The problem is that the system boots too fast, and the splash screen disappears before the animation is complete. Only part of the 300 images are shown before it switches to the desktop.
My goal:
I want the Pi to wait for the full animation to finish before continuing the boot process or reaching the desktop.
Here's what I have done so far:
I created a custom Plymouth theme using script plugin that loops through all 300 images.
The animation logic works perfectly.
But Raspberry Pi OS finishes booting too early and exits Plymouth before it completes.
Is there a proper way to delay the system from reaching graphical.target or desktop until Plymouth finishes?
I’ve seen plymouth --wait being used in systemd services — would adding a custom systemd unit help in this case?
Appreciate any help or suggestions!
Thanks in advance!
I'm using Raspberry Pi OS (Bookworm) and have set up a custom Plymouth theme that displays a 300-frame image sequence as a boot animation.
The problem is that the system boots too fast, and the splash screen disappears before the animation is complete. Only part of the 300 images are shown before it switches to the desktop.
My goal:
I want the Pi to wait for the full animation to finish before continuing the boot process or reaching the desktop.
Here's what I have done so far:
I created a custom Plymouth theme using script plugin that loops through all 300 images.
The animation logic works perfectly.
But Raspberry Pi OS finishes booting too early and exits Plymouth before it completes.
Is there a proper way to delay the system from reaching graphical.target or desktop until Plymouth finishes?
I’ve seen plymouth --wait being used in systemd services — would adding a custom systemd unit help in this case?
Appreciate any help or suggestions!
Thanks in advance!
Statistics: Posted by remzirecep — Wed May 14, 2025 5:52 am