[SOLVED] C2 won't boot up after upgrading systemd to 245-1 on Arch

[stas-t]

Original post: https://archlinuxarm.org/forum/viewtopi ... 65&t=14334
As you can see - many services fail to start. Downgrading systemd solves the boot problem. It's related to the lack of support of ambient capabilities in 3.16.78-1-ARCH kernel. Also I cannot upgrade to 3.16.81 due to RTC issues I've reported earlier.

A question to Hardkernel team: is there a work-around to make the system boot at least?

[soulrebell]

Same problem here. I am using kernel 3.16.81 upgrade to systemd 245-3.

[graysky]

This board [ODROID-C2] is just too quirky I think due primarily to its ancient kernel support by Hard Kernel. Here are a few major issues I see with mine:
* No boot bug mentioned in this thread with currently stable version of systemd (impacting everything).
* CGroups (impacting LXC and virtualization).
* Bridge networking (impacting LXC and virtualization).

As we approach the official EOL of the 3.16.x branch which is June of 2020 (just a few months), what is the plan moving forward from Hard Kernel?

[odroid]

Since the latest Ubuntu 18.04.4 update is still using the systemd version 237, we didn't know what has changed in version 245.
The RTC shield also worked fine on that old systemd + Kernel 3.16.81 on Ubuntu so far.
We need to learn which part of the latest systemd blocks the booting process from ALARM developers.

We have a plan to build a trial Ubuntu 20.04 LTS image in July/August based on Kernel 5.4.y.
But it will contain very limited GPU/VPU acceleration drivers due to lack of our upstream capability.

Meanwhile, you can try the latest Armbian images which comes with Kernel 5.4.y if your target application is not a 4K video playing nor gaming machine.

[soulrebell]

@odroid: Thank you for your reply

We need to learn which part of the latest systemd blocks the booting process from ALARM developers.

Can you estimate a timeline?

[odroid]

We have no firm schedule yet.

[mdrjr]

Hello,

This commit: https://github.com/hardkernel/linux/com ... f18b78941a
Fixes the issue.

I've also send a PR to get our kernel updated: https://github.com/archlinuxarm/PKGBUILDs/pull/1778

[reydecopas]

boot fails if I upgrade the ArchArm to "aarch64 core systemd 245-3"

and I cannot install docker or other packages if adding to pacman.conf
IgnorePkg = systemd systemd-libs systemd-sysvcompat

[odroid]

You might need to update the kernel first.

[graysky]

You might need to update the kernel first.

I kept both the kernel and systemd* packages in the package manager's ignore list until now.

Code: Select all

IgnorePkg   = linux-odroid-c2 linux-odroid-c2-headers systemd systemd-libs systemd-sysvcompat

I commented that line and updated:

Code: Select all

:: Starting full system upgrade...
resolving dependencies...
looking for conflicting packages...

Packages (5) linux-odroid-c2-3.16.82-1  linux-odroid-c2-headers-3.16.82-1  systemd-245-3  systemd-libs-245-3
             systemd-sysvcompat-245-3

I appear to be running OK with the exception of my RTC sheild. Thank you for the help to get the systemd bug ironed out, let's talk about the RTC shield in the other thread.

@stas-t - I think you can mark this as solved if the update works for you as well.

[stas-t]

@graysky: thank you for testing! I'm going to trust you and mark it as resolved.
However, since RTC is still not working for me - I've rolled back the kernel instead of upgrading everything.

[mdrjr]

I'm looking onto the RTC issue

[graysky]

I'm looking onto the RTC issue

Thank you please let me know if you need stuff tested.

[graysky]

I'm looking onto the RTC issue

I'm guessing since no new posts, you have no ideas to get the RTC shield working?