Identify APUs from hardware

[Mario Limonciello]

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

[Daniel Letzeisen (dtl131)]

Is there going to be any way to override this like you can with amdgpu.ids?
amdgpu.ids lacked an entry for my 5600G, so it defaulted to generic "Radeon Graphics". I added a "Radeon Vega 7" entry. (I also suggested that libdrm add this, but was told that "Radeon Graphics" was the official marketing name.)

cpuinfo gives "AMD Ryzen 5 5600G with Radeon Graphics", which is more specific than "Radeon Graphics", but that's the CPU name and not the name of the GPU within.

Thanks

[Mario Limonciello (superm1)]

Similar feedback was raised upstream. I'll see what I can come up with on an upstream PR.

[Daniel Letzeisen (dtl131)]

Okay, I see you're just going to cut it down to "Radeon" part: https://gitlab.freedesktop.org/mesa/libdrm/-/merge_requests/433

In my case, that is once again going to leave it with "Radeon Graphics", which is really generic and virtually useless. Even the PCI name is better than that - [AMD/ATI] Cezanne [Radeon Vega Series / Radeon Vega Mobile Series]

[Mario Limonciello (superm1)]

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.

[Mario Limonciello (superm1)]

OK - I pushed another change to the MR per your comment. Can you comment there please?

[Mario Limonciello (superm1)]

I've added those changes, thanks for the feedback.

[Launchpad Janitor (janitor)]

This bug was fixed in the package libdrm - 2.4.127-1ubuntu1

---------------
libdrm (2.4.127-1ubuntu1) resolute; urgency=medium

  * patches: Identify APUs from hardware (LP: #2127944)

 -- Timo Aaltonen <email address hidden> Thu, 23 Oct 2025 17:33:16 +0300

[Nick Rosbrook (enr0n)]

Hello Mario, or anyone else affected,

Accepted libdrm into questing-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/libdrm/2.4.125-1ubuntu0.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-questing to verification-done-questing. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-questing. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

[Nick Rosbrook (enr0n)]

Why does questing have debian/patches/amdgpu-add-env-support-for-amdgpu-ids.patch, while noble does not? Should it be included in both? Neither? Or is the current way correct?

[David Perry (davidperry)]

Tested proposed package libdrm 2.4.125-1ubuntu0.1 with Questing using an AMD Hawkpoint reference board.

I can confirm that with proposed package, graphics print-out successfully changes from generic "AMD Radeon™ Graphics" to the iGPU ID listed in the /proc/cpuinfo. ("AMD Radeon™ 780M Graphics" in this case)

Moving to verification-done.

[Timo Aaltonen (tjaalton)]

that patch was added for https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/2100483 but not backported

[Timo Aaltonen (tjaalton)]

also, it has been submitted upstream but not merged yet, but in the short term I don't think it is needed in noble atm

for 24.04.4 though libdrm needs a full backport (because of mesa), but that'll come later :)

[Ubuntu SRU Bot (ubuntu-sru-bot)]

All autopkgtests for the newly accepted libdrm (2.4.125-1ubuntu0.1) for questing have finished running.
The following regressions have been reported in tests triggered by the package:

clutter-1.0/unknown (amd64)
drm-info/unknown (amd64)
ffmpeg/unknown (i386)
kodi/unknown (amd64)
libcamera/unknown (amd64)
libsdl2/unknown (amd64)
mutter/49.0-2ubuntu5 (s390x)
rust-drm-sys/unknown (amd64)

Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-migration/questing/update_excuses.html#libdrm

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

[Nick Rosbrook (enr0n)]

> that patch was added for https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/2100483 but not backported

Hm, so it should not have been included in the questing upload then really? At least not without SRU documentation for bug 2100483?

In any case, I guess we can continue with the noble upload.

[Nick Rosbrook (enr0n)]

Hello Mario, or anyone else affected,

Accepted libdrm into noble-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/libdrm/2.4.122-1~ubuntu0.24.04.2 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-noble to verification-done-noble. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-noble. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

[Ubuntu SRU Bot (ubuntu-sru-bot)]

All autopkgtests for the newly accepted libdrm (2.4.122-1~ubuntu0.24.04.2) for noble have finished running.
The following regressions have been reported in tests triggered by the package:

mutter/46.2-1ubuntu0.24.04.10 (s390x)

Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-migration/noble/update_excuses.html#libdrm

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

[Mario Limonciello (superm1)]

I upgraded a system with the ID missing in amdgpu.ids to 2.4.122.1~ubuntu0.24.04.2 and can confirm that the about dialog now shows the correct string which comes from the sliced and diced /proc/cpuinfo as intended.

[Launchpad Janitor (janitor)]

This bug was fixed in the package libdrm - 2.4.125-1ubuntu0.1

---------------
libdrm (2.4.125-1ubuntu0.1) questing; urgency=medium

  * patches: Identify APUs from hardware (LP: #2127944)

 -- Timo Aaltonen <email address hidden> Fri, 24 Oct 2025 17:43:46 +0300

[Nick Rosbrook (enr0n)]

The verification of the Stable Release Update for libdrm has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

[Launchpad Janitor (janitor)]

This bug was fixed in the package libdrm - 2.4.122-1~ubuntu0.24.04.2

---------------
libdrm (2.4.122-1~ubuntu0.24.04.2) noble; urgency=medium

  * patches: Identify APUs from hardware (LP: #2127944)

 -- Timo Aaltonen <email address hidden> Fri, 24 Oct 2025 17:48:33 +0300