Ubuntu
nvidia-graphics-drivers-390 package

nvidia-dkms-390 390.42-0ubuntu1: nvidia kernel module failed to build

Bug #1761015 reported by Edgar Roca on 2018-04-03

This bug report is a duplicate of: Bug #1760876: DKMS driver builds fail with: Cannot use CONFIG_STACK_VALIDATION=y, please install libelf-dev, libelf-devel or elfutils-libelf-devel. Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	nvidia-graphics-drivers-390 (Ubuntu)	New	Undecided	Unassigned

Bug Description

nvidia

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: nvidia-dkms-390 390.42-0ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
Uname: Linux 4.15.0-12-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu2
Architecture: amd64
DKMSKernelVersion: 4.15.0-14-generic
Date: Tue Apr 3 16:07:39 2018
InstallationDate: Installed on 2018-02-28 (34 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180227)
PackageVersion: 390.42-0ubuntu1
Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-2
PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
RelatedPackageVersions:
dpkg 1.19.0.5ubuntu1
apt 1.6~beta1
SourcePackage: nvidia-graphics-drivers-390
Title: nvidia-dkms-390 390.42-0ubuntu1: nvidia kernel module failed to build
UpgradeStatus: No upgrade log present (probably fresh install)

Tags:

Revision history for this message

Edgar Roca (felitin2000) wrote on 2018-04-03:

DKMSBuildLog.txt Edit (27.2 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (3.7 KiB, text/plain; charset="utf-8")
ProcCpuinfoMinimal.txt Edit (1.0 KiB, text/plain; charset="utf-8")

Revision history for this message

Daniel van Vugt (vanvugt) wrote on 2018-04-04:

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1760983, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.