Pi 2 won't boot after update

[pottzie]

I installed arch on a Pi2 a few days ago, and it was working great. Did an update today, and after rebooting, it failed to boot. Thought the card might be corrupted, so I wiped the micro sd card and reinstalled. Put the card in the Pi and it loaded and worked great. I then ran pacman -Syyu, and after the update rebooted. It failed to boot again, and stopped with the same error, " Entering kdb, pid1 on processor 2 due to Keyboard entry "

And is there a way I can fix it or run fdisk with the micro sd card inserted on another (Fedora) computer?

[WarheadsSE]

What do you have hooked up to it? It looks like it is seeing spurious keyboard input ...

[jlm]

I am having a similar problem. After a pacman -Syu, my 2 RPi2 are unreachable (ie. do not respond to ping). Upgraded around 13:00 CEST on April 21th.

Nothing but network and power attached, and verified the issue on a almost new RPi (running fine on the April 1 images, and unreachable after a pacman -Syu).

[pottzie]

WarheadsSE, the error shown is what's on my screen after a second attempt at rebooting. The first time I rebooted, there were a bunch of I/O errors, but it did report the keyboard as OK, even showing that it recognized the brand. I'll swap keyboards and see if that does anything, but I'm not expecting much to change.

[cremersdh]

If it does not boot I can not help you, but if you only lost network connectivity you probably have the same problem as I did.

After the update my network was not functioning anymore. It was easily solved by removing "ipv6.disable=1" from your kernel parameters. It seems to be a bug in the update of yesterday where having this kernel parameter will disable your network interface completely.

Maybe it would help you 2

[cremersdh]

ps see https://bugs.freedesktop.org/show_bug.cgi?id=90103

[jlm]

An update: my Rpi2 does boot. It is, however, running headless and I have no hardware present to attach a console to the serial port.

@cremersdh: there is no ipv6.disable in my kernel parameters, so there is nothing to remove. Finally, I tried to ssh to the RPi using the inet6 address instead of the inet4 address. And this works So, thanks for the hint towards IPV6.

Conclusion: on my RPi, running the "alarm/raspberrypi-firmware to 20150422-1" stuff, only the inet6 is up, and the inet4 is not.

[postblue]

I have the exact same problem as @jim, unless my router doesn't support IPV6, so I'm stuck (I'll check if it's possible to assign an IPV6 adress if I share my connection by the Ethernet port of my laptop). Is there any update fixing the problem yet?

EDIT: Hopefully I installed and configured avahi and nss-mdns, so I was able to SSH to mymachine.local.

[rinkaenbyou]

Downgrading systemd, libsystemd and systemd-sysvcompat to version 218-2 fixed it for me.

[jlm]

As can be seen above, I also had problems. I even filed a bug report relating it to systemd, but that came back immediately as "not reproducible". And that was right. I seemed to be a (setup?) error on my dhcp server. Apparently, the upgrade of systemd revealed that issue.

I'm using a Fritzbox modem and I read a message in the IRC that there was another user having similar issues, and was also using a Fritzbox. We might have found a bug in the FritzOS.

Having said this. I'm currently running the 219-6 systemd without any issue, so I'm convinced (now) that it is not an issue with systemd.