It seems that the issue mentioned here (which was closed) is still present. Adding amdgpu.dcdebugmask=0x410 as a kernel parameter fixes the issue but from my understanding this disables PSR which results in more battery usage.
Has anyone else experienced this and possibly found other solutions?
Is this still happening on clean installs? (I have tried a live USB and the issue persisted so I am assuming that clean installs do not help but I could be wrong)
Use the appropriate kernel and GPU drivers.
At least, when I have these artifacts showing up, I go to the AMD page to download the latest driver package again.
There doesn’t seem to be any fix. Maybe some of the many issues on amdgpu’s gitlab (should be in the freedesktop gitlab) is still open, so you can comment there. If not, open a new one, maybe at some point they get this sorted out.
This is Linux, not Windows. There are no AMD drivers (of relevance, as the ADMGPU Pro drivers are not only irrelevant for pretty much everyone, but also unusable for most) you can download and install. They are baked into the kernel. To update them, you need to update the kernel. But even on 6.16.2 they are present, even with the latest firmware (assuming AMD is capable of at least auto-updating that and doesn’t just refuse loading it upon initrd built like with microcode).
Yeah, if you are on RHEL, Ubuntu or SLED. And only if you have a very good reason to do so. Beyond that, it’s very much discouraged to use them, they will basically have not a single benefit beyond some extremely niche apps and most likely cause more downsides (just like Nvidias proprietary crap) and even AMD is moving away from them. So no, under no circumstances should you install them unless you have an app that requires them.
You are using AMDVLK as basis of the AMDGPU Pro stack, but as far as I understand the installer, that doesn’t mean you only installed AMDVLK from that stack. Besides AMDVLK being inferior to RADV.
