So they finally have caught up with Linux. Noice!
this post was submitted on 31 Jul 2023
132 points (91.2% liked)
Technology
58055 readers
4950 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each another!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
Approved Bots
founded 1 year ago
MODERATORS
Have they? VRR support in Linux is still a total crapshoot in my experience. VRR doesn't work at all with multiple displays in X.
X is legacy software that just needs to die.
And don't even get me started on the window and compositing manager with the same name.
I switched to Wayland and everything has been working smoothly.
Which DE? I am using Plasma and notice some weird things like flickering screen when I am playing YouTube videos in Fullscreen with VRR.
is this an nvidia moment?
I'm using Wayland KDE Plasma as well and have no issues (on an AMD GPU)
Using x is the problem here
Is this a joke? X can’t do VRR at all and I have yet to find a Wayland DE that doesn’t require a separate server pinned to each monitor. And neither support HDR.
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.
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.
Can't wait for this to be rolled out with bugs and spending 30 minutes tracking down the reg code to disable it.
I wonder if this actually fixes the ancient dwm bug that causes simultaneous motion on multiple monitors with different refresh rates to make the whole window manager choppy. That bug has existed since at least Vista, and it sucks. Nothing like buying a 240Hz monitor and not being able to watch videos on my secondary one without bringing them both down to what looks like 60.
Didn't even know this was a thing, and since I live by multiple monitors, this makes me glad I've held off.
Yea the idle power draw is fine if I only attach one monitor. But I have 3…
Not much can be done about that. If you're not hitting a vertical blanking interval compatibility issue, you're likely hitting a bandwidth constraint requiring maximum mclk at idle to sustain those displays.
With that said, the idle power improvements have hit various display configurations, including many dual monitor setups.
Improvements as in better than W10 too? Or just a resolution to issues with W11?
Nope but the new drivers will fix that issue.