On Tue, 9 Oct 2018 21:33:53 +0000 Marc Murphy <marc.murphy@xxxxxxxxxxxxxx> wrote: > Ok now I have the system booting to a login prompt. > > The mmcblkp1 issue was a dodgy line in fstab... currently commented > out as not needed. > > Now the question is how to get the app up and running? Hi Marc, The log is correct. The audit message are reminder to "work in progress" issues. So you should see on the screen what is called the "homescreen". It is what is used to start applications. If you don't see the homescreen you have to check what's wrong. You should start by issuing the following command and check for reported errors. $ systemctl status *homescreen* *window* I attached the output for my running system. Best regards José Bollo > Bootlog now looks like; > [ 18.322913] Bluetooth: SCO socket layer initialized > [ 18.376561] usbcore: registered new interface driver btusb > [ 18.384646] Bluetooth: hci0: rtl: examining hci_ver=06 > hci_rev=000b lmp_ver=06 lmp_subver=8723 [ 18.393506] Bluetooth: > hci0: rtl: loading rtl_bt/rtl8723b_config.bin [ 18.400053] > bluetooth hci0: Direct firmware load for rtl_bt/rtl8723b_config.bin > failed with error -2 [ 18.411864] Bluetooth: hci0: Failed to load > rtl_bt/rtl8723b_config.bin [ 18.419071] Bluetooth: hci0: rtl: > loading rtl_bt/rtl8723b_fw.bin [ 18.425239] bluetooth hci0: Direct > firmware load for rtl_bt/rtl8723b_fw.bin failed with error -2 > [ 18.434097] Bluetooth: hci0: Failed to load rtl_bt/rtl8723b_fw.bin > [ OK ] Listening on Load/Save RF Kill Switch Status /dev/rfkill > Watch. [ OK ] Reached target Sockets. [ OK ] Reached target Basic > System. Starting neard service... Starting Save/Restore Sound Card > State... Starting Modem Manager... > Starting Telephony service... > [ OK ] Started D-Bus System Message Bus. > [ 20.410229] nfc: nfc_init: NFC Core ver 0.1 > [ 20.431933] NET: Registered protocol family 39 > [ OK ] Started neard service. > [ OK ] Started Telephony service. > Starting Connection service... > [ OK ] Started Hardware RNG Entropy Gatherer Daemon. > [ 20.620554] random: crng init done > Starting Start the security manager... > Starting Driver configuration for Unicens2... > Starting Initiate afm-system-setup... > [ OK ] Started System Logging Service. > Starting Login Service... > Starting Terminate Psplash Boot Screen... > [ OK ] Started Kernel Logging Service. > Starting Bluetooth service... > [ OK ] Reached target Containers. > Starting Disk Manager (legacy version)... > Starting Avahi mDNS/DNS-SD Stack... > [ OK ] Reached target cynara sockets. > Starting Cynara service... > [ OK ] Started Network Service. > [ OK ] Started Start the security manager. > [ OK ] Started Save/Restore Sound Card State. > [FAILED] Failed to start Driver configuration for Unicens2. > See 'systemctl status unicens-config.service' for details. > [ OK ] Started Terminate Psplash Boot Screen. > [ 21.627164] net eth0: initializing cpsw version 1.12 (0) > [ 21.695256] cpsw 4a100000.ethernet: initialized cpsw ale version > 1.4 [ 21.701658] cpsw 4a100000.ethernet: ALE Table size 1024 > [ 21.714221] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 > [ 21.714227] Bluetooth: BNEP filters: protocol multicast > [ 21.714249] Bluetooth: BNEP socket layer initialized > [ OK ] Started Connection service. > [ OK ] Started Cynara service. > [ 21.963003] Atheros 8035 ethernet 4a101000.mdio:00: attached PHY > driver [Atheros 8035 ethernet] (mii_bus:phy_addr=4a101000.mdio:00, > irq=-1) [ 21.995379] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not > ready [ OK ] Started Bluetooth service. [ OK ] Started Avahi > mDNS/DNS-SD Stack. [ OK ] Started Disk Manager (legacy version). > [ OK ] Started Login Service. > [ OK ] Started Automount Disk Manager. > [ OK ] Reached target Bluetooth. > [ OK ] Started Bluetooth Audio ALSA Backend. > Starting Hostname Service... > Starting WPA supplicant... > Starting Authorization Manager... > Starting Load/Save RF Kill Switch Status... > [ OK ] Reached target Sound Card. > [ OK ] Started Initiate afm-system-setup. > Starting Weston Wayland Compositor... > [ OK ] Started Application Framework Master, system side. > [ OK ] Started Load/Save RF Kill Switch Status. > [ OK ] Started WPA supplicant. > [ OK ] Reached target Network. > Starting Permit User Sessions... > Starting Berkeley Internet Name Domain (DNS)... > [ OK ] Started Hostname Service. > [ OK ] Started Permit User Sessions. > [ OK ] Started Serial Getty on ttyS0. > [ OK ] Reached target Login Prompts. > [ OK ] Started Initiate afm-user-session 0. > [ 23.816423] audit: type=1006 audit(1539033327.180:2): pid=434 > uid=0 subj=System old-auid=4294967295 auid=0 tty=(none) > old-ses=4294967295 ses=1 res=1 [ OK ] Started Authorization > Manager. [ OK ] Created slice User Slice of root. Starting User > Manager for UID 0... [ OK ] Started Session 1 of user root. > [ 24.722806] audit: type=1006 audit(1539033328.090:3): pid=445 > uid=0 subj=System old-auid=4294967295 auid=0 tty=(none) > old-ses=4294967295 ses=2 res=1 [ 24.849378] audit: type=1400 > audit(1539033328.210:4): lsm=SMACK fn=smack_key_permission > action=denied subject="System" object="_" requested=w pid=445 > comm="(systemd)" key_serial=450447809 > key_desc="_uid.0" [ 24.920244] audit: type=1400 > audit(1539033328.280:5): lsm=SMACK fn=smack_inode_permission > action=denied subject="System" object="_" requested=w pid=437 > comm="named" name="bind" dev="mmcblk0p2" ino=27178 [ 24.920326] > audit: type=1300 audit(1539033328.280:5): arch=40000028 syscall=33 > per=800000 success=no exit=-13 a0=48dfdc a1=2 a2=558f2b00 a3=558f2b00 > items=0 ppid=432 pid=437 auid=4294967295 uid=987 gid=987 euid=987 > suid=987 fsuid=987 egid=987 sgid=987 fsgid=987 tty=(none) > ses=4294967295 comm="named" exe="/usr/sbin/named" subj=System > key=(null) [ 24.920384] audit: type=1327 audit(1539033328.280:5): > proctitle=2F7573722F7362696E2F6E616D6564002D750062696E64 [ OK ] > Started Modem Manager. [ 25.477327] audit: type=1300 > audit(1539033328.210:4): arch=40000028 syscall=311 per=800000 > success=no exit=-13 a0=8 a1=fffffffc a2=fffffffd a3=0 items=0 ppid=1 > pid=445 auid=0 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 > fsgid=0 tty=(none) ses=2 comm="(systemd)" exe="/lib/systemd/systemd" > subj=System key=(null) [ OK ] Started Weston Wayland Compositor. > [ 25.698196] audit: type=1327 audit(1539033328.210:4): > proctitle="(systemd)" [ OK ] Started Berkeley Internet Name Domain > (DNS). [ OK ] Reached target Host and Network Name Lookups. > [ OK ] Reached target Multi-User System. Starting Update UTMP about > System Runlevel Changes... [ 26.163550] cpsw 4a100000.ethernet > eth0: Link is Up - 1Gbps/Full - flow control rx/tx [ 26.171500] > IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [ OK ] > Started Update UTMP about System Runlevel Changes. [ 26.353379] > 8021q: 802.1Q VLAN Support v1.8 [ 26.380143] 8021q: adding VLAN 0 > to HW filter on device eth0 > > Automotive Grade Linux 6.0.0 beaglebone ttyS0 > > > Thanks > Marc > > > From: automotive-discussions-bounces@xxxxxxxxxxxxxxxxxxxxxxxxx > [mailto:automotive-discussions-bounces@xxxxxxxxxxxxxxxxxxxxxxxxx] On > Behalf Of Marc Murphy Sent: 09 October 2018 10:40 To: > automotive-discussions@xxxxxxxxxxxxxxxxxxxxxxxxx Subject: > Flounder demo > > Hello All > I have managed to get a build of Flounder booting on our BBE board > (based on a beaglebone black) and would like to know if there are any > setup requirements to get the demo application to launch. > > On boot most services seem to start, we get the psplash screen and > some messages scrolling on the progress bar. Watson application > doesn't seem to be started. Is there a filesystem or hardware > requirement for it to start? > > Last part of the boot log causes the system to go into recovery mode; > > [ OK ] Listening on Load/Save RF Kill Switch Status /dev/rfkill > Watch. Starting Load/Save RF Kill Switch Status... > [ OK ] Started Load/Save RF Kill Switch Status. > [*** ] A start job is running for dev-mmcblkp1.device (33s / 1min > 30s)[ 37.322585] random: crng init done [ TIME ] Timed out waiting > for device dev-mmcblkp1.device. [DEPEND] Dependency failed for /boot. > [DEPEND] Dependency failed for Local File Systems. > [ OK ] Closed Syslog Socket. > [ OK ] Reached target Login Prompts. > Starting Network Service... > [ OK ] Reached target Host and Network Name Lookups. > [ OK ] Reached target Bluetooth. > [ OK ] Reached target Sound Card. > [ OK ] Reached target cynara sockets. > [ OK ] Reached target Sockets. > Starting Rebuild Journal Catalog... > Starting Rebuild Dynamic Linker Cache... > [ OK ] Started Emergency Shell. > Starting Create Volatile Files and Directories... > [ OK ] Reached target Emergency Mode. > [ OK ] Reached target Timers. > [ OK ] Started Network Service. > [ OK ] Started Rebuild Journal Catalog. > [ OK ] Reached target Network. > [ OK ] Started Create Volatile Files and Directories. > Starting Update UTMP about System Boot/Shutdown... > [ OK ] Started Rebuild Dynamic Linker Cache. > [ OK ] Started Update UTMP about System Boot/Shutdown. > Starting Update UTMP about System Runlevel Changes... > Starting Update is Completed... > [ OK ] Started Update is Completed. > [ OK ] Started Update UTMP about System Runlevel Changes. > You are in emergency mode. After logging in, type "journalctl -xb" to > view system logs, "systemctl reboot" to reboot, "systemctl default" > or ^D to boot into default mode. > Press Enter for maintenance > (or press Control-D to continue): > > > Wondering why it would be waiting for dev-mmcblkp1.device. and what > is supposed to be on it ? > > Kind Regards > Marc
Attachment:
output
Description: Binary data
_______________________________________________ automotive-discussions mailing list automotive-discussions@xxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linuxfoundation.org/mailman/listinfo/automotive-discussions
