Hi Alex,

On 13.08.2015 10:07, chengxuan liu wrote:
I am using Tizen 3.0 Common and the profile is wayland32.
Just to clarify: in this case the tizen version is 3.0 and the profile is called Common.
Mali DDK has been installed indeed. I wonder why it can not start up when the system boots up. Every time I have to start the weston manually.
If you are able to start it manually then just use the same command and adjust ExecStart of systemd service display-manager-run.

Best regards,
Leon


Best regards.
Alex


2015-08-13 14:28 GMT+08:00 Leon Anavi <[email protected] <mailto:[email protected]>>:

    Hi Alex,

    On 13.08.2015 08:48, chengxuan liu wrote:
    Hi, Leon
    The target device I use is exynos OdroidX2. The weston.log is
    like the following:
    [20:07:37.799] weston 1.7.0
    http://wayland.freedesktop.org
                   Bug reports to:
    
https://bugs.freedesktop.org/enter_bug.cgi?product=Wayland&component=weston&version=1.7.0
                   Build: unknown (not built from git or tarball)
    [20:07:37.815] OS: Linux, 3.10.60-dirty, #86 SMP PREEMPT Thu Jul
    23 14:18:11 CST 2015, armv7l
    [20:07:37.815] warning: XDG_RUNTIME_DIR "/run/display" is not
    configured
    correctly.  Unix access mode must be 0700 (current mode is 770),
    and must be owned by the user (current owner is UID 381).
    Refer to your distribution on how to get it, or
    http://www.freedesktop.org/wiki/Specifications/basedir-spec
    on how to implement it.
    [20:07:37.860] Using config file '/etc/xdg/weston/weston.ini'
    [20:07:37.875] Loading module '/usr/lib/weston/drm-backend.so'
    [20:07:38.061] initializing drm backend
    [20:07:38.089] fatal: drm backend should be run using
    weston-launch binary or as root
    [20:07:38.089] fatal: failed to create compositor

    The UID 381 corresponds to the display user. And if i use the
    original weston within the tizen image, the weston is ok.
    Any ideas?

    Which Tizen image and profile are you using?

    Have you installed Mali DDK for hardware graphics acceleration in
    Wayland and Weston?

    You can find its version for Tizen 3.0 here:
    https://source.tizen.org/mali-ddk-tizen-3.0-wayland-enabled
    As far as I remember this Mali DDK was appropriate for Odroid-U3
    which seems to have the same SoC, Exynos 4412, as Odroid-X2.

    Alternatively, without hardware graphics acceleration, you can try
    starting weston with frame buffer support using the following
    configuration for its backend: --backend=fbdev-backend.so In this
    case Weston should work but Crosswalk and HTML5 applications will
    not work.

    Best regards,
    Leon

    P.S. Always keep the address of the mailing list in CC. This way
    the discussion is transparent and more people can get involved.

    Thanks
    Alex

    2015-08-13 13:36 GMT+08:00 Leon Anavi <[email protected]
    <mailto:[email protected]>>:

        Hi Alex,

        On 13.08.2015 06:31, chengxuan liu wrote:

            Hi,
            recently I compiled the Wayland and Weston source on the
            Tizen environment and installed them then. However, the
            Weston could not be launched automatically when the
            system booted up. And if i launched it manually, it was
            ok. So, I think it may be the authority problem. Has
            anyone encountered this?

            And i used the systemctl to check the
            display-manager-run.service,got the following information:

            * display-manager-run.service - Weston display daemon
               Loaded: loaded
            (/usr/lib/systemd/system/display-manager-run.service;
            enabled; vendor preset: enabled)
               Active: activating (auto-restart) (Result: exit-code)
            since Wed 2015-08-12 20:27:01 PDT; 6s ago
              Process: 1673 ExecStart=/bin/sh -c backend=drm ; [ -d
            /dev/dri ] || backend=fbdev ; exec /usr/bin/weston
            --backend=$backend-backend.so -i0
            --log=/run/%u/weston.log (code=exited, status=1/FAILURE)
             Main PID: 1673 (code=exited, status=1/FAILURE)
               Memory: 0B
               CGroup: /system.slice/display-manager-run.service


        According to the status of display-manager-run.service weston
        fails to start. Check weston.log for details. It might be
        something related to the hardware graphics acceleration.

        On what device are you trying to run Tizen and Weston?

        Best regards,
        Leon

-- Leon Anavi
        Software Engineer
        konsulko.com <http://konsulko.com>



-- Leon Anavi
    Software Engineer
    konsulko.com  <http://konsulko.com>



--
Leon Anavi
Software Engineer
konsulko.com

_______________________________________________
Dev mailing list
[email protected]
https://lists.tizen.org/listinfo/dev

Reply via email to