Booting Sabayon fails since the last equo upgrade [Solved]

[Freier Radikaler]

[email protected],

since the last equo update/upgrade I can't boot my Sabayon Linux anymore.
After the upgrade was successfully installed I tried to reboot the mashine. However the reboot and poweroff binary(-links) weren't there anymore. So I had to reset the mashine by hand. Since then the boot process gets stuck shortly after the decryption of the HDD and systemd start. There is no obvious error. However systemd complains about "System is tainted: var_run-bad".
The full output shortly before entering the encryption key and all output after this looks as follows:

Code: Select all

starting version 233
Could not get boot entry.
** No iSCSI initiator found
Encryption password (/dev/sda3): : ****************************************
systemd[1]: System is tainted: var-run-bad
thinkpad_acpi: Disabling thinkpad-acpi brightness events by default...
tpm tpm0: A TPM error (6) occured attempting to read a pcr value
ACPI Warning: SystemIO range 0x.....-0x........ conflicts with OpRegion 0x..... - 0x....... (\_SB.PCI0.LPC.PMIO) (20170728/utaddress-247)
ACPI Warning: SystemIO range 0x.....-0x........ conflicts with OpRegion 0x..... - 0x....... (\_SB.PCI0.LPC.LPIO) (20170728/utaddress-247)
ACPI Warning: SystemIO range 0x.....-0x........ conflicts with OpRegion 0x..... - 0x....... (\_SB.PCI0.LPC.LPIO) (20170728/utaddress-247)
ACPI Warning: SystemIO range 0x.....-0x........ conflicts with OpRegion 0x..... - 0x....... (\_SB.PCI0.LPC.LPIO) (20170728/utaddress-247)
lpc_ich: Resource conflict(s) found affecting gpio_ich
uvcvideo 1-12:1.0: Entity type for entity Extension 4 was not initialized!
uvcvideo 1-12:1.0: Entity type for entity Extension 3 was not initialized!
uvcvideo 1-12:1.0: Entity type for entity Processing 2 was not initialized!
uvcvideo 1-12:1.0: Entity type for entity Camera 1 was not initialized!

After this the booting process stops.

I'm able to chroot into the not booting Sabayon if I boot with a USB-LiveStick. Within the chroot everything look fine. I can install programms using equo or emerge without problems. I also did an "equo --empty install systemd" which installed all necessary dependencies again. Unfortunately without any improvement.
Debugging is really complicated as I don't get to the point in the booting process where a terminal would be available.

I assume this problem is related to the change of systemd and the sysvinit behavior that was mentioned in the "eselect news read" section by End of January 2018.

Does somebody know how I can figure out what is going wrong / I can fix the issue?

[Stupot]

viewtopic.php?f=86&t=34063

[Freier Radikaler]

The fix in this thread worked for me. THX

[albfneto]

please mark the topic as [Solved]

Marked, thanks.

[bunjee50]

I installed Sabayon with my DVD .
Got the upgrade with RIGO.
Rebooted the system and now I have no desktop.
I have no taskbar.
I have no launch pad.
All I have is my host name with a blinking cursor.
Anyone feel like helping me out?

[Ryuno-Ki]

Hi, bunjee50.

We would need some more information from you:

• Did you installed Monthly or Daily image? (link to the download page you used would help. We need the name of the ISO file)
• Which Desktop Environment did you used? (GNOME, KDE, …)
• Do you get to the login screen or do you experience your situation before?