Pi 2 won't boot after update

[rinkaenbyou]

I also think it isn't a problem in systemd per se, as it is running fine on 3 other machines running archlinux just fine with version 219.
I'm running on a Fritzbox as well, but the only client that makes troubles is the raspberrypi with alarm.
Has anyone an idea what could be the problem?
I mean manually bringing the ipv4 interface up works fine, and it seems to get an ipv6 address as well.

[WarheadsSE]

Yup. Problems we've been hearing with this. We've brought it to the attention of the systemd devs, and are working on a fix ourselves. However. this does not happen to everyone.

[makoven]

Cubieboard 2. Same problem

viewtopic.php?f=60&t=8777

[Syncopated]

Cubieboard 2, too. I lost network connection to the device a few hours ago after pacman -Syu. On top of that I had never enabled HDMI and didn't manage to for some reason. (I tried making some mali.conf file on the device's microSD from an Arch Linux x86 machine, but to no avail.)

In the end, I mounted the Cubieboard 2's microSD on another, working, ArchLinux ARM device and used pacman with -r, -b, --config, and --logfile options to -U the systemd, libsystemd and systemd-sysvcompat back to 218. At first I tried the same from the Arch Linux x86 machine but learnt that pacman doesn't work across architectures, so I had to use my still-working Arch Linux ARM device.

My journal shows this from the unsuccessful boot after the update:

$this->bbcode_second_pass_code('', 'Apr 30 00:50:07 cave systemd-networkd[102]: Enumeration completed
Apr 30 00:50:07 cave systemd-networkd[102]: eth0 : eth0 : could not bring up interface: Operation not supported
Apr 30 00:50:07 cave systemd[1]: Started Network Service.
-- Subject: Unit systemd-networkd.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit systemd-networkd.service has finished starting up.
')

I don't know where to look to investigate the "Operation not supported".

That was a very bad experience wasting 3 hours of time. I hope for a fix soon. Meanwhile, I'm staying away from pacman upgrading. I hope everyone beware of this and avoid wasting time on this problem until the fix appears.

[yershov]

I have BBB, the eth0 was unresponsive after recent update.

The journal also shows $this->bbcode_second_pass_code('', ' systemd-networkd[10*]: eth0 : eth0 : could not bring up interface: Operation not supported') at every boot.

I've enabled ethernet over usb0 by creating 2 files: '/etc/modules-load.d/g_ether.conf' with
$this->bbcode_second_pass_code('', 'g_ether')
and 'cat /etc/systemd/network/usb0.network' with
$this->bbcode_second_pass_code('', '
[Match]
Name=usb0

[Network]
Address=192.168.10.2/24
')

Now, systemd-networkd cannot bring up both eth0 and usb0 interfaces with the same message.

Enabling 'Environment=SYSTEMD_LOG_LEVEL=debug' in '/usr/lib/systemd/system/systemd-networkd.service' provides a bit more information to the journal
$this->bbcode_second_pass_code('', '
Apr 27 22:34:19 alarm systemd-networkd[146]: usb0 : flags change: +MULTICAST +BROADCAST
Apr 27 22:34:19 alarm systemd-networkd[146]: usb0 : link 3 added
Apr 27 22:34:19 alarm systemd-networkd[146]: device 0xb6ffc790 has devpath '/devices/ocp.3/47400000.usb/musb-hdrc.0.auto/gadget/net/usb0'
Apr 27 22:34:19 alarm systemd-networkd[146]: usb0 : link pending udev initialization...
Apr 27 22:34:19 alarm systemd-networkd[146]: usb0 : saved original MTU: 1500
Apr 27 22:34:19 alarm systemd-networkd[146]: eth0 : flags change: +MULTICAST +BROADCAST
Apr 27 22:34:19 alarm systemd-networkd[146]: eth0 : link 2 added
Apr 27 22:34:19 alarm systemd-networkd[146]: device 0xb6ffc918 has devpath '/devices/ocp.3/4a100000.ethernet/net/eth0'
Apr 27 22:34:19 alarm systemd-networkd[146]: eth0 : link pending udev initialization...
Apr 27 22:34:19 alarm systemd-networkd[146]: eth0 : saved original MTU: 1500
Apr 27 22:34:19 alarm systemd-networkd[146]: usb0 : usb0 : could not bring up interface: Operation not supported
Apr 27 22:34:19 alarm systemd-networkd[146]: usb0 : link configured
Apr 27 22:34:19 alarm systemd-networkd[152]: usb0 : usb0 : could not bring up interface: Operation not supported
Apr 27 22:34:19 alarm systemd-networkd[152]: usb0 : link configured
Apr 27 22:34:19 alarm systemd-networkd[146]: usb0 : udev initialized link
Apr 27 22:34:19 alarm systemd-networkd[146]: usb0 : link state is up-to-date
Apr 27 22:34:19 alarm systemd-networkd[146]: usb0 : found matching network '/etc/systemd/network/usb0.network'
Apr 27 22:34:19 alarm systemd-networkd[146]: usb0 : bringing link up
Apr 27 22:34:19 alarm systemd-networkd[146]: usb0 : setting addresses
Apr 27 22:34:19 alarm systemd-networkd[146]: usb0 : usb0 : could not bring up interface: Operation not supported
Apr 27 22:34:19 alarm systemd-networkd[146]: usb0 : Adding address: 192.168.10.2/24 (valid for (null))
Apr 27 22:34:20 alarm systemd-networkd[146]: usb0 : addresses set
Apr 27 22:34:20 alarm systemd-networkd[146]: usb0 : link configured
Apr 27 22:34:20 alarm systemd-networkd[149]: usb0 : usb0 : could not bring up interface: Operation not supported
Apr 27 22:34:20 alarm systemd-networkd[149]: usb0 : link configured
Apr 27 22:34:20 alarm systemd-networkd[146]: eth0 : eth0 : could not bring up interface: Operation not supported
Apr 27 22:34:20 alarm systemd-networkd[146]: eth0 : udev initialized link
Apr 27 22:34:20 alarm systemd-networkd[146]: eth0 : link state is up-to-date
Apr 27 22:34:20 alarm systemd-networkd[146]: eth0 : found matching network '/etc/systemd/network/eth0.network'
Apr 27 22:34:20 alarm systemd-networkd[146]: eth0 : bringing link up
Apr 27 22:34:20 alarm systemd-networkd[146]: eth0 : eth0 : could not bring up interface: Operation not supported
Apr 27 22:34:20 alarm systemd-networkd[144]: eth0 : eth0 : could not bring up interface: Operation not supported
Apr 27 22:34:20 alarm systemd-networkd[148]: eth0 : eth0 : could not bring up interface: Operation not supported
Apr 27 22:34:20 alarm systemd-networkd[149]: eth0 : eth0 : could not bring up interface: Operation not supported
Apr 27 22:34:20 alarm systemd-networkd[152]: eth0 : eth0 : could not bring up interface: Operation not supported
Apr 27 22:34:20 alarm systemd-networkd[146]: eth0 : eth0 : could not bring up interface: Operation not supported
')

[yershov]

Some update from my BBB install.
I've downgraded to
$this->bbcode_second_pass_code('', '
systemd-218-2-armv7h
systemd-sysvcompat-218-2-armv7h
netctl-1.10-1-any
')
and now everything is back to normal.

[moonman]

@yershov what kernel are you running? No problem with 4.0 here, but 3.8 had the same problem. Might be kernel related.

[yershov]

@moonman: you are right, I am running 3.8.

Question: if 'pacman -Syu' does not upgrade the kernel, then what are my next best option? I would appreciate any guide on that.

[sheevaplugger]

I have the same probleme on my odroid-c1. After updating systemd to 219-6 I'm not able the connect to the device over ssh.

viewtopic.php?f=63&t=8803&hilit=systemd

I can not downgrade because I don't have the previous version on my system.

[sheevaplugger]

I can confirm that the problem has something to do with the FritzBox.

When I use another router my odroid-c1 is available over ethernet.