[Bug 2083020] Re: Backport packages for 24.04.2 HWE stack
AaronMa
2083020 at bugs.launchpad.net
Mon Dec 23 11:35:58 UTC 2024
sudo apt install libglx-mesa0=24.2.8-1ubuntu1~24.04.1 mesa-
libgallium=24.2.8-1ubuntu1~24.04.1 libdrm2=2.4.122-1~ubuntu0.24.04.1
libdrm-common=2.4.122-1~ubuntu0.24.04.1 libegl-
mesa0=24.2.8-1ubuntu1~24.04.1 libdrm-amdgpu1=2.4.122-1~ubuntu0.24.04.1
libdrm-intel1=2.4.122-1~ubuntu0.24.04.1 libdrm-
intel1=2.4.122-1~ubuntu0.24.04.1 libdrm-
radeon1=2.4.122-1~ubuntu0.24.04.1 libgbm1=24.2.8-1ubuntu1~24.04.1
libglapi-mesa=24.2.8-1ubuntu1~24.04.1 libgl1-mesa-
dri=24.2.8-1ubuntu1~24.04.1
Tested on:
AMD Ryzen AI 7 PRO 360 w/ Radeon 880M
c4:00.0 Display controller: Advanced Micro Devices, Inc. [AMD/ATI] Device 150e (rev d2)
Intel ARL-S:
00:02.0 VGA compatible controller: Intel Corporation Arrow Lake-U [Intel Graphics] (rev 03)
Intel ADL-U:
00:02.0 VGA compatible controller: Intel Corporation Alder Lake-P GT2 [Iris Xe Graphics] (rev 0c)
01:00.0 VGA compatible controller: NVIDIA Corporation GA103M [GeForce RTX 3080 Ti Mobile] (rev a1)
Ubuntu GUI works fine.
glxgears tests fine.
glmark2 tests fine.
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to libdrm in Ubuntu.
https://bugs.launchpad.net/bugs/2083020
Title:
Backport packages for 24.04.2 HWE stack
Status in OEM Priority Project:
New
Status in libdrm package in Ubuntu:
Invalid
Status in llvm-toolchain-19 package in Ubuntu:
Invalid
Status in mesa package in Ubuntu:
Invalid
Status in meson-1.5 package in Ubuntu:
New
Status in spirv-llvm-translator-19 package in Ubuntu:
Invalid
Status in libdrm source package in Noble:
Fix Committed
Status in llvm-toolchain-19 source package in Noble:
Fix Committed
Status in mesa source package in Noble:
Fix Committed
Status in meson-1.5 source package in Noble:
Fix Committed
Status in spirv-llvm-translator-19 source package in Noble:
In Progress
Bug description:
[Impact]
The graphics HWE stack from oracular needs to be backported for 24.04.2
libdrm
- build-dep of mesa
spirv-llvm-translator
- build-dep of llvm
- note that some symbols changed/added/dropped on certain archs due to older
gcc/toolchain, so dh_makeshlibs was overridden to not care about those
llvm-toolchain-19
- new source in noble
- build-dep of mesa
- required for new AMD platforms
- needs two uploads:
* 1st stage bootstrap build
* 2nd stage after spirv-llvm-translator has built against 1st stage
mesa
- new major release, last of the series (24.2.8) so it has accumulated all
the fixes upstream considered worthy for it
- new HW support, Lunar Lake, Battlemage..
meson-1.5
- needed by mesa
- Conflicts/Replaces meson, because otherwise all of the python lib should be
renamed, along with the includes etc so it's not a trivial amount of work
- tests disabled because four irrelevant ones fail for some reason, doesn't
affect the mesa backport
[Test case]
We want to cover at least 2-3 different, widely used and already previously supported GPU generations from both AMD and Intel which are supported by this release, as those are the ones that cover most bases; nouveau users tend to switch to the NVIDIA driver after installation. No need to test ancient GPU's supported by mesa-amber. And best to focus on the newer generations (~5y and newer) as the older ones are less likely to break at this point.
- AMD: Vega, Navi1x (RX5000*), Navi2x (RX6000*), Navi3x (RX7000*)
- Intel: gen9 (SKL/APL/KBL/CFL/WHL/CML), gen11 (ICL), gen12 (TGL/ADL/RKL/RPL/DG2)
Install the new packages and run some tests:
- check that the desktop is still using hw acceleration and hasn't fallen back to swrast/llvmpipe
- run freely available benchmarks that torture the GPU (Unigine Heaven/Valley/Superposition)
- run some games from Steam if possible
and in each case check that there is no gfx corruption happening or
worse.
Note that upstream releases have already been tested for OpenGL and
Vulkan conformance by their CI.
[Where things could go wrong]
This is a major update of Mesa, there could be regressions but we'll try to catch any with testing. And since it shares bugs with oracular, we'd already know if there are serious issues.
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/2083020/+subscriptions
More information about the foundations-bugs
mailing list