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

    Oh sorry, I misunderstood, so you actually get locked into a low mclk under specific display configurations? I’ve genuinely never heard of or personally experienced that across a breadth of hw and sw configs.

    I’m wondering if it could be worth probing the power play sysfs interface or hwmon the next time this happens to try and understand what’s happening there.

    Do you use client apps to interact with tuning settings like LACT? Can you link me to an existing bug report so I can follow up with engineering?

    • vodka@feddit.org
      link
      fedilink
      English
      arrow-up
      3
      ·
      4 days ago

      So I never personally raised a bug report, but this issue was the one I saw when I first got the gpu: https://gitlab.freedesktop.org/drm/amd/-/issues/2460 Exact same issue I’ve always had, MCLK gets stuck at 96MHz and refuses to budge, but since it was relatively easily solved with a quick script that just changes one of my monitors between 60hz and 59.97hz I just accepted that 3 second operation as part of what I had to do to play games lol.

      There’s also a level1techs thread with people with similar issues here: https://forum.level1techs.com/t/linux-really-sucks-right-now/223700 And also this Bazzite issue: https://github.com/ublue-os/bazzite/issues/1070

      I can replicate the issue, though right now I’ve got the opposite issue since getting a 4K144Hz monitor that ends with the MCLK being stuck at maximum at all times, which tbh I’m fine with as I don’t care about the efficiency, I need the heating in this -30c weather anyway.

      • Vik@lemmy.world
        link
        fedilink
        English
        arrow-up
        6
        ·
        4 days ago

        Thanks for these, I’ll discuss with the DAL team when I get the chance