Hi,
Thanks all for this nice product. I am starting to use RuneAudio on a RPI2. I experience a strange thing: when starting up the RPI2, it takes more then 90 seconds before I can contact the RPI2 via the browser. A ping is working nearly immediately after the power-up. I am using a wired Ethernet-connection and no WiFi-dongle.
I checked the log-files, in which I can see that the RPI2 is waiting on a wlan0-interface. After 96 seconds, it gives a time-out, after which everything is working perfectly.
[ 9.765622] systemd[1]: Started Network Name Resolution.
[ 11.087582] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0xC5E1
[ 11.093616] systemd-networkd[184]: eth0 : gained carrier
[ 11.107860] systemd-networkd[184]: eth0 : could not start IPv6 router discovery
[ 11.107916] systemd-networkd[184]: eth0 : failed
[ 96.252130] systemd[1]: Job sys-subsystem-net-devices-wlan0.device/start timed out.
[ 96.252249] systemd[1]: Timed out waiting for device sys-subsystem-net-devices-wlan0.device.
[ 96.252401] systemd[1]: Dependency failed for Automatic wireless network connection using netctl profiles.
I tried to find somewhere a configuration-file in which a wlan0 is asked to start, but I couldn’t find such a file.
Does anyone knows how I can get rid of those 90 seconds-delay?
On a RPI B+, I didn’t have that problem.
Regards, Frank M.
debug-log:
http://pastebin.com/x20mqkMK