https://bugs.kde.org/show_bug.cgi?id=456697
--- Comment #6 from koce...@tutanota.com --- (In reply to tux from comment #5) > (In reply to Shmerl from comment #4) > > Any news on this? It would be very useful to work around bugs like this: > > https://gitlab.freedesktop.org/drm/amd/-/issues/1403 > > > > Right now it's impossible in the Wayland session. > > If you can get the full binary EDID from your monitor, you can edit it with > something like Custom Resolution Utility (CRU) via wine. When importing the > original EDID file in CRU, enable/check "Import complete EDID". After adding > the desired refresh rates/modes, you can export the EDID to a new file (e.g. > "/usr/lib/firmware/edid/your_edid.bin"). Then add the new EDID to your > kernel boot line by adding "drm.edid_firmware=edid/your_edid.bin", which > will get applied after a reboot. You can also try loading it directly and > simulating a hotplug on your monitor. See here for more information: > https://wiki.archlinux.org/title/Kernel_mode_setting#Forcing_modes_and_EDID > > Custom Resolution Utility (CRU) via wine seems to work fine for me, but it > may not work for you, so your mileage may vary. Thanks for the suggestion, it also works for me. -- You are receiving this mail because: You are watching all bug changes.
