mirror of
https://git.yoctoproject.org/poky
synced 2026-02-09 10:13:03 +01:00
af38235305
psplash-start.service expected to find /dev/fb0 and failed if device was not found. This failure breaks systemd oeqa runtime test with "runqemu nographic". Starting psplash based on detected framebuffer device fixes systemd boot status and systemd oeqa runtime tests for qemu boots with and without graphics support. Note that psplash-systemd.service still depends on /dev/fb0 so startup with multiple framebuffer devices may not work correctly. I don't have devices with multiple framebuffer devices to test with. On qemu machine with graphics, psplash displays yocto logo correctly and boot progress bar as well. Once boot completes to systemd "running" state, the logo is replaced by login prompt. On qemu machine without graphics, boot completes without psplash or failures and login over serial console works normally. Tested with genericarm64 machine poky-altcfg distro and core-image-base image on qemu. AMD kv260 tested as well but graphics stack is not yet working there so boot is similar to qemu without graphics. (From OE-Core rev: 3820f6f342c2309ba7d51d3c08b3a951c2c17781) Signed-off-by: Mikko Rapeli <mikko.rapeli@linaro.org> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
13 lines
251 B
Desktop File
13 lines
251 B
Desktop File
[Unit]
|
|
Description=Start psplash boot splash screen
|
|
DefaultDependencies=no
|
|
RequiresMountsFor=/run
|
|
ConditionFileIsExecutable=/usr/bin/psplash
|
|
After=dev-%i.device
|
|
Wants=dev-%i.device
|
|
|
|
[Service]
|
|
Type=notify
|
|
ExecStart=/usr/bin/psplash
|
|
RemainAfterExit=yes
|