25
Nvidia will have to copy our frame generation approach, says AMD
(www.pcgamesn.com)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 11 Jan 2024
25 points (87.9% liked)
PC Gaming
8664 readers
436 users here now
For PC gaming news and discussion. PCGamingWiki
Rules:
- Be Respectful.
- No Spam or Porn.
- No Advertising.
- No Memes.
- No Tech Support.
- No questions about buying/building computers.
- No game suggestions, friend requests, surveys, or begging.
- No Let's Plays, streams, highlight reels/montages, random videos or shorts.
- No off-topic posts/comments, within reason.
- Use the original source, no clickbait titles, no duplicates. (Submissions should be from the original source if possible, unless from paywalled or non-english sources. If the title is clickbait or lacks context you may lightly edit the title.)
founded 2 years ago
MODERATORS
That is factually true, unless you're happy with the performance of Nouveau or whatever the OSS Nvidia driver is called.
To get an Nvidia card working you need a proprietary driver. Many distros can get it for you automatically during install but that still doesn't mean it won't cause issues. Every time there's a kernel update, DKMS needs to kick in and recompile the driver for the new kernel. If that fails for any reason, you might end up without a GUI on your next boot. To fix that, assuming it's even possible, you need some level of savvy. There's the lack of Wayland support, which is a problem for many, especially with Plasma 6 looming over the horizon and being Wayland-only.
Great! I'm glad your setup works flawlessly for you. Saying it always will for everybody is disingenuous at best though.
There you go. And no, it's not a Wayland problem. It's a lack of Wayland compatibility in the drivers. Fixing that is completely outside of the scope of Wayland.
I have a 7900XTX on Debian now, and zero hassle. I don't know what Arch has done to make your life difficult but it shouldn't have been the case. I have also run Nobara, Fedora and Bazzite on this hardware without a single issue. Well, I did have issues with Bazzite but none related to the GPU.
For my current Debian setup, the only GPU-related "tweaking" I had to do was to copy firmware blobs from the upstream kernel tree because some of them had not yet been packaged for the distro. This is a one-time operation though, and well documented.
Granted, I've been mostly on Wayland and KDE/Plasma but I have dipped into X every now and then for performance comparison. Never had a single driver issue.
Not saying your experience is invalid in any way but it shouldn't really be the case. It might be some quirk of Arch.
Yeah we established AI is a problem. It's irrelevant to gaming though, which is what we're discussing. I wonder if whatever tweaks and hacks you had to do to your AMD Radeon system to use AI on it might be part of the causes of your problems. No idea, honestly - but again, irrelevant.
Ah yes, the FUD bogeyman.
DKMS has been around for over 20 years, "But it might fail! I have anecdotal evidence!" I mean if that's the case, we should probably stop using cell phones and laptops because batteries are known to swell and explode, right?
"But it's proprietary!" So you have an issue with using a proprietary driver, but you're perfectly fine with running Steam and the thousands of proprietary games on Linux?
AMD just works? Well sure, but then you reference some obscure blog post as "well documented", at the same time saying a DKMS driver install might fail and it might not be possible to resolve, as if booting off a rescue USB and downgrading packages isn't a well documented procedure.
Hey, sorry if I hit a nerve. It really wasn't my goal.
That said:
I never said that. I haven't provided anecdotal evidence either. It's not hard to find it though: https://duckduckgo.com/?t=ffab&q=dkms+failure+nvidia&ia=web
Ironically, you're the one presenting anecdotal evidence. Your own. Nothing more.
This is a strawman, I'm not going to engage.
Like I said, the blog post is mine. It documents how I set up my system. From there, there are links to Debian's official docs. If you had actually read any of it, you would have found that out yourself.
Also, it's nothing to do with drivers. It's firmware.
Ah yeah - booting off a rescue USB and downgrading the kernel plus going through DKMS on a live system (perhaps a chroot, I'm not sure what the procedure would be). That's what I consider smooth sailing and no shenanigans!
The firmware that's missing on Debian's packages are present in other systems by default - and they're only missing on Debian because they're still fresh. They're static so you install them once and are done with it for the life of the system. No recompilation, no reinstalls, nothing at all.
Furthermore, the GPU works without them, but it lacks some functionality and it can have an impact on performance. The system never becomes unstable or without a GUI though.
Apologies. I have a 3090 in my old system which I run headless in a closet as a dedicated AI LLM/image generator. When buying a new system, I listened to all the "Nvidia sucks, AMD just works!" hype, and opted for a 7900XTX. To say I'm disappointed is an understatement, and I sincerely wished I had not listened to the Linux community at large.
But yes, ESO/Neverwinter/Solasta and the few other RPG's I play under Proton/Steam work well and rarely crash.
Compared to what you documented in your blog? Not to mention the rescue CD is if DKMS fails, your steps are just to get it working.
No need to apoligise! I get that you're frustrated and why. AMD is really not (yet?) anywhere close to Nvidia for AI (or Ray Tracing!).
Yes. What I documented on the blog is a few commands once in a lifetime, from the comfort of your GUI, with the browser running where you can copy-paste from directly into the terminal emulator. I do consider that a lot less faff than booting off a live USB and figuring out how to compile a driver that DKMS failed to do automatically, then make sure it will work when I boot from my actual system.
Not quite. The system works fine without that. In fact, I played a few games with no issues whatsoever before I figured out there were firmware files missing. In fact, the only thing that tipped me to thag were errors in
dmesgwhich I only looked because I'm a stickler for that kind of stuff and decided to poke and prod as many logs as I could when I was building the system.Also like I mentioned, this is only necessary because Debian haven't packaged those files yet. Many distros have them out of the box.
In any case, I know that plenty of people run Nvidia on Linux and face no issues. I have no interest in AI stuff on my Linux box and I have no love lost for Nvidia. That, coupled with AMD having been historically a lot friendlier to Linux than Nvidia, plus the fact that the drivers compile and ship with the kernel, made my purchase decision pretty easy. To each their own though, and clearly for your needs Nvidia is the way to go.
So going back to the start of the conversation, neither GPU is completely shenanigans free. Both require research, documentation, and additional work. Linux has a learning curve.
Does AMD 'work out of the box'? Sort of, but it really depends on the card and distribution. I know with Arch for example, things like scrolling in Youtube were horrendously laggy and I spent a few hours trying to install missing packages trying to figure out what was wrong. I haven't tried any other distros with an AMD card, but I've run PopOS, Ubuntu, and Arch on Nvidia without significant issues (other than modifying the kernel cmdline), but let's be honest that's less work than setting up almost anything else you're going to run on Linux.
Booting off a USB is also incredibly easy, and it's probably something everyone should have some experience with. Less than 3 hours after a fresh install I accidentally removed my user from the
wheelgroup and lost sudo privileges ...