Today, AMD are bringing out the big guns with the formal release of their next generation desktop GPUs with the AMD Radeon RX 6800 and the RX 6800 XT. Announced back in late October, these cards are AMD's first to come with hardware accelerated Ray Tracing support. Although for Linux, we're still waiting on The Khronos Group to formalise the cross-vendor Ray Tracing Vulkan extensions for that.
Here's a reminder of the specifications:
RX 6900 XT | RX 6800 XT | RX 6800 | |
---|---|---|---|
Compute Units | 80 | 72 | 60 |
Process | TSMC 7nm | TSMC 7nm | TSMC 7nm |
Game clock (MHz) | 2,015 | 2,015 | 1,815 |
Boost clock (MHz) | 2,250 | 2,250 | 2,105 |
Infinity Cache (MB) | 128 | 128 | 128 |
Memory | 16GB GDDR6 | 16GB GDDR6 | 16GB GDDR6 |
TDP (Watt) | 300 | 300 | 250 |
Price (USD) | $999 | $649 | $579 |
Available | 08/12/2020 | 18/11/2020 | 18/11/2020 |
For running them on Linux, the driver situation isn't the best. AMD have put out the Radeon Software for Linux version 20.45, which adds support for the Radeon RX 6800 Series but that driver only officially supports Ubuntu 20.04, RHEL/CentOS 7.9 and RHEL/CentOS 8.2. For Mesa drivers, you're going to need Linux Kernel 5.9, Mesa 20.2 (or newer) and also LLVM 11.0 which means most normal distributions will be missing out unless you're prepared to do major manual upgrades. So, unless you really know what you're doing with everything, you will likely want to hold off.
If you do manage to find one because, as expected, most places are sold out and you get everything it needs setup - expect to see some incredible performance. We don't get sent any hardware from AMD, so we're going by what others have been cooking up. It seems Level1Linux on YouTube are very happy with it, and the Phoronix benchmarks show them doing well too. From a price point of view, the performance does seem pretty amazing considering how close it appears to be with the NVIDIA 3080 and if you prefer the open source side of things it doesn't get better than this.
Quoting: tuubiYou should simply remove the old xorg.conf file. You don't need one for AMD or Intel.
In case you want to fiddle with options (e.g. to enable TearFree), it's better to just create a new file in /etc/X11/xorg.conf.d/ containing nothing but the device section for the driver.
You don't need one with Nvidia, either, and the butchered thing that their automated tool produces is just awful.
The invention of xorg.conf.d and being able to use snippets rather than having to specify the whole thing was a great improvement.
Quoting: MohandevirFrom what I heard from another user, couldn't Debian testing be considered a rolling release? Might give it a shot, eventually.
For the most part it's rolling. During Debian freeze period that precedes the release it's not.
There are some options for updating key components during the freeze though.
Last edited by Shmerl on 18 November 2020 at 6:49 pm UTC
Quoting: x_wingNo, it's more about getting a current mesa build. DKMS is easy. Though from my understanding is it shouldn't be needed with the AMD as it's in the kernel instead of needing a separate thing (though for the non-kernel driver you mention, sure the dkms would work).Quoting: slaapliedjeWith AMD being kernel based and needing latest Mesa, hardly anyone really packages those unless you want to make your system less stable and are into the whole ppa things. or you start compiling things from source, which I'm not exactly keen on doing for just the graphics card to work. You almost need to be running a rolling release like Arch to be able to just pop the card in and have it go.
I told you this before: you can install AMDGPU dkms using AMDGPU-PRO package release. You don't need a rolling release, having the driver in the kernel has nothing to do with the "problem" you mention. And if your point is that having a dkms driver makes your system less stable... well, that's exactly what happens with Nvidia.
Edit: Also of note, Debian doesn't seem to package amdgpu as dkms. They even have OpenRazer dkms packages, but not any radeon / AMD ones (last Radeon one I can see is from Jessie and is the fglrx one, which is ancient).
Last edited by slaapliedje on 18 November 2020 at 8:41 pm UTC
Quoting: ShmerlYeah, I run Debian Sid. Only really becomes unstable when they do the temp freeze on testing and that short period after a new stable comes out (as a huge amount of packages get flooded in).Quoting: MohandevirFrom what I heard from another user, couldn't Debian testing be considered a rolling release? Might give it a shot, eventually.
For the most part it's rolling. During Debian freeze period that precedes the release it's not.
There are some options for updating key components during the freeze though.
So, I'm happy the support is better than usual but what's the damn point if you can't buy the f**king thing... So pissed off right now, they ruined the party for me.
It should be illegal to promote and advertise product that are not fully available. Looking at the Ps 5, Xbox series X, rtx 3xxx and now Rx 6xxx...
Edit : how could I forgot the ryzen 59xx series... MIA too.
Last edited by TobyGornow on 18 November 2020 at 8:03 pm UTC
Quoting: slaapliedjeNo, it's more about getting a current mesa build. DKMS is easy. Though from my understanding is it shouldn't be needed with the AMD as it's in the kernel instead of needing a separate thing (though for the non-kernel driver you mention, sure the dkms would work).
I'm not sure what you mean here. Hopefully this will clarify your picture:
AMGPU: It's the AMD driver module that lives inside the kernel. You can update it by getting the latest stable/unstable kernel in your distro or by installing it as DKMS (the latter is what I mean by "installing it from AMDGPU-PRO").
Mesa: these are userspace libraries/drivers that implements graphics APIs (OpenGL, Vulkan, etc.). You can get a version by several ways:
- From your distro official repositories
- Third party repositories
- AMDGPU-PRO linux drivers package
- By compiling them by yourself (this step includes dealing with dependencies!)
So, getting the latest Mesa build is fairly trivial now days and the same can be said in order to get the latest kernel (at least in the majority of distros). IMO, any user that wants to setup his system for the latest Nvidia GPU will probably have to deal with both issues as well (with the difference that he may have to avoid some Linux kernel versions).
Last edited by x_wing on 18 November 2020 at 8:28 pm UTC
Quoting: x_wingYes, I know what all of that is. I've been using Linux for 20+ years at this point. I also vividly remember the hassle I had of trying to get the one AMD system I ever owned to work. Either the fglrx wouldn't compile with newer kernels, or the open source driver had shit performance. I was hoping this situation had improved, but it doesn't seem that way.Quoting: slaapliedjeNo, it's more about getting a current mesa build. DKMS is easy. Though from my understanding is it shouldn't be needed with the AMD as it's in the kernel instead of needing a separate thing (though for the non-kernel driver you mention, sure the dkms would work).
I'm not sure what you mean here. Hopefully this will clarify your picture:
AMGPU: It's the AMD driver module that lives inside the kernel. You can update it by getting the latest stable/unstable kernel in your distro or by installing it as DKMS (the latter is what I mean by "installing it from AMDGPU-PRO").
Mesa: these are userspace libraries/drivers that implements graphics APIs (OpenGL, Vulkan, etc.). You can get a version by several ways:
- From your distro official repositories
- Third party repositories
- AMDGPU-PRO linux drivers package
- By compiling them by yourself (this step includes dealing with dependencies!)
So, getting the latest Mesa build is fairly trivial now days and the same can be said in order to get the latest kernel (at least in the majority of distros). IMO, any user that wants to setup his system for the latest Nvidia GPU will probably have to deal with both issues as well (with the difference that he may have to avoid some Linux kernel versions).
1) official repos don't have it (debian sid)
2) I try to avoid third party repositories because they tend to break shit
3) AMDGPU-PRO linux package is not available for any Debian system.
4) Compiling myself is what I try to avoid.
So yeah, there are pros and cons to how AMD does it and how nvidia does it. Most distributions seem to favor the nvidia method, otherwise they'd take the AMDGPU Pro drivers and put them in the repos.
Quoting: x_wingSo, getting the latest Mesa build is fairly trivial now days and the same can be said in order to get the latest kernel (at least in the majority of distros). IMO, any user that wants to setup his system for the latest Nvidia GPU will probably have to deal with both issues as well (with the difference that he may have to avoid some Linux kernel versions).
Not really. nVidia bundles the API libraries with the driver, so I don't think Mesa really plays big role at all. I remember that there used to be bit trouble with that as driver would overwrite Mesa libraries. I don't know if these days things are less hassle as distro packaging has gotten better or drivers integrate with the system bit nicer way.
Kernel stuff is pretty much true though. Good thing is that you don't need to update the kernel. Bad thing is that you can't update to latest kernel, you'll have to wait for the support. You'll have to even longer if your distro doesn't provide the latest driver.
Last edited by Anza on 18 November 2020 at 8:53 pm UTC
Quoting: slaapliedjeYes, I know what all of that is. I've been using Linux for 20+ years at this point. I also vividly remember the hassle I had of trying to get the one AMD system I ever owned to work. Either the fglrx wouldn't compile with newer kernels, or the open source driver had shit performance. I was hoping this situation had improved, but it doesn't seem that way.
1) official repos don't have it (debian sid)
2) I try to avoid third party repositories because they tend to break shit
3) AMDGPU-PRO linux package is not available for any Debian system.
4) Compiling myself is what I try to avoid.
So yeah, there are pros and cons to how AMD does it and how nvidia does it. Most distributions seem to favor the nvidia method, otherwise they'd take the AMDGPU Pro drivers and put them in the repos.
Most distros doesn't favor Nvidia method, they just add their drivers because is the only way to make that hardware work (the "easiness" of Nvidia drivers is 100% thanks to the work the community does). And if you buy the latest Nvidia hardware, you are forced to use a third party repository, just like with AMD if you get their latest GPU. In the end, both delivers the same but AMD gives more options and more freedom.
Last edited by x_wing on 18 November 2020 at 9:05 pm UTC
See more from me