Jure Repinc

Digital and software freedom/rights advocate from Slovenia, Europe. Also a member of the Pirate party. You can find me on Mastodon: @JRepin@mstdn.io

  • 22 Posts
  • 9 Comments
Joined 1 year ago
cake
Cake day: June 8th, 2023

help-circle

  • I am also gaming a lot and used nvidia in the past and by the description you give I would say openSUSE Tumbleweed is the one. It is rolling release, but they also have extensive QA tests before letting packages get released as updates so it is very stable for a rolling release. And another thing that openSUSE is awesome for is that they have BTRFS snappshotting very nicely configured out of the box so before and after each update it creates a snappshot and if something goes wrong you can just select an old working snappshot from GRUB boot menu. And with Nvidia this breakage was happening well more often the I would like. I also like their Open Build Service where you can find many additional packages which might not be packaged by distro people themselves.



  • Agree and hope it brings even better GNU/Linux gaming support, as it is the OS that is in this democratic users/people owned operating system, just as other free as in freedom and opensource collaborative software. In this regard Valve does quite a very good job of improving and sponsoring GNU/Linux, Mesa drivers KDE and other opensource projects. What all other gaming companies fail terribly at. What comes after Valve must be even better at it.
























  • From my experince AMD drivers are pretty close, I’d even say slightly better on GNU/Linux, definitely more stable and consistent. For Nvidia, yeah they are bad at supporting GNU/Linux. Improved a lot through the years but still not there. For Intel, well not exactly an option for gaming, at least not the integrated GPUs I have used so far, but still better than in Windows in a similar way as in AMD case.

    P.S. Another great thing with libre/opensource GNU/Linux drivers: When you report a bug with Mesa3D drivers the bug is quite quickly fixed, especially when you can provide them with backtrace and/or Vulkan/OpenGL API trace. Doing a bisect of source code commits amd identifying the commit that introduced a regression also help a great deal. Good luck doing the same with closed/Windows drivers: you can wait for years and no fix.