Announcement

Collapse
No announcement yet.

AMD Prepares More Graphics Driver Code For Linux 5.15

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • AMD Prepares More Graphics Driver Code For Linux 5.15

    Phoronix: AMD Prepares More Graphics Driver Code For Linux 5.15

    Last week's AMDGPU pull request to DRM-Next for Linux 5.15 added support for the "Cyan Skillfish" APU and other early work while an additional pull request was submitted on Friday...

    Phoronix, Linux Hardware Reviews, Linux hardware benchmarks, Linux server benchmarks, Linux benchmarking, Desktop Linux, Linux performance, Open Source graphics, Linux How To, Ubuntu benchmarks, Ubuntu hardware, Phoronix Test Suite

  • #2
    I hope the idle power issue for higher res displays will be eventually addressed.

    Comment


    • #3
      Originally posted by shmerl View Post
      I hope the idle power issue for higher res displays will be eventually addressed.
      a new issue or a years ongoing one?

      on windows, some people have noticed the display subtiming settings can have an effect on power draw (which is mainly the gddr clockspeed+voltage required for that speed, if it can handle a lower than max speed for high refresh/high resolution/multimonitor)

      most monitors can run within a range of these settings, it's the same ones used for overclocking the refresh rate (only certain modes or timings can work, my monitor for example can go up to 71hz without artifacts)

      Comment


      • #4
        Originally posted by kn00tcn View Post

        a new issue or a years ongoing one?
        Not sure for how long it exists, but for a while for sure: https://gitlab.freedesktop.org/drm/amd/-/issues/1403

        Comment


        • #5
          Originally posted by shmerl View Post

          Not sure for how long it exists, but for a while for sure: https://gitlab.freedesktop.org/drm/amd/-/issues/1403
          yes, look at the multiple posts talking about those special display settings having an effect, but i dont have a proper low level understanding of the quirks or if there are bugs introduced in the drivers over time, only that there are common experiences & workarounds across windows+linux (presumably meaning it's not exactly driver specific but combination of hardware or timing specific)

          Comment

          Working...
          X