nvidia dkms failure on upgrade from disco to eoan

Bug #1844939 reported by Brad Figg
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

INFO:Enable nvidia
DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/put_your_quirks_here
DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/dell_latitude
DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/lenovo_thinkpad
Removing old nvidia-390.129 DKMS files...

------------------------------
Deleting module version: 390.129
completely from the DKMS tree.
------------------------------
Done.
Loading new nvidia-390.129 DKMS files...
Building for 5.0.0-29-generic 5.3.0-10-generic
Building for architecture x86_64
Building initial module for 5.0.0-29-generic
ERROR (dkms apport): kernel package linux-headers-5.0.0-29-generic is not supported
Error! Bad return status for module build on kernel: 5.0.0-29-generic (x86_64)
Consult /var/lib/dkms/nvidia/390.129/build/make.log for more information.
dpkg: error processing package nvidia-dkms-390 (--configure):
 installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 10
dpkg: dependency problems prevent configuration of nvidia-driver-390:
 nvidia-driver-390 depends on nvidia-dkms-390 (= 390.129-0ubuntu1); however:
  Package nvidia-dkms-390 is not configured yet.

dpkg: error processing package nvidia-driver-390 (--configure):
 dependency problems - leaving unconfigured
No apport report written because the error message indicates its a followup error from a previous failure.
                                                                                                          Processing triggers for linux-image-5.3.0-10-generic (5.3.0-10.11) ...
/etc/kernel/postinst.d/dkms:
 * dkms: running auto installation service for kernel 5.3.0-10-generic

Kernel preparation unnecessary for this kernel. Skipping...

Building module:
cleaning build area...
unset ARCH; env NV_VERBOSE=1 'make' -j12 NV_EXCLUDE_BUILD_MODULES='' KERNEL_UNAME=5.3.0-10-generic IGNORE_XEN_PRESENCE=1 IGNORE_CC_MISMATCH=1 SYSSRC=/lib/modules/5.3.0-10-generic/build LD=/usr/bin/ld.bfd modules........
cleaning build area...

DKMS: build completed.

nvidia.ko:
Running module version sanity check.
modinfo: ERROR: missing module or filename.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /lib/modules/5.3.0-10-generic/updates/dkms/

nvidia-modeset.ko:
Running module version sanity check.
modinfo: ERROR: missing module or filename.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /lib/modules/5.3.0-10-generic/updates/dkms/

nvidia-drm.ko:
Running module version sanity check.
modinfo: ERROR: missing module or filename.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /lib/modules/5.3.0-10-generic/updates/dkms/

nvidia-uvm.ko:
Running module version sanity check.
modinfo: ERROR: missing module or filename.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /lib/modules/5.3.0-10-generic/updates/dkms/

depmod...

DKMS: install completed.
   ...done.
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-5.3.0-10-generic
/etc/kernel/postinst.d/zz-update-grub:
Sourcing file `/etc/default/grub'
Sourcing file `/etc/default/grub.d/init-select.cfg'
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-5.3.0-10-generic
Found initrd image: /boot/initrd.img-5.3.0-10-generic
Found linux image: /boot/vmlinuz-5.0.0-29-generic
Found initrd image: /boot/initrd.img-5.0.0-29-generic
Found linux image: /boot/vmlinuz-5.0.0-28-generic
Found initrd image: /boot/initrd.img-5.0.0-28-generic
Found memtest86+ image: /boot/memtest86+.elf
Found memtest86+ image: /boot/memtest86+.bin
Found Ubuntu 16.04.3 LTS (16.04) on /dev/sda1
done
Processing triggers for initramfs-tools (0.133ubuntu10) ...
update-initramfs: Generating /boot/initrd.img-5.3.0-10-generic
Processing triggers for dictionaries-common (1.28.1) ...
Processing triggers for libc-bin (2.30-0ubuntu1) ...
Processing triggers for rygel (0.38.1-2ubuntu2) ...
Processing triggers for tex-common (6.12) ...
Running updmap-sys. This may take some time... done.
Running mktexlsr /var/lib/texmf ... done.
Building format(s) --all.
        This may take some time... done.
Processing triggers for libgdk-pixbuf2.0-0:amd64 (2.39.2-3) ...
Processing triggers for dbus (1.12.14-1ubuntu2) ...
Processing triggers for libvlc-bin:amd64 (3.0.8-2) ...
Errors were encountered while processing:
 nvidia-dkms-390
 nvidia-driver-390
E: Sub-process /usr/bin/dpkg returned an error code (1)

Tags: disco
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 1844939

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
tags: added: disco
Brad Figg (brad-figg)
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Alberto Milone (albertomilone) wrote :

I can't reproduce the problem here. Any chance you could attach your /var/lib/dkms/nvidia/390.129/build/make.log ?

Revision history for this message
Brad Figg (brad-figg) wrote :
Revision history for this message
Alberto Milone (albertomilone) wrote :

It looks like the same problem with the new gcc flags:

error: ‘-mindirect-branch’ and ‘-fcf-protection’ are not compatible

I am pretty sure Seth fixed in the kernel as per LP: #1830961

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.