I have observed exactly same issue on my hardware.
Just fresh ROME install on AMD Ryzen 7 7700X with nVidia GeForce RTX 4080.
After installation system was booting without a problem using nouveau driver.
Then I tried to install nVidia propriety drivers and finished with crashing Plasma6 around 30 seconds after login through sddm.
Currently I am using OM Plasma6 with just bypassing sddm login and nvidia drivers are working fine. I haven’t tried mentioned workaround yet (installing drivers without loggin through sddm), but just want to confirm the same issue exists on my hardware. I hope that developers will find a root cause of that behavior.
I hope to stay with OM distro for a longer way - my first linux distribution of a choice was a Mandrake 7.0 or 8.0, distributed as CDs with some magazine in press shop, but it was in a previous century. I have been an Ubuntu user for a long time, but Lunduke Journal convinced me to try OM, and here I am.
The workaround doesn’t work for me. I followed the steps in Rich’s post and I still get logged out every 2 minutes. I guess I’ll go back to Arch and watch these forums for it to be fixed.
I did get the workaround I posted above to work, where it will log in if you select “X11” but I can’t get it to play games in Steam. Right now I have OM installed on an external USB Hard drive to experiment with, and on my Intel based laptop.
It would be nice if the open-nvidia driver was worthy of using as I would bet a lot of the issues we’re seeing would go away.
We are currently using 565.77 which is the version where nvidia claims the open driver and the closed driver have feature parity. Which would seem to be accurate, because they have the same issues. That being said, we package the open driver but we do not have any devs that have an nvidia card new enough to test it (16xx or newer).
Although installing the nvidia drivers has solved this problem for me i have noticed that for a split second between the boot splash and login screens i get some error messages. I’ve tried journalctl and dmsg to track them down but not sure if i have found them
Jan 21 22:37:19 Z710-OMrome kernel: ACPI: OSL: Resource conflict; ACPI support missing from driver?
Jan 21 22:37:19 Z710-OMrome kernel: ACPI Warning: SystemIO range 0x0000000000000830-0x000000000000083F conflicts with OpRegion 0x0000000000000800-0x000000000000085F (\_SB.PCI
0.PEG0.PEGP.GPIO) (20240827/utaddress-204)
Jan 21 22:37:19 Z710-OMrome kernel: ACPI Warning: SystemIO range 0x0000000000000830-0x000000000000083F conflicts with OpRegion 0x0000000000000800-0x000000000000083F (\GPRL) (
20240827/utaddress-204)
Jan 21 22:37:19 Z710-OMrome kernel: ACPI Warning: SystemIO range 0x0000000000000830-0x000000000000083F conflicts with OpRegion 0x0000000000000800-0x0000000000000BFF (\GPR) (2
0240827/utaddress-204)
after googling around i found out this this is often connected to nvidia gpus and can cause suspend resume to not work another problem i’m having and haven’t solved yet. as this is all nvidia related could both problems be connected to this warning. Also from what i saw it was mostly found with older hardware.
Ran through my script above, but instead of installing the closed source drivers, from Konsole: sudo dnf in nvidia-dkms-kmod-open-565.77-3-omv2490.x86_64.rpm
This installed the necessary dependencies, and updated the kernel to 6.13.RC5
After rebooting, I didn’t touch anything and let it boot straight to SDDM.
4.1 NO ERRORS!!
4.2 Was using the desktop for about two hours, installed Steam, Lutris and browsed the web.
4.3 Tested four games, three worked fine, one of them has known issues. two of them were running through Proton.
4.4 Tested WebGL. The de-googled Chromium it ran terrible. In the Vivaldi flatpak I installed it was smooth.
Cons:
There seems to be more screen tearing in games, didn’t notice any on the desktop.
I don’t know if this is related, but when I press CTRL+ALT+F4 to switch to TTY4, it is stuck on the loading display that OMLx shows when first loading from Grub. I tried also booting from the new Kernel straight to the Console and the same thing happens. It gets stuck on the loading screen, and I can’t switch to other TTY.
Conclusion:
Overall given how poorly the proprietary drivers worked for me in OMLx the open source drivers performed MUCH better. The Desktop was super responsive and made me hopeful for eventually replacing my Arch install on the desktop.
Sadly they still have better performance / $ over AMD. I’m hopeful the new Intel cards can compete better on that front.
The used 1660 TIs are now going for about ~ $100.
A comparable 6-8 GB AMD card is twice as much (6600 XT). Honestly looking back at the issues I’ve had, I’d almost rather have paid a little more to update these both to 6600 XTs.
You can also use the non dkms flavor. We really only recommend that if you are building your own kernels, or really want to test it on Cooker with a new kernel and it’s failing to build in ABF. In ROME, the kernel and the kmod will get updated at the same time.
It should replace nvidia-kmod-desktop since the other one provides the kmod.
TTY’s have been finicky on nvidia proprietary drivers for a while, but it seems the open ones might have inherited it. It has to do with their framebuffer being fairly new. We include the framebuffer kernel mode parameter in grub already.
I decided to come back to OM after some time “flirting” with bluefin (I like the idea, but I think it’s not for me). Anyway, after installing I ran after the same problem again, and started trying stuff once more.
The problem seems to be SDDM. Right now I’m using lightdm as a session manager and it’s been working as expected, without messing with the nVidia drivers. I tried replacing the plasma6-sddm package with the SDDM one, but neither worked.
I guess the steps to follow would be these:
sudo dnf install lightdm --allowerasing
Note: I had to add the --allowerasing flag because lightdm conflicts with SDDM. If it doesnt delete the sddm packages automatically you can do so manually. Please check that it doesn’t uninstall half the system with it, as I think it did once when I was fiddling around.
Check if lightdm is enabled:
systemctl status lightdm.service
And if it’s not enabled by default, enable it with:
sudo systemctl enable lightdm.service
Anyway, I hope this is useful to someone else. Please let us know if it worked for you, so as to see if the SDDM package has a beef with nVidia graphic cards
I just found this thread by @pastorczo13 , which seems to address the same (or a similar) issue. Maybe the problem has to do with how SDDM manages the compositor?
