As part of our automation efforts, we've recently added a battery of log tests on all boards. We are unsure if the following messages are valid for jasperforest. Please let us know if they can be safely ignored. *********************** | Log: /var/log//daemon.log | ----------------------- Mar 30 07:12:04 genericx86-64 dbus[687]: [system] Activating service name='org.bluez' (using servicehelper) Mar 30 07:12:04 genericx86-64 dbus[687]: [system] Activated service 'org.bluez' failed: Launch helper exited with unknown return code 1 Mar 30 07:12:04 genericx86-64 neard[826]: NEAR daemon version 0.14 Mar 30 07:12:04 genericx86-64 neard[826]: Unable to find NFC netlink family Mar 30 07:12:04 genericx86-64 neard[826]: netlink init failed Mar 30 07:12:04 genericx86-64 neard[826]: *** NETLINK INITIALIZATION FAILED *** Mar 30 07:12:42 genericx86-64 avahi-daemon[814]: Joining mDNS multicast group on interface eth0.IPv4 with address 169.254.108.93. Mar 30 07:12:42 genericx86-64 avahi-daemon[814]: New relevant interface eth0.IPv4 for mDNS. Mar 30 07:12:42 genericx86-64 avahi-daemon[814]: Registering new address record for 169.254.108.93 on eth0.IPv4.
Well, it certainly doesn't surprise me that there is no NFC on a Jasper Forest :-) On a genericx86-64 system, these sorts of *warnings* are going to be common as we enable more than is present on any one particular board. I'd ask Ross Burton to confirm, but I'd be inclined to close this as NOT A BUG.
Yep, neard failing to find NFC devices is expected on hardware without NFC support. NFC is enabled because Poky has NFC enabled at the distro level, and you can add a USB NFC reader. These errors should be whitelisted, or you should get a USB NFC reader for enhanced testing. :)
Before we close this we need to whitelist the error since none of the platforms we test on have this hardware, thus the error is expected. Mihail could you take care of that?
My colleague Lucian is handling the actual whitelisting, so assigning to him.
Errors were added to the whitelist. Closing this.