weston sometime fails to start using systemd unit file

[Matt Hoosier]

Hi;

I think that you might rather have more success if you just instruct your
weston.service unit file that Weston isn't allowed to start until the DRI
device appears. E.g.,

  [Unit]
  ...
  Requires=dev-dri-card0.device # or dev-drm-card0.device as appropriate
for your board
  After=dev-dri-card0.device

Just make sure to put TAG+="systemd" in your UDev rule that handles the J6
DRI driver.

On Wed, Jan 18, 2017 at 7:22 AM, Vikas Patil <vikasmpatil at gmail.com> wrote:

> Hi Daniel,
>
> Any clue/inputs after looking at the logs?
>
> Regards,
> Vikash
>
> On Wed, Jan 11, 2017 at 10:55 AM, Vikas Patil <vikasmpatil at gmail.com>
> wrote:
>
>> Hi Daniel,
>>
>> Thanks a lot for your quick reply. See comments below.
>>
>> On Tue, Jan 10, 2017 at 9:28 PM, Daniel Díaz Rodríguez <
>> daniel.diaz at linaro.org> wrote:
>>
>>> Hello!
>>>
>>>
>>> On 10 January 2017 at 06:39, Vikas Patil <vikasmpatil at gmail.com> wrote:
>>> >> We are starting weston (1.9.0) using below systemd unit file of type
>>> notify
>>> >> (backported sd_notify related changes from weston 1.11.0 to weston
>>> 1.9.0).
>>> >> It works well with i.MX6 (NXP, fbdev backend) based platform, however
>>> with
>>> >> Jacinto (TI, drm backend) based platform sometimes it fails to start
>>> and
>>> >> sometime it works after reboot. It always works if we start weston
>>> service
>>> >> manually after platform boots up using “systemctl”.
>>> >> Is there anyone encountered this issue? Any suggestion/inputs to fix
>>> this?
>>>
>>> > We have seen this, as the DRM device is not readily available by the
>>> > time Weston launches. Our service unit is a bit different [1], but the
>>> > approach that proved most convenient was to use this udev rule to call
>>> > for Weston:
>>>   > https://github.com/96boards/meta-96boards/blob/master/recipe
>>> s-graphics/wayland/weston-init/71-weston-drm.rules
>>> <https://github.com/96boards/meta-96boards/blob/master/recipes-graphics/wayland/weston-init/71-weston-drm.rules>
>>
>>
>> I have tried this udev rule and unfortunately it didn't help. I have
>> added the rule in "/etc/udev/rules.d/localextra.rules" file on target.
>> Then I have another service as below to trigger it.
>>
>> root at linux-1:~# cat /lib/systemd/system/udevd.service
>>
>> [Unit]
>> Description=udevd service
>> DefaultDependencies=false
>>
>> [Service]
>> Type=forking
>> ExecStart=/lib/systemd/systemd-udevd --daemon
>> ExecStartPost=/bin/udevadm test /sys/devices/platform/omapdrm.0/drm/card0
>>
>>  Attached here the weston log and service file when it fails. (what see
>> is , weston starts but within four or five seconds it stops)
>>
>> How could I find what issue/problem it is having? Is there any more logs
>> from systemd I need to enable?
>>
>>
>> Regards,
>> Vikash
>>
>>
>
> _______________________________________________
> wayland-devel mailing list
> wayland-devel at lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/wayland-devel
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/wayland-devel/attachments/20170202/42f3cb50/attachment.html>