SELinux boot failure

English Applications
1

Hi,
there are several issues on my upgrade from Leap 15.6 to Leap 16.
I am actually very disappointed with the upgrade.
But the most serious error on my upgrade was that I installed everything, then installed the codecs from packman and had some reboots during the day.
Was adjusting to the new environment when today I booted the computer to a SELinux error on boot.

[!!!!!!] Failed to load SELinux policy.

The boot process was halted and had to be rebooted with a hardware reset button.
The solution after searching online was to disable SELinux from boot …
For those that have the same problem it is simple:

On boot when choosing the kernel to boot simple press e to enter edit mode.
Once in edit mode go to the end of the linux boot parameters and simple wirte:

selinux=0

And that’s it, SELinux will be disable at boot you pc should have no problems booting.
This upgrade was full of problems.

  • Ethernet did not work, had to manually install Sauerland dirvers for RTL8111F ethernet adapter,
  • Cockpit socket can not be created … still not working.
  • Hostapd does not work.
  • slow auto-hide for the taskbar
  • and worst of all there is no VirtualBox …this is a deal killer for me.
    I may have to start some more threads if I can not solve these many issues …
    Regards.
1 Like
2

Ethernet: If you use my driver before Update, it will be blacklisting the Kernel driver and you do not get Internet after Upgrade and Reboot.

Cockpit: Maybe because of a different /etc/nsswitch.conf.

Virtualbox: Use the Virtualization Repo, it’s working here.

Selinux: Because of missing rpms, install them by using myrlyn.
Search there for selinux. myrlyn sometimes is not installed, so install it before.
https://bugzilla.opensuse.org/show_bug.cgi?id=1255897

1 Like
3

Hi,

I had to use your drivers before the update because the motherboard had the ethernet adapter (a little QFN RTL 8111F chip onboard ) and hence the only way for the ethernet to work was with your drivers. Glad you replied because I have the opportunity to thank you for the drivers :+1:
I’m still sorting other issues related with my personal programming environment. I will go to the other issues soon and maybe will get back in here with either my solutions or defeated in my quest and begging for help :slight_smile:
Thanks.

1 Like
4

Cockpit: Maybe because of a different /etc/nsswitch.conf.

Virtualbox: Use the Virtualization Repo, it’s working here.

Both cases solved and that was exactly the problem.
Virtualbox was easy just installing from the correct repo’s.
In the case of Cockpit it was /etc/nsswitch.conf like the system logs suggested, it was Simply a matter of copying the recommended config file.
Thanks.