# Framework 16 internal display freezing

**URL:** <https://community.frame.work/t/framework-16-internal-display-freezing/75069>\
**Category:** Community Support\
**Tags:** framework-laptop-16-amd-7040, display-issues, graphics-module-amd-rx7700s\
**Created:** [September 9, 2025, 12:33pm UTC](https://community.frame.work/t/framework-16-internal-display-freezing/75069 "2025-09-09T12:33:15Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![Cookiespace](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/cookiespace/32/17893_2.png) [@Cookiespace](https://community.frame.work/u/Cookiespace)\
**Post date:** [September 9, 2025, 12:33pm UTC](https://community.frame.work/t/framework-16-internal-display-freezing/75069/1 "2025-09-09T12:33:15Z")

</div>

The internal display of my Framework 16 tends to freeze.  
This happens every time the screen goes black (because of screen saver or sleep mode).  
It happens sometimes when connect or disconnect an external display.  
Today it also simply happens every time on start up.

It happens after the log in. The log in itself works fine.  
External displays also work fine. I can also plug them in when the internal one already froze and it connects just fine.  
When that happens I need to restart the system, although today even that didn’t help because it just freezes again.

I use the 7040 series with AMD Radeon™ RX 7700S.  
My OS is Fedora 42.

Has anybody experienced this before or has an idea how to deal with it?

---

<div class="post-metadata">

**Author:** ![Eagle](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/eagle/32/39020_2.png) [@Eagle](https://community.frame.work/u/Eagle)\
**Post date:** [September 9, 2025, 3:23pm UTC](https://community.frame.work/t/framework-16-internal-display-freezing/75069/2 "2025-09-09T15:23:31Z")

</div>

Hey @Cookiespace Have you contacted our [support](https://framework.kustomer.help/contact/support-request-ryon9uAuq?)?

---

<div class="post-metadata">

**Author:** ![Alex\_Morozov](https://avatars.discourse-cdn.com/v4/letter/a/bc79bd/32.png) [@Alex\_Morozov](https://community.frame.work/u/Alex_Morozov)\
**Post date:** [September 9, 2025, 5:17pm UTC](https://community.frame.work/t/framework-16-internal-display-freezing/75069/3 "2025-09-09T17:17:17Z")

</div>

@Cookiespace could be an issue fixed by setting dcdebugmask on boot. Check this thread:

> [@Xorg i3 Freezes on AMD Ryzen AI 300 mainboard](https://community.frame.work/t/xorg-i3-freezes-on-amd-ryzen-ai-300-mainboard/68543):
>
> I’ve upgraded my FW13 laptop from an AMD Ryzen 7040 mainboard to the Ryzen AI 9 HX 370 today. After sorting through some secureboot issues, now I get inexplicable system hangs about a minute or so after launch, with nothing obvious in dmesg or journalct. If I run to TTY and run startx, I have a working system again for about 5 minutes. I’m running manjaro 25.0.0, My kernel is 6.12.21-4-MANJARO I use i3wm. . Edit: this may be an xorg issue, sway works. Edit: So far, I suspect it might hav…

there is also a bunch of original threads about the issue on this forum.

---

<div class="post-metadata">

**Author:** ![dimitris](https://avatars.discourse-cdn.com/v4/letter/d/db5fbb/32.png) [@dimitris](https://community.frame.work/u/dimitris)\
**Post date:** [September 9, 2025, 7:15pm UTC](https://community.frame.work/t/framework-16-internal-display-freezing/75069/4 "2025-09-09T19:15:36Z")

</div>

It’s also worth looking into this, possible workaround in kernel command line:

> [@Main display sometimes fails while using external monitor](https://community.frame.work/t/main-display-sometimes-fails-while-using-external-monitor/74677):
>
> Hi all, bit of a weird issue… I’ve been using my laptop in a ‘docked’ configuration for a while, with various devices connected. At seemingly random intervals the built in display will stop updating (being stuck showing the last thing it was displaying) and will only work again after a reboot. Devices connected are as follows: usb-c –\> power/ethernet adaptor –\> network cable & usb power supply usb-c –\> usb-a kvm hub with mouse and keyboard attached hdmi –\> kvm hub (same device) –\> hdmi –\> ac…

---

<div class="post-metadata">

**Author:** ![Ken\_Hawley](https://avatars.discourse-cdn.com/v4/letter/k/f6c823/32.png) [@Ken\_Hawley](https://community.frame.work/u/Ken_Hawley)\
**Post date:** [September 9, 2025, 8:12pm UTC](https://community.frame.work/t/framework-16-internal-display-freezing/75069/5 "2025-09-09T20:12:44Z")

</div>

Yes, I had a variation of this same issue (display would freeze seemingly at random, external display fine) and adding the kernel command line argument seems to have helped. I would recommend using grubby, I think it’s built in to Fedora…

> From the Fedora forum: ( [Adding kernel commandline options? - #2 by litemotiv - Fedora Discussion](https://discussion.fedoraproject.org/t/adding-kernel-commandline-options/146974/2) )  
> ”To add or remove a kernel command line arg use grubby.
> 
> **sudo grubby --update-kernel=ALL --args=amdgpu.dcdebugmask=0x10**
> 
> It’s easier then the steps @litemotiv outlined.”

I’ve modified the line from the original post, so you could just copy paste it (the line in bold) if you wanted. It’s what I did and seems to have worked for me.

---

<div class="post-metadata">

**Author:** ![Cookiespace](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/cookiespace/32/17893_2.png) [@Cookiespace](https://community.frame.work/u/Cookiespace)\
**Post date:** [September 10, 2025, 6:56am UTC](https://community.frame.work/t/framework-16-internal-display-freezing/75069/6 "2025-09-10T06:56:17Z")

</div>

Not yet, thought I’d try a few things myself first

---

<div class="post-metadata">

**Author:** ![Cookiespace](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/cookiespace/32/17893_2.png) [@Cookiespace](https://community.frame.work/u/Cookiespace)\
**Post date:** [September 10, 2025, 6:57am UTC](https://community.frame.work/t/framework-16-internal-display-freezing/75069/7 "2025-09-10T06:57:52Z")

</div>

Hey, thanks a lot for the command. It partially helped. The screen works after restart again, but still freezes after waking up from sleep mode

---

<div class="post-metadata">

**Author:** ![Cookiespace](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/cookiespace/32/17893_2.png) [@Cookiespace](https://community.frame.work/u/Cookiespace)\
**Post date:** [September 10, 2025, 7:17am UTC](https://community.frame.work/t/framework-16-internal-display-freezing/75069/8 "2025-09-10T07:17:29Z")

</div>

> [@Internal display freezes after login](https://community.frame.work/t/internal-display-freezes-after-login/73799):
>
> Hello! Since a few weeks I’m experiencing the issue, that the internal display freezes after a few seconds after resuming/logging in with Gnome. The keyboard still responds, I can change the screen brightness and make screen shots from the contents of the screen. I can unfreeze it with running printf freeze \> /sys/power/state (I set a hotkey for that) loginctl suspend does not help. My feeling is, that something in the handover between the lock/login screen and the gnome session goes wrong. Th…

this workaround with the freeze command works but I had to adapt it to `echo freeze | sudo tee /sys/power/state` which needs sudo, which means I need to enter my password while not knowing if the password dialog is actually open or not…

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex001/uploads/framework3/original/1X/64c81a89f963ddb07633887baceb642a4b056046.png) [@system](https://community.frame.work/u/system)\
**Post date:** [March 9, 2026, 7:18am UTC](https://community.frame.work/t/framework-16-internal-display-freezing/75069/9 "2026-03-09T07:18:00Z")

</div>

This topic was automatically closed 180 days after the last reply. New replies are no longer allowed.
