This is most likely a mesa bug. You should report it there.
Thereās a kernel here which includes some AMD driver crash fixes:
Seems like Framework laptops with the high DPI and refresh rate tend to be pretty good with exposing driver bugs.
I couldnāt figure out the debs to download, but thanks for the link! Itās good to know work is in progress.
As an update, most of my problems have been solved by moving to kernel 6.16.0, mesa 25.1.7~kisak1~p.
The one remaining problem is the periodic screen flickering/warping. Has anyone found a fix for that? Is there a combo of drivers/kernel that makes this GPU work reliably yet?
As an update, most of my problems have been solved by moving to kernel 6.16.0, mesa 25.1.7~kisak1~p
Oh, thatās wild⦠I didnāt know the versions had progressed that high, Iām sitting here running 25.0.7 thinking that was brand new and up to date. I might try that, I havenāt seen the flickering in a very long time but I still have weird userland GPU issues that might be impacted by it. Thanks for the tip.
Is there a combo of drivers/kernel that makes this GPU work reliably yet?
The best workaround Iāve encountered so far has been FW supportās recommendation to enable āgaming modeā in the BIOS to lock 2 GB of RAM to the GPU. That doesnāt make it fully reliable for me, but it reduces the rate of trouble to once every week or so which is more-or-less tolerable.
I tried the trick of telling BIOS to dedicate 2GB to the GPU, latest mesa (25.3.2~kisak1~p), kernel (6.18.1) ā still getting the occasional flicker, especially in firefox.
Iām at my witās end. Anyone had any luck getting this chipset to work? What did you do?
Update: Thereās a better thread about the specific GPU flickering issue over here: Flickering when using Firefox under KDE Wayland on Ryzen AI 300 - #38 by Sleeping_bird ā sounds like they are hopeful they can work around it in the driver.
There is a report of underflow going on. I donāt have the link handy at the moment, but you can try to turn off memory self refresh using the amdgpu dcdebugmask and then try visiting a website that is tickling it.
If that helps then there is a potential patch to extend the timing of hysterisis loop by a few microseconds which is reported by several people to help.