Issues with Launching Weston on Yocto Kirkstone for i.MX 8

[aoiblue]

Hello everyone,

I'm currently facing an issue with launching Weston on my i.MX 8 platform using Yocto Kirkstone. I aim to launch Weston automatically using services, but even manual attempts to launch it have been unsuccessful. Below are the commands and errors I've encountered:

# weston --backend=/usr/lib/libweston-10/drm-backend.so --tty 7
[18:02:47.948] weston 10.0.1
https://wayland.freedesktop.org
Bug reports to: https://gitlab.freedesktop.org/wayland/weston/issues/
Build: lf-5.15.52-2.1.0+
[18:02:47.948] Command line: weston --backend=/usr/lib/libweston-10/drm-backend.so --tty 7
[18:02:47.948] OS: Linux, 5.15.71-2.2.0+yocto+gaaf028b285b7+p0, #1 SMP PREEMPT Thu Nov 30 09:24:26 UTC 2023, aarch64
[18:02:47.948] Flight recorder: enabled
[18:02:47.952] Using config file '/etc/xdg/weston/weston.ini'
[18:02:47.955] Output repaint window is 16 ms maximum.
[18:02:47.958] Loading module '/usr/lib/libweston-10/drm-backend.so'
[18:02:47.978] initializing drm backend
[18:02:47.978] Trying logind launcher...
[18:02:47.979] logind: cannot find systemd session for uid: 0 -61
[18:02:47.979] logind: cannot setup systemd-logind helper error: (No data available), using legacy fallback
[18:02:47.979] Trying weston_launch launcher...
[18:02:47.979] could not get launcher fd from env
[18:02:47.979] Trying direct launcher...
[18:02:47.979] no drm device found
[18:02:47.980] BUG: layer_list is not empty after shutdown. Calls to weston_layer_fini() are missing somewhere.
[18:02:47.980] fatal: failed to create compositor backend
Internal warning: debug scope 'drm-backend' has not been destroyed.

Other attempts:
root@nitrogen8mm:~# weston-launch -t /dev/tty7 -u root
[18:03:54.108] weston 10.0.1
https://wayland.freedesktop.org
Bug reports to: https://gitlab.freedesktop.org/wayland/weston/issues/
Build: lf-5.15.52-2.1.0+
[18:03:54.109] Command line: /usr/bin/weston
[18:03:54.109] OS: Linux, 5.15.71-2.2.0+yocto+gaaf028b285b7+p0, #1 SMP PREEMPT Thu Nov 30 09:24:26 UTC 2023, aarch64
[18:03:54.109] Flight recorder: enabled
[18:03:54.109] fatal: environment variable XDG_RUNTIME_DIR is not set.
Refer to your distribution on how to get it, or
http://www.freedesktop.org/wiki/Specifications/basedir-spec
on how to implement it.
root@nitrogen8mm:~# XDG_RUNTIME_DIR=/tmp/root-weston/ weston --backend=/usr/lib/libweston-10/drm-backend.so --tty 7
Date: 2022-04-28 UTC
[18:04:21.069] weston 10.0.1
https://wayland.freedesktop.org
Bug reports to: https://gitlab.freedesktop.org/wayland/weston/issues/
Build: lf-5.15.52-2.1.0+
[18:04:21.069] Command line: weston --backend=/usr/lib/libweston-10/drm-backend.so --tty 7
[18:04:21.069] OS: Linux, 5.15.71-2.2.0+yocto+gaaf028b285b7+p0, #1 SMP PREEMPT Thu Nov 30 09:24:26 UTC 2023, aarch64
[18:04:21.069] Flight recorder: enabled
[18:04:21.074] Using config file '/etc/xdg/weston/weston.ini'
[18:04:21.077] Output repaint window is 16 ms maximum.
[18:04:21.080] Loading module '/usr/lib/libweston-10/drm-backend.so'
[18:04:21.102] initializing drm backend
[18:04:21.102] Trying logind launcher...
[18:04:21.103] logind: cannot find systemd session for uid: 0 -61
[18:04:21.103] logind: cannot setup systemd-logind helper error: (No data available), using legacy fallback
[18:04:21.103] Trying weston_launch launcher...
[18:04:21.103] could not get launcher fd from env
[18:04:21.103] Trying direct launcher...
[18:04:21.104] no drm device found
[18:04:21.104] BUG: layer_list is not empty after shutdown. Calls to weston_layer_fini() are missing somewhere.
[18:04:21.104] fatal: failed to create compositor backend
Internal warning: debug scope 'drm-backend' has not been destroyed.

I've followed the recommended steps from this:

https://www.ezurio.com/resources/software-announcements/yocto-kirkstone-release-for-i-mx-8-platforms...

I've also tried the steps here, but nothing changed the errors.

https://docs.yoctoproject.org/4.0.20/dev-manual/wayland.html

Has anyone encountered similar issues or have any suggestions on resolving this? Any help would be greatly appreciated!

This is with a custom display/driver, not sure if that's related though. It should still start.

Thank you!

[Chavira · Accepted solution]

HI @aoiblue!

In our boards doesn't happen that issue.

I recommed to contacting ezurio support because we don't provide the software for this board.

Best Regards!

Chavira