this post was submitted on 04 Sep 2024
11 points (100.0% liked)

Linux Gaming

17491 readers
261 users here now

Discussions and news about gaming on the GNU/Linux family of operating systems (including the Steam Deck). Potentially a $HOME away from home for disgruntled /r/linux_gaming denizens of the redditarian demesne.

This page can be subscribed to via RSS.

Original /r/linux_gaming pengwing by uoou.

Resources

WWW:

Discord:

IRC:

Matrix:

Telegram:

founded 2 years ago
MODERATORS
[email protected]
11
Way to stay on Nvidia 550 w/ Fedora 40? (lemmy.today)
submitted 6 months ago by [email protected] to c/[email protected]
12 comments fedilink hide all child comments
 

Been running Fedora 40 for a few months, and having a hard time keeping Wayland as the desktop environment. Just did a fresh install, and the Nvidia driver updates to 555.58.02. I really want to stick with the Recommended branch, not the New Feature branch. Every update, Wayland breaks. How do I rollback to 550, and switch to the Recommended Branch for updates?

all 16 comments
sorted by: hot top controversial new old
[–] [email protected] 6 points 6 months ago (1 children)

Every update, Wayland breaks

Would you elaborate? If anything 555 and 560 should be more stable on Wayland

[–] [email protected] 2 points 6 months ago* (last edited 6 months ago)

Yes, and thank you for your interest in helping. Appreciated! After an update, I will eventually reboot. When doing so, the options in the gear at the Gnome login will be

  • Gnome
  • Gnome Classic

Both of these options are X11. I verify this with $ echo $XDG_SESSION_TYPE and see X11. When Wayland is working, the Gnome login will show four session types:

  • Gnome
  • Gnome Classic
  • Gnome on X.org
  • Gnome Classic on X.org

I haven't been able to locate a log file where something looks relevant to the decision made at boot for XDG, Wayland, or X11 that chooses one over the other. It's just as though Wayland stops being an option. 3 or 4 updates later, I'll have Wayland back again - but no idea why it comes and goes. My caveman intuition tells me it happens around nvidia updates, but I haven't kept strict notes on that.

[–] [email protected] 6 points 6 months ago* (last edited 6 months ago) (3 children)

You could maybe try Bazzite or Aurora/Bluefin.

They are all Fedora Atomic, the "immutable" Fedora variant, and offer baked in Nvidia support.

The cool thing is:

  1. If the driver/ Wayland breaks on your install, then it will break on thousands of others simultaneously, and the devs can fix it very very quickly, because every installation is identical.
  2. If it breaks, you can roll back in seconds and keep using the image that still worked yesterday. And in the meantime, the developers are already working on a fix, which takes just hours or a day max.
  3. You don't have to install and update anything yourself. Just do your computer stuff and stop worrying.
  4. There's also a GTS (or whatever it's called) variant around, which is the last major version of Fedora. You won't get the newest stuff and will be half a year behind in terms of features, but then there won't be any surprises. I believe the bluefin:gts isn't around yet, but will come with the next major release.
[–] [email protected] 3 points 6 months ago

I did try Bazzite after this post - defaults to Nvidia 560 driver, which is still not the stable. Also installs extra things that I had to turn off - ended up re-wiping and going back to Fedora 40. I may retry in the future, though - but in general, I'm less interested in immutable at this point.

Thank you for the suggestions!

[–] [email protected] 1 points 6 months ago (1 children)

Also, the Nvidia version comes with X11 set up, iirc, and you can swap compositors in the login screen (should be SDDM).

[–] [email protected] 3 points 6 months ago (2 children)

I personally think X11 shouldn't be used anymore. Fedora dropped official support for it recently iirc and it will soon be deprecated, so it might be even worse in the future.

Wayland works perfectly fine under Gnome from what I've heard, and with Plasma, it should be working great too.

[–] [email protected] 3 points 6 months ago

I agree, but I'm not going to force my opinions on someone. They can make their own informed decisions, and if they're having regular trouble with Wayland, maybe they can have a better experience with another option!

[–] [email protected] 1 points 6 months ago

Yeah, I'm ready to be done with X11. Dunno why Fedora with a perfectly working Wayland & Nvidia and updates set to manual will not offer Wayland in the session manager at login about 80% of the time. Must be something I'm doign wrong, but IDK what it is. I wish I had wayland 100% of the time o'er here.

[–] [email protected] 2 points 6 months ago

Sorry for not replying sooner, life stuff.

I've had problems with the 555 driver like KDE's lock screen would freeze for up to 30 seconds whilst trying to unlock and resuming from suspend resulted in a black screen.

So I went back to the 550 driver - I've uploaded the RPMs/SRPMs that I use; https://misc.lapwing.org/rpms/nvidia-550/

Please note this is just a dump of RPMs/SRPMs and not a repo, so it's just a stop gap until 560 arrives and (hopefully) fixes my issues.

You will probably have to fight dnf a bit to get it to actually replace the 555 RPMs, but I've not had a recurrence and the akmod dance works just as ~~jankily~~ well as before.

[–] [email protected] 1 points 6 months ago* (last edited 6 months ago)

Wayland support wasn't working with NVIDIA and commenting out the suspend / resume checks (that can disable Wayland) fixed it. This was early - possibly F40 beta so it may not be necessary anymore but everything still works.

cp /usr/lib/udev/rules.d/61-gdm.rules /etc/udev/rules.d/61-gdm.rules

Comment out the suspend / resume tests in /etc/udev/rules.d/61-gdm.rules. Any issues delete /etc/udev/rules.d/61-gdm.rules.

Create alias to check if current session is Wayland:

alias iswayland='loginctl show-session 2 -p Type | awk -F= '\''{print $2}'\'''