Hi, Need to add some more information, I find that weston.service cannot be started, but weston can be started by the command in /lib/systemd/system/weston.service manually: hikey960:~# systemctl status weston.service ● weston.service - Weston Wayland Compositor Loaded: loaded (/lib/systemd/system/weston.service; enabled; vendor preset: enabled) Active: failed (Result: protocol) since Tue 2018-12-25 05:59:35 UTC; 4min 14s ago Process: 20772 ExecStart=/usr/bin/weston --idle-time=0 --tty=1 --backend=drm-backend.so --log=/run/platform/display/weston.log (code=exited, status=1/FAILURE) Process: 20765 ExecStartPre=/usr/bin/chsmack -a User::App-Shared -t /run/platform/display/share (code=exited, status=0/SUCCESS) Process: 20764 ExecStartPre=/bin/mkdir -p /run/platform/display/share (code=exited, status=0/SUCCESS) Main PID: 20772 (code=exited, status=1/FAILURE) Dec 25 05:59:35 hikey960 systemd[1]: Starting Weston Wayland Compositor... Dec 25 05:59:35 hikey960 systemd[1]: weston.service: Main process exited, code=exited, status=1/FAILURE Dec 25 05:59:35 hikey960 systemd[1]: Failed to start Weston Wayland Compositor. Dec 25 05:59:35 hikey960 systemd[1]: weston.service: Unit entered failed state. Dec 25 05:59:35 hikey960 systemd[1]: weston.service: Failed with result 'protocol'. Thanks & Brs, Clive -----Original Message----- From: automotive-discussions-bounces@xxxxxxxxxxxxxxxxxxxxxxxxx [mailto:automotive-discussions-bounces@xxxxxxxxxxxxxxxxxxxxxxxxx] On Behalf Of Clive Xu (Arm Technology China) Sent: 2018年12月25日 13:22 To: Jan-Simon Moeller <jsmoeller@xxxxxxxxxxxxxxxxxxx>; José Bollo <jose.bollo@xxxxxxx>; Phong Tran <tranmanphong@xxxxxxxxx> Cc: AGL ml <automotive-discussions@xxxxxxxxxxxxxxxxxxxxxxxxx> Subject: Re: [agl-discussions] Cannot start afm-user-daemon.service Hi, Jan-Simon, Jose, Phong, Thanks very much for your suggestions, it really helps. I have tried to use meta-96boards and its patch to setup the AGL, it tooks some time to fix weston build errors and some DRM issues. Now, the weston can be started manually and displayed with following command - mkdir -p /tmp/wayland && chmod 0700 /tmp/wayland - XDG_RUNTIME_DIR=/tmp/wayland LD_LIBRARY_PATH="$LD_LIBRARY_PATH:/home/0/yocto_mali_libs/server:/usr/lib:/usr/local/lib" weston --tty=1 --backend=drm-backend.so --idle-time=0 *afm-util list* can show a lot of runnable widgets now, attached the list. I can start the widgets manually using following command: - systemctl restart run-agl-postinsts.service - afm-util start homescreen@0.1 - afm-util run launcher@0.1 *afm-util ps* shows nothing, but this command also shows nothing on *qemux86-64* which display the the AGL homescreen correctly. *ps -ef* shows afbd-homescreen-service, afbd-launcher and some other afbd services have started, attached the log of *ps -ef", but the widgets are not displayed on the screen, the journalctl log attached. Is there something wrong with my steps? Really appreciate your suggestions. Thanks & Brs, Clive -----Original Message----- From: automotive-discussions-bounces@xxxxxxxxxxxxxxxxxxxxxxxxx [mailto:automotive-discussions-bounces@xxxxxxxxxxxxxxxxxxxxxxxxx] On Behalf Of Jan-Simon Moeller Sent: 2018年12月18日 2:40 To: José Bollo <jose.bollo@xxxxxxx> Cc: AGL ml <automotive-discussions@xxxxxxxxxxxxxxxxxxxxxxxxx> Subject: Re: [agl-discussions] Cannot start afm-user-daemon.service Hi Clive! You might want to look at the dragoboard 410/820 support that is in the tree and do likewise. Best, Jan-Simon On Mon, Dec 17, 2018 at 1:11 PM José Bollo <jose.bollo@xxxxxxx> wrote: > > Hi Clive, > > In the journal I can read: > > [ 0.038955] Security Framework initialized > [ 0.043134] SELinux: Initializing. > [ 0.046731] SELinux: Starting in permissive mode > > AGL runs Smack LSM, not SELinux. > > Could you check how other BSP are made [1]? > > AGL use a setup script [2]. It allows to tune features. > > There is also a troubleshooting section there [3] > > Best regrds > José Bollo > > > [1] > https://gerrit.automotivelinux.org/gerrit/gitweb?p=AGL/meta-agl.git;a= > tree;f=meta-agl-bsp;h=a4948f62d2d65ed9e228bd5a2050cf71980c5136;hb=refs > /heads/master > > [2] > https://docs.automotivelinux.org/docs/getting_started/en/dev/reference > /source-code.html#set-up-build-environment-info > > [3] > https://docs.automotivelinux.org/docs/getting_started/en/dev/reference > /troubleshooting.html _______________________________________________ > automotive-discussions mailing list > automotive-discussions@xxxxxxxxxxxxxxxxxxxxxxxxx > https://lists.linuxfoundation.org/mailman/listinfo/automotive-discussi > ons _______________________________________________ automotive-discussions mailing list automotive-discussions@xxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linuxfoundation.org/mailman/listinfo/automotive-discussions IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you. IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
Attachment:
weston.service
Description: weston.service
Attachment:
weston_start_manually_successfully.log
Description: weston_start_manually_successfully.log
Attachment:
weston_systemctl_restart_failed.log
Description: weston_systemctl_restart_failed.log
_______________________________________________ automotive-discussions mailing list automotive-discussions@xxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linuxfoundation.org/mailman/listinfo/automotive-discussions
