My desktop has some issues with its DP output. Part of the image is flickering on both of my monitors. On one of them it’s the top left corner. On the other one it’s the entire top part.
Framework’s support team just can’t figure out what’s wrong. They are focusing on the cable maybe a little bit too much. But this is happening only at 1080p and 60Hz on one of the monitors and at 1440p@75Hz on the other. So no high resolutions or high refresh rates which could require better cables. I tried three different cables. One of them is a usb-c to dp cable I use every day with my work laptop. It works without issues. But not with the framework.
Am I the only one who has this problem? Any ideas what’s wrong? What could I do?
Normally I would not try to find a solution. I would just return it and buy a new one, but that would take months in this case..
I’m looking for the actual source of the problem and an actual solution not just a workaround or a guess. If after all the troubleshooting there is any suspicion left, that there is a hardware issue I will return the machine. I won’t keep a 2500€ machine that is not 100% in an absolutely perfect condition.
I would make that absolutely clear to support, because that rules out software issues, it makes clear that there has to be a hardware fault, question is which hardware it is.
You tried DP and USB-C, so that means the issue happens with at least two different connectors on the Desktop - do both connectors with the same display show the issue the same way?
If not done so I would recommend to test with a highest spec (currently UHBR20) not longer than 1m DP cable, that would be handy to have in your toolbox for diagnostic purposes anyway, if the issue appears even with such a cable the cable is out of the question.
And if the issue is reproducible with two different displays with same cable on the same port showing the BIOS screen the issue has to be with the signal from the ports on the Desktop, and there’s only one way to find out if it’s a compatibility issue or the one board you have, and that would be to send you a replacement board.
I have the same issue: FW Desktop connected via a DP cable, which worked fine on my old PC with a 6900XT. Flickering on the top right corner in bios and in CachyOS.
I was reading a lot of posts about problems with DSC introduced with display port version 1.4. After switching my monitor from DP1.4 to DP1.2 everything works, but I am limited to 75hz at 3840x1600 (monitor is an LG 38GN950).
I also used different cables (also one USB-C to DP), but nothing worked. Everything is also fine with HDMI, but I am also limited to 75hz.
My assumption is, that there is either a problem with a low quality cable (and as a result DSC not working correctly) or the feature negotiation between monitor (DP1.4a) and the desktop (DP2.1) is a bit wonky and the desktop uses a higher protocol than monitor and cable support.
So, I ordered a DP2.1 certified cable to check, if it is a cable issue. Will let you know, if it helped.
TLDR: If possible, try to set your monitor to DP1.2 or use HDMI.
Of course, I told them about the bios multiple times.
I tried all the outputs on the PC and only HDMI works, or at least seems to work. Maybe I just did not stare at the monitor long enough The same display always shows the issue the same way, no matter which connector or cable I use. There is a difference between the two monitors, but within one it’s always the same. I also ordered a 1m DP 1.4 cable just to test this. My monitors only support DP 1.2. I really don’t think that the issue is caused by a noisy signal. Only if the Desktop already makes a noisy signal. That might be possible. However, to me it looks like some timing/synchronization issue. You can see on my screenshot there is a second ghost image with an offset during the flicker. But who knows, I don’t know much about computer hardware, I’m just a software engineer
The final solution will have to be a replacement board. When I contacted the support I was really hoping they will come back with a simple answer, like “oh yeah, that’s a known issue, just update the bios”. Because getting a replacement will take a long time. They don’t have the 128GB version in stock.
I also have an update and for me the new cable solved the flickering in bios and cachyos. I also had the issue that the screen went black for 1-2 seconds, which seems to be a known issue with arch based Linux distros and AMD gpus (AMDGPU - ArchWiki). After changing the power profile to high the screen did not go black once, but I am still monitoring this.
I have your exact same issue. The DP output has flickering on the top for me in Windows 11.
When I use HDMI I get weird artifacts on startup and during installation. I installed Windows 11 blind and once I saw the Windows desktop in higher resolution all the issues were gone.
But now I wanted to install Fedora and I am not even able to start the installation from bios, the artifacts remain.
I have tries multiple cables & DisplayPort, the last one gives the same issues as your screenshot.
I have also created a ticket. It’s not fun but I hope it gets taken care of…
I’m also getting flickering in windows at resolutions 3840x1600 at 120hz and above while using the DisplayPort. It’s seems fine at 3840x1600 at 75hz.
I’ve tried multiple cables that are at least 1.4 certified and have proven to work on macbook pro with a dock and a gaming pc with AMD 7900XT at 120 and 144hz without issue. So I don’t think it’s the monitor or the cables
Bios: 3.02
OS: Windows 11 with latest 7-10 drivers from framework.
Monitor: LG 38GN950 (3840x1600 at 144hz)
Display Cables: two different 1.4 certified cables and one 2.0 certified cables
The same display always shows the issue the same way, no matter which connector or cable I use. There is a difference between the two monitors, but within one it’s always the same. I also ordered a 1m DP 1.4 cable just to test this. My monitors only support DP 1.2. I really don’t think that the issue is caused by a noisy signal. Only if the Desktop already makes a noisy signal. That might be possible. However, to me it looks like some timing/synchronization issue. You can see on my screenshot there is a second ghost image with an offset during the flicker. But who knows, I don’t know much about computer hardware, I’m just a software engineer 
