• State Resolved
  • Locked Locked
  • Replies 6 replies
  • Answers 1 answer
  • Subscribers 102 subscribers
  • Views 2452 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Linux/DRA71XEVM: weston failed

user5067720
Prodigy 120 points
Part Number: DRA71XEVM

Tool/software: Linux

Hi TI,

Error occurred when running weston --tty=1 --backend=drm-backend.so

sdk: ti-processor-sdk-linux-automotive-dra7xx-evm-03.03.00.03-installer

kernel:4.4.84

log:

root@dra7xx-evm:~# weston --tty=1 --backend=drm-backend.so
Date: 2017-08-31 UTC
[07:31:04.993] weston 1.9.0
               http://wayland.freedesktop.org
               Bug reports to: bugs.freedesktop.org/enter_bug.cgi
               Build: 1.8.93-2-gb05cdb8 configure.ac: bump to version 1.9.0 for the official release (2015-09-21 18:11:26 -0700)
[07:31:04.999] OS: Linux, 4.4.84-dirty, #37 SMP PREEMPT Thu Dec 28 11:32:08 CST 2017, armv7l
[07:31:05.000] Using config file '/etc//weston.ini'
[07:31:05.000] Loading module '/usr/lib/weston/drm-backend.so'
[07:31:05.015] Output repaint window is 7 ms maximum.
[07:31:05.015] initializing drm backend
[07:31:05.025] using /dev/dri/card0
[07:31:05.026] Loading module '/usr/lib/weston/gl-renderer.so'
failed to load module: /usr/lib/gbm/gbm_dri.so: cannot open shared object file: No such file or directory
failed to load module: /usr/lib/gbm/gbm_gallium_drm.so: cannot open shared object file: No such file or directory
loaded module : gbm_pvr.so
found valid GBM backend : gbm_pvr.so
[07:31:05.040] warning: either no EGL_EXT_platform_base support or specific platform support; falling back to eglGetDisplay.
PVR:(Error): OpenServices: PVRDRMOpenRender failed [0, ]
PVR:(Error): PVRSRVConnect: Unable to open connection. [0, ]
PVR:(Error): Couldn't connect to services [0, ]
[07:31:05.044] failed to initialize display
[07:31:05.044] EGL error state: EGL_BAD_ALLOC (0x3003)
[07:31:05.044] failed to initialize egl
[07:31:05.045] fatal: failed to create compositor backend

thanks!

  • 0
    TI__Expert 4885 points
    Hi, ,

    Your query has been forwarded to an expert to comment directly here.

    Regards,
    Mariya
  • 0 in reply to Mariya Petkova
    TI__Expert 7015 points

    Can you post the output when you run kmscube?

  • 0 in reply to Subhajit Paul
    Prodigy 120 points

    Hi paul,

    There was nothing display on the lcd panel when running kmscube, but it can display gray level when running kmstest.

    root@dra7xx-evm:~# kmscube
    trying to load module omapdrm...success.
    no connected connector!
    failed to initialize DRM

    root@dra7xx-evm:~# kmstest
    Connector 0/@32: HDMI-A-1
      Crtc 0/@34 (plane 0/@33): 1920x1080 145.200 1920/140/20/120 1080/10/4/6 60 (60.00) 0x1a00000a 0x48
        Fb 40 1920x1080-XR24
    press enter to exit

    root@dra7xx-evm:~# kmsprint
    Connector 0 (32) HDMI-A-1 (connected)
      Encoder 0 (31) TMDS

    root@dra7xx-evm:~# modetest
    trying to open device 'i915'...failed
    trying to open device 'radeon'...failed
    trying to open device 'nouveau'...failed
    trying to open device 'vmwgfx'...failed
    trying to open device 'omapdrm'...done
    Encoders:
    id      crtc    type    possible crtcs  possible clones
    31      0       TMDS    0x00000001      0x00000000

    Connectors:
    id      encoder status          name            size (mm)       modes   encoders
    32      0       unknown HDMI-A-1        0x0             1       31
      modes:
            name refresh (Hz) hdisp hss hse htot vdisp vss vse vtot)
      1920x1080 60 1920 2060 2080 2200 1080 1090 1094 1100 flags: nhsync, nvsync; type: preferred, driver





    thanks!

  • 0 in reply to user5067720
    TI__Expert 7015 points
    Your modetest output shows the connector, encoder and crtc are not linked by default. Do you have a login screen on the LCD when the system boots up? Does your LCD backlight turn on during boot up?

    You can modify kmscube source code (function init_drm()) so that it does not search for connector based on encoder and crtc. You can statically define the connector ID and crtc ID to be used in drmModeSetCrtc and see if you can see a spinning cube

    Regards,
    Siubhajit
  • 0 in reply to Subhajit Paul
    Prodigy 120 points
    Hi Paul,

    Are there any shell commands or omap tools to statically define the connector ID and crtc ID ?

    thanks!
  • 0 in reply to user5067720
    TI__Mastermind 42515 points
    Hi,

    you should be able to pass the connector id to kmscube with "-c" option. See this wiki for example:
    processors.wiki.ti.com/index.php

    Regards,
    Yordan