@waveform You would be correct that this is just a version bump to what we have in Oracular. Our original graphics stack enablement happened on Oracular, so we're mostly just trying to get that effort SRU'd back to Noble
** Description changed: [ Description ] Intel has requested us to update the media driver (free and non-free) to 24.3.4 due to the need to have Lunar Lake (LNL) and Battle Mage (BMG) support. This request has a strong dependency on an intel-gmmlib version bump to 22.5.2 and a libva version bump to 2.22.0. [ Impact ] * Users with Lunar Lake or Battlemage currently do not have an LTS support option, which is not a good option for some users, as seen here: https://github.com/canonical/intel-graphics-preview/issues/8 * Users with Lunar Lake or Battlemage hardware will not have hardware- enabled media support, which can effect the power consumption and CPU utilization of the machine during encode/decode/transcode operations, video calls, streaming, etc. [ Test Plan ] # On a Lunar Lake or Battlemage machine # Required at this time to get baseline enablement sudo add-apt-repository ppa:kobuk-team/intel-graphics-testing sudo apt update # Get the original versions back sudo apt install -y intel-media-va-driver-non-free=24.1.0+ds1-1 libva2=2.20.0-2build1 libigdgmm12=22.3.17+ds1-1 vainfo=2.12.0+ds1-1 libva-drm2=2.20.0-2build1 libva-wayland2=2.20.0-2build1 libva-x11-2=2.20.0-2build1 # This should result in an error sudo vainfo sudo add-apt-repository -y ppa:mckeesh/testing && sudo apt -y update # Only upgrade the media packages sudo apt install -y intel-media-va-driver-non-free=24.3.4+ds1-0ubuntu1 libva2=2.22.0-1ubuntu1 libigdgmm12=22.5.2-0ubuntu1 libva-drm2=2.22.0-1ubuntu1 libva-wayland2=2.22.0-1ubuntu1 libva-x11-2=2.22.0-1ubuntu1 vainfo=2.12.0+ds1-1 # This should no longer result in an error sudo vainfo [ Where problems could occur ] * This is a sizable change, and while significant testing goes into making sure the media stack does not regress, it's always a risk. Ubuntu has a large user base with many, many corner cases, and media stack bumps can always accidentally regress a less popular codec on an older platform. However, we can address any smaller regressions that might arise when the benefit is enablement of LNL and BMG. * Beyond Intel's extensive in-house testing, we have done our own testing via FFMPEG to check for AV1, VP9, and H264 hardware acceleration for encode and decode at 1080p and 4K. In addition to Lunar Lake and Battlemage, we have also tested Alder Lake, Comet Lake, and Gemini Lake and found no regressions across these platforms [ Other Info ] + + * This would ideally land at the same time as the libvpl version bump + SRU here: https://bugs.launchpad.net/ubuntu/+source/onevpl/+bug/2096823 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libva in Ubuntu. https://bugs.launchpad.net/bugs/2095074 Title: [SRU] Upgrade to media driver version 24.3.4 in Noble Status in intel-gmmlib package in Ubuntu: Fix Released Status in intel-media-driver package in Ubuntu: Fix Released Status in intel-media-driver-non-free package in Ubuntu: Fix Released Status in libva package in Ubuntu: Fix Released Status in intel-gmmlib source package in Noble: New Status in intel-media-driver source package in Noble: New Status in intel-media-driver-non-free source package in Noble: New Status in libva source package in Noble: New Bug description: [ Description ] Intel has requested us to update the media driver (free and non-free) to 24.3.4 due to the need to have Lunar Lake (LNL) and Battle Mage (BMG) support. This request has a strong dependency on an intel-gmmlib version bump to 22.5.2 and a libva version bump to 2.22.0. [ Impact ] * Users with Lunar Lake or Battlemage currently do not have an LTS support option, which is not a good option for some users, as seen here: https://github.com/canonical/intel-graphics-preview/issues/8 * Users with Lunar Lake or Battlemage hardware will not have hardware-enabled media support, which can effect the power consumption and CPU utilization of the machine during encode/decode/transcode operations, video calls, streaming, etc. [ Test Plan ] # On a Lunar Lake or Battlemage machine # Required at this time to get baseline enablement sudo add-apt-repository ppa:kobuk-team/intel-graphics-testing sudo apt update # Get the original versions back sudo apt install -y intel-media-va-driver-non-free=24.1.0+ds1-1 libva2=2.20.0-2build1 libigdgmm12=22.3.17+ds1-1 vainfo=2.12.0+ds1-1 libva-drm2=2.20.0-2build1 libva-wayland2=2.20.0-2build1 libva-x11-2=2.20.0-2build1 # This should result in an error sudo vainfo sudo add-apt-repository -y ppa:mckeesh/testing && sudo apt -y update # Only upgrade the media packages sudo apt install -y intel-media-va-driver-non-free=24.3.4+ds1-0ubuntu1 libva2=2.22.0-1ubuntu1 libigdgmm12=22.5.2-0ubuntu1 libva-drm2=2.22.0-1ubuntu1 libva-wayland2=2.22.0-1ubuntu1 libva-x11-2=2.22.0-1ubuntu1 vainfo=2.12.0+ds1-1 # This should no longer result in an error sudo vainfo [ Where problems could occur ] * This is a sizable change, and while significant testing goes into making sure the media stack does not regress, it's always a risk. Ubuntu has a large user base with many, many corner cases, and media stack bumps can always accidentally regress a less popular codec on an older platform. However, we can address any smaller regressions that might arise when the benefit is enablement of LNL and BMG. * Beyond Intel's extensive in-house testing, we have done our own testing via FFMPEG to check for AV1, VP9, and H264 hardware acceleration for encode and decode at 1080p and 4K. In addition to Lunar Lake and Battlemage, we have also tested Alder Lake, Comet Lake, and Gemini Lake and found no regressions across these platforms [ Other Info ] * This would ideally land at the same time as the libvpl version bump SRU here: https://bugs.launchpad.net/ubuntu/+source/onevpl/+bug/2096823 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-gmmlib/+bug/2095074/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
