** Description changed:
+ SRU Justification
+
+ Impact: The nvidia-435 drivers are missing from linux-restricted-modules
+ in eoan. On install ubuntu-drivers picks 435 as the newest version, and
+ users must use self-signed dkms drivers and enroll a MOK.
+
+ Fix: Add nvidia-435 dkms builds to linux and l-r-m for eoan.
+
+ Test Case: A test build is available in ppa:sforshee/test-builds. Verify
+ that signed drivers for nvidia-435 can be installed for eoan via the
+ linux-modules-nvidia-435-{generic,lowlatency} packages.
+
+ Regression Potential: The nvidia-435 l-r-m drivers are new packages
+ built from the same source as the nvidia-435 dkms driver, so regressions
+ are unlikely.
+
+ ---
+
The linux-restricted-modules package exists so that users who install
the nvidia drivers can get known-good, signed modules instead of having
to locally self-sign and enroll a signing key through MOK. But lrm in
eoan is only building driver packages for nvidia 390 and 430, and nvidia
435 is present in eoan.
So on a new Ubuntu 19.10 install, ubuntu-drivers is picking 435 as the
newest driver instead of using the signed 430 driver.
We should never allow the archive to get into this situation. We should
be enforcing that any version of the nvidia driver that we expect
ubuntu-drivers to install by default on any hardware is integrated into
linux-restricted-modules, and we should ensure that ubuntu-drivers
always prefers the signed drivers over other options.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1856407
Title:
nvidia-435 is in eoan, linux-restricted-modules only builds against
430, ubiquity gives me the self-signed modules experience instead of
using the Canonical-signed modules
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856407/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
