# FW16 Screen Freezeing on Linux **URL:** \ **Category:** Linux\ **Tags:** arch\ **Created:** [August 15, 2025, 6:33pm UTC](https://community.frame.work/t/fw16-screen-freezeing-on-linux/73958 "2025-08-15T18:33:03Z")\ **Posts on this page:** 20\ **Page:** 3
**Author:** ![Richard](https://avatars.discourse-cdn.com/v4/letter/r/f0a364/32.png) [@Richard](https://community.frame.work/u/Richard)\ **Post date:** [November 25, 2025, 3:35pm UTC](https://community.frame.work/t/fw16-screen-freezeing-on-linux/73958/42 "2025-11-25T15:35:19Z")
I’m quite convinced - wether this is a hardware or a software issue - this must be an issue that’s rooted in the mode the GPU is in. Once this issue appears, it will continue appearing within minutes even after a reboot if I don’t turn off the device for at least like half an hour, reproducibly. Though there’s exactly one scenario that seems to be reliably preventing it: playing a video. I can’t tell if it just needs to be in the foreground or if it needs to be full screen (I only have it playing full screen), but no matter how I play it, be it locally through mpv or like a YouTube video through Firefox, it will always prevent it from happening. Though I can’t tell if watching the video or if the hardware accelerated playback is doing the fix. Also, in tty mode it barely ever happens. EDIT: just having the video play in the foreground is enough, doesn’t need to be fullscreen. Though I haven’t yet tested software vs hardware decoding. And I can confirm this for Debian Testing, Gnome (up to 49.2 currently) and BIOS 4.02, on basically any kernel of the past year or so. Though I haven’t tried suspending for fixing it yet, all I tried was `rmmod -f amdgpu && modprobe amdgpu` (which either fails or takes a very long time to complete, no idea) and just using the SysRQ key combination for rebooting (which fails sometimes, while the combination for shutdown basically never works). ---
**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:** [December 18, 2025, 9:14pm UTC](https://community.frame.work/t/fw16-screen-freezeing-on-linux/73958/43 "2025-12-18T21:14:18Z")
Yeah. That tracks with my experience back when I was having this issue. I’ve had even stranger manifestations of it, where it would crash with graphical corruption, I would power off and do something else for an hour, and then when I powered back on the system the corruption would be overlaid on the screen over top of the bootloader and whatever else I was doing with the machine. That was what apparently finally firmly convinced Framework support that it was a hardware issue 🥲 ---
**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:** [December 18, 2025, 9:18pm UTC](https://community.frame.work/t/fw16-screen-freezeing-on-linux/73958/44 "2025-12-18T21:18:40Z")
> I get that this is frustrating, but I dont think you are hitting the bug, and if you are, its not really on framework’s end. Its on the developers for the distro you are running. Have you tried to create a bugzilla for Fedora? Fedora Bugzilla link I can definitively say that this was either a hardware or BIOS issue for me when I ran into it, not a software issue. It happened on Ubuntu live CD, and replacing my mainboard with a new one Framework shipped me fixed the issue still running the same software. Upgrading the old mainboard to BIOS 03.07 _also_ fixed it, so thanks to Perri for the recommendation, but the new mainboard fixed it apparently on all BIOSes in addition to some other issues it was having. ---
**Author:** ![CobFather](https://avatars.discourse-cdn.com/v4/letter/c/c77e96/32.png) [@CobFather](https://community.frame.work/u/CobFather)\ **Post date:** [December 27, 2025, 8:30pm UTC](https://community.frame.work/t/fw16-screen-freezeing-on-linux/73958/45 "2025-12-27T20:30:33Z")
I’ve been having this issue as well. I tested just running this laptop without an external monitor the internal display would freeze plugging in a monitor I could use my laptop. If I would suspend the laptop by closing the screen and reopening it would fix the issue. Initially I was having this issue on Ubuntu then I tried switching over to Bazzite to see if it would fix the issue it still occurs. The display freezes when playing games such as Elden Ring or doing a google meets call. ---
**Author:** ![Richard](https://avatars.discourse-cdn.com/v4/letter/r/f0a364/32.png) [@Richard](https://community.frame.work/u/Richard)\ **Post date:** [January 17, 2026, 1:55pm UTC](https://community.frame.work/t/fw16-screen-freezeing-on-linux/73958/46 "2026-01-17T13:55:22Z")
I’ve now created an issue at Framework’s official [firmware issue tracker](https://github.com/FrameworkComputer/SoftwareFirmwareIssueTracker). No idea if this is caused by Linux, firmware/BIOS or hardware, but this has been around for too long, and the fact that I haven’t heard of any other AMD 7040 series laptops being affected suggests Linux isn’t really the cause. Once I finally get a working replacement mainboard (from another issue) I’ll report back if that was able to fix things. ---
**Author:** ![Richard](https://avatars.discourse-cdn.com/v4/letter/r/f0a364/32.png) [@Richard](https://community.frame.work/u/Richard)\ **Post date:** [January 21, 2026, 4:28pm UTC](https://community.frame.work/t/fw16-screen-freezeing-on-linux/73958/47 "2026-01-21T16:28:04Z")
I can now confirm that a mainboard replacement didn’t fix the issue. In fact, it seems like AMD has a very bad streak of bad drivers over the past months. It seems there are several bugs around that cause screen freezes. The main one affecting us might be this one: > **[7840U/780M: \`\*ERROR\* \[CRTC:83:crtc-1\] flip\_done timed out\`, leads to frozen...](https://gitlab.freedesktop.org/drm/amd/-/issues/4141)** > > Machine is a Framework 13 7840U running Fedora with kernel 6.13.11-200.fc41.x86\_64, but note this has also been reported on a Thinkpad with... with many issues being opened around this: [Making sure you're not a bot!](https://gitlab.freedesktop.org/drm/amd/-/issues/?search=flip_done%20timed%20out) A few people do report that setting `amdgpu.dcdebugmask=0x10` as boot option may help (it disables panel self refresh, so it significantly lowers efficiency). I’m trying that one out right now. Also, it seems that while right now only AMD GPUs seem to be affected, it may be a very fundamental issue of the Linux kernle itself/how it handles “page flips”. As at least the amdgpu recovery method seems to be failing for months now, plans are to introduce a manufacturer-independant way to recover from this misbehavior: [Display Next Hackfest 2025 | Xaver’s blog](https://zamundaaa.github.io/wayland/2025/07/22/display-next-hackfest-2025.html#:~:text=My%20%E2%80%9CFavorite%E2%80%9D%3A%20Pageflip%20Timeouts) So everything indicates there may be nothing we (unless you are a highly skilled kernel dev) or Framework can do about this. ---
**Author:** ![RyzenFromFire](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/ryzenfromfire/32/44852_2.png) [@RyzenFromFire](https://community.frame.work/u/RyzenFromFire)\ **Post date:** [January 26, 2026, 11:52pm UTC](https://community.frame.work/t/fw16-screen-freezeing-on-linux/73958/48 "2026-01-26T23:52:22Z")
I have also had similar freezes on the main screen only (external monitors work fine), usually right at logon. If I have external monitors connected, I’m generally able to un-freeze it by going into display settings for the built-in screen and changing some parameter (e.g., switch refresh rate from 165 to 60 Hz) then change it back (or just click “Revert” in the popup). Running EndeavourOS with kernel 6.18.6-arch1-1 and using KDE Plasma with Wayland. ---
**Author:** ![Richard](https://avatars.discourse-cdn.com/v4/letter/r/f0a364/32.png) [@Richard](https://community.frame.work/u/Richard)\ **Post date:** [January 29, 2026, 3:38pm UTC](https://community.frame.work/t/fw16-screen-freezeing-on-linux/73958/49 "2026-01-29T15:38:11Z")
I can now confirm that adding `amdgpu.dcdebugmask=0x10` as kernel boot parameter does prevent this from happening. ---
**Author:** ![RyzenFromFire](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/ryzenfromfire/32/44852_2.png) [@RyzenFromFire](https://community.frame.work/u/RyzenFromFire)\ **Post date:** [February 10, 2026, 5:47am UTC](https://community.frame.work/t/fw16-screen-freezeing-on-linux/73958/50 "2026-02-10T05:47:40Z")
I didn’t have this set, so I’ll give it a shot. Hopefully disabling PSR doesn’t tank my battery life too much. Somewhat relatedly, I was looking into ways to auto-switch refresh rate from 165 to 60 Hz when on AC power vs. battery, respectively. [Here’s a relevant forum article](https://community.frame.work/t/auto-switch-60hz-165hz-on-off-battery-with-plasma-wayland/52538). The point is, this might work as a hacky fix for the issue I’m seeing. ---
**Author:** ![Richard](https://avatars.discourse-cdn.com/v4/letter/r/f0a364/32.png) [@Richard](https://community.frame.work/u/Richard)\ **Post date:** [February 10, 2026, 6:28am UTC](https://community.frame.work/t/fw16-screen-freezeing-on-linux/73958/51 "2026-02-10T06:28:03Z")
No idea what you’re seeing, but it won’t change anything about the screen freezes. But I might have some good news. With kernel 6.19 RC8, it seems PR is now again successfully disabling PSR. So while the PSR flickers are still present for me, not setting any special parameters, it seems we are no longer affected. Only devices with screens that only support PSR and not PR are still affected. ---
**Author:** ![Lukasz\_Siudut](https://avatars.discourse-cdn.com/v4/letter/l/cdc98d/32.png) [@Lukasz\_Siudut](https://community.frame.work/u/Lukasz_Siudut)\ **Post date:** [February 10, 2026, 7:00am UTC](https://community.frame.work/t/fw16-screen-freezeing-on-linux/73958/52 "2026-02-10T07:00:32Z")
The fact that some users are reporting it and some not is very puzzling. Two observations of mine: - there’s more AMD reports where issues seem to come in batches, as once they start they continue to happen - I’m referring to your post from November - I’m having similar impression regarding GPU page faults that I experience - have you or support ever considered faulty panel? I have no idea how much sense it makes, but gosh, how to explain the fact that not everyone sees this if not different than motherboard hardware component? ---
**Author:** ![Richard](https://avatars.discourse-cdn.com/v4/letter/r/f0a364/32.png) [@Richard](https://community.frame.work/u/Richard)\ **Post date:** [February 10, 2026, 7:22am UTC](https://community.frame.work/t/fw16-screen-freezeing-on-linux/73958/53 "2026-02-10T07:22:38Z")
If only FW devices where affected, I would agree, but that’s far from the situation. Also, software has way too much of an impact that hardware could be the cause. ---
**Author:** ![DawnofDonuts](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/dawnofdonuts/32/47748_2.png) [@DawnofDonuts](https://community.frame.work/u/DawnofDonuts)\ **Post date:** [April 28, 2026, 1:22am UTC](https://community.frame.work/t/fw16-screen-freezeing-on-linux/73958/54 "2026-04-28T01:22:09Z")
I am having the same issue where my system will freeze up but my music will still keep playing normally (although i cant pause it with my dwm hotkey). For me it only happens when im on “extreme performance” mode when playing a game. So I do think this is a gpu mode issue because on balanced mode I never freeze. I only just got my kernel logging working so i can look at kernel logs so i will try to reproduce it and see what logs I get. I should also probably mention im on artix linux using runit as my init system (which is why i only now got kernel logging working cuz i had to set that up with runit) ---
**Author:** ![DawnofDonuts](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/dawnofdonuts/32/47748_2.png) [@DawnofDonuts](https://community.frame.work/u/DawnofDonuts)\ **Post date:** [April 28, 2026, 2:32am UTC](https://community.frame.work/t/fw16-screen-freezeing-on-linux/73958/55 "2026-04-28T02:32:08Z")
I was able to reproduce the freeze and i saved the log. this seemed to be the relevant part: ```auto [Mon Apr 27 21:54:34 2026] pcieport 0000:00:01.1: pciehp: Slot(0): Link Down [Mon Apr 27 21:54:34 2026] pcieport 0000:00:01.1: pciehp: Slot(0): Card not present [Mon Apr 27 21:54:34 2026] amdgpu 0000:03:00.0: amdgpu: device lost from bus! [Mon Apr 27 21:54:34 2026] amdgpu 0000:03:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram? [Mon Apr 27 21:54:34 2026] amdgpu 0000:03:00.0: amdgpu: Failed to export SMU metrics table! [Mon Apr 27 21:54:34 2026] amdgpu 0000:03:00.0: amdgpu: device lost from bus! [Mon Apr 27 21:54:34 2026] amdgpu 0000:03:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram? [Mon Apr 27 21:54:34 2026] amdgpu 0000:03:00.0: amdgpu: Failed to export SMU metrics table! [Mon Apr 27 21:54:34 2026] amdgpu 0000:03:00.0: amdgpu: device lost from bus! [Mon Apr 27 21:54:34 2026] amdgpu 0000:03:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram? [Mon Apr 27 21:54:34 2026] amdgpu 0000:03:00.0: amdgpu: Failed to export SMU metrics table! [Mon Apr 27 21:54:34 2026] amdgpu 0000:03:00.0: amdgpu: device lost from bus! [Mon Apr 27 21:54:34 2026] amdgpu 0000:03:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram? [Mon Apr 27 21:54:34 2026] amdgpu 0000:03:00.0: amdgpu: Failed to export SMU metrics table! [Mon Apr 27 21:54:34 2026] amdgpu 0000:03:00.0: amdgpu: device lost from bus! [Mon Apr 27 21:54:34 2026] amdgpu 0000:03:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram? [Mon Apr 27 21:54:34 2026] amdgpu 0000:03:00.0: amdgpu: Failed to export SMU metrics table! [Mon Apr 27 21:54:34 2026] amdgpu 0000:03:00.0: amdgpu: device lost from bus! [Mon Apr 27 21:54:34 2026] amdgpu 0000:03:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram? [Mon Apr 27 21:54:34 2026] amdgpu 0000:03:00.0: amdgpu: Failed to export SMU metrics table! [Mon Apr 27 21:54:34 2026] amdgpu 0000:03:00.0: amdgpu: device lost from bus! [Mon Apr 27 21:54:34 2026] amdgpu 0000:03:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram? [Mon Apr 27 21:54:34 2026] amdgpu 0000:03:00.0: amdgpu: Failed to export SMU metrics table! [Mon Apr 27 21:54:34 2026] amdgpu 0000:03:00.0: amdgpu: Failed to get fan speed(PWM)! [Mon Apr 27 21:54:34 2026] amdgpu 0000:03:00.0: amdgpu: device lost from bus! [Mon Apr 27 21:54:34 2026] amdgpu 0000:03:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:13 param:0x00000000 message:GetEnabledSmuFeaturesHigh? [Mon Apr 27 21:54:34 2026] amdgpu 0000:03:00.0: amdgpu: Failed to retrieve enabled ppfeatures! [Mon Apr 27 21:54:34 2026] amdgpu 0000:03:00.0: amdgpu: device lost from bus! [Mon Apr 27 21:54:34 2026] amdgpu 0000:03:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram? [Mon Apr 27 21:54:34 2026] amdgpu 0000:03:00.0: amdgpu: Failed to export SMU metrics table! [Mon Apr 27 21:54:34 2026] amdgpu 0000:03:00.0: amdgpu: device lost from bus! [Mon Apr 27 21:54:34 2026] amdgpu 0000:03:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:18 param:0x00000005 message:TransferTableSmu2Dram? [Mon Apr 27 21:54:34 2026] amdgpu 0000:03:00.0: amdgpu: Failed to export SMU metrics table! [Mon Apr 27 21:54:34 2026] snd_hda_intel 0000:03:00.1: GPU sound probed, but not operational: please add a quirk to driver_denylist [Mon Apr 27 21:54:35 2026] amdgpu 0000:03:00.0: amdgpu: amdgpu: finishing device. [Mon Apr 27 21:54:35 2026] amdgpu 0000:03:00.0: amdgpu: device lost from bus! [Mon Apr 27 21:54:35 2026] amdgpu 0000:03:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:41 param:0x00000000 message:DisallowGfxOff? [Mon Apr 27 21:54:35 2026] amdgpu 0000:03:00.0: amdgpu: Failed to disable gfxoff! [Mon Apr 27 21:54:37 2026] amdgpu 0000:03:00.0: amdgpu: amdgpu_job_timedout - device unplugged skipping recovery on scheduler:sdma0 [Mon Apr 27 21:54:38 2026] amdgpu 0000:03:00.0: amdgpu: MES failed to respond to msg=REMOVE_QUEUE [Mon Apr 27 21:54:38 2026] amdgpu 0000:03:00.0: amdgpu: failed to unmap legacy queue [Mon Apr 27 21:54:40 2026] amdgpu 0000:03:00.0: amdgpu: MES failed to respond to msg=REMOVE_QUEUE [Mon Apr 27 21:54:40 2026] amdgpu 0000:03:00.0: amdgpu: failed to unmap legacy queue [Mon Apr 27 21:54:43 2026] amdgpu 0000:03:00.0: amdgpu: MES failed to respond to msg=REMOVE_QUEUE [Mon Apr 27 21:54:43 2026] amdgpu 0000:03:00.0: amdgpu: failed to unmap legacy queue [Mon Apr 27 21:54:46 2026] amdgpu 0000:03:00.0: amdgpu: MES failed to respond to msg=REMOVE_QUEUE [Mon Apr 27 21:54:46 2026] amdgpu 0000:03:00.0: amdgpu: failed to unmap legacy queue [Mon Apr 27 21:54:48 2026] amdgpu 0000:03:00.0: amdgpu: MES failed to respond to msg=REMOVE_QUEUE [Mon Apr 27 21:54:48 2026] amdgpu 0000:03:00.0: amdgpu: failed to unmap legacy queue [Mon Apr 27 21:54:51 2026] amdgpu 0000:03:00.0: amdgpu: MES failed to respond to msg=REMOVE_QUEUE [Mon Apr 27 21:54:51 2026] amdgpu 0000:03:00.0: amdgpu: failed to unmap legacy queue [Mon Apr 27 21:54:54 2026] amdgpu 0000:03:00.0: amdgpu: MES failed to respond to msg=REMOVE_QUEUE [Mon Apr 27 21:54:54 2026] amdgpu 0000:03:00.0: amdgpu: failed to unmap legacy queue [Mon Apr 27 21:54:56 2026] amdgpu 0000:03:00.0: amdgpu: MES failed to respond to msg=REMOVE_QUEUE [Mon Apr 27 21:54:56 2026] amdgpu 0000:03:00.0: amdgpu: failed to unmap legacy queue [Mon Apr 27 21:54:59 2026] amdgpu 0000:03:00.0: amdgpu: MES failed to respond to msg=REMOVE_QUEUE [Mon Apr 27 21:54:59 2026] amdgpu 0000:03:00.0: amdgpu: failed to unmap legacy queue [Mon Apr 27 21:55:00 2026] [drm:gfx_v11_0_hw_fini [amdgpu]] *ERROR* failed to halt cp gfx [Mon Apr 27 21:55:00 2026] amdgpu 0000:03:00.0: amdgpu: ring_buffer_start = 000000005e80f4ac; ring_buffer_end = 0000000064a5ad7b; write_frame = 000000001c91edc3 [Mon Apr 27 21:55:00 2026] amdgpu 0000:03:00.0: amdgpu: write_frame is pointing to address out of bounds [Mon Apr 27 21:55:00 2026] amdgpu 0000:03:00.0: amdgpu: ring_buffer_start = 000000005e80f4ac; ring_buffer_end = 0000000064a5ad7b; write_frame = 000000001c91edc3 [Mon Apr 27 21:55:00 2026] amdgpu 0000:03:00.0: amdgpu: write_frame is pointing to address out of bounds [Mon Apr 27 21:55:00 2026] amdgpu 0000:03:00.0: amdgpu: ring_buffer_start = 000000005e80f4ac; ring_buffer_end = 0000000064a5ad7b; write_frame = 000000001c91edc3 [Mon Apr 27 21:55:00 2026] amdgpu 0000:03:00.0: amdgpu: write_frame is pointing to address out of bounds [Mon Apr 27 21:55:00 2026] amdgpu 0000:03:00.0: amdgpu: ring_buffer_start = 000000005e80f4ac; ring_buffer_end = 0000000064a5ad7b; write_frame = 000000001c91edc3 [Mon Apr 27 21:55:00 2026] amdgpu 0000:03:00.0: amdgpu: write_frame is pointing to address out of bounds [Mon Apr 27 21:55:00 2026] amdgpu 0000:03:00.0: amdgpu: psp reg (0x16080) wait timed out, mask: 8000ffff, read: ffffffff exp: 80000000 [Mon Apr 27 21:55:00 2026] [drm:psp_v13_0_ring_destroy [amdgpu]] *ERROR* Fail to stop psp ring [Mon Apr 27 21:55:01 2026] pci_bus 0000:03: busn_res: [bus 03] is released [Mon Apr 27 21:55:01 2026] pci_bus 0000:02: busn_res: [bus 02-03] is released [Mon Apr 27 21:55:01 2026] pcieport 0000:00:01.1: pciehp: Slot(0): Card present [Mon Apr 27 21:55:01 2026] pcieport 0000:00:01.1: pciehp: Slot(0): Link Up [Mon Apr 27 21:55:01 2026] pci 0000:01:00.0: [1002:1478] type 01 class 0x060400 PCIe Switch Upstream Port [Mon Apr 27 21:55:01 2026] pci 0000:01:00.0: BAR 0 [mem 0x00000000-0x00003fff] [Mon Apr 27 21:55:01 2026] pci 0000:01:00.0: PCI bridge to [bus 00] [Mon Apr 27 21:55:01 2026] pci 0000:01:00.0: bridge window [io 0x0000-0x0fff] [Mon Apr 27 21:55:01 2026] pci 0000:01:00.0: bridge window [mem 0x00000000-0x000fffff] [Mon Apr 27 21:55:01 2026] pci 0000:01:00.0: bridge window [mem 0x00000000-0x000fffff 64bit pref] [Mon Apr 27 21:55:01 2026] pci 0000:01:00.0: Max Payload Size set to 256 (was 128, max 512) [Mon Apr 27 21:55:01 2026] pci 0000:01:00.0: PME# supported from D0 D3hot D3cold [Mon Apr 27 21:55:01 2026] pci 0000:01:00.0: Adding to iommu group 14 [Mon Apr 27 21:55:01 2026] pci 0000:01:00.0: bridge configuration invalid ([bus 00-00]), reconfiguring [Mon Apr 27 21:55:01 2026] pci 0000:02:00.0: [1002:1479] type 01 class 0x060400 PCIe Switch Downstream Port [Mon Apr 27 21:55:01 2026] pci 0000:02:00.0: PCI bridge to [bus 00] [Mon Apr 27 21:55:01 2026] pci 0000:02:00.0: bridge window [io 0x0000-0x0fff] [Mon Apr 27 21:55:01 2026] pci 0000:02:00.0: bridge window [mem 0x00000000-0x000fffff] [Mon Apr 27 21:55:01 2026] pci 0000:02:00.0: bridge window [mem 0x00000000-0x000fffff 64bit pref] [Mon Apr 27 21:55:01 2026] pci 0000:02:00.0: Max Payload Size set to 256 (was 128, max 512) [Mon Apr 27 21:55:01 2026] pci 0000:02:00.0: PME# supported from D0 D3hot D3cold [Mon Apr 27 21:55:01 2026] pci 0000:02:00.0: Adding to iommu group 15 [Mon Apr 27 21:55:01 2026] pci 0000:01:00.0: PCI bridge to [bus 02-03] [Mon Apr 27 21:55:01 2026] pci 0000:02:00.0: bridge configuration invalid ([bus 00-00]), reconfiguring [Mon Apr 27 21:55:01 2026] pci 0000:03:00.0: [1002:7480] type 00 class 0x030000 PCIe Legacy Endpoint [Mon Apr 27 21:55:01 2026] pci 0000:03:00.0: BAR 0 [mem 0x00000000-0x0fffffff 64bit pref] [Mon Apr 27 21:55:01 2026] pci 0000:03:00.0: BAR 2 [mem 0x00000000-0x001fffff 64bit pref] [Mon Apr 27 21:55:01 2026] pci 0000:03:00.0: BAR 4 [io 0x0000-0x00ff] [Mon Apr 27 21:55:01 2026] pci 0000:03:00.0: BAR 5 [mem 0x00000000-0x000fffff] [Mon Apr 27 21:55:01 2026] pci 0000:03:00.0: ROM [mem 0x00000000-0x0001ffff pref] [Mon Apr 27 21:55:01 2026] pci 0000:03:00.0: Max Payload Size set to 256 (was 128, max 256) [Mon Apr 27 21:55:01 2026] pci 0000:03:00.0: PME# supported from D1 D2 D3hot D3cold [Mon Apr 27 21:55:01 2026] pci 0000:03:00.0: Adding to iommu group 16 [Mon Apr 27 21:55:01 2026] pci 0000:03:00.0: vgaarb: bridge control possible [Mon Apr 27 21:55:01 2026] pci 0000:03:00.0: vgaarb: VGA device added: decodes=io+mem,owns=none,locks=none [Mon Apr 27 21:55:01 2026] pci 0000:03:00.1: [1002:ab30] type 00 class 0x040300 PCIe Legacy Endpoint [Mon Apr 27 21:55:01 2026] pci 0000:03:00.1: BAR 0 [mem 0x00000000-0x00003fff] [Mon Apr 27 21:55:01 2026] pci 0000:03:00.1: Max Payload Size set to 256 (was 128, max 256) [Mon Apr 27 21:55:01 2026] pci 0000:03:00.1: PME# supported from D1 D2 D3hot D3cold [Mon Apr 27 21:55:01 2026] pci 0000:03:00.1: Adding to iommu group 17 [Mon Apr 27 21:55:01 2026] pci 0000:02:00.0: PCI bridge to [bus 03] [Mon Apr 27 21:55:01 2026] pci_bus 0000:03: busn_res: [bus 03] end is updated to 03 [Mon Apr 27 21:55:01 2026] pci_bus 0000:02: busn_res: [bus 02-03] end is updated to 03 [Mon Apr 27 21:55:01 2026] pci 0000:01:00.0: bridge window [mem 0x7c00000000-0x7e001fffff 64bit pref]: assigned [Mon Apr 27 21:55:01 2026] pci 0000:01:00.0: bridge window [mem 0x90d00000-0x90efffff]: assigned [Mon Apr 27 21:55:01 2026] pci 0000:01:00.0: BAR 0 [mem 0x90f00000-0x90f03fff]: assigned [Mon Apr 27 21:55:01 2026] pci 0000:01:00.0: bridge window [io 0xa000-0xafff]: assigned [Mon Apr 27 21:55:01 2026] pci 0000:02:00.0: bridge window [mem 0x7c00000000-0x7e001fffff 64bit pref]: assigned [Mon Apr 27 21:55:01 2026] pci 0000:02:00.0: bridge window [mem 0x90d00000-0x90efffff]: assigned [Mon Apr 27 21:55:01 2026] pci 0000:02:00.0: bridge window [io 0xa000-0xafff]: assigned [Mon Apr 27 21:55:01 2026] pci 0000:03:00.0: BAR 0 [mem 0x7c00000000-0x7c0fffffff 64bit pref]: assigned [Mon Apr 27 21:55:01 2026] pci 0000:03:00.0: BAR 2 [mem 0x7c10000000-0x7c101fffff 64bit pref]: assigned [Mon Apr 27 21:55:01 2026] pci 0000:03:00.0: BAR 5 [mem 0x90d00000-0x90dfffff]: assigned [Mon Apr 27 21:55:01 2026] pci 0000:03:00.0: ROM [mem 0x90e00000-0x90e1ffff pref]: assigned [Mon Apr 27 21:55:01 2026] pci 0000:03:00.1: BAR 0 [mem 0x90e20000-0x90e23fff]: assigned [Mon Apr 27 21:55:01 2026] pci 0000:03:00.0: BAR 4 [io 0xa000-0xa0ff]: assigned [Mon Apr 27 21:55:01 2026] pci 0000:02:00.0: PCI bridge to [bus 03] [Mon Apr 27 21:55:01 2026] pci 0000:02:00.0: bridge window [io 0xa000-0xafff] [Mon Apr 27 21:55:01 2026] pci 0000:02:00.0: bridge window [mem 0x90d00000-0x90efffff] [Mon Apr 27 21:55:01 2026] pci 0000:02:00.0: bridge window [mem 0x7c00000000-0x7e001fffff 64bit pref] [Mon Apr 27 21:55:01 2026] pci 0000:01:00.0: PCI bridge to [bus 02-03] [Mon Apr 27 21:55:01 2026] pci 0000:01:00.0: bridge window [io 0xa000-0xafff] [Mon Apr 27 21:55:01 2026] pci 0000:01:00.0: bridge window [mem 0x90d00000-0x90efffff] [Mon Apr 27 21:55:01 2026] pci 0000:01:00.0: bridge window [mem 0x7c00000000-0x7e001fffff 64bit pref] [Mon Apr 27 21:55:01 2026] pcieport 0000:00:01.1: PCI bridge to [bus 01-03] [Mon Apr 27 21:55:01 2026] pcieport 0000:00:01.1: bridge window [io 0xa000-0xafff] [Mon Apr 27 21:55:01 2026] pcieport 0000:00:01.1: bridge window [mem 0x90d00000-0x90ffffff] [Mon Apr 27 21:55:01 2026] pcieport 0000:00:01.1: bridge window [mem 0x7c00000000-0x7e0fffffff 64bit pref] [Mon Apr 27 21:55:01 2026] pcieport 0000:01:00.0: enabling device (0000 -> 0003) [Mon Apr 27 21:55:01 2026] pcieport 0000:02:00.0: enabling device (0000 -> 0003) [Mon Apr 27 21:55:01 2026] amdgpu 0000:03:00.0: enabling device (0000 -> 0003) [Mon Apr 27 21:55:01 2026] amdgpu 0000:03:00.0: amdgpu: initializing kernel modesetting (IP DISCOVERY 0x1002:0x7480 0xF111:0x0007 0xC1). [Mon Apr 27 21:55:01 2026] amdgpu 0000:03:00.0: amdgpu: register mmio base: 0x90D00000 [Mon Apr 27 21:55:01 2026] amdgpu 0000:03:00.0: amdgpu: register mmio size: 1048576 [Mon Apr 27 21:55:01 2026] amdgpu 0000:03:00.0: amdgpu: detected ip block number 0 (soc21_common) [Mon Apr 27 21:55:01 2026] amdgpu 0000:03:00.0: amdgpu: detected ip block number 1 (gmc_v11_0) [Mon Apr 27 21:55:01 2026] amdgpu 0000:03:00.0: amdgpu: detected ip block number 2 (ih_v6_0) [Mon Apr 27 21:55:01 2026] amdgpu 0000:03:00.0: amdgpu: detected ip block number 3 (psp) [Mon Apr 27 21:55:01 2026] amdgpu 0000:03:00.0: amdgpu: detected ip block number 4 (smu) [Mon Apr 27 21:55:01 2026] amdgpu 0000:03:00.0: amdgpu: detected ip block number 5 (dm) [Mon Apr 27 21:55:01 2026] amdgpu 0000:03:00.0: amdgpu: detected ip block number 6 (gfx_v11_0) [Mon Apr 27 21:55:01 2026] amdgpu 0000:03:00.0: amdgpu: detected ip block number 7 (sdma_v6_0) [Mon Apr 27 21:55:01 2026] amdgpu 0000:03:00.0: amdgpu: detected ip block number 8 (vcn_v4_0) [Mon Apr 27 21:55:01 2026] amdgpu 0000:03:00.0: amdgpu: detected ip block number 9 (jpeg_v4_0) [Mon Apr 27 21:55:01 2026] amdgpu 0000:03:00.0: amdgpu: detected ip block number 10 (mes_v11_0) [Mon Apr 27 21:55:01 2026] amdgpu 0000:03:00.0: amdgpu: ACPI VFCT table present but broken (too short #2),skipping [Mon Apr 27 21:55:01 2026] amdgpu 0000:03:00.0: amdgpu: Fetched VBIOS from ROM BAR [Mon Apr 27 21:55:01 2026] amdgpu: ATOM BIOS: 113-BRT125778.001 [Mon Apr 27 21:55:01 2026] amdgpu 0000:03:00.0: amdgpu: CP RS64 enable [Mon Apr 27 21:55:01 2026] amdgpu 0000:03:00.0: amdgpu: Trusted Memory Zone (TMZ) feature not supported [Mon Apr 27 21:55:01 2026] amdgpu 0000:03:00.0: amdgpu: GPU posting now... [Mon Apr 27 21:55:01 2026] amdgpu 0000:03:00.0: amdgpu: vm size is 262144 GB, 4 levels, block size is 9-bit, fragment size is 9-bit [Mon Apr 27 21:55:01 2026] amdgpu 0000:03:00.0: BAR 0 [mem 0x7c00000000-0x7c0fffffff 64bit pref]: releasing [Mon Apr 27 21:55:01 2026] amdgpu 0000:03:00.0: BAR 2 [mem 0x7c10000000-0x7c101fffff 64bit pref]: releasing [Mon Apr 27 21:55:01 2026] pcieport 0000:02:00.0: bridge window [mem 0x7c00000000-0x7e001fffff 64bit pref]: releasing [Mon Apr 27 21:55:01 2026] pcieport 0000:01:00.0: bridge window [mem 0x7c00000000-0x7e001fffff 64bit pref]: releasing [Mon Apr 27 21:55:01 2026] pcieport 0000:00:01.1: bridge window [mem 0x7c00000000-0x7e0fffffff 64bit pref]: releasing [Mon Apr 27 21:55:01 2026] pcieport 0000:00:01.1: bridge window [mem 0xa00000000-0xc001fffff 64bit pref]: assigned [Mon Apr 27 21:55:01 2026] pcieport 0000:01:00.0: bridge window [mem 0xa00000000-0xc001fffff 64bit pref]: assigned [Mon Apr 27 21:55:01 2026] pcieport 0000:02:00.0: bridge window [mem 0xa00000000-0xc001fffff 64bit pref]: assigned [Mon Apr 27 21:55:01 2026] amdgpu 0000:03:00.0: BAR 0 [mem 0xa00000000-0xbffffffff 64bit pref]: assigned [Mon Apr 27 21:55:01 2026] amdgpu 0000:03:00.0: BAR 2 [mem 0xc00000000-0xc001fffff 64bit pref]: assigned [Mon Apr 27 21:55:01 2026] pcieport 0000:00:01.1: PCI bridge to [bus 01-03] [Mon Apr 27 21:55:01 2026] pcieport 0000:00:01.1: bridge window [io 0xa000-0xafff] [Mon Apr 27 21:55:01 2026] pcieport 0000:00:01.1: bridge window [mem 0x90d00000-0x90ffffff] [Mon Apr 27 21:55:01 2026] pcieport 0000:00:01.1: bridge window [mem 0xa00000000-0xc001fffff 64bit pref] [Mon Apr 27 21:55:01 2026] pcieport 0000:01:00.0: PCI bridge to [bus 02-03] [Mon Apr 27 21:55:01 2026] pcieport 0000:01:00.0: bridge window [io 0xa000-0xafff] [Mon Apr 27 21:55:01 2026] pcieport 0000:01:00.0: bridge window [mem 0x90d00000-0x90efffff] [Mon Apr 27 21:55:01 2026] pcieport 0000:01:00.0: bridge window [mem 0xa00000000-0xc001fffff 64bit pref] [Mon Apr 27 21:55:01 2026] pcieport 0000:02:00.0: PCI bridge to [bus 03] [Mon Apr 27 21:55:01 2026] pcieport 0000:02:00.0: bridge window [io 0xa000-0xafff] [Mon Apr 27 21:55:01 2026] pcieport 0000:02:00.0: bridge window [mem 0x90d00000-0x90efffff] [Mon Apr 27 21:55:01 2026] pcieport 0000:02:00.0: bridge window [mem 0xa00000000-0xc001fffff 64bit pref] [Mon Apr 27 21:55:01 2026] amdgpu 0000:03:00.0: amdgpu: VRAM: 8176M 0x0000008000000000 - 0x00000081FEFFFFFF (8176M used) [Mon Apr 27 21:55:01 2026] amdgpu 0000:03:00.0: amdgpu: GART: 512M 0x00007FFF00000000 - 0x00007FFF1FFFFFFF [Mon Apr 27 21:55:01 2026] [drm] Detected VRAM RAM=8176M, BAR=8192M [Mon Apr 27 21:55:01 2026] [drm] RAM width 128bits GDDR6 [Mon Apr 27 21:55:01 2026] amdgpu 0000:03:00.0: amdgpu: amdgpu: 8176M of VRAM memory ready [Mon Apr 27 21:55:01 2026] amdgpu 0000:03:00.0: amdgpu: amdgpu: 15634M of GTT memory ready. [Mon Apr 27 21:55:01 2026] [drm] GART: num cpu pages 131072, num gpu pages 131072 [Mon Apr 27 21:55:01 2026] [drm] PCIE GART of 512M enabled (table at 0x00000081FEB00000). [Mon Apr 27 21:55:01 2026] amdgpu 0000:03:00.0: amdgpu: [drm] Loading DMUB firmware via PSP: version=0x07002F00 [Mon Apr 27 21:55:01 2026] amdgpu 0000:03:00.0: amdgpu: [VCN instance 0] Found VCN firmware Version ENC: 1.24 DEC: 9 VEP: 0 Revision: 16 [Mon Apr 27 21:55:01 2026] amdgpu 0000:03:00.0: amdgpu: reserve 0x1300000 from 0x81fc000000 for PSP TMR [Mon Apr 27 21:55:01 2026] amdgpu 0000:03:00.0: amdgpu: RAS: optional ras ta ucode is not available [Mon Apr 27 21:55:01 2026] amdgpu 0000:03:00.0: amdgpu: RAP: optional rap ta ucode is not available [Mon Apr 27 21:55:01 2026] amdgpu 0000:03:00.0: amdgpu: SECUREDISPLAY: optional securedisplay ta ucode is not available [Mon Apr 27 21:55:01 2026] amdgpu 0000:03:00.0: amdgpu: smu driver if version = 0x00000035, smu fw if version = 0x00000040, smu fw program = 0, smu fw version = 0x00525f00 (82.95.0) [Mon Apr 27 21:55:01 2026] amdgpu 0000:03:00.0: amdgpu: SMU driver if version not matched [Mon Apr 27 21:55:01 2026] amdgpu 0000:03:00.0: amdgpu: SMU is initialized successfully! [Mon Apr 27 21:55:01 2026] amdgpu 0000:03:00.0: amdgpu: [drm] Display Core v3.2.359 initialized on DCN 3.2.1 [Mon Apr 27 21:55:01 2026] amdgpu 0000:03:00.0: amdgpu: [drm] DP-HDMI FRL PCON supported [Mon Apr 27 21:55:01 2026] amdgpu 0000:03:00.0: amdgpu: [drm] DMUB hardware initialized: version=0x07002F00 [Mon Apr 27 21:55:03 2026] amdgpu 0000:03:00.0: amdgpu: [drm] eDP-3: PSR support 0, DC PSR ver -1, sink PSR ver 0 DPCD caps 0x0 su_y_granularity 0 [Mon Apr 27 21:55:03 2026] amdgpu 0000:03:00.0: amdgpu: [drm] DP-10: PSR support 0, DC PSR ver -1, sink PSR ver 0 DPCD caps 0x0 su_y_granularity 0 [Mon Apr 27 21:55:03 2026] amdgpu: HMM registered 8176MB device memory [Mon Apr 27 21:55:03 2026] kfd kfd: amdgpu: Allocated 3969056 bytes on gart [Mon Apr 27 21:55:03 2026] kfd kfd: amdgpu: Total number of KFD nodes to be created: 1 [Mon Apr 27 21:55:03 2026] amdgpu: Virtual CRAT table created for GPU [Mon Apr 27 21:55:03 2026] amdgpu: Topology: Add dGPU node [0x7480:0x1002] [Mon Apr 27 21:55:03 2026] kfd kfd: amdgpu: added device 1002:7480 [Mon Apr 27 21:55:03 2026] amdgpu 0000:03:00.0: amdgpu: SE 2, SH per SE 2, CU per SH 8, active_cu_number 32 [Mon Apr 27 21:55:03 2026] amdgpu 0000:03:00.0: amdgpu: ring gfx_0.0.0 uses VM inv eng 0 on hub 0 [Mon Apr 27 21:55:03 2026] amdgpu 0000:03:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 1 on hub 0 [Mon Apr 27 21:55:03 2026] amdgpu 0000:03:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 4 on hub 0 [Mon Apr 27 21:55:03 2026] amdgpu 0000:03:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 6 on hub 0 [Mon Apr 27 21:55:03 2026] amdgpu 0000:03:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 7 on hub 0 [Mon Apr 27 21:55:03 2026] amdgpu 0000:03:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 8 on hub 0 [Mon Apr 27 21:55:03 2026] amdgpu 0000:03:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 9 on hub 0 [Mon Apr 27 21:55:03 2026] amdgpu 0000:03:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 10 on hub 0 [Mon Apr 27 21:55:03 2026] amdgpu 0000:03:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 11 on hub 0 [Mon Apr 27 21:55:03 2026] amdgpu 0000:03:00.0: amdgpu: ring sdma0 uses VM inv eng 12 on hub 0 [Mon Apr 27 21:55:03 2026] amdgpu 0000:03:00.0: amdgpu: ring sdma1 uses VM inv eng 13 on hub 0 [Mon Apr 27 21:55:03 2026] amdgpu 0000:03:00.0: amdgpu: ring vcn_unified_0 uses VM inv eng 0 on hub 8 [Mon Apr 27 21:55:03 2026] amdgpu 0000:03:00.0: amdgpu: ring jpeg_dec uses VM inv eng 1 on hub 8 [Mon Apr 27 21:55:03 2026] amdgpu 0000:03:00.0: amdgpu: ring mes_kiq_3.1.0 uses VM inv eng 14 on hub 0 [Mon Apr 27 21:55:03 2026] amdgpu 0000:03:00.0: amdgpu: Using BOCO for runtime pm [Mon Apr 27 21:55:03 2026] amdgpu 0000:03:00.0: [drm] Registered 4 planes with drm panic [Mon Apr 27 21:55:03 2026] [drm] Initialized amdgpu 3.64.0 for 0000:03:00.0 on minor 0 [Mon Apr 27 21:55:03 2026] amdgpu 0000:03:00.0: [drm] Cannot find any crtc or sizes [Mon Apr 27 21:55:03 2026] pci 0000:03:00.1: D0 power state depends on 0000:03:00.0 [Mon Apr 27 21:55:03 2026] snd_hda_intel 0000:03:00.1: enabling device (0000 -> 0002) [Mon Apr 27 21:55:03 2026] snd_hda_intel 0000:03:00.1: Handle vga_switcheroo audio client [Mon Apr 27 21:55:03 2026] snd_hda_intel 0000:03:00.1: Force to non-snoop mode [Mon Apr 27 21:55:03 2026] snd_hda_intel 0000:03:00.1: bound 0000:03:00.0 (ops amdgpu_dm_audio_component_bind_ops [amdgpu]) [Mon Apr 27 21:55:03 2026] input: HDA ATI HDMI HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:01.1/0000:01:00.0/0000:02:00.0/0000:03:00.1/sound/card1/input34 [Mon Apr 27 21:55:03 2026] input: HDA ATI HDMI HDMI/DP,pcm=7 as /devices/pci0000:00/0000:00:01.1/0000:01:00.0/0000:02:00.0/0000:03:00.1/sound/card1/input35 [Mon Apr 27 21:55:03 2026] input: HDA ATI HDMI HDMI/DP,pcm=8 as /devices/pci0000:00/0000:00:01.1/0000:01:00.0/0000:02:00.0/0000:03:00.1/sound/card1/input36 [Mon Apr 27 21:55:03 2026] input: HDA ATI HDMI HDMI/DP,pcm=9 as /devices/pci0000:00/0000:00:01.1/0000:01:00.0/0000:02:00.0/0000:03:00.1/sound/card1/input37 ``` worth noting that it never unfroze ---
**Author:** ![DawnofDonuts](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/dawnofdonuts/32/47748_2.png) [@DawnofDonuts](https://community.frame.work/u/DawnofDonuts)\ **Post date:** [May 1, 2026, 4:27am UTC](https://community.frame.work/t/fw16-screen-freezeing-on-linux/73958/56 "2026-05-01T04:27:10Z")
i just recently got the 240 watt adapter and that seems to have fixed the freezes as i can now be on “extreme performance” mode and i dont freeze ---
**Author:** ![Alex\_H](https://avatars.discourse-cdn.com/v4/letter/a/3e96dc/32.png) [@Alex\_H](https://community.frame.work/u/Alex_H)\ **Post date:** [May 3, 2026, 4:39am UTC](https://community.frame.work/t/fw16-screen-freezeing-on-linux/73958/57 "2026-05-03T04:39:06Z")
But that’s not a real fix, just a workaround. I have similar freeze issues with my Framework 13 7840u, but only on battery with no external monitor in energy savings mode. I don’t know how to reproduce it though :S ---
**Author:** ![Alex\_H](https://avatars.discourse-cdn.com/v4/letter/a/3e96dc/32.png) [@Alex\_H](https://community.frame.work/u/Alex_H)\ **Post date:** [May 28, 2026, 5:37pm UTC](https://community.frame.work/t/fw16-screen-freezeing-on-linux/73958/58 "2026-05-28T17:37:14Z")
I run into this more often if I’m on my internal screen and just let Fedora idle without doing anything. If I come back after 10-20 minutes, there is a high chance it is frozen. I can still press buttons and pause/unpause videos etc. But the screen stays frozen and will not react. ---
**Author:** ![Alex\_H](https://avatars.discourse-cdn.com/v4/letter/a/3e96dc/32.png) [@Alex\_H](https://community.frame.work/u/Alex_H)\ **Post date:** [May 29, 2026, 6:03pm UTC](https://community.frame.work/t/fw16-screen-freezeing-on-linux/73958/59 "2026-05-29T18:03:00Z")
Happened 4 times today in a row. But this time I could not use the desktop/unpause audio etc. I’ve collected logs, but it is not much: ```auto May 29 19:23:47 [...] kernel: amdgpu 0000:c1:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data May 29 19:23:47 [...] kernel: amdgpu 0000:c1:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data May 29 19:23:47 [...] kernel: amdgpu 0000:c1:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data May 29 19:23:57 [...] kernel: amdgpu 0000:c1:00.0: [drm] *ERROR* [CRTC:363:crtc-0] flip_done timed out ``` ---
**Author:** ![Alex\_H](https://avatars.discourse-cdn.com/v4/letter/a/3e96dc/32.png) [@Alex\_H](https://community.frame.work/u/Alex_H)\ **Post date:** [June 7, 2026, 7:41am UTC](https://community.frame.work/t/fw16-screen-freezeing-on-linux/73958/60 "2026-06-07T07:41:02Z")
I’ve managed to reproduce the issue while an external monitor was attached. Surprisingly only the internal monitor froze. The “solution” was to go to the display settings, turn the internal screen off and then on again. ---
**Author:** ![Nina\_Alexandra\_Klama](https://avatars.discourse-cdn.com/v4/letter/n/ecd19e/32.png) [@Nina\_Alexandra\_Klama](https://community.frame.work/u/Nina_Alexandra_Klama)\ **Post date:** [September 24, 2026, 3:14am UTC](https://community.frame.work/t/fw16-screen-freezeing-on-linux/73958/61 "2026-09-24T03:14:04Z")
I just downgraded my kernel from 6.18.48 back to 6.6.47, because while I rarely got the `flip_done timed out` error with my 6.6.47 kernel, they where very common when running on 6.18.48. This problem went from once a month or so, to two to three times within 24h. I thought this was quite odd, because apparently the issue should have been fixed in the newer kernel. [Previous page](https://community.frame.work/t/fw16-screen-freezeing-on-linux/73958.md?page=2)