18
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 13 Nov 2023
18 points (100.0% liked)
Linux Gaming
15304 readers
8 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 1 year ago
MODERATORS
As others have said "Ya doin it wrong!"
AMD has the AMDGPU kernel driver already in place in the linux kernel, and excluding the newest generations of cards for about a month or two after they come out, that part should work fine. Additionally, you need Mesa installed for the userspace drivers. It is typically preinstalled and covers the OpenGL and Vulkan drivers for your card.
Pretty much the only time you want to run the driver from AMD's site is if you're using some particular professional applications, otherwise Mesa tends to outperform it. There are relatively few games that AMDVLK (the AMD official open source Vulkan driver) is ahead, and it's got an edge in most (all?) raytracing cases currently.
Lastly, the reason it doesn't work is because the driver install script is checking your os-release version to see if it matches the Ubuntu version it was packaged for. If you're confident that you can fix any problems that arise from doing this, you could presumably just change the string in /etc/os-release to match what it's looking for. I don't recommend doing this, though, unless you don't care if the drivers break things because they weren't packaged for the release you're using.
Reading his comment, it looks like KDE Neon ships with a two-year-old kernel, so I assume that that's the issue.
https://en.wikipedia.org/wiki/KDE_neon
Linux 5.15 came out in October 2021, and his card was just released.
The kernel in use should support RDNA3, I believe.
Edit: judging from the comment made a bit ago, it wasn't the kernel or mesa, they were just missing the firmware. And yeah, that'll do it. I remember being frustrated with my 7900xtx not working on Pop! before I pulled in the firmware back on release.
Thanks. I wasn't aware of the difference privative vs public ones on AMD. On Nvidia (where I came from) it's kinda the opposite, noveau kinda works, but if you really want to play with proper performance, you should head for the privative one. In the end it was just easier to download the AMD firmware from the latest linux release, and recompile with that. It worked after that.
If you were missing firmware, that's not actually a driver issue. You do need the firmware and (unless you also installed the professional drivers as well) you should be all good now and using the full open source stack.
Anyway, glad to hear it's working for you!
Yeah...kinda. Now on multi-monitor setup I have a weird glitch...when one of the monitors are turned off. Screen will start flickering rearranging the windows. Weird.
Do you mean it constantly does it when a monitor is turned off or that when you initially turn off a monitor, it rearranges all windows to fit on the remaining monitor.
If the first, I'm not sure what the problem might be, but the second is pretty normal, I think. The card sees that the display was detached and moves your windows to the attached display so you can see them.
...the first, I'm afraid. It continues to jump the windows out of place, about 3 times within 2 seconds, every 20 seconds or so...