[SOLVED] ODROID-C2 won't boot up...systemd to 245-1

[stast]

After installing software updates my C2 box stopped booting: network connection is not available and only black screen is shown.

After extracting eMMC card and chrooting into it I've discovered a lot of these messages in the system log:
$this->bbcode_second_pass_code('', '
XXXX: Failed to apply ambient capabilities (before UID change): Invalid argument
XXXX: Failed at step CAPABILITIES spawning YYYY Invalid argument
')
Here XXXX is systemd unit and YYYY is an executable it tries to spawn. The list of failed units: dbus.service, alsa-restore.service, mkinitcpio-generate-shutdown-ramfs.service, systemd-random-seed.service, user-runtime-dir@1000.service, systemd-user-sessions.service, systemd-update-utmp.service, run-user-1000.mount, tmp.mount, lvm2-monitor.service.

These are the packages that I've upgraded today:
$this->bbcode_second_pass_code('', '[2020-03-10T19:56:22+0100] [ALPM] transaction started
[2020-03-10T19:56:22+0100] [ALPM] upgraded systemd-libs (244.3-1 -> 245-1)
[2020-03-10T19:56:24+0100] [ALPM] upgraded systemd (244.3-1 -> 245-1)
[2020-03-10T19:56:25+0100] [ALPM] upgraded curl (7.69.0-3 -> 7.69.0-5)
[2020-03-10T19:56:25+0100] [ALPM] upgraded dconf-editor (3.34.4-1 -> 3.36.0-1)
[2020-03-10T19:56:25+0100] [ALPM] upgraded four-in-a-row (3.35.92+4+g8d136a7-1 -> 3.36.0-1)
[2020-03-10T19:56:25+0100] [ALPM] upgraded gnome-2048 (3.34.5-1 -> 3.36.0-1)
[2020-03-10T19:56:26+0100] [ALPM] upgraded gnome-klotski (3.34.4-1 -> 3.36.0-1)
[2020-03-10T19:56:26+0100] [ALPM] upgraded gnome-session (3.35.3+9+g86d4132c-1 -> 3.36.0-1)
[2020-03-10T19:56:26+0100] [ALPM] upgraded gnome-taquin (3.34.4-1 -> 3.36.0-1)
[2020-03-10T19:56:26+0100] [ALPM] upgraded gnome-tetravex (3.35.92+6+g65f0423-1 -> 3.36.0-1)
[2020-03-10T19:56:27+0100] [ALPM] upgraded goocanvas (2.0.4-4 -> 2.0.4-5)
[2020-03-10T19:56:27+0100] [ALPM] upgraded iagno (3.34.5-1 -> 3.36.0-1)
[2020-03-10T19:56:27+0100] [ALPM] upgraded python-pycparser (2.19-3 -> 2.20-1)
[2020-03-10T19:56:27+0100] [ALPM] upgraded python2-pycparser (2.19-3 -> 2.20-1)
[2020-03-10T19:56:30+0100] [ALPM] upgraded qt5-webkit (5.212.0alpha3-9 -> 5.212.0alpha4-1)
[2020-03-10T19:56:30+0100] [ALPM] upgraded systemd-sysvcompat (244.3-1 -> 245-1)
[2020-03-10T19:56:31+0100] [ALPM] upgraded tracker (2.3.2-1 -> 2.3.4-1)
[2020-03-10T19:56:31+0100] [ALPM] upgraded tracker-miners (2.3.2-1 -> 2.3.3-1)
[2020-03-10T19:56:32+0100] [ALPM] transaction completed
')
The filesystem is not corrupted. Also this command shows no corrupted packages:
$this->bbcode_second_pass_code('', 'paccheck --sha256sum systemd-libs systemd curl systemd-sysvcompat')

Kernel version:
$this->bbcode_second_pass_code('', 'linux-odroid-c2 3.16.78-1')
I'm running older kernel version because of RTC issues described here: viewtopic.php?f=15&t=14225

EDIT: Put actual log messages.
EDIT2: Put back a message template and added a list of failed units.

[stast]

Reverting systemd, systemd-libs and systemd-sysvcompat back to 244.3-1 “fixed” the issue directly.
Is there any real fix for this problem?

[hereticmaggot]

I have exactly the same problem since yesterday.
I would also like to know if there is a proper fix for this

[FunkinStoopid]

systemd 245-2 doesn't solve problem

[stast]

@FunkinStoopid: thank you for checking!

After a quick search I've made yesterday it seems that the kernel is too old for this systemd.exec feature (AmbientCapabilities): https://www.freedesktop.org/software/sy ... .exec.html.

Not sure if there is a work-around yet.

[graysky]

Recommend that you post this to the Hard Kernel odroid-c2 forum: https://forum.odroid.com/viewforum.php?f=141

Make it clear to them that their official kernel is too old and ask if they have a work-around. I doubt that Arch ARM maintainers will want to add an odroid-c2 specific systemd package if that is the only way to get this working. ...is there a legacy mode systemd can use?

[stast]

@graysky: thank you for suggestion. I will do that and wait for few more days. Afterwards I will probably switch to CoreELEC because I'm giving up on Arch for this box. To summarize:
- Kodi 18 is unavailable for Ubuntu/Arch for this box
- qemu stopped working after upgrade to 3.16.x
- upgrade to linux-odroid-c2-3.16.81-1 breaks RTC
- new systemd problem
- mainline kernel is still not ready for my needs for this box

There is clearly a gap in functionality between initial 3.14 kernel and the mainline one and I don't expect it to be resolved the nearest month. Even though CoreELEC still uses 3.14 kernel for their C2 image - I believe that Kodi with a minimal set of addons is safe enough.

[graysky]

Of all the ARM devices I own, the ODROID-C2 is the lamest one. Too many quirks and not enough support from Hard Kernel. Recommend you sell it on ebay and get a RPi4.

[stast]

True, lack of support is obvious. But instead of selling it I will make a pure Kodi box out of it and later buy a different board for anything else.

[graysky]

$this->bbcode_second_pass_quote('stast', 'T')rue, lack of support is obvious. But instead of selling it I will make a pure Kodi box out of it and later buy a different board for anything else.