installing linux-modules-nvidia does not remove nvidia-dkms, and the kernel prioritizes the wrong version of the module from disk

Bug #1856414 reported by Steve Langasek
14
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux-restricted-modules (Ubuntu)
High
Andy Whitcroft
nvidia-graphics-drivers-430 (Ubuntu)
Undecided
Unassigned

Bug Description

Installing nvidia-driver-430 pulls in nvidia-dkms-430 as a dependency. Installing linux-modules-nvidia-430-generic does not satisfy this dependency in its place; so nvidia-dkms-430 can't be removed without also removing nvidia-driver-430, and then a bunch of other packages also want to be removed as unused:

$ sudo apt purge nvidia-dkms-430
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer required:
  dkms libatomic1:i386 libbsd0:i386 libdrm-amdgpu1:i386 libdrm-intel1:i386
  libdrm-nouveau2:i386 libdrm-radeon1:i386 libdrm2:i386 libedit2:i386
  libelf1:i386 libexpat1:i386 libffi6:i386 libgl1:i386 libgl1-mesa-dri:i386
  libglapi-mesa:i386 libglvnd0:i386 libglx-mesa0:i386 libglx0:i386
  libllvm9:i386 libnvidia-cfg1-430 libnvidia-common-430 libnvidia-compute-430
  libnvidia-compute-430:i386 libnvidia-decode-430 libnvidia-decode-430:i386
  libnvidia-encode-430 libnvidia-encode-430:i386 libnvidia-fbc1-430
  libnvidia-fbc1-430:i386 libnvidia-gl-430 libnvidia-gl-430:i386
  libnvidia-ifr1-430 libnvidia-ifr1-430:i386 libpciaccess0:i386
  libsensors5:i386 libstdc++6:i386 libx11-6:i386 libx11-xcb1:i386 libxau6:i386
  libxcb-dri2-0:i386 libxcb-dri3-0:i386 libxcb-glx0:i386 libxcb-present0:i386
  libxcb-sync1:i386 libxcb1:i386 libxdamage1:i386 libxdmcp6:i386 libxext6:i386
  libxfixes3:i386 libxnvctrl0 libxshmfence1:i386 libxxf86vm1:i386
  nvidia-compute-utils-430 nvidia-kernel-source-430 nvidia-prime
  nvidia-settings nvidia-utils-430 screen-resolution-extra
  xserver-xorg-video-nvidia-430
Use 'sudo apt autoremove' to remove them.
The following packages will be REMOVED:
  nvidia-dkms-430* nvidia-driver-430*
0 upgraded, 0 newly installed, 2 to remove and 0 not upgraded.
After this operation, 1,269 kB disk space will be freed.
Do you want to continue? [Y/n] n
Abort.
$

And it's not sufficient to leave both linux-modules-nvidia and nvidia-dkms installed, because when both are present, the kernel erroneously picks up the modules from nvidia-dkms first, and fails to load them if SecureBoot is on and the local MOK is not enrolled.

linux-modules-nvidia-430-generic probably needs a versioned Provides: so that it can be installed in place of nvidia-dkms-430.

Steve Langasek (vorlon)
Changed in linux-restricted-modules (Ubuntu):
importance: Undecided → High
Andy Whitcroft (apw)
Changed in linux-restricted-modules (Ubuntu):
assignee: nobody → Andy Whitcroft (apw)
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package linux-restricted-modules - 5.4.0-18.22

---------------
linux-restricted-modules (5.4.0-18.22) focal; urgency=medium

  * Master version: 5.4.0-18.22

  * Miscellaneous Ubuntu changes
    - debian/dkms-versions -- update from master

linux-restricted-modules (5.4.0-17.21) focal; urgency=medium

  * Master version: 5.4.0-17.21
  * Bump upload number.

linux-restricted-modules (5.4.0-17.20) focal; urgency=medium

  * Master version: 5.4.0-17.20

linux-restricted-modules (5.4.0-16.19) focal; urgency=medium

  * Master version: 5.4.0-16.19

  * Miscellaneous Ubuntu changes
    - debian/dkms-versions -- update from master

linux-restricted-modules (5.4.0-15.18) focal; urgency=medium

  * Master version: 5.4.0-15.18

  * Miscellaneous Ubuntu changes
    - debian/dkms-versions -- update from master

 -- Seth Forshee <email address hidden> Sat, 07 Mar 2020 10:25:55 -0600

Changed in linux-restricted-modules (Ubuntu):
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers