Especially with systemd its seen that psplash-start service starts before /dev/fb0 is created by kernel which results in
[FAILED] Failed to start Start psplash boot splash screen.
this is quite frequent race now with kernel 6.1
Add device dependency on sys-devices-platform-gpu-graphics-fb0.device via a unit file drop-in
- What I did
Fix psplash-start.service for branch kirkstone to avoid errors like:
Jan 01 00:00:09 raspberrypi4 systemd[1]: Starting Start psplash boot splash screen...
Jan 01 00:00:09 raspberrypi4 psplash[297]: Error opening /dev/fb0
Jan 01 00:00:09 raspberrypi4 systemd[1]: psplash-start.service: Main process exited, code=exited, status=255/EXCEPTION
Jan 01 00:00:09 raspberrypi4 systemd[1]: psplash-start.service: Failed with result 'exit-code'.
Jan 01 00:00:09 raspberrypi4 systemd[1]: Failed to start Start psplash boot splash screen.
Tested on Raspberry Pi 4.
- How I did it
Cherry-picked @kraj patch 98349bb367418866e008ba22ca75f4ab2984561a to branch kirkstone. Considering this is Yocto LTS release until Apr. 2026 it makes sense to backport this particular patch.
Especially with systemd its seen that psplash-start service starts before /dev/fb0 is created by kernel which results in
[FAILED] Failed to start Start psplash boot splash screen.
this is quite frequent race now with kernel 6.1
Add device dependency on sys-devices-platform-gpu-graphics-fb0.device via a unit file drop-in
- What I did
Fix
psplash-start.servicefor branch kirkstone to avoid errors like:Tested on Raspberry Pi 4.
- How I did it
Cherry-picked @kraj patch 98349bb367418866e008ba22ca75f4ab2984561a to branch kirkstone. Considering this is Yocto LTS release until Apr. 2026 it makes sense to backport this particular patch.