# FW 16 with display issues

**URL:** <https://community.frame.work/t/fw-16-with-display-issues/79442>\
**Category:** Linux\
**Tags:** arch\
**Created:** [January 5, 2026, 8:28am UTC](https://community.frame.work/t/fw-16-with-display-issues/79442 "2026-01-05T08:28:58Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![Andrew\_Moise](https://avatars.discourse-cdn.com/v4/letter/a/ce7236/32.png) [@Andrew\_Moise](https://community.frame.work/u/Andrew_Moise)\
**Post date:** [January 5, 2026, 10:56pm UTC](https://community.frame.work/t/fw-16-with-display-issues/79442/3 "2026-01-05T22:56:27Z")

</div>

This looks exactly like the graphical corruption I got when I was being bit by the infamous FW16 GPU freeze bug.

In my case, it took a mainboard replacement to resolve it. Some people have reported success with kernel arguments or BIOS updates (though it seems like you’re running a recent enough version that it should be fine?). There are discussions about the issue here, without really a clear resolution:

> [@FW16 Screen Freezeing on Linux](https://community.frame.work/t/fw16-screen-freezeing-on-linux/73958/20):
>
> That’s sadly the difficult truth. I don’t even know how far AMD gives testing devices to their Linux devs. If you have something very rare (for all I remember only one other person or so said to have the same or a similar bug) it becomes really difficult to figure these things out. One of the AMD guys even recommended to me to try to bisect the problem to figure out the offending commit. But when you can’t even tell how to reliably trigger the issue, and when you have not the slightest clue abo…

> **[System Freeze after upgrading to kernel 6.12.30 (#4305) · Issues · drm / amd...](https://gitlab.freedesktop.org/drm/amd/-/issues/4305)**
>
> After upgrading my debian kernel from 6.12.27 to 6.12.30, I began getting the following error a few minutes after startup, which eventually locks up the entire system: Log...

> **[Periodic display hang on Framework 16 / Phoenix1 \[15bf\] - dmub\_replay\_enable...](https://gitlab.freedesktop.org/drm/amd/-/issues/4399)**
>
> Brief summary of the problem: About once every 2-5 days of use, my laptop's display hangs. Sometimes there is graphical corruption...

You might try the kernel arguments that other people have tried, or you might talk to Framework support about the issue. One way or another it definitely seems to be an issue on Framework’s side.

---

_[View the full topic](https://community.frame.work/t/fw-16-with-display-issues/79442)._
