Framework 16 internal display freezing

Community Support
, ,
1

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?

2

Hey @Hendrik_Warnecke Have you contacted our support?

3

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

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

4

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

5

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 )
”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.

6

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

7

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

8

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…