Open Shinjilestat opened 8 months ago
AMD does not support all HDMI 2.1 features on their open source driver unfortunately. The explanation is here. It's because of annoying DRM licensing schemes. https://arstechnica.com/gadgets/2024/02/hdmi-forum-to-amd-no-you-cant-make-an-open-source-hdmi-2-1-driver/
VRR is an HDMI 2.1 feature.
AMD does not support all HDMI 2.1 features on their open source driver unfortunately. The explanation is here. It's because of annoying DRM licensing schemes. https://arstechnica.com/gadgets/2024/02/hdmi-forum-to-amd-no-you-cant-make-an-open-source-hdmi-2-1-driver/
VRR is an HDMI 2.1 feature.
No it's not. It will not work at HDMI 2.1 resolution and refresh rate, but VRR will still work at lower resolution and refresh rate. I had my C1 once negotiate a 4K 60 Hz (IIRC, not sure on the framerate) VRR link, but it's extremely hard to train the display as the OP mentioned and get a proper image out of it. This was 6 months ago, so it seems that Valve improved the non VRR behavior at least.
Can confirm i get this on my LGC2.
Unplugging and replugging will sometimes resolve it.
Your system information
Please describe your issue in as much detail as possible:
When my Steam Deck Oled is connected to my TV LG OLED55C15LA in HDR mode and i’m toggling VRR on from the "..." menu in the Deck's game mode, the image on the screen begins to shake, and after 5 to 10 minutes it disappears completely.
My TV then displays either a black screen or the message that there is no signal anymore. To solve this problem, I need to disable VRR (VRR and AMD Freesync Premium options) on my TV in its settings.
After resetting the Steam Deck to the factory setting, VRR was deactivated by default, but the problem immediately returns as soon as I reactivated it.
With VRR disabled, there's no problem displaying 1080P@120hz with HDR. I bought a new Belkin 2.1 certified cable but it didn't make any difference. I even tried changing the settings to 1080P@60hz or disabling HDR before activating VRR, but without succes.
I have no issue with a Sony PS5 configured in the same way with the same cable and plugged into the same HDMI port.
Attempted troubleshooting:
Steps for reproducing this issue: