I hope this fixes my 7900xtx’s 100w idle power issue…

    • beefcat@kbin.social
      link
      fedilink
      arrow-up
      14
      ·
      11 months ago

      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.

    • MooseBoys@lemmy.world
      cake
      link
      fedilink
      English
      arrow-up
      3
      ·
      11 months ago

      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.

      • LoafyLemon@kbin.social
        link
        fedilink
        arrow-up
        2
        ·
        edit-2
        11 months ago

        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.

        • MooseBoys@lemmy.world
          cake
          link
          fedilink
          English
          arrow-up
          2
          ·
          edit-2
          11 months ago

          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.

  • UmbrellAssassin@lemmy.world
    link
    fedilink
    English
    arrow-up
    7
    arrow-down
    1
    ·
    11 months ago

    Can’t wait for this to be rolled out with bugs and spending 30 minutes tracking down the reg code to disable it.

  • Kogasa@programming.dev
    link
    fedilink
    English
    arrow-up
    4
    ·
    11 months ago

    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.

    • fuzzzerd@kbin.social
      link
      fedilink
      arrow-up
      3
      ·
      11 months ago

      Didn’t even know this was a thing, and since I live by multiple monitors, this makes me glad I’ve held off.

      • Vik@lemmy.world
        link
        fedilink
        English
        arrow-up
        2
        ·
        edit-2
        11 months ago

        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.