Ubuntu
nvidia-graphics-drivers package

package nvidia-current 195.36.15-0ubuntu3 failed to install/upgrade: nvidia-current kernel module failed to build

Bug #590292 reported by Tomas Cassidy on 2010-06-06

This bug report is a duplicate of: Bug #576648: package nvidia-* failed to install/upgrade: nvidia-* kernel module failed to build (Unable to determine the target kernel version.). Edit Remove

This bug affects 1 person

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

Bug Description

This crash appeared in apport after startup/login.

ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: nvidia-current
ProcVersionSignature: Ubuntu 2.6.32-22.36-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-22-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
Date: Sat May 29 17:51:58 2010
DkmsStatus:
nvidia-current, 195.36.15, 2.6.32-21-generic, x86_64: installed
nvidia-current, 195.36.15, 2.6.32-22-generic, x86_64: installed
nvidia-current, 195.36.15, 2.6.32-02063212-generic, x86_64: built
ErrorMessage: nvidia-current kernel module failed to build
InstallationMedia: Mythbuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100427.1)
MachineType: Gigabyte Technology Co., Ltd. G31M-S2L
PackageVersion: 195.36.15-0ubuntu3
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-22-generic root=UUID=2c598869-6588-4165-89e6-fe2c616381cc ro quiet splash
SourcePackage: nvidia-graphics-drivers
Title: package nvidia-current 195.36.15-0ubuntu3 failed to install/upgrade: nvidia-current kernel module failed to build
dmi.bios.date: 12/29/2008
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F9
dmi.board.name: G31M-S2L
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF9:bd12/29/2008:svnGigabyteTechnologyCo.,Ltd.:pnG31M-S2L:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnG31M-S2L:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
dmi.product.name: G31M-S2L
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
glxinfo: Error: [Errno 2] No such file or directory
system:
distro: Ubuntu
codename: lucid
architecture: x86_64
kernel: 2.6.32-22-generic

Tags:

Revision history for this message

Tomas Cassidy (tomas-cassidy) wrote on 2010-06-06:

BootDmesg.txt Edit (39.5 KiB, text/plain; charset="utf-8")
CurrentDmesg.txt Edit (5.0 KiB, text/plain; charset="utf-8")
DKMSBuildLog.txt Edit (985 bytes, text/plain; charset="utf-8")
Dependencies.txt Edit (1.3 KiB, text/plain; charset="utf-8")
Lspci.txt Edit (19.1 KiB, text/plain; charset="utf-8")
Lsusb.txt Edit (391 bytes, text/plain; charset="utf-8")
PciDisplay.txt Edit (1.9 KiB, text/plain; charset="utf-8")
ProcCpuinfo.txt Edit (1.4 KiB, text/plain; charset="utf-8")
ProcInterrupts.txt Edit (1.5 KiB, text/plain; charset="utf-8")
ProcModules.txt Edit (2.7 KiB, text/plain; charset="utf-8")
RelatedPackageVersions.txt Edit (231 bytes, text/plain; charset="utf-8")
UdevDb.txt Edit (102.2 KiB, text/plain; charset="utf-8")
UdevLog.txt Edit (214.3 KiB, text/plain; charset="utf-8")
XorgConf.txt Edit (213 bytes, text/plain; charset="utf-8")
XorgLog.txt Edit (12.9 KiB, text/plain; charset="utf-8")
XorgLogOld.txt Edit (13.2 KiB, text/plain; charset="utf-8")
Xrandr.txt Edit (2.0 KiB, text/plain; charset="utf-8")
setxkbmap.txt Edit (233 bytes, text/plain; charset="utf-8")
xdpyinfo.txt Edit (21.9 KiB, text/plain; charset="utf-8")
xkbcomp.txt Edit (44.4 KiB, text/plain; charset="utf-8")

Revision history for this message

Nikolaj Sheller (nikolajsheller) wrote on 2010-06-12:

Related to: #587895?

Revision history for this message

Daniel van Vugt (vanvugt) wrote on 2011-05-26:

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 #576648, 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.