I'm an arch/systemd novice. After building a Wandbaord img as per the installion guide I've booted it in qemu with:
$this->bbcode_second_pass_code('', 'qemu-system-arm -m 1024M -M vexpress-a9 -cpu cortex-a9 -kernel zImage3.13 -append "root=/dev/mmcblk0p1 rw rootfstype=ext4 console=ttyAMA0" -drive if=sd,cache=writeback,file=archwand.img -net nic -net tap,ifname=tap0,script=no ')
Using the default network set-up on the image (netctl-ifplugd@eth0.service) I went through the preliminary config of keyboard/locale/hostname/user addition etc. Installed htop without a system update , rebooted a couple of time and all was OK. Then after a pacman -Syu which brings in systemd 210-3 with some message about udev and network device which were not re-named, there is no network connection after a re-boot.
$this->bbcode_second_pass_code('', '
systemctl status netctl-ifplugd@eth0.service
netctl-ifplugd@eth0.service - Automatic wired network connection using netctl profiles
Loaded: loaded (/usr/lib/systemd/system/netctl-ifplugd@.service; enabled)
Active: inactive (dead)
Docs: man:netctl.special(7)
Mar 17 11:37:15 awand systemd[1]: Dependency failed for Automatic wired network connection using netctl profiles.')
The emualted nic is present and recognised:
$this->bbcode_second_pass_code('', 'ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN mode DEFAULT group default qlen 1000
link/ether 52:54:00:12:34:56 brd ff:ff:ff:ff:ff:ff
3: tunl0: <NOARP> mtu 0 qdisc noop state DOWN mode DEFAULT group default
link/ipip 0.0.0.0 brd 0.0.0.0')
I made no changes to the default network settings in the wandboard image. Nothing to confilct that I know of and there are no rules in /etc/udev/rules.d.
A manual "dhcpcd eth0" brings the eth0 interface up
Any ideas why the systemd update should render it non-working?