Cubieboard 2 stopped working after update

[udakak]

Maybe someone can help me or has an idea what's going on.

I ran a system update with pacman today, but after I rebootet my Cubieboard2, I couldn't reach it anymore via ssh. I'm not sure if it's a problem with the connection or if the board doesn't boot at all, but I get the error "No route to host". The blue led on the board is blinking like it usually does though...

I tried a new installation of ArchlinuxARM to see if I had butchered the system myself by playing around with it and I could reach the newly installed system via ssh, as I expected. But after I ran "pacman -Syu" and rebooted I could not reach the cubieboard anymore.

Like I said I'm not sure if the board is failing during boot, or if something is going wrong with the connection, but I want to make sure the mistake is not on my side. Maybe I'm missing something, or my router is making difficulties, so I'm looking if someone has similar problems or has an Idea what is going wrong...

[PLyttle]

You are leaving a few things out, so I am going to assume you boot from the SD-card, and you connect via Ethernet.

After you updated, did you make sure all the files were written to the card before you rebooted? hint: use the sync command.

You probably had to reflash your u-boot. Are you sure you did that correctly?

When you connect with wifi, it is possible you need to restart the wlan.

The lights are flashing, meaning the board is doing something. It might have booted from nand.

When at all possible, you should consider getting a serial debug cable. That way you can see what is happening and you always have a gateway to the board, so you can correct things that went wrong.

LP

$this->bbcode_second_pass_quote('PLyttle', 'Y')ou are leaving a few things out, so I am going to assume you boot from the SD-card, and you connect via Ethernet.

[WarheadsSE]

DO either of you have a serial connection to the board actively? This will provide FAR more detail.

[udakak]

$this->bbcode_second_pass_quote('WarheadsSE', 'D')O either of you have a serial connection to the board actively? This will provide FAR more detail.

[WarheadsSE]

https://github.com/archlinuxarm/PKGBUILDs/issues/861

Looks like this is affecting several of our "older" kernels. Seeing this on Everything with a 3.4 kernel at this point.

[aristidesfl]

Having the same issue after pacman -Syu

[PLyttle]

I believe this is where it goes wrong:

$this->bbcode_second_pass_code('', '<27>systemd[1]: Failed to mount cgroup at /sys/fs/cgroup/systemd: No such file or directory
[ 5.286153] systemd[1]: Failed to mount cgroup at /sys/fs/cgroup/systemd: No such file or directory
')

That is as far as I got right now,
PS this is on a Phoenix A20. The only difference is script.bin

LP

[Veyrdite]

Judging by your cgroup-related error message, I think it's related to this issue:
viewtopic.php?f=47&t=7330&p=40153&hilit=cgroup#p40153

[PLyttle]

To follow up on last night.

WarheadSE was right. this is indeed the indicated problem

Cloned into Maggu's sunxi-3.4-xattr branch, applied the working-bcmdhd-driver.patch
(and a sunxi_tp_hwmon.patch), substituted my .config and recompiled a kernel.

This solved the problem, the system works again with the new systemd. Thanks Maggu!

LP