You're viewing a single thread.
I'm holding out building a new gaming rig until AMD sorts out better ray-tracing and cuda support. I'm playing on a Deck now so I have plenty of time to work through my old backlog.
I was straight up thinking of going to AMD just to have fewer GPU problems on Linux myself
In my experience,
AMD is a bliss on Linux,
while Nvidia is a headache.Also, AMD has ROCM,
it's their equivalent of Nvidia's CUDA.Yeah but is it actually equivalent?
If so I'm 100% in but it needs to actually be. a drop in replacement for "it just works" like cuda is.
Once I've actually got drivers all set cuda "just works". Is it equivalent in that way? Or am I going to get into a library compatibility issue in R or Python?
Not all software that uses CUDA has support for ROCM.
But as far as setup goes, I just installed the correct drivers and ROCM compatible software just worked.
So - it can be a an equivalent alternative, but that depends on the software you want to run.
It's the equivalent, but does the software make use of the ROCM if they are programmed for CUDA?
Never had an issue with Nvidia on Linux. Yes, you have to use proprietary drivers, but outside of that I've been running Linux with Nvidia cards for 20 years.
Wayland is non-stop issues.
Been running Wayland for 2 years and only issue I had with it was Synergy not working.
Even not the "issue" that basically every time you update something, you have to wait a long time to download proprietary nvidia drivers?
That's what annoyed me the most back in the day with the Nvidia drivers,
so many hours wasted on updating the drivers.With AMD, this is not the case.
And haven't even talked about my issues with Optimus (Intel on-board graphics + Nvidia GPU) yet, which was a true nightmare, took me weeks of research to finally make it work correctly.
You don't need to update NVIDIA drivers every time there's a release. I don't even do that on my Windows machine. Most driver updates are just tweaks for the latest game, not bug fixes or performance improvements.
And hell, you're using Linux. Vim updates more often than the graphics driver, what do you expect?
It automatically happened,
I believe with every install of an updated Flatpak, which is rather often.Been a while though, since lately I've been happily using AMD for quite some time.
But I do recall Nvidia driver updates slowing down my update process by a lot,
while I have none of that with AMD.Ah, I always update the driver through the package manager and it never auto-updates.
My experience with the Deck outside of CS2 has been nothing short of mind-boggling. I don't even REALLY have a problem with CS2 but I cannot play online for VAC reasons I can't sort out. I have a ticket open with Steam Support. 🤷
Yeah, the deck has really increased my trust in AMD hardware.
CUDA isn't the responsibility of AMD to chase; it's the responsibility of Nvidia to quit being anticompetitive.
It's also not my problem either. I don't give a shit what nvidia or AMD does, I just want to be able to run AI stuff on my rig in as open-source a manner as is possible.
...in as open-source a manner as is possible.
And that means "not with CUDA," because CUDA is proprietary.
This is a semantic argument I don't feel like getting into. I don't give a shit what library it is -- I want AMD to be able to crunch pytorch as well as nvidia.
The fact that CUDA is proprietary to Nvidia isn't even slightly "semantics;" it's literally the entire problem this thread is discussing. CUDA doesn't work on AMD because Nvidia doesn't allow it to work on AMD.
More than that, they have zluda and Nvidia actively forbid others to run it
Permanently Deleted
Amd
Cuda support
😐