Maybe AMD can put some resources into fixing RDNA3 instability with the latest kernels this year? I’ve had unrecoverable system crashes (no access to TTY, keyboard/mouse locked up) when gaming with RDNA3 on any kernel >6.12, and mostly on wayland, numerous times now. I don’t undervolt/overclock. And I’m only running a 7900XT (a 2+ year old card now).
I’m basically relegated to running either on the 6.12 kernel, or run everything with gamescope just to attempt to guarantee stability and recoverability from crashes. Gamescope “works”, but seems to run best using “-f” for fullscreen mode – anything else seems to have some quirkiness for me.
I run cachyos. I know that they like to tweak the kernel and change numerous settings which can make gaming less stable in my specific scenario. I think I’m going to just run everything via gamescope now since I seem to have the proper flags to make it just work without oddities for me (I liked being borderless, but that causes issues with some games, so I am avoiding that now). And then see if I get any crashes. If I continue to see crashes, hopefully recoverable this time, then I may stick with linux-lts kernel instead of using cachy’s.
Maybe AMD can put some resources into fixing RDNA3 instability with the latest kernels this year? I’ve had unrecoverable system crashes (no access to TTY, keyboard/mouse locked up) when gaming with RDNA3 on any kernel >6.12, and mostly on wayland, numerous times now.
7900XT
There may be some kind of regression, but as a data point, I run 6.12.48+deb13, which is what Debian stable uses, on a XT 7900 XTX and haven’t had stability problems with games.
It could be about 1,000 different things, including hardware issues completely unrelated to the OS. I also have a PC with a 7900XTX on Linux 6.18.2, using Plasma/Wayland and I’ve never had an unrecoverable system crash. Two of the other people that I game with are also running the exact same setup (Arch,btw/Linux6.18.2/Plasma/Wayland) without issue.
Blaming graphics cards sometimes feels like a meme. Its like if someone has any kind of problem and happen to mention that they use NVIDIA, you’ll see a huge portion of commenters, with nothing other to add, jump in to imply that it’s probably the NVIDIA card.
Well when the crash happens and the screen shows an enormous amount of green artifacting, sure looks like a graphics driver and/or kernel issue to me. But yeah, I’m probably wrong because your experience is pristine. And the many hours of research I’ve done on this subject leads to the conclusion that there are issues with 6.13+ kernel, amdgpu driver, and Wayland, and especially if having more than one display connected (despite setting the refresh rates to the lowest common denominator).
But I’m sure I’m wrong and it’s something completely different. Thanks for the insight.
In fairness, distros do include their own patches, and it’s possible that there is some regression that showed up somewhere above 6.12 and he’s running a vanilla kernel and the Arch guys put in some patch that fixes whatever he’s seeing that isn’t in vanilla or something. Or maybe he’s using a distro that includes some kind of kernel patch that introduces the problem, if he’s not building his own kernels. I mean, I’ve got no idea what the guy is running; he doesn’t say.
I don’t doubt that it could be the graphics card. It is just that we don’t have the information to say for sure and their description leaves a lot of other possibilities.
Yeah, same. At first it was just Nioh 2 (and, fair. That game is such a technical mess that it is a miracle to run it under normal circumstances) but I’ve increasingly had crashes in Warframe which makes me REAL sad.
Was aware of the kernel bypass. Wasn’t aware that gamescope had an impact so will definitely try that. Thanks
Maybe AMD can put some resources into fixing RDNA3 instability with the latest kernels this year? I’ve had unrecoverable system crashes (no access to TTY, keyboard/mouse locked up) when gaming with RDNA3 on any kernel >6.12, and mostly on wayland, numerous times now. I don’t undervolt/overclock. And I’m only running a 7900XT (a 2+ year old card now).
I’m basically relegated to running either on the 6.12 kernel, or run everything with gamescope just to attempt to guarantee stability and recoverability from crashes. Gamescope “works”, but seems to run best using “-f” for fullscreen mode – anything else seems to have some quirkiness for me.
I had the same experience. Bazzite 41 or 42 (can’t remember) fixed it for me.
I run cachyos. I know that they like to tweak the kernel and change numerous settings which can make gaming less stable in my specific scenario. I think I’m going to just run everything via gamescope now since I seem to have the proper flags to make it just work without oddities for me (I liked being borderless, but that causes issues with some games, so I am avoiding that now). And then see if I get any crashes. If I continue to see crashes, hopefully recoverable this time, then I may stick with linux-lts kernel instead of using cachy’s.
There may be some kind of regression, but as a data point, I run 6.12.48+deb13, which is what Debian stable uses, on a XT 7900 XTX and haven’t had stability problems with games.
It could be about 1,000 different things, including hardware issues completely unrelated to the OS. I also have a PC with a 7900XTX on Linux 6.18.2, using Plasma/Wayland and I’ve never had an unrecoverable system crash. Two of the other people that I game with are also running the exact same setup (Arch,btw/Linux6.18.2/Plasma/Wayland) without issue.
Blaming graphics cards sometimes feels like a meme. Its like if someone has any kind of problem and happen to mention that they use NVIDIA, you’ll see a huge portion of commenters, with nothing other to add, jump in to imply that it’s probably the NVIDIA card.
Well when the crash happens and the screen shows an enormous amount of green artifacting, sure looks like a graphics driver and/or kernel issue to me. But yeah, I’m probably wrong because your experience is pristine. And the many hours of research I’ve done on this subject leads to the conclusion that there are issues with 6.13+ kernel, amdgpu driver, and Wayland, and especially if having more than one display connected (despite setting the refresh rates to the lowest common denominator).
But I’m sure I’m wrong and it’s something completely different. Thanks for the insight.
Gosh, you sure got me. I certainly look like an idiot basing my opinion on what you wrote.
Thanks to your sarcastic reply I’ve learned to read the mind of commenters before replying.
What an idiot I am for not realizing all of the troubleshooting steps that you’ve taken simply because you never mentioned them.
👍
In fairness, distros do include their own patches, and it’s possible that there is some regression that showed up somewhere above 6.12 and he’s running a vanilla kernel and the Arch guys put in some patch that fixes whatever he’s seeing that isn’t in vanilla or something. Or maybe he’s using a distro that includes some kind of kernel patch that introduces the problem, if he’s not building his own kernels. I mean, I’ve got no idea what the guy is running; he doesn’t say.
I agree.
I don’t doubt that it could be the graphics card. It is just that we don’t have the information to say for sure and their description leaves a lot of other possibilities.
Yeah, same. At first it was just Nioh 2 (and, fair. That game is such a technical mess that it is a miracle to run it under normal circumstances) but I’ve increasingly had crashes in Warframe which makes me REAL sad.
Was aware of the kernel bypass. Wasn’t aware that gamescope had an impact so will definitely try that. Thanks