Wayland VRR works out of the box with most popular DEs like KDE or Gnome
Neither KDE nor GNOME even detect either of my 144Hz panels as capable of it. Logs indicate that amdgpu failed to parse their EDIDs. Forcing the mode with a kernel command option causes link training to fail altogether. Meanwhile, the exact same system, panels, and cables running Windows works perfectly.
AMD experience was nothing but flawless
See above. I’ve also tried NVDIA and had the same experience - neither HDR high-refresh panel are usable in Linux, but both work on Windows.
Plus there’s the fact that about 50% of the time, when the panels power off from idle, they never come back on. This is apparently a known issue on AMD that’s been around for years but nobody seems to care to fix - everyone just says to disable screen blanking.
And don’t even get me started on heterogenous DPI.
Xorg works fine with VRR on a single display although no one should use Xorg, it’s legacy software and no longer in development.
Wayland VRR works out of the box with most popular DEs like KDE or Gnome.
HDR can be added to gamescope, but be aware it’s still considered experimental.
AMD experience was nothing but flawless, only Nvidia was buggy due to their drivers, but they’re preparing Wayland support soon.
Neither KDE nor GNOME even detect either of my 144Hz panels as capable of it. Logs indicate that
amdgpufailed to parse their EDIDs. Forcing the mode with a kernel command option causes link training to fail altogether. Meanwhile, the exact same system, panels, and cables running Windows works perfectly.See above. I’ve also tried NVDIA and had the same experience - neither HDR high-refresh panel are usable in Linux, but both work on Windows.
Plus there’s the fact that about 50% of the time, when the panels power off from idle, they never come back on. This is apparently a known issue on AMD that’s been around for years but nobody seems to care to fix - everyone just says to disable screen blanking.
And don’t even get me started on heterogenous DPI.