3 ms·
Even more frustrating is on the Linux side. We've had a couple of threads about how bad Wayland is, when most of the problems are due to Nvidia binary drivers
by bryanlarsen 3y ago
Even more frustrating is on the Linux side. We've had a couple of threads about how bad Wayland is, when most of the problems are due to Nvidia binary drivers.
It's been 11 years since Linus gave Nvidia the finger. Nobody who is thinking of possibly running Linux should ever buy an Nvidia product. Yet Nvidia is still very commonly spec'd into Linux builds even today.
- shmerl 3y agoOn Linux people are clearly leaning to AMD for a while already, especially when gaming is concerned: https://www.gamingonlinux.com/index.php?module=statistics&view=trends#GPUVendor-top https://www.gamingonlinux.com/index.php?module=statistics&vi... In the Windows land it's indeed mostly Nvidia.
- robotnikman 3y agoIronically, ARM drivers for Nvidia are available for Linux, but not for Windows
- Filligree 3y agoAMD cards are _very bad_ at running CUDA. If you're running linux on a desktop, there's a decent chance you're the type who wants to play with ML as well...
- latchkey 3y agoAMD has a translation layer called HIP as part of the ROCm toolset. This doesn't get us 100% of the way there, but it is an alternative that is gaining traction as they work to improve it.
- smoldesu 3y agoKDE's Wayland session is fine on Nvidia, at least with my 3070. There used to be more visual artifacts, but everything I'm using works, from CUDA to Mesa to DLSS. The largest remaining bug I'm aware of has to do with how blurred windows are presented. It's pretty functionally solid, at least with newer drivers.
- bryanlarsen 3y agoI am still getting a lot of visual artifacts on a 970.
- anon291 3y agoI've used NVIDIA on linux for decades and the support has always been great in my experience