For AMD you really should just stick to the drivers that will already be included out of the box, and generally you’ll get a better experience using newer kernels, especially for a relatively recent architecture like RDNA3.
Oof. I had the same issue when I (back when it was new) used a 6800XT on a Mint install with an old kernel. Maybe it’s worth testing with a newer kernel or on a distro that pushes more frequent kernel/Mesa updates
Yeah thanks! I got it working in the end with the updated recent AMD firmware from the kernel release, updating to an 6.5-oem kernel, and rebuilding initramfs with the updated firmware files, as detailed here: askubuntu.com/…/how-to-make-ubuntu-22-04-work-wit…
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.
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.
Reading his comment, it looks like KDE Neon ships with a two-year-old kernel, so I assume that that’s the issue.
So…what can I do? Neon is mostly Ubuntu 22.04 to most effects. Kernel is 6.2.0-36-generic.
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.
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.
I changed the file download to the latest, which at this moment is linux-firmware-20231111.tar.gz. After the update-initramfs, reboot (since I already ran the PPA earlier…to no avail), and this time it worked, and it immediately showed me the second monitor, which had been dead for the last couple of hours since I started fighting this thing.
A second update after this is, since I’m using Wayland and multi-monitor (two HDMI connections, one the main monitor, the second to a big LCD TV)…when the TV is turned off, the monitor starts to flicker rearranging the windows (!?). I describe the issue a bit more in detail here… lemm.ee/post/14853567
You can go download their stuff if you want the absolute latest or something, but unless I had some kind of problem with the driver my distro shipped, I probably wouldn’t bother.
I also have a 7800 XT and use Debian. I had to download firmware from git.kernel.org, as not even the package in unstable is new enough: stable has 2023-02-10, unstable currently has 2023-05-15, while 7800 XT (and 7700 XT) needs 2023-08-04 or newerAt least bookworm-backports has a new enough kernel now. (6.5, IIRC 6.4 is the minimum.)
But to get ROCm working, I ended up adding AMD repositories and using its drivers with the 6.1 kernel from stable.
Nobara! It is awesome for gaming and performsnce intensive tasks and beside being an obscure distro is maintained by reputable people (glorious eggroll, proton GE creayor)
It’s great! You can expect updates that don’t take literal years, but you will need to maintain your system a bit more (Garuda provides utilities to make it easier).
Simple stuff like managing some dependency issues (like when packages get renamed), actually knowing how to use the command line (you don’t need to learn awk, grep, and sed just yet), and knowing how your bootloader wants to be treated.
You’ll get it as time passes, but Garuda assists in most of these things.
I’m currently using Garuda! I love the arch features (rolling release, AUR, etc) and love the game integration tools: 1 click to install nvidia drivers, wine w/winetricks, retroarch, and a bunch more.
However sometimes I observe some kind of stuttering during games. I have a 3070Ti and that kind of stuff shouldn’t be happening on 5+ year old games.
I would still recommend it as a lot more people seems to be running it without issues, but idk, I guess no system is perfect.
Garuda was the first Linux distro I was using as a daily driver. To me it was working nice out of the box with a Nvidia GPU and It was beginner friendly to me. I have since switched to Arch now, but yeah. Give it a go
Garuda is easily my favorite arch based distro, nice to see ppl talking about it! Once you get used to using yay instead of apt-get and the AUR in general it’s such a better experience
yay (desired package) You’ll see multiple choices most likely, pick one and it’s pretty self-explanatory from there.
To remove program: yay -R (program)
system update/update all packages: yay -Syu
There are a few different package management tools too like Octopi which let you directly browse the AUR by category in a GUI but I think that’s pm the basics.
With regards to Arch based distros: Do you still need to read Arch news to spot potentially breaking updates and know how to diff pacsave/pacnew, etc. or have Garuda found a way to manage these things?
It’s probably wise to check the forums regularly, I had to reinstall the entire OS once (arguably because of NVIDIA) but on more than one occasion it’s stopped a update for me because packages were in conflict. So it’s nice that there’s some foresight on their part.
S is for sync, which installs packages from the repositories. u is for upgrade, which upgrades out-of-date packages. y causes pacman to refresh the package databases. In short, it upgrades all packages that are out of date. It’s a very standard command and not dangerous lol. Btw, with yay just typing in “yay” without -Syu does the same thing, which is convenient
I can’t speak for Garuda, but if its Arch based I’d imagine it’d be pretty smooth. Gaming on Arch was like a few button clicks to enable proton in my laptop and thats it. I think theres a steam package on the AUR, idk if Garuda can use arch user repository I’ve never looked at it. I’d say go for it, especially if you backup your current setup.
linux_gaming
Hot
This magazine is from a federated server and may be incomplete. Browse more on the original instance.