Comment # 7
on bug 110856
from Ropid
I saw the same issue when I tried the BenQ EX3203R for a few days. I could work around the problem by extracting and saving the monitor's EDID in a file, and changing the VRR range in that file from the original 24-144Hz to 48-144Hz. I then overrode the monitor's EDID on the kernel command line with this parameter here: drm_kms_helper.edid_firmware=DP-1:edid/edid-benq-xr3203r-vrr-48-144.bin My customized EDID file is this: $ base64 /usr/lib/firmware/edid/edid-benq-xr3203r-vrr-48-144.bin AP///////wAJ0WZ/RVQAABkcAQS1Rid4P901rE9FrCYQUFQlSwDR/NHo0cCzAKnAgYCBAIHAVl4A oKCgKVAvIDUAgGghAAAaAAAA/QAwkN7ePAEKICAgICAgAAAA/ABCZW5RIEVYMzIwM1IKAAAAEAAA AAAAAAAAAAAAAAAAAdUCA1VwUVxbWj9AEB8iISAEExIDAWFrIwkHB4MBAADiAMBtAwwAEAA4eCAA YAECA2fYXcQBeAADbRoAAAIDMJAAA2A3CC/jBeMB5A9g/AHmBgcBYF06+OMAoKCgMlAIIJgEgGgh AAAeB4KAUHA4TUAIIPgM4A4RAAAcAAAAAAAAqw== If you want to try this custom EDID file I used, run that base64 encoded text I shared here through "base64 --decode > filename.bin" to get the binary file. For the kernel parameter, the output ports are named differently than in Xorg. You can get the output port name where the monitor is connected like this: $ grep . /sys/class/drm/card*-*/status /sys/class/drm/card0-DP-1/status:connected /sys/class/drm/card0-DP-2/status:disconnected ... About how I created the EDID file, it was with a Windows tool named "Custom Resolution Utility". It can extract the EDID from the monitor/driver and save it in a file, and can customize the VRR data structure in there. I only tried 48Hz for minimum VRR range and this worked fine, there were no black screens anymore. I don't know what other values work with the EX3203R.
You are receiving this mail because:
- You are the assignee for the bug.
_______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/dri-devel
