20.04.5 (20220829.1 build) has kernel 5.13 packages
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux-restricted-modules-hwe-5.15 (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
ubuntu-meta (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
[Impact]
* Linux-restricte
* Including the 390 release in the ISO causes the 5.13 packages to be pulled in.
[Test Plan]
* Install the hwe-515 kernel and make sure that the NVIDIA 390 driver can be installed with its linux-restricte
[Where problems could occur]
* The addition of modules for an already existing driver series would not
cause any regressions, since the whole package generation process is automated, and this is the only commit that we are going to revert:
https:/
[Other Info]
* Other kernel releases support the 390 series.
_________
Examining the .list file for the amd64 image it contains various kernel 5.13 .deb packages.
http://
e.g.
/pool/main/
/pool/restricte
/pool/restricte
/pool/restricte
/pool/restricte
This is a little unexpected given that 5.15 is the default kernel.
Possibly nvidia-390 doesn't have 5.15 packages?
This impacts all flavours as well that include nvidia stuff in their ISO - so if the solution is to change the meta file for a revised regexp for nvidia then all flavours that include nvidia will likewise need their meta packages updated.
tags: | added: iso-testing |
description: | updated |
description: | updated |
description: | updated |
description: | updated |
...discussed this with the kernel team and it seems to be a bug in the 5.15 hwe lrm kernel packages. Apparently because of an error, the nvidia-390 packages have not been prepared for this kernel. And since we pull in 390 (and should), this causes the build infrastructure to pull in the old 5.13 kernels along with them.
The kernel team is working on a lrm-only respin.