Overriding EDID makes VRR stop working under WAYLAND -> ( "vrr_capable" (immutable): range [0, 1] = 0 )

Have this on Gentoo running Gnome 47 with nvidia driver 570.86.16.
Graphics Card 5080, Monitor Samsung G80SD (main) + Dell U2723QE (seconday), both on DP2.1 cables.
Without EDID VRR works but only 60hz is available, with EDID I can run 120hz but VRR is gone.

Of note, I was previously using an AMD 7900XTX which could do 120hz (so better than the nvidia driver by default) and VRR but screen would flicker black if VRR at 120hz (60hz was fine) was turned on. Using EDID for the Samsung monitor fixed the black flicker
 but VRR disappeared


Possible this is a Wayland issue? Or are both AMD and Nvidia drivers broken for EDID override?

I solved this by extracting the EDID in windows using a different program. Initially I used MonitorInfoView to extract the EDID, but using this broke VRR on linux and only gave me a max of 120hz on my 240hz G80SD.

I saw someone else had solved the problem on Level1tech and decided to look for different ways to extract EDID and found a program called EnTech Monitor Asset Manager 2.9. With this I set monitor to 240hz VRR on windows (no idea if this is needed or not?) and then selected the RealTime entry for the monitor and clicked File → Save As and save as dibin file.

Loaded this EDID file in linux via kernel command line (drm.edid_firmware=DP-2:edid/g80sd-dibin240-edid.bin), now I get 240hz VRR on driver 570.86.16 on my 5080 using Displayport connection.

I just tried this, and unfortunately for changing VRR range, this doesn’t work.

I edited properly the key for the VRR range (changed from 60-165 Hz to 48-165 Hz), and in EnTech Monitor Asset Manager I opened the edid to make sure I edited the VRR range properly.

On loading the EDID on Linux, I do get the VRR option on Wayland, however it remains at 60-165 Hz, ignoring the edid.

If I load the EDID created by CRU with the extended VRR range, it works on X11 with the VRR range extended. If I load it on Wayland, the VRR option disappears, as reported by this bug.

So yeah, this is definitely a bug on Nvidia’s side, and something about EnTech Monitor Asset Manager doesn’t properly apply VRR range settings for them to reflect when you load the EDID created/edited by that program.

Edit: Opening the edid created by EnTech Monitor Asset Manager in wxedid gives warnings that the file contains errors. So I think the edid is simply not being loaded, that’s why I still get VRR under Wayland with the default 60-165 HZ range.

If I open the edid created by CRU, it gives no errors on wxedid. Works on X11 with the VRR range extended to 48 Hz, but on Wayland the bug of not getting VRR


At this pace, this bug is going to have a happy birthday party


The issue is being tracked in an internal bug 1745575. We have some rough changes for supporting the DRM sysfs edid_override node that needs some cleanup. Will use the VRR range changing example to validate these changes.

2 Likes

Thank you for the update. Can you please add the missing 24Hz to the available frequency options? I personally would not need to use any EDID override in that case.

@adolfotregosa do you have the original monitor EDID before the override. I could try testing with it and see why the 3840x2160@24Hz modeline is not enumerating.

Sure, straight from NVIDIA Settings, acquire EDID in X11.
edid_nvidia_settings_x11.bin.zip (384 Bytes)

Freshly extracted stock edid using CRU in Windows.
LG_Onkyo_stock.bin.zip (364 Bytes)

They should match but I acquired both just in case.

Windows detects all frequencies correctly.

Hi. Did you manage to have a look why 24Hz is not enumerating ?
Thank you

Hi. Any news on this ?

575.51.02 Beta confirmed fixed.

There’s still the matter that some refresh rates are missing when comparing to Windows. E.g 24Hz and 30Hz are not available.

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