[Kernel-packages] [Bug 1856407] Re: 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
The Eoan Ermine has reached end of life, so this bug will not be fixed
for that release
** Changed in: ubuntu-meta (Ubuntu Eoan)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-restricted-modules in 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
Status in linux package in Ubuntu:
Invalid
Status in linux-restricted-modules package in Ubuntu:
Invalid
Status in nvidia-graphics-drivers-435 package in Ubuntu:
Confirmed
Status in ubuntu-drivers-common package in Ubuntu:
Confirmed
Status in ubuntu-meta package in Ubuntu:
New
Status in linux source package in Eoan:
Fix Released
Status in linux-restricted-modules source package in Eoan:
Fix Released
Status in nvidia-graphics-drivers-435 source package in Eoan:
Confirmed
Status in ubuntu-drivers-common source package in Eoan:
Confirmed
Status in ubuntu-meta source package in Eoan:
Won't Fix
Bug description:
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.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856407/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1856407] Re: 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
The ubuntu-drivers-common task here appears to be to change it to prefer
the pre-built/signed drivers (linux-modules-nvidia-*) over the DKMS
counterparts. I'd recommend at that point that we start seeding linux-
modules-nvidia-[0-9]+-generic onto the desktop ISO instead of the DKMS
counterparts, so the offline install experiences matches.
** Also affects: ubuntu-meta (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-restricted-modules in 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
Status in linux package in Ubuntu:
Invalid
Status in linux-restricted-modules package in Ubuntu:
Invalid
Status in nvidia-graphics-drivers-435 package in Ubuntu:
Confirmed
Status in ubuntu-drivers-common package in Ubuntu:
Confirmed
Status in ubuntu-meta package in Ubuntu:
New
Status in linux source package in Eoan:
Fix Released
Status in linux-restricted-modules source package in Eoan:
Fix Released
Status in nvidia-graphics-drivers-435 source package in Eoan:
Confirmed
Status in ubuntu-drivers-common source package in Eoan:
Confirmed
Status in ubuntu-meta source package in Eoan:
New
Bug description:
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.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856407/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1856407] Re: 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
This bug was fixed in the package linux-restricted-modules - 5.3.0-26.28
---
linux-restricted-modules (5.3.0-26.28) eoan; urgency=medium
* Master version: 5.3.0-26.28
* 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 (LP: #1856407)
- [Packaging] Add support for nvidia-435 dkms builds
linux-restricted-modules (5.3.0-25.27) eoan; urgency=medium
* Master version: 5.3.0-25.27
* Miscellaneous Ubuntu changes
- debian/dkms-versions -- update from master
-- Khalid Elmously Wed, 18 Dec 2019
00:27:52 -0500
** Changed in: linux-restricted-modules (Ubuntu Eoan)
Status: Fix Committed => Fix Released
** Changed in: linux (Ubuntu Eoan)
Status: Fix Committed => Fix Released
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2019-14895
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2019-14896
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2019-14897
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2019-14901
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2019-18660
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2019-19055
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2019-19072
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-restricted-modules in 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
Status in linux package in Ubuntu:
Invalid
Status in linux-restricted-modules package in Ubuntu:
Invalid
Status in nvidia-graphics-drivers-435 package in Ubuntu:
Confirmed
Status in ubuntu-drivers-common package in Ubuntu:
Confirmed
Status in linux source package in Eoan:
Fix Released
Status in linux-restricted-modules source package in Eoan:
Fix Released
Status in nvidia-graphics-drivers-435 source package in Eoan:
Confirmed
Status in ubuntu-drivers-common source package in Eoan:
Confirmed
Bug description:
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.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856407/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1856407] Re: 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
This bug was fixed in the package linux - 5.3.0-26.28 --- linux (5.3.0-26.28) eoan; urgency=medium * eoan/linux: 5.3.0-26.28 -proposed tracker (LP: #1856807) * 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 (LP: #1856407) - Add nvidia-435 dkms build linux (5.3.0-25.27) eoan; urgency=medium * eoan/linux: 5.3.0-25.27 -proposed tracker (LP: #1854762) * CVE-2019-14901 - SAUCE: mwifiex: Fix heap overflow in mmwifiex_process_tdls_action_frame() * CVE-2019-14896 // CVE-2019-14897 - SAUCE: libertas: Fix two buffer overflows at parsing bss descriptor * CVE-2019-14895 - SAUCE: mwifiex: fix possible heap overflow in mwifiex_process_country_ie() * [CML] New device id's for CMP-H (LP: #1846335) - mmc: sdhci-pci: Add another Id for Intel CML - i2c: i801: Add support for Intel Comet Lake PCH-H - mtd: spi-nor: intel-spi: Add support for Intel Comet Lake-H SPI serial flash - mfd: intel-lpss: Add Intel Comet Lake PCH-H PCI IDs * i915: Display flickers (monitor loses signal briefly) during "flickerfree" boot, while showing the BIOS logo on a black background (LP: #1836858) - [Config] FRAMEBUFFER_CONSOLE_DEFERRED_TAKEOVER=y * Please add patch fixing RK818 ID detection (LP: #1853192) - SAUCE: mfd: rk808: Fix RK818 ID template * Kernel build log filled with "/bin/bash: line 5: warning: command substitution: ignored null byte in input" (LP: #1853843) - [Debian] Fix warnings when checking for modules signatures * Lenovo dock MAC Address pass through doesn't work in Ubuntu (LP: #1827961) - r8152: Add macpassthru support for ThinkPad Thunderbolt 3 Dock Gen 2 * Dell XPS 13 9350/9360 headphone audio hiss (LP: #1654448) // [XPS 13 9360, Realtek ALC3246, Black Headphone Out, Front] High noise floor (LP: #1845810) - ALSA: hda/realtek: Reduce the Headphone static noise on XPS 9350/9360 * no HDMI video output since GDM greeter after linux-oem-osp1 version 5.0.0-1026 (LP: #1852386) - drm/i915: Add new CNL PCH ID seen on a CML platform - SAUCE: drm/i915: Fix detection for a CMP-V PCH * [broadwell-rt286, playback] Since Linux 5.2rc2 audio playback no longer works on Dell Venue 11 Pro 7140 (LP: #1846539) - [Config] Drop snd-sof-intel-bdw build - SAUCE: ASoC: SOF: Intel: Broadwell: clarify mutual exclusion with legacy driver * [CML-S62] Need enable turbostat patch support for Comet lake- S 6+2 (LP: #1847451) - SAUCE: tools/power turbostat: Add Cometlake support * External microphone can't work on some dell machines with the codec alc256 or alc236 (LP: #1853791) - SAUCE: ALSA: hda/realtek - Move some alc256 pintbls to fallback table - SAUCE: ALSA: hda/realtek - Move some alc236 pintbls to fallback table * Memory leak in net/xfrm/xfrm_state.c - 8 pages per ipsec connection (LP: #1853197) - xfrm: Fix memleak on xfrm state destroy * CVE-2019-18660: patches for Ubuntu (LP: #1853142) // CVE-2019-18660 - powerpc/64s: support nospectre_v2 cmdline option - powerpc/book3s64: Fix link stack flush on context switch - KVM: PPC: Book3S HV: Flush link stack on guest exit to host kernel * Raydium Touchscreen on ThinkPad L390 does not work (LP: #1849721) - HID: i2c-hid: fix no irq after reset on raydium 3118 * Make Goodix I2C touchpads work (LP: #1853842) - HID: i2c-hid: Remove runtime power management - HID: i2c-hid: Send power-on command after reset * Touchpad doesn't work on Dell Inspiron 7000 2-in-1 (LP: #1851901) - Revert "UBUNTU: SAUCE: mfd: intel-lpss: add quirk for Dell XPS 13 7390 2-in-1" - lib: devres: add a helper function for ioremap_uc - mfd: intel-lpss: Use devm_ioremap_uc for MMIO * CVE-2019-19055 - nl80211: fix memory leak in nl80211_get_ftm_responder_stats * CML: perf enabling for core (LP: #1848978) - perf/x86/intel: Add Comet Lake CPU support - perf/x86/msr: Add Comet Lake CPU support - perf/x86/cstate: Add Comet Lake CPU support - perf/x86/msr: Add new CPU model numbers for Ice Lake - perf/x86/cstate: Update C-state counters for Ice Lake * Boot hangs after "Loading initial ramdisk ..." (LP: #1852586) - SAUCE: Revert "tpm_tis_core: Set TPM_CHIP_FLAG_IRQ before probing for interrupts" - SAUCE: Revert "tpm_tis_core: Turn on the TPM before probing IRQ's" * [CML-S62] Need enable intel_rapl patch support for Comet lake- S 6+2 (LP: #1847454) - powercap/intel_rapl: add support for CometLake Mobile - powercap/intel_rapl: add support for Cometlake desktop * [CML-S62] Need enable intel_pmc_core driver patch for Comet lake- S 6+2 (LP: #1847450) - SAUCE: platform/x86: intel_pmc_core: Add Comet Lake (CML) platform support to intel_pmc_core driver * update ENA driver for DIMLIB dynamic interrupt
[Kernel-packages] [Bug 1856407] Re: 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
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
eoan' to 'verification-done-eoan'. If the problem still exists, change
the tag 'verification-needed-eoan' to 'verification-failed-eoan'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: verification-needed-eoan
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-restricted-modules in 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
Status in linux package in Ubuntu:
Invalid
Status in linux-restricted-modules package in Ubuntu:
Invalid
Status in nvidia-graphics-drivers-435 package in Ubuntu:
Confirmed
Status in ubuntu-drivers-common package in Ubuntu:
Confirmed
Status in linux source package in Eoan:
Fix Committed
Status in linux-restricted-modules source package in Eoan:
Fix Committed
Status in nvidia-graphics-drivers-435 source package in Eoan:
Confirmed
Status in ubuntu-drivers-common source package in Eoan:
Confirmed
Bug description:
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.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856407/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1856407] Re: 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
** Changed in: linux-restricted-modules (Ubuntu Eoan)
Status: In Progress => Fix Committed
** Changed in: linux (Ubuntu Eoan)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in 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
Status in linux package in Ubuntu:
Invalid
Status in linux-restricted-modules package in Ubuntu:
Invalid
Status in nvidia-graphics-drivers-435 package in Ubuntu:
Confirmed
Status in ubuntu-drivers-common package in Ubuntu:
Confirmed
Status in linux source package in Eoan:
Fix Committed
Status in linux-restricted-modules source package in Eoan:
Fix Committed
Status in nvidia-graphics-drivers-435 source package in Eoan:
Confirmed
Status in ubuntu-drivers-common source package in Eoan:
Confirmed
Bug description:
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.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856407/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1856407] Re: 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
I don't think any updates to nvidia-graphics-drivers-435 are necessary.
I don't know whether ubuntu-drivers-common needs to be updated.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in 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
Status in linux package in Ubuntu:
Invalid
Status in linux-restricted-modules package in Ubuntu:
Invalid
Status in nvidia-graphics-drivers-435 package in Ubuntu:
Confirmed
Status in ubuntu-drivers-common package in Ubuntu:
Confirmed
Status in linux source package in Eoan:
In Progress
Status in linux-restricted-modules source package in Eoan:
In Progress
Status in nvidia-graphics-drivers-435 source package in Eoan:
Confirmed
Status in ubuntu-drivers-common source package in Eoan:
Confirmed
Bug description:
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.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856407/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1856407] Re: 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
https://lists.ubuntu.com/archives/kernel-team/2019-December/106438.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in 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
Status in linux package in Ubuntu:
Invalid
Status in linux-restricted-modules package in Ubuntu:
Invalid
Status in nvidia-graphics-drivers-435 package in Ubuntu:
Confirmed
Status in ubuntu-drivers-common package in Ubuntu:
Confirmed
Status in linux source package in Eoan:
In Progress
Status in linux-restricted-modules source package in Eoan:
In Progress
Status in nvidia-graphics-drivers-435 source package in Eoan:
Confirmed
Status in ubuntu-drivers-common source package in Eoan:
Confirmed
Bug description:
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.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856407/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1856407] Re: 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
** 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 Kernel
Packages, which is subscribed to linux in 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
Status in linux package in Ubuntu:
Invalid
Status in linux-restricted-modules package in Ubuntu:
Invalid
Status in nvidia-graphics-drivers-435 package in Ubuntu:
Confirmed
Status in ubuntu-drivers-common package in Ubuntu:
Confirmed
Status in linux source package in Eoan:
In Progress
Status in linux-restricted-modules source package in Eoan:
In Progress
Status in nvidia-graphics-drivers-435 source package in Eoan:
Confirmed
Status in ubuntu-drivers-common source package in Eoan:
Confirmed
Bug description:
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.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856407/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1856407] Re: 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
Assign Seth Forshee during the desktop team meeting in #ubuntu-desktop on December 17th. If it turns out these assignments are incorrect we can reassign them. ** Changed in: nvidia-graphics-drivers-435 (Ubuntu Eoan) Assignee: (unassigned) => Seth Forshee (sforshee) ** Changed in: ubuntu-drivers-common (Ubuntu Eoan) Assignee: (unassigned) => Seth Forshee (sforshee) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in 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 Status in linux package in Ubuntu: Invalid Status in linux-restricted-modules package in Ubuntu: Invalid Status in nvidia-graphics-drivers-435 package in Ubuntu: Confirmed Status in ubuntu-drivers-common package in Ubuntu: Confirmed Status in linux source package in Eoan: In Progress Status in linux-restricted-modules source package in Eoan: In Progress Status in nvidia-graphics-drivers-435 source package in Eoan: Confirmed Status in ubuntu-drivers-common source package in Eoan: Confirmed Bug description: 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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856407/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1856407] Re: 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
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ubuntu-drivers-common (Ubuntu Eoan) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in 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 Status in linux package in Ubuntu: Invalid Status in linux-restricted-modules package in Ubuntu: Invalid Status in nvidia-graphics-drivers-435 package in Ubuntu: Confirmed Status in ubuntu-drivers-common package in Ubuntu: Confirmed Status in linux source package in Eoan: In Progress Status in linux-restricted-modules source package in Eoan: In Progress Status in nvidia-graphics-drivers-435 source package in Eoan: Confirmed Status in ubuntu-drivers-common source package in Eoan: Confirmed Bug description: 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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856407/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1856407] Re: 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
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nvidia-graphics-drivers-435 (Ubuntu Eoan) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in 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 Status in linux package in Ubuntu: Invalid Status in linux-restricted-modules package in Ubuntu: Invalid Status in nvidia-graphics-drivers-435 package in Ubuntu: Confirmed Status in ubuntu-drivers-common package in Ubuntu: Confirmed Status in linux source package in Eoan: In Progress Status in linux-restricted-modules source package in Eoan: In Progress Status in nvidia-graphics-drivers-435 source package in Eoan: Confirmed Status in ubuntu-drivers-common source package in Eoan: Confirmed Bug description: 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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856407/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1856407] Re: 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
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nvidia-graphics-drivers-435 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in 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 Status in linux package in Ubuntu: Invalid Status in linux-restricted-modules package in Ubuntu: Invalid Status in nvidia-graphics-drivers-435 package in Ubuntu: Confirmed Status in ubuntu-drivers-common package in Ubuntu: Confirmed Status in linux source package in Eoan: In Progress Status in linux-restricted-modules source package in Eoan: In Progress Status in nvidia-graphics-drivers-435 source package in Eoan: Confirmed Status in ubuntu-drivers-common source package in Eoan: Confirmed Bug description: 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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856407/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1856407] Re: 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
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ubuntu-drivers-common (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in 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 Status in linux package in Ubuntu: Invalid Status in linux-restricted-modules package in Ubuntu: Invalid Status in nvidia-graphics-drivers-435 package in Ubuntu: Confirmed Status in ubuntu-drivers-common package in Ubuntu: Confirmed Status in linux source package in Eoan: In Progress Status in linux-restricted-modules source package in Eoan: In Progress Status in nvidia-graphics-drivers-435 source package in Eoan: Confirmed Status in ubuntu-drivers-common source package in Eoan: Confirmed Bug description: 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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856407/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1856407] Re: 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
I've got patches to add nvidia-435 to linux/l-r-m for eoan, will need to upload to a ppa for testing. They should be ready tormorrow. ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Eoan) Importance: Undecided Status: New ** Also affects: linux-restricted-modules (Ubuntu Eoan) Importance: Undecided Status: New ** Also affects: ubuntu-drivers-common (Ubuntu Eoan) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-435 (Ubuntu Eoan) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => Invalid ** Changed in: linux-restricted-modules (Ubuntu) Status: New => Invalid ** Changed in: linux (Ubuntu Eoan) Importance: Undecided => High ** Changed in: linux (Ubuntu Eoan) Status: New => In Progress ** Changed in: linux (Ubuntu Eoan) Assignee: (unassigned) => Seth Forshee (sforshee) ** Changed in: linux-restricted-modules (Ubuntu Eoan) Importance: Undecided => High ** Changed in: linux-restricted-modules (Ubuntu Eoan) Status: New => In Progress ** Changed in: linux-restricted-modules (Ubuntu Eoan) Assignee: (unassigned) => Seth Forshee (sforshee) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in 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 Status in linux package in Ubuntu: Invalid Status in linux-restricted-modules package in Ubuntu: Invalid Status in nvidia-graphics-drivers-435 package in Ubuntu: New Status in ubuntu-drivers-common package in Ubuntu: New Status in linux source package in Eoan: In Progress Status in linux-restricted-modules source package in Eoan: In Progress Status in nvidia-graphics-drivers-435 source package in Eoan: New Status in ubuntu-drivers-common source package in Eoan: New Bug description: 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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856407/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
