Desktop logs out to lock screen (nvidia)

richp · January 10, 2025, 6:50am

That sounds like it’s worth trying, for the moment I’ve been using rock and for what i do it works great but I really want to try plasma6. I don’t know what dark magic openmandriva use for the install but i have never seen an install go so fast. Over the last couple of days i’ve done around 10 different baremetal installs of different isos and-or because i botched my system trying to fix - workaroung this problem. It may sound like i’m complaining but this is the most fun i’ve had with linux for a while and getting to know better the inerworkings of my system is also great.

richp · January 10, 2025, 8:41am

Thanks @seraphim im posting this from my newly up and running romeplasma6. This seems to fix the problem but why dose the live iso work, are the proprietary drivers included? But then I istalled arch with plasma6 and sddm and worked that without.

seraphim · January 10, 2025, 1:26pm

@richp I’m glad it’s working now Could you share the output of “lshw -class display”? It seems that your card is supported by Nvidia’s latest driver, so I’m curious if your system is actually using it. I know mine isn’t, so that’s why I believe the solution isn’t the driver itself but something the driver does at installation that affects the SDDM or graphical login process. As you said, the live iso worked perfectly for me as well, and starting the desktop environment with startx (without installing the Nvidia driver) works perfectly.

Mordechai · January 10, 2025, 2:17pm

Was seeing the same behavior on my desktop. Generally I avoid Wayland as X.org works better with NVIDIA.

I fresh installed the latest ROME OMLx, updated the software, installed NVIDIA, rebooted, logged in (which took a long time) and within a minute the screen goes black and goes back to the log in. From there, it is super flaky and may let you log in (which will just loop again) or it may black out back to the log in.

Here’s my HW INFO:

inxi -F                                                                                                                                [6:48:38]
System:
  Host: shechem Kernel: 6.12.8-zen1-1-zen arch: x86_64 bits: 64
  Desktop: KDE Plasma v: 6.2.5 Distro: EndeavourOS
Machine:
  Type: Desktop Mobo: Gigabyte model: B550 UD AC v: x.x
    serial: <superuser required> UEFI: American Megatrends LLC. v: F2 Y1
    date: 07/13/2021
CPU:
  Info: 6-core model: AMD Ryzen 5 5600X bits: 64 type: MT MCP cache: L2: 3 MiB
  Speed (MHz): avg: 3981 min/max: 550/4651 cores: 1: 3981 2: 3981 3: 3981
    4: 3981 5: 3981 6: 3981 7: 3981 8: 3981 9: 3981 10: 3981 11: 3981 12: 3981
Graphics:
  Device-1: NVIDIA TU116 [GeForce GTX 1660 Ti] driver: nvidia v: 565.77
  Display: x11 server: X.Org v: 21.1.15 with: Xwayland v: 24.1.4 driver: X:
    loaded: nvidia gpu: nvidia,nvidia-nvswitch resolution: 1: 1920x1080
    2: 1920x1080
  API: EGL v: 1.5 drivers: nvidia platforms: gbm,x11,surfaceless,device
  API: OpenGL v: 4.6.0 vendor: nvidia v: 565.77 renderer: NVIDIA GeForce
    GTX 1660 Ti/PCIe/SSE2
  API: Vulkan v: 1.4.303 drivers: N/A surfaces: xcb,xlib
Audio:
  Device-1: NVIDIA TU116 High Definition Audio driver: snd_hda_intel
  Device-2: Advanced Micro Devices [AMD] Starship/Matisse HD Audio
    driver: snd_hda_intel
  Device-3: C-Media Audio Adapter (Unitek Y-247A)
    driver: cmedia_hs100b,snd-usb-audio,usbhid type: USB
  API: ALSA v: k6.12.8-zen1-1-zen status: kernel-api
  Server-1: PipeWire v: 1.2.7 status: active
Network:
  Device-1: Intel Dual Band Wireless-AC 3168NGW [Stone Peak] driver: iwlwifi
  IF: wlan0 state: up mac: a4:6b:b6:c8:5a:37
  Device-2: Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet
    driver: r8169
  IF: enp5s0 state: down mac: d8:5e:d3:03:a7:7e
Bluetooth:
  Device-1: Intel Wireless-AC 3168 Bluetooth driver: btusb type: USB
  Report: btmgmt ID: hci0 rfk-id: 0 state: down bt-service: disabled
    rfk-block: hardware: no software: no address: N/A
Drives:
  Local Storage: total: 2.27 TiB used: 495.41 GiB (21.3%)
  ID-1: /dev/nvme0n1 vendor: Crucial model: CT2000P3PSSD8 size: 1.82 TiB
  ID-2: /dev/sda vendor: Samsung model: SSD 840 Series size: 465.76 GiB
Partition:
  ID-1: / size: 48.11 GiB used: 18.8 GiB (39.1%) fs: btrfs dev: /dev/nvme0n1p4
  ID-2: /home size: 1.77 TiB used: 341.07 GiB (18.8%) fs: f2fs
    dev: /dev/nvme0n1p3
  ID-3: /var/log size: 48.11 GiB used: 18.8 GiB (39.1%) fs: btrfs
    dev: /dev/nvme0n1p4
Swap:
  Alert: No swap data was found.
Sensors:
  System Temperatures: cpu: 36.5 C mobo: 24.0 C gpu: nvidia temp: 36 C
  Fan Speeds (rpm): N/A gpu: nvidia fan: 33%
Info:install the proprietary nvidia drivers.

  Memory: total: 32 GiB available: 31.28 GiB used: 7.99 GiB (25.5%)
  Processes: 439 Uptime: 1h 27m Shell: Zsh inxi: 3.3.36

(Currently running EndeavorOS on this HW as I need something that works)

richp · January 10, 2025, 2:54pm

For anyone else who has this problem here are details of the work around using x11 i have not tested for wayland

Boot but before logging in open a terminal using ctrl+alt+f4 and login
user name - enter
password - enter
to start plasma with startx you first need to stop SDDM
sudo systemctl stop sddm
Now you can start the plasma6 desltop with startx
startx /usr/bin/startplasma-x11
Once plasma has started you can now install the proprietaty nvidia drivers.
Open the software repository selector app and enable the non-free repository
Now from OMWelcome - configure - hardware you should be able to install the Nvidia drivers
If all went well you can reboot and log in using sddm.

This is more of a work around than a solution but it gets the system working.
Thanks again to @seraphim for your 2 cents.

richp · January 10, 2025, 3:01pm

Seem like the new driver is working

-display                 
       description: 3D controller
       product: GM108M [GeForce 840M]
       vendor: NVIDIA Corporation
       physical id: 0
       bus info: pci@0000:01:00.0
       version: a2
       width: 64 bits
       clock: 33MHz
       capabilities: pm msi pciexpress bus_master cap_list rom
       configuration: driver=nvidia latency=0
       resources: irq:39 memory:d0000000-d0ffffff memory:a0000000-afffffff memory:b0000000-b1ffffff ioport:4000(size=128) memory:b2000000-b207ffff
  *-display
       description: VGA compatible controller
       product: 4th Gen Core Processor Integrated Graphics Controller
       vendor: Intel Corporation
       physical id: 2
       bus info: pci@0000:00:02.0
       version: 06
       width: 64 bits
       clock: 33MHz
       capabilities: msi pm vga_controller bus_master cap_list rom
       configuration: driver=i915 latency=0
       resources: irq:30 memory:d1000000-d13fffff memory:c0000000-cfffffff ioport:5000(size=64) memory:c0000-dffff

I know that in mint i installed the recomended driver and i had the option to use the nvidia card only on demand would it show the driver in use if you weren’t actually using it? I will boot into mint and see what lshw reports.

richp · January 10, 2025, 3:15pm

Checked with mint and when i switch to energy saving mode the card is there but the the driver is not in use. With mint i can do this with the nvidia applet in the task bar but i dont see that in plasma, there has to be a config file for that somewhere.

Mordechai · January 10, 2025, 5:54pm

In terms of process (To make sure I get this right when I try again):

Install OMLx
Update OMLx
Before logging into Plasma
3.1 open TTY4 (CTRL+ALT+F4)
3.2 login
3.3 sudo systemctl stop sddm
3.4 startx /usr/bin/startplasma-x11
Log in from SDDM login prompt
Enable non-free repos in Welcome center
Install NVIDIA drivers
Reboot
Log in / no errors?

richp · January 10, 2025, 6:13pm

Sorry maybe i was unclear.
If you want to update i would do this from the tty i never had time after logging in with sddm to perform an update before being logged out. after updating it is probably better to reboot, just use the reboot command from the tty. After rebooting you can restart the process. When you eopen the tty you will need to login with your username, from there you can start plasma with startx instead of sddm. The problem seems to be with sddm thats why we stop it and use startx as the luancher. After using the startx command a plasma session will start for whichever user issed the command, dont login to the tty as root or use sudo for the startx command. I dont think plasma allows a plasma session under root but if it worked it wouldn’t be wise to use plasma as root anyway or at least this is my understanding. If the plasma session fails to start maybe you installed the wayland iso, if so you have 2 options
1 install task-x11 with sudo dnf install task-x11 and the retry the startx /usr/bib/startplasma-x11 command
2 try startx /usr/bin/startplasma-wayland and followthe remaining steps (i have no idea if this would work but i dont think it will break anything if you try. Hope this helps.

Mordechai · January 10, 2025, 8:16pm

Sorry maybe i was unclear.

Nah - you were clear enough. On the desktop I’m using I can log in via Plasma and run the updates without it acting weird.

Performing these steps, I was able to get the NVIDIA driver installed and running without the weird black screen / logging out behavior.

ben79 · January 10, 2025, 8:34pm

A pretty standard way in OMLx to start the desktop if the system appears to boot but stops at login screen or does not load the desktop. Like for example “boots to black screen” or “boots to black screen with >something<”.

At Grub2 Menu go to Advanced Options>Console Mode that should boot to a login prompt
login with your user name
For Plasma5 or 6 X11 type startx or startplasma-x11 for P5 or 6 Wayland startplasma-wayland for IceWM start-icewm for XFCE startxfce4 or if you are using some other desktop with X11 and don’t know type startx. Those are the ones I can remember but whatever the desktop is it will have some start commandl in /usr/bin. That then starts the desktop bypassing sddm or other login software like gdm or lightdm.
If you are using nVida graphics with Wayland and have problems try X11, this is a no brainer.

Mordechai · January 10, 2025, 8:45pm

There’s your problem

Mordechai · January 10, 2025, 9:13pm

Status:

Computer 1:
Ryzen 5 2600
GeForce 1660 TI
16 GB RAM

Booted into live cd fine, followed steps got a working install.

Computer 2:
Ryzen 5 5600X
GeForce 1660 TI
32 GB RAM

Locks up after loading “Plymouth” (Which I believe is Wayland loader right?)

I used the same ISO on both, the official X11 linked on the main page.

To get the second computer working, I just moved up the steps in the process.

From ISO Grub menu select Advanced Options Then boot to the CLI
type live and press enter
Type startx /usr/bin/startplasma-x11
Install to your hardware
Reboot
From the hardware install GRUB select Advanced Options then boot into the CLI
Log in to your user
Type startx /usr/bin/startplasma-x11
I first run the updater, add the extra/non-free repos
reboot
From the hardware install GRUB select Advanced Options then boot into the CLI
Log in to your user
Type startx /usr/bin/startplasma-x11
install the NVIDIA drivers from the Welcome menu
reboot into your system

UPDATE:

On the second system, I’m still getting some strange behavior after that final reboot. In the middle of installing an application it black screened back to the log in.
System Info:

Operating System: OpenMandriva ROME 24.12
KDE Plasma Version: 6.2.4
KDE Frameworks Version: 6.9.0
Qt Version: 6.8.1
Kernel Version: 6.12.6-desktop-1omv2490 (64-bit)
Graphics Platform: X11
Processors: 12 × AMD Ryzen 5 5600X 6-Core Processor
Memory: 31.3 GiB of RAM
Graphics Processor: NVIDIA GeForce GTX 1660 Ti/PCIe/SSE2
Manufacturer: Gigabyte Technology Co., Ltd.
Product Name: B550 UD AC

inxi -F

Graphics:
  Device-1: NVIDIA TU116 [GeForce GTX 1660 Ti] driver: nvidia v: 565.77
  Display: x11 server: X.org v: 1.21.1.15 driver: X: loaded: nvidia
    unloaded: fbdev,modesetting,nouveau,vesa gpu: nvidia,nvidia-nvswitch
    resolution: 1: 1920x1080~60Hz 2: 1920x1080~60Hz
  API: EGL v: 1.5 drivers: kms_swrast,nvidia
    platforms: gbm,x11,surfaceless,device
  API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: nvidia v: 565.77
    renderer: NVIDIA GeForce GTX 1660 Ti/PCIe/SSE2
  API: Vulkan v: 1.4.303 drivers: N/A surfaces: xcb,xlib

ben79 · January 10, 2025, 9:15pm

I only have one box but I can use either.

But OM has a lot of users on old hw and that is one reason why we keep X11. The devs currently focus on X11 more, not due to lack of desire but lack of resources, mainly developer time. Volunteers welcome.

We do not want people to have to throw away still usable hardware so we make an effort to be a backward compatible as possible for a very up to date distro.

ben79 · January 10, 2025, 9:17pm

You only need one of those startx should be enough. Or startplasma-x11.

ben79 · January 10, 2025, 9:23pm

If this works that is great. Ofc we don’t like it when users have these problems and we try to help as much as we can. But we are not magicians. And nVidia graphics is a big challenge for a very small, all part-time, volunteer group.

Ofc we hope the group is about to get larger also.

Mordechai · January 10, 2025, 9:29pm

It seems to be growing rapidly.

I’m glad to be here - The community here is fantastic. I’ve been in several other communities recently trying to deal with hardware problems and this is by far the best experience as small as it is.

seraphim · January 11, 2025, 1:41am

I did some more testing, just to discard other options, and found that the problem persist when using another DE (X11 failsafe and XFCE) and Wayland (In Plasma 6 and XFCE). I’d love to find a solution without the nvidia driver workaround, as my card isn’t suported and the GPU does feel the extra work when nouveau isn’t around, so I’ll keep testing to see what I can find.

Mordechai · January 11, 2025, 11:28am

I did some additional testing last night, but I will likely open a new chat about this.

As mentioned I have the two desktop computers, that are very similar. The 2600 and 5600X both with 1660 TIs.

Mandriva / Plasma / X11 / Steam run great on the 2600.

5600 with the same setup, was flaky in Plasma and I couldn’t get any Proton games to run in Steam.

pastorczo13 · January 19, 2025, 8:28pm

I am having the same issue, it only happened when I tried to install steam.