I updated the CuBox-i4-Pro (Fedora 22) to Kernel 4.1-rc2, but the (re)boot process was very sluggish, with several key commands failing:
..... systemd: Unit dbus.service entered failed state ..... [FAILED] Failed to start Login Service. ..... [FAILED] Failed to start Modem Manager. ..... [FAILED] Failed to start Avahi mDNS/DNS-SD Stack. ..... [FAILED] Failed to start Network Manager.
The boot process eventually completed, but there was no networking, and various systemctl commands failed:
Error getting authority: Error initializing authority: Could not connect: Connection refused (g-io-error-quark, 39)
dbus-daemon was not running at all, and attempts to start it manually failed..
My first suspicion was that 4.1-rc2 was the culprit, but reverting to known/good 4.1-rc1 and 4.0.0 resulted in the same problems..
I then tried (re)installing dbus, systemd, etc, but with no change..
I then checked SELinux – which I always have configured as ‘disabled’ – but it appeared to be active, despite this..:
# sestatus SELinux status: enabled SELinuxfs mount: /sys/fs/selinux SELinux root directory: /etc/selinux Loaded policy name: targeted Current mode: permissive Mode from config file: disabled Policy MLS status: disabled Policy deny_unknown status: denied Max kernel policy version: 29 # getenforce Permissive
Attempts to disable SELinux manually did nothing, and so I decided to ‘remove’ SELinux by de-selecting it in the kernel config, and re-compiling/installing the kernel.
After this, everything worked OK!
I have other ARM systems with similar configurations, where SELinux is behaving correctly (staying ‘disabled’!) and I have another Fedora 22 system (X86_64) with the same software versions where everything also works OK, so have no explanation as to the real cause of this – apart from some possible SELinux persistent aberration on this single system..
But… at least I have an acceptable – if somewhat drastic – fix..
Robert Gadsdon. May 05, 2015.