Luis Chamberlain sent out the modules changes today for the Linux 6.6 merge window. Most notable with the modules update is a change that better builds up the defenses against NVIDIA’s proprietary kernel driver from using GPL-only symbols. Or in other words, bits that only true open-source drivers should be utilizing and not proprietary kernel drivers like NVIDIA’s default Linux driver in respecting the original kernel code author’s intent.
Back in 2020 when the original defense was added, NVIDIA recommended avoiding the Linux 5.9 for the time being. They ended up having a supported driver several weeks later. It will be interesting to see this time how long Linux 6.6+ thwarts their kernel driver.
I’ve had a mixed experience with my newer AMD card, and that’s being charitable.
What were some of the positives and negatives? Me personally, I have an RDNA2 card and got bitten by the gamma being too dark on hardware cursors (now resolved) and memory clock stuck at 1 GHz with some refresh rates (workaround is not to use refresh above ~144 Hz).
I have an RDNA3 card (upgraded from a 1080) and am running a multi-boot triple-head setup with mixed refresh rates (60, 144).
Pros: most things work and work well. Installation of the physical card went without a hitch and it was relatively simple to install the drivers. No issues with web video, streaming, video encoding, or standard use.
Cons: the drivers are still lacking significant features - I am still unable to reliably control fan curves/speeds, clock speeds, etc. FreeSync is unusable as well. I have also been experiencing regular crashes on certain games (BG3, Apex Legends, etc.) and support has been nonexistent, despite similar complaints from other users. When the card does crash, it usually results in a ring timeout and an accompanied total session crash. AMD does not seem to be responsive to these issues in either their official forum or any other space where people are lodging complaints.
The hardware seems fine; the drivers are the main issue. If I had to do it over again, I’d hold my nose and buy NVIDIA.
EDIT: regarding the cursor issue, I’ve had to switch to a software cursor on Linux. The hardware cursor wasn’t showing up at all.
I had an rx480 that worked fantasic until a firmware update made it start freezing my pc in games after suspend, solution was to rollback that package to an older one or never use suspend. I currently have a 6650xt and that just crashes whenever it wants to sometimes, works fine for a few months then decides to freeze my whole pc, playing bg3 atm it froze on me like 3 times already
Ah, I just upgraded from RX580 to 6600XT and haven’t had any freezes so far. On RX580 I sometimes had games that managed to freeze the system complete with random pixel noise and VRAM fragments shown on screen for seconds before it rebooted, but that was a long time back and only on bleeding-edge Mesa and Proton Experimental so my own fault.
Mesa 22 and 23 have been great so far. Maybe the firmware got more stable as well (I’m on Debian). I’d definitely recommend an RDNA2 card over any Nvidia today despite some of these hiccups.
The GTX 1070 in my other machine has given me more headaches (kernel modules not compatible with newer kernels, random Vulkan issues resulting in broken shaders showing nonsense like sparkles or black areas, etc.).
My rx 480 worked way better in terms of not crashing, it did have graphical glitches in games but i guessed thats down to using Wine. Im also using Arch so maybe that in combination with the 6650 is making it more unstable, i gotta revert to using LTS kernel every few months to stop my system crashing randomly
I’ve had over twenty crashes in BG3 at this point. Crashing soeems to be more prevalent in certain areas of the game - Grymforge, especially.
deleted by creator
To be fair AMD closed-source drivers were much worse
There’s been some oddball nasty issues with Mesa recently. SteamVR causing the driver to crash (and the display just won’t come back :/) H265 encoding causing driver crashing, just weird stuff. Simple things like Wayland work great, but if you have even a slightly unique workload you may run into major issues
I’ve had lost of issues with SteamVR too but not with anything else. I suspect those issues are actually SteamVR’s fault tho because it’s pretty buggy on Linux in general.
Nah, straight up driver crashes are on Mesa’s side, not SteamVR’s. No userland software should be able to permanently bring down your driver.