** Description changed: [Impact] libdrm has an interface that is used by a variety of software (such as GNOME about dialog, nvtop, rocminfo etc) to describe the GPU connected to the system. libdrm by default will try to match an AMD GPU to lines in amdgpu.ids. If there is no match it will fall back to "Radeon Graphics". This is a constant game of cat and mouse because every single SKU of a new product needs a line added. On APUs this is unnecessary though. The string that comes from /proc/cpuinfo describing the model comes from the hardware itself. - A change has been made in upstream libdrm that will prefer this string - when working on an APU instead of the amdgpu.ids file. + A change has been made in upstream libdrm that will fall back to this + string when working on an APU and nothing is found in amdgpu.ids file. [Where problems could occur] - The strings identified by the hardware include more words (like Ryzen or Ryzen AI max), which wasn't in the original string. If there is any software that assumes a short string this could be problematic. + Problems would be localized to exposing the strings that came from /proc/cpuinfo. [Test Plan] * Verify dGPU string in amdgpu.ids shows up properly in GNOME / Settings / About * Verify on an APU string matches /proc/cpuinfo and GNOME / Settings / About. [Other Info] Actual patches: https://gitlab.freedesktop.org/mesa/libdrm/-/commit/2c1d39eff8b9c8296b57212bffd031029ce74491 https://gitlab.freedesktop.org/mesa/libdrm/-/commit/90656fc8e4150fc175ddadb788912674b2c4a705 https://gitlab.freedesktop.org/mesa/libdrm/-/commit/871e326ac799ae28ee4d98da9025028050c085cd
** Description changed: [Impact] libdrm has an interface that is used by a variety of software (such as GNOME about dialog, nvtop, rocminfo etc) to describe the GPU connected to the system. libdrm by default will try to match an AMD GPU to lines in amdgpu.ids. If there is no match it will fall back to "Radeon Graphics". This is a constant game of cat and mouse because every single SKU of a new product needs a line added. On APUs this is unnecessary though. The string that comes from /proc/cpuinfo describing the model comes from the hardware itself. A change has been made in upstream libdrm that will fall back to this string when working on an APU and nothing is found in amdgpu.ids file. [Where problems could occur] Problems would be localized to exposing the strings that came from /proc/cpuinfo. [Test Plan] * Verify dGPU string in amdgpu.ids shows up properly in GNOME / Settings / About - * Verify on an APU string matches /proc/cpuinfo and GNOME / Settings / About. + * Verify on an unknown APU string matches substring from /proc/cpuinfo in GNOME / Settings / About (or modify amdgpu.ids locally to prove this out). [Other Info] Actual patches: https://gitlab.freedesktop.org/mesa/libdrm/-/commit/2c1d39eff8b9c8296b57212bffd031029ce74491 https://gitlab.freedesktop.org/mesa/libdrm/-/commit/90656fc8e4150fc175ddadb788912674b2c4a705 https://gitlab.freedesktop.org/mesa/libdrm/-/commit/871e326ac799ae28ee4d98da9025028050c085cd -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2127944 Title: Identify APUs from hardware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/2127944/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
