[Bug 2106038] Re: [FFe] Intel BMG 0xe211 PCI ID is not supported

[Launchpad Bug Tracker]

This bug was fixed in the package intel-compute-runtime -
24.52.32224.13-0ubuntu3

---------------
intel-compute-runtime (24.52.32224.13-0ubuntu3) plucky; urgency=medium

  *  Backport patch to add Battlemage PCI ID 0xE211 (LP: #2106038)

 -- Shane McKee <shane.mckee at canonical.com>  Thu, 03 Apr 2025 17:28:23
+0400

** Changed in: intel-compute-runtime (Ubuntu)
       Status: Triaged => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/2106038

Title:
  [FFe] Intel BMG 0xe211 PCI ID is not supported

Status in intel-compute-runtime package in Ubuntu:
  Fix Released
Status in intel-gmmlib package in Ubuntu:
  Triaged
Status in intel-media-driver package in Ubuntu:
  Fix Released
Status in intel-media-driver-non-free package in Ubuntu:
  Fix Released
Status in onevpl-intel-gpu package in Ubuntu:
  Fix Released

Bug description:
  [ Impact ]

  A new Intel Battlemage card SKU is unsupported in Ubuntu Plucky and
  lower. This FFe adds the minimum necessary patches (Adding the PCI-ID)
  to enable the new Intel Battlemage hardware across several packages.
  No other changes are necessary for this enablement, and impact to
  existing hardware is minimal because there are no functional changes
  included. We should backport these changes to Plucky, Oracular and
  Noble. The latter two will be done in a separate SRU with the previous
  set of PCI IDs added (LP: #2104011).

  The upstream changesets can be found in the following locations:

  mesa
  * https://gitlab.freedesktop.org/mesa/mesa/-/commit/d3ec467031780136412366a2a36a46d4c4d8cfdc

  Timo is handling Mesa, but I will leave the patch here to indicate
  that the efforts should be connected

  intel-compute-runtime
  * https://github.com/intel/compute-runtime/commit/3d9fc8968e6dc12a30093212dd2cd99bf84b9c7c

  intel-media-driver(and -non-free)
  * https://github.com/intel/media-driver/commit/59859ccd3f9956aa992105ec191813e8f691547b

  onevpl-intel-gpu
  * https://github.com/intel/vpl-gpu-rt/commit/4b7b2dfe7751c6a3b8603ecc1ec058eaf3498495

  intel-gmmlib
  * https://github.com/intel/gmmlib/commit/60304dc18a2f735808f2b92b8b9dfd3175f46513

  [ Test Plan ]

  To reproduce, run our checkbox-media testing on one of the new GPUs
  before adding these patches. To confirm that the media patches worked,
  install packages with those patches applied, and re-run checkbox-media
  tests.

  https://github.com/canonical/checkbox-media

  This will test hardware encode and decode at 1080p and 4K for H264,
  AV1, and VP9 as well as running the VPL tests. This testing will cover
  all packages affected here.

  [ Where problems could occur ]

  While this is a simple, routine change already accepted upstream, no
  change can be totally risk free. In this case, we’re changing
  something as central as Mesa, which is central for multiple hardware
  vendors. A bug there could cause a lot of issues for basic GUI
  function.

  For intel-gmmlib, intel-media-driver, and onevpl-intel-gpu, a bug
  could cause a failure in hardware support for media on Intel.

  Issues in compute-runtime would cause failures in OpenCL support for
  Intel hardware.

  [ Other Info ]

  PPA link: https://launchpad.net/~mckeesh/+archive/ubuntu/lp2106038-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/intel-compute-runtime/+bug/2106038/+subscriptions