topic Re: wayland service not starting at boot i.mx6DL in i.MX Processors

wayland service not starting at boot i.mx6DL

Chandrashekhar_MVE — Wed, 12 Jun 2024 16:42:01 GMT

command to build yoctos is:(imx-linux-nanbield -m imx-6.6.3-1.0.0.xml)

DISTRO=fsl-imx-xwayland MACHINE=imx6dlsabresd source imx-setup-release.sh -b build-xwayland
bitbake imx-image-full

We have issue with latest wayland build. weston.service is not started at boot up.

root@KitchenBrains:~# systemctl status weston.service
x weston.service - Weston, a Wayland compositor, as a system service
Loaded: loaded (/usr/lib/systemd/system/weston.service; enabled; preset: enabled)
Active: failed (Result: exit-code) since Wed 2024-06-12 21:46:56 UTC; 3min 29s ago
TriggeredBy: * weston.socket
Docs: man:weston(1)
man:weston.ini(5)
http://wayland.freedesktop.org/
Process: 825 ExecStart=/usr/bin/weston --log=${XDG_RUNTIME_DIR}/weston.log --modules=systemd-notify.so (code=exited, status=1/FAILURE)
Main PID: 825 (code=exited, status=1/FAILURE)

Jun 12 21:46:56 KitchenBrains systemd[1]: Starting Weston, a Wayland compositor, as a system service...
Jun 12 21:46:56 KitchenBrains (weston)[825]: pam_unix(weston-autologin:session): session opened for user root(uid=0) by (uid=0)
Jun 12 21:46:56 KitchenBrains (weston)[825]: weston.service: Referenced but unset environment variable evaluates to an empty string: XDG_RUNTIME_DIR
Jun 12 21:46:56 KitchenBrains systemd[1]: weston.service: Main process exited, code=exited, status=1/FAILURE
Jun 12 21:46:56 KitchenBrains systemd[1]: weston.service: Failed with result 'exit-code'.
Jun 12 21:46:56 KitchenBrains systemd[1]: Failed to start Weston, a Wayland compositor, as a system service.
root@KitchenBrains:~#

my weston.ini file shows as below,

[core]
#gbm-format=argb8888
use-g2d=1
idle-time=0
xwayland=true
#enable-overlay-view=1

[shell]

[libinput]
touchscreen_calibrator=true

#[output]
#name=HDMI-A-1
#mode=1920x1080@60
#transform=rotate-90

#[output]
#name=HDMI-A-2
#mode=off
# WIDTHxHEIGHT Resolution size width and height in pixels
# off Disables the output
# preferred Uses the preferred mode
# current Uses the current crt controller mode
#transform=rotate-90

[screen-share]
command=/usr/bin/weston --backend=rdp-backend.so --shell=fullscreen-shell.so --no-clients-resize
#start-on-startup=true

What exactly need to change in yocto setup to get proper LVDS settings? and also get proper evnvirnoment to set for XDG_RUNTIME_DIR?

Rgds

Chandra

Re: wayland service not starting at boot i.mx6DL

Chandrashekhar_MVE — Thu, 13 Jun 2024 09:39:34 GMT

additional information,

after system boot i am manually creating the exports,

export WAYLAND_DISPLAY=wayland-0
export XDG_RUNTIME_DIR=/run/user/0
mkdir --parents $XDG_RUNTIME_DIR
chmod 0700 $XDG_RUNTIME_DIR

after this running weston have backport issue,

root@KitchenBrains:~# weston
Date: 2024-06-13 UTC
[13:29:49.1995357521] weston 10.0.5
https://wayland.freedesktop.org
Bug reports to: https://gitlab.freedesktop.org/wayland/weston/issues/
Build: lf-5.15.71-2.2.2+
[13:29:49.2126190608] Command line: weston
[13:29:49.2126190112] OS: Linux, 6.6.3-gc7ab1ace3177, #6 SMP PREEMPT Fri Jun 7 17:55:22 UTC 2024, armv7l
[13:29:49.2126190112] Flight recorder: enabled
[13:29:49.757100403] Using config file '/etc/xdg/weston/weston.ini'
[13:29:49.000] Output repaint window is 7 ms maximum.
[13:29:49.569049594] Loading module '/usr/lib/libweston-10/wayland-backend.so'
[13:29:49.569049594] Failed to load module: /usr/lib/libweston-10/wayland-backend.so: cannot open shared object file: No such file or directory
[13:29:49.2126190112] fatal: failed to create compositor backend

if change the backport to fbdev-backend thenwe have display but screen is not as expected,

weston --tty=1 --device=/dev/fb0 --use-g2d=1 --backend=fbdev-backend.so &

root@KitchenBrains:~# weston --tty=1 --device=/dev/fb0 --use-g2d=1 --backend=fbdev-backend.so &
[1] 829
root@KitchenBrains:~# Date: 2024-06-13 UTC
[14:59:33.1996143953] weston 10.0.5
https://wayland.freedesktop.org
Bug reports to: https://gitlab.freedesktop.org/wayland/weston/issues/
Build: lf-5.15.71-2.2.2+
[14:59:33.2123458496] Command line: weston --tty=1 --device=/dev/fb0 --use-g2d=1 --backend=fbdev-backend.so
[14:59:33.2123458000] OS: Linux, 6.6.3-gc7ab1ace3177, #6 SMP PREEMPT Fri Jun 7 17:55:22 UTC 2024, armv7l
[14:59:33.2123458000] Flight recorder: enabled
[14:59:33.757100403] Using config file '/etc/xdg/weston/weston.ini'
[14:59:33.000] Output repaint window is 7 ms maximum.
[14:59:33.-1308306002] Loading module '/usr/lib/libweston-10/fbdev-backend.so'
[14:59:33.002] initializing fbdev backend
[14:59:33.2123457696] warning: the fbdev backend is deprecated, please migrate to the DRM backend
[14:59:33.2123457580] Trying logind launcher...
[14:59:33.6999664] logind: cannot find systemd session for uid: 0 -61
[14:59:33.2123457568] logind: cannot setup systemd-logind helper error: (No data available), using legacy fallback
[14:59:33.1633886266] Trying weston_launch launcher...
[14:59:33.1995434227] could not get launcher fd from env
[14:59:33.1868767325] Trying direct launcher...
[14:59:33.-1308306002] Loading module '/usr/lib/libweston-10/g2d-renderer.so'
[14:59:33.000] Opening fbdev frame buffer.
[14:59:33.2123457352] Calculating pixman format from:
- type: 0 (aux: 0)
- visual: 2
- bpp: 24 (grayscale: 0)
- red: offset: 16, length: 8, MSB: 0
- green: offset: 8, length: 8, MSB: 0
- blue: offset: 0, length: 8, MSB: 0
- transp: offset: 0, length: 0, MSB: 0
[14:59:33.1996079421] Created head '/dev/fb0' for device /dev/fb0 (DISP3 BG - DI1)
[14:59:33.2123457456] param->device = /dev/fb0, disp_count = 1, backend->clone_mode = 0
[14:59:33.1001] event0 - Atmel maXTouch Touchscreen: is tagged by udev as: Touchscreen
[14:59:33.2123456216] event0 - Atmel maXTouch Touchscreen: device is a touch device
[14:59:33.7272732] Touchscreen - Atmel maXTouch Touchscreen - /sys/devices/platform/soc/2100000.bus/21a0000.i2c/i2c-0/0-004a/input/input0/event0
[14:59:33.1996104863] libinput: configuring device "Atmel maXTouch Touchscreen".
[14:59:33.1995662983] input device event0 has no enabled output associated (none named), skipping calibration for now.
[14:59:33.1993187256] Color manager: no-op
[14:59:33.2123457740] Creating fbdev output.
[14:59:33.1995662983] Output '/dev/fb0' using color profile: built-in default sRGB SDR profile
[14:59:33.000] g2d_renderer_output_create device=/dev/fb0
[14:59:33.2123457584] clone_display_num = 0
[14:59:33.2123457584] The number of the Framebuffer: 3
[14:59:33.2123457584] Opend device=/dev/fb0
[14:59:33.000] fbdev output 1024×600 px
guessing 103 Hz and 96 dpi
[14:59:33.000] associating input device event0 with output /dev/fb0 (none by udev)
[14:59:33.2123457704] Output '/dev/fb0' enabled with head(s) /dev/fb0
[14:59:33.1995593567] Compositor capabilities:
arbitrary surface rotation: yes
screen capture uses y-flip: yes
cursor planes: no
arbitrary resolutions: no
view mask clipping: yes
explicit sync: yes
color operations: no
presentation clock: CLOCK_MONOTONIC_RAW, id 4
presentation clock resolution: 0.000000001 s
[14:59:33.-1308306002] Loading module '/usr/lib/weston/desktop-shell.so'
[14:59:33.1995921952] launching '/usr/libexec/weston-keyboard'
[14:59:33.001] Warning: support for deprecated wl_shell interface is enabled. Please migrate legacy clients to xdg-shell.
[14:59:33.002] launching '/usr/libexec/weston-desktop-shell'
[ 460.567706] weston-keyboard[831]: memfd_create() called without MFD_EXEC or MFD_NOEXEC_SEAL set
could not load cursor 'dnd-move'
could not load cursor 'dnd-move'
could not load cursor 'dnd-copy'
could not load cursor 'dnd-copy'
could not load cursor 'dnd-none'
could not load cursor 'dnd-none'

root@KitchenBrains:~#

Re: wayland service not starting at boot i.mx6DL

Chandrashekhar_MVE — Thu, 13 Jun 2024 16:28:49 GMT

Please help we struck due to this display issue, unable to findout what is issue with weston, psplashscreen works good, it means we are good with framebuffer and lcd configurations

root@KitchenBrains:~# fbset

mode "1024x600-101"
# 71.901 MHz, H: 62.851 kHz, V: 100.722 Hz
geometry 1024 600 1024 1800 24
timings 13908 24 72 10 12 24 2
rgba 8/16,8/8,8/0,0/0
endmode

Re: wayland service not starting at boot i.mx6DL

brian14 — Fri, 14 Jun 2024 17:10:03 GMT

Hi @Chandrashekhar_MVE,

Thank you for contacting NXP Support.

First of all, I would like to ask about your board. Are you trying in a custom board or our EVK?
I'm working with a similar error in other board and my research indicates that could be a problem of driver and libraries installation. In your case, if you are using the BSP provided by NXP, could you please try with other BSP version to verify if there is a specific issue with that version?

Have a great day!

Re: wayland service not starting at boot i.mx6DL

Chandrashekhar_MVE — Fri, 14 Jun 2024 17:57:06 GMT

Hi ,

This is our custom board. We have only LVDS1 connected in our system . no HDMI & no LVDS0. This issue seems to us something to do with wayland. We are good with psplash screen. Please refer my earlier post.

Re: wayland service not starting at boot i.mx6DL

Chandrashekhar_MVE — Mon, 17 Jun 2024 11:13:18 GMT

Hi Brian,

Did you get any solution to this problem.

Rgds

Chandra

Re: wayland service not starting at boot i.mx6DL

brian14 — Tue, 18 Jun 2024 03:02:56 GMT

Hi @Chandrashekhar_MVE,

Could you please tell me if you are trying to start Weston from the serial terminal or SSH?
If it's the case the problem is related with the session used to start Weston.
I could resolve the issue in my side starting Weston in the display output (the terminal shown in your LVDS display).

Have a great day!

Re: wayland service not starting at boot i.mx6DL

Chandrashekhar_MVE — Tue, 18 Jun 2024 05:34:23 GMT

Hi Brian,

export WAYLAND_DISPLAY=wayland-0
export XDG_RUNTIME_DIR=/run/user/0
mkdir --parents $XDG_RUNTIME_DIR
chmod 0700 $XDG_RUNTIME_DIR

weston --tty=1 --device=/dev/fb0 --use-g2d=1 --backend=fbdev-backend.so &

above are my steps to get the broken screen,

Can you please share your steps?

Rgds

Chandra

Re: wayland service not starting at boot i.mx6DL

Chandrashekhar_MVE — Wed, 19 Jun 2024 13:39:12 GMT

Please share your steps and exports.

Rgds

Chandra

Re: wayland service not starting at boot i.mx6DL

brian14 — Wed, 19 Jun 2024 18:47:16 GMT

Hi @Chandrashekhar_MVE,

Here are my steps:

$ export XDG_RUNTIME_DIR=/run/user/0 $ weston

Have a great day!

Re: wayland service not starting at boot i.mx6DL

Chandrashekhar_MVE — Wed, 19 Jun 2024 19:06:17 GMT

Hi Brian,

Here is my results,

root@imx6dlsabresd:~# export XDG_RUNTIME_DIR=/run/user/0
root@imx6dlsabresd:~# weston
Date: 2024-06-20 UTC
[00:27:43.1996184913] weston 10.0.5
https://wayland.freedesktop.org
Bug reports to: https://gitlab.freedesktop.org/wayland/weston/issues/
Build: lf-5.15.71-2.2.2+
[00:27:43.2123065360] Command line: weston
[00:27:43.2123064864] OS: Linux, 6.6.3-gc7ab1ace3177, #6 SMP PREEMPT Fri Jun 7 17:55:22 UTC 2024, armv7l
[00:27:43.2123064864] Flight recorder: enabled
[00:27:43.2123064864] fatal: environment variable XDG_RUNTIME_DIR
is set to "/run/user/0", which is not a directory.
Refer to your distribution on how to get it, or
http://www.freedesktop.org/wiki/Specifications/basedir-spec
on how to implement it.
root@imx6dlsabresd:~#

Please post your result after weston.

Rgds

Chandra

Re: wayland service not starting at boot i.mx6DL

Chandrashekhar_MVE — Wed, 26 Jun 2024 13:56:10 GMT

Hi Brian,

Can you please help to close this issue?

Rgds

Chandra