Issuses with 1Aug2016 "latest" for utilite

[DevilCrayon]

I've been trying to rebuilt my utilite pro after pacman updated glibc and I started getting the Kernel TOO OLD message.

I've been using my recovery microssd to boot and install following the instructions here:
https://archlinuxarm.org/platforms/armv7/freescale/utilite
using the http://co.us.mirror.archlinuxarm.org/os/ArchLinuxARM-utilite-latest.tar.gz%20tarball

There are quite a number of problems with this version of the tarball.

the /etc/resolv.conf is linked to /run/systemd/resolve/resolv.conf but the entire /run dir in the tarball is empty.

All the following services fail to start:
$this->bbcode_second_pass_code('', '
[root@fraser log]# systemctl --failed
UNIT LOAD ACTIVE SUB DESCRIPTION
* systemd-journald.service loaded failed failed Journal Service
* systemd-logind.service loaded failed failed Login Service
* systemd-networkd.service loaded failed failed Network Service
* systemd-resolved.service loaded failed failed Network Name Resolution
* systemd-timesyncd.service loaded failed failed Network Time Synchronization
* systemd-journald-dev-log.socket loaded failed failed Journal Socket (/dev/log)
* systemd-journald.socket loaded failed failed Journal Socket
* systemd-networkd.socket loaded failed failed Network Service Netlink Sock

LOAD = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB = The low-level unit activation state, values depend on unit type.

8 loaded units listed. Pass --all to see loaded but inactive units, too.
To show all installed unit files use 'systemctl list-unit-files'.
')

trying to start any of them, say systemd.journald.service results in a fail loop until init-limit-hit:
$this->bbcode_second_pass_code('', '
[root@fraser etc]# systemctl start systemd-journald.socket
[ 3288.737114] systemd[1]: Listening on Journal Socket.
[root@fraser etc]# systemctl start systemd-journald.service
[ 3298.361460] systemd[1]: Starting Journal Service...
[ 3298.553388] systemd[1]: systemd-journald.service: Main process exited, code=exited, status=228/SECCOMP
[ 3298.640466] systemd[1]: Failed to start Journal Service.
[ 3298.646151] systemd[1]: systemd-journald.service: Unit entered failed state.
[ 3298.653259] systemd[1]: systemd-journald.service: Failed with result 'exit-code'.
[ 3298.663579] systemd[1]: systemd-journald.service: Service has no hold-off time, scheduling restart.
Job for systemd-journald.service failed because the control process exited with error code.
See [ 3298.679450] systemd[1]: Stopped Journal Service.
"systemctl status systemd-journald.service" and "journalctl -xe" for details.
[ 3298.791349] systemd[1]: Starting Journal Service...
[root@fraser etc]# [ 3299.443954] systemd[1]: systemd-journald.service: Main process exited, code=exited, status=228/SECCOMP
[ 3299.550489] systemd[1]: Failed to start Journal Service.
[ 3299.555978] systemd[1]: systemd-journald.service: Unit entered failed state.
[ 3299.563089] systemd[1]: systemd-journald.service: Failed with result 'exit-code'.
[ 3299.571776] systemd[1]: systemd-journald.service: Service has no hold-off time, scheduling restart.
[ 3299.581191] systemd[1]: Stopped Journal Service.
[ 3299.721314] systemd[1]: Starting Journal Service...
[ 3299.933879] systemd[1]: systemd-journald.service: Main process exited, code=exited, status=228/SECCOMP
[ 3300.010461] systemd[1]: Failed to start Journal Service.
')

Any help getting this back to working system would be greatly appreciated.

[Nikus]

I had the same problem after I updated my system around end of July beginning of August. I just realized it after a reboot yesterday.
I just updated again today (18th of August) and the problem was fixed.
I hope it will be as easy for you as it was for me.

[DevilCrayon]

Were you able to update past the glibc/kernel mismatch problem also?

[DevilCrayon]

Got it working by updating uboot and switching to the linux-image-imx6 kernel, resetting and updating the uboot env with the help of these threads:

viewtopic.php?f=45&t=8503
and
viewtopic.php?f=45&t=8736

pacman -Syu installed the new glibc and it didn't blow up! Hooray.
Now to rebuild all my configurations.