After 15.5 -> 15.6 upgrade, no KDE desktop, only text mode - NVIDIA GPU

English Install/Boot/Login
1

Desktop with Ryzen 5 5600X, RTX 2060, a bunch or partitions, dual-boot with windows 10 (for some steam games).
After upgrading one (old) laptop and three desktops (one old with GT 710 GPU), one Ryzen 2200 with onboard graphics and one Ryzen 5 2600 with an RX 550 AMD GPU, all without issues, I decided to take the plunge and upgrade my main desktop, described above, for the first time enabling online repos and updating packman and KDE:Extra repos to 15.6 (first time I tried this), to avoid the endless conflict resolutions due mostly to packman.
As per Murphy’s Law, after rebooting and enrolling MOK keys (I think due to NVIDIA driver), I’m dumped in a text terminal. startx as root errors out with message:

xinit failed. /usr/bin/Xorg is not setuid, maybe that's the reason?

lsmod | grep -i nvid nor lsmod \ grep nouv show anything.

The newest similar topic here is from 2010, apparently.

I’m at a loss on what to do, it’s been a long time since I experimented something like this.

Thanks!

2

There are several questions:

  • did you exchange the Nvidia repo as there are different versions for Leap 15.5 and 15.6?
  • as you are using the external KDE repos: did you exchange them to the 15.6 version?

When using several external repos whilst distribution upgrade, you need to take extra care.

3

Yes, absolutely. Changed both URLs to 15.6. Just checked now with yast2, it’s OK. I don’t post the repo list because I don’t know (yet) how to mount a DOS pendrive from the terminal. GUI guy, I know…

4

Just removed all nvidia G06 and firmware packages, but still end up in a terminal. startx and init 5 do not work.

5

Maybe something to do with the bootloader? BIOS says secureboot is enabled but not active, and CSM support is disabled. That’s how it worked with 15.5

6

@brunomcl
Any error spit on the screen before taking it to the text terminal.
Did you check for a broken fstab?
I been in this situation before and sometimes the culprit is fstab.
Or just rebuilding the initramfs sometimes it is able to boot normally.

7

I took the (semi) nuclear option, reinstalled the system but keeping /home. All’s working now. Thanks to hui and conram who replied!
@conram: no errors I could see; fstab was OK, except for /windowsD partition that was ro (fixed now); rebuild iniramfs - I didn’t think of it, will make a note for my next SNAFU :upside_down_face:

1 Like
8

Looks like you’re still using ext4 like here on my side. When I do nuclear I always do a screenshot of my favorite applications so I wouldn’t miss those apps at install time.

9

root is btrfs, home is XFS following oS standard. Only two older data drives (3TB and 8TB) are ext4.
Since openSUSE 12 I’ve listed all post-install procedures I like to do, what apps and widgets to install, how to set desktop behavior to my liking, etc., and update these as things change.
I also save important system config files like fstab, exports, etc. before install - although I usually forget to back up smb.conf, perhaps it’s my subconscious…

10

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.