Re: [poky] [PATCH 2/2] psplash: start via udev if framebuffer device detected

Richard Purdie <[email protected]>
Newsgroups org.yoctoproject.lists.poky,org.openembedded.lists.openembedded-core
Message-ID <a7821314c57220b19a189530d48a64934c4b4820.camel@linuxfoundation.org>
On Thu, 2025-02-06 at 16:44 +0200, Mikko Rapeli via lists.yoctoproject.org wrote:
> 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.
> 
> Signed-off-by: Mikko Rapeli <[email protected]>
> ---
>  meta/recipes-core/psplash/files/fb.rules                 | 1 +
>  .../{psplash-start.service => [email protected]}    | 5 ++---
>  meta/recipes-core/psplash/files/psplash-systemd.service  | 8 +++-----
>  meta/recipes-core/psplash/psplash_git.bb                 | 9 ++++++---
>  4 files changed, 12 insertions(+), 11 deletions(-)
>  create mode 100644 meta/recipes-core/psplash/files/fb.rules
>  rename meta/recipes-core/psplash/files/{psplash-start.service => [email protected]} (84%)

Unfortunately I think this has introduced an intermittent QA test
failure showing up in meta-arm in particular. Examples:

https://autobuilder.yoctoproject.org/valkyrie/#/builders/75/builds/994/steps/22/logs/stdio
https://gitlab.com/jonmason00/meta-arm/-/jobs/9155263483

but it doesn't always fail. There were other failures if you look
through the meta-arm builds.

Cheers,

Richard
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.