i.MX8QM-MEK: cannot launch weston with "no drm device found" error

cancel
Showing results for 
Search instead for 
Did you mean: 

i.MX8QM-MEK: cannot launch weston with "no drm device found" error

725 Views
Seokha
Contributor II

HW: i.MX8QM-MEK

images: official releases from https://www.nxp.com/design/software/embedded-software/i-mx-software/embedded-linux-for-i-mx-applicat...

boot mode: sdcard

HDMI interface

 

I tested 5.15.32_2.0.0 (https://www.nxp.com/webapp/Download?colCode=L5.15.32_2.0.0_MX8QM&appType=license) and 5.10.72_2.2.2 (https://www.nxp.com/webapp/Download?colCode=L5.10.72_2.2.2_MX8QM&appType=license)

but weston does not launch with "no drm device found" error.

 

Please see the full log of weston

a. linux 5.15.32_2.0.0, weston 10.0.0

 

 

 

 

root@imx8qmmek:~# cat /run/user/0/weston.log
Date: 2022-09-07 UTC
[06:38:49.809] weston 10.0.0
https://wayland.freedesktop.org
Bug reports to: https://gitlab.freedesktop.org/wayland/weston/issues/
Build: 10.0.0
[06:38:49.810] Command line: /usr/bin/weston --log=/run/user/0/weston.log --modules=systemd-notify.so
[06:38:49.810] OS: Linux, 5.15.32-lts-next+gfa6c3168595c, #1 SMP PREEMPT Tue Jun 7 02:34:46 UTC 2022, aarch64
[06:38:49.810] Flight recorder: enabled
[06:38:49.813] Using config file '/etc/xdg/weston/weston.ini'
[06:38:49.819] Output repaint window is 16 ms maximum.
[06:38:49.820] Loading module '/usr/lib/libweston-10/drm-backend.so'
[06:38:49.843] initializing drm backend
[06:38:49.843] Trying logind launcher...
[06:38:49.856] logind: session control granted
[06:38:49.877] no drm device found
[06:38:49.878] BUG: layer_list is not empty after shutdown. Calls to weston_layer_fini() are missing somwhere.
[06:38:49.878] fatal: failed to create compositor backend

 

 

 

 

but I could see the DRM node

 

 

 

root@imx8qmmek:/# drmdevice 
--- Checking the number of DRM device available ---
--- Devices reported 2 ---
--- Retrieving devices information (PCI device revision is ignored) ---
device[0]
+-> available_nodes 0x05
+-> nodes
|   +-> nodes[0] /dev/dri/card1
|   +-> nodes[2] /dev/dri/renderD129
+-> bustype 0002
|   +-> platform
|       +-> fullname	/display-subsystem
+-> deviceinfo
    +-> platform
        +-> compatible
                    fsl,imx-display-subsystem

--- Opening device node /dev/dri/card1 ---
--- Retrieving device info, for node /dev/dri/card1 ---
device[0]
+-> available_nodes 0x05
+-> nodes
|   +-> nodes[0] /dev/dri/card1
|   +-> nodes[2] /dev/dri/renderD129
+-> bustype 0002
|   +-> platform
|       +-> fullname	/display-subsystem
+-> deviceinfo
    +-> platform
        +-> compatible
                    fsl,imx-display-subsystem

--- Opening device node /dev/dri/renderD129 ---
--- Retrieving device info, for node /dev/dri/renderD129 ---
device[0]
+-> available_nodes 0x05
+-> nodes
|   +-> nodes[0] /dev/dri/card1
|   +-> nodes[2] /dev/dri/renderD129
+-> bustype 0002
|   +-> platform
|       +-> fullname	/display-subsystem
+-> deviceinfo
    +-> platform
        +-> compatible
                    fsl,imx-display-subsystem

device[1]
+-> available_nodes 0x05
+-> nodes
|   +-> nodes[0] /dev/dri/card0
|   +-> nodes[2] /dev/dri/renderD128
+-> bustype 0002
|   +-> platform
|       +-> fullname	/bus@54100000/imx8_gpu1_ss
+-> deviceinfo
    +-> platform
        +-> compatible
                    fsl,imx8qm-gpu
                    fsl,imx8-gpu-ss

--- Opening device node /dev/dri/card0 ---
--- Retrieving device info, for node /dev/dri/card0 ---
device[1]
+-> available_nodes 0x05
+-> nodes
|   +-> nodes[0] /dev/dri/card0
|   +-> nodes[2] /dev/dri/renderD128
+-> bustype 0002
|   +-> platform
|       +-> fullname	/bus@54100000/imx8_gpu1_ss
+-> deviceinfo
    +-> platform
        +-> compatible
                    fsl,imx8qm-gpu
                    fsl,imx8-gpu-ss

--- Opening device node /dev/dri/renderD128 ---
--- Retrieving device info, for node /dev/dri/renderD128 ---
device[1]
+-> available_nodes 0x05
+-> nodes
|   +-> nodes[0] /dev/dri/card0
|   +-> nodes[2] /dev/dri/renderD128
+-> bustype 0002
|   +-> platform
|       +-> fullname	/bus@54100000/imx8_gpu1_ss
+-> deviceinfo
    +-> platform
        +-> compatible
                    fsl,imx8qm-gpu
                    fsl,imx8-gpu-ss

root@imx8qmmek:/# 
root@imx8qmmek:/# ls /dev/dri/
by-path  card0	card1  renderD128  renderD129

 

 

 

 

a. linux 5.10.72_2.2.2, weston 9.0.0

 

 

 

 

root@imx8qmmek:~# cat /run/user/0/weston.log
Date: 2021-03-24 UTC
[10:25:24.779] weston 9.0.0
https://wayland.freedesktop.org
Bug reports to: https://gitlab.freedesktop.org/wayland/weston/issues/
Build: 9.0.0
[10:25:24.779] Command line: /usr/bin/weston --log=/run/user/0/weston.log --modules=systemd-notify.so
[10:25:24.779] OS: Linux, 5.10.72-lts-5.10.y+gc59614bdd6f6, #1 SMP PREEMPT Wed Jun 29 12:55:32 UTC 2022, aarch64
[10:25:24.782] Using config file '/etc/xdg/weston/weston.ini'
[10:25:24.787] Output repaint window is 16 ms maximum.
[10:25:24.788] Loading module '/usr/lib/libweston-9/drm-backend.so'
[10:25:24.802] initializing drm backend
[10:25:24.810] logind: session control granted
[10:25:24.828] no drm device found
[10:25:24.828] fatal: failed to create compositor backend

 

 

 

 

 

How can I launch the weston?

Tags (4)
0 Kudos
6 Replies

653 Views
Seokha
Contributor II

issue resolved by replacing u-boot device tree environment "imx8qm-mek-rpmsg.dtb" with "imx8qm-mek-hdmi.dtb".

BTW, why isn't "imx8qm-mek-hdmi.dtb" used by default?

0 Kudos

657 Views
Seokha
Contributor II

@Bio_TICFSL 

Could you please review my question?

0 Kudos

679 Views
Seokha
Contributor II

for more information.

There is no drm connector. I guess it's the root cause.
And I am using HDMI interface.

How can I handle this problem?

Do I need specific configurations to enable DRM? (kernel, u-boot arg etc)

 

5.15.32_2.0.0 (https://www.nxp.com/webapp/Download?colCode=L5.15.32_2.0.0_MX8QM&appType=license

 

 

 

 

root@imx8qmmek:~# ./drm-info /dev/dri/card0
Device /dev/dri/card0:
  Capabilities:
    DRM_CAP_DUMB_BUFFER: unknown
    DRM_CAP_VBLANK_HIGH_CRTC: unknown
    DRM_CAP_DUMB_PREFERRED_DEPTH: unknown
    DRM_CAP_DUMB_PREFER_SHADOW: unknown
    DRM_CAP_PRIME: 3

cannot retrieve DRM resources (95): Operation not supported



root@imx8qmmek:~# ./drm-info /dev/dri/card1
Device /dev/dri/card1:
  Capabilities:
    DRM_CAP_DUMB_BUFFER: 1
    DRM_CAP_VBLANK_HIGH_CRTC: 1
    DRM_CAP_DUMB_PREFERRED_DEPTH: 0
    DRM_CAP_DUMB_PREFER_SHADOW: 0
    DRM_CAP_PRIME: 3

  Resources:
    Width: 1 - 5120
    Height: 1 - 4096
    Framebuffers: 0
    CRTCs: 4
      CRTC 38:
        Dimensions: 0 x 0
        Buffer: 0
        Position: 0, 0
        Gamma size: 0
        Mode: (invalid)

      CRTC 67:
        Dimensions: 0 x 0
        Buffer: 0
        Position: 0, 0
        Gamma size: 0
        Mode: (invalid)

      CRTC 96:
        Dimensions: 0 x 0
        Buffer: 0
        Position: 0, 0
        Gamma size: 0
        Mode: (invalid)

      CRTC 125:
        Dimensions: 0 x 0
        Buffer: 0
        Position: 0, 0
        Gamma size: 0
        Mode: (invalid)

    Encoders: 0
    Connectors: 0

 

 

 

 

 

 

0 Kudos

704 Views
Seokha
Contributor II

For more information...

 

I also tried imx-5.15.5-1.0.0.xml, result was the same. (weston does not launch with error "no drm device found")

 

So, I have tested the following versions up to now, and Weston is not launched in all of them with the same error "no drm device found"

 

versions: 

- 5.15.32_2.0.0 (it's the latest version)

- 5.15.5_1.0.0

5.10.72_2.2.2

 

Build configurations

- DISTRO=fsl-imx-wayland

- MACHINE=imx8qmmek

- image name: imx-image-full

 

0 Kudos

714 Views
Bio_TICFSL
NXP TechSupport
NXP TechSupport

Hello,

Try a new kernel, and re-burn the SDcard.

 

Regards

0 Kudos

711 Views
Seokha
Contributor II

Thank you for your reply.

But I already tested official image 5.15.32_2.0.0 (https://www.nxp.com/webapp/Download?colCode=L5.15.32_2.0.0_MX8QM&appType=license) and yocto build by myself (https://source.codeaurora.org/external/imx/imx-manifest/log/?h=imx-linux-kirkstone based on https://www.nxp.com/docs/en/user-guide/IMX_YOCTO_PROJECT_USERS_GUIDE.pdf

 

I think these are the latest version, is there anything else?

0 Kudos