debcrafters-packages team mailing list archive

[Mario Limonciello <2127944@xxxxxxxxxxxxxxxxxx>]

Hmm.  In that case maybe we really are better doing it after the
amdgpu.ids comparison so that we still have a chance to have a better
string than the hardware identifies.

-- 
You received this bug notification because you are a member of
Debcrafters packages, which is subscribed to libdrm in Ubuntu.
https://bugs.launchpad.net/bugs/2127944

Title:
  Identify APUs from hardware

Status in libdrm package in Ubuntu:
  New
Status in libdrm source package in Noble:
  New
Status in libdrm source package in Questing:
  New
Status in libdrm source package in Resolute:
  New

Bug description:
  [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.

  [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.

  [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 patch: https://gitlab.freedesktop.org/mesa/libdrm/-/commit/2c1d39eff8b9c8296b57212bffd031029ce74491

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/2127944/+subscriptions