Ubuntu
nvidia-graphics-drivers package

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

Bug #891375 reported by Wesley Schwengle on 2011-11-16

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

fails to install

ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: nvidia-current 195.36.15-0ubuntu2
ProcVersionSignature: Ubuntu 2.6.32-31.61-generic 2.6.32.32+drm33.14
Uname: Linux 2.6.32-31-generic i686
NonfreeKernelModules: nvidia
Architecture: i386
Date: Wed Nov 16 21:29:53 2011
DkmsStatus:
nvidia-173, 173.14.22, 2.6.32-31-generic, i686: installed
nvidia-173, 173.14.22, 2.6.32-35-generic, i686: installed
nvidia-173, 173.14.22, 2.6.32-34-generic, i686: installed
nvidia-173, 173.14.22, 2.6.32-27-generic, i686: built
nvidia-current, 195.36.15: added
ErrorMessage: nvidia-current kernel module failed to build
InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release i386 (20100816.1)
MachineType: stem manufacturer System Product Name
PackageVersion: 195.36.15-0ubuntu2
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-31-generic root=UUID=170476a9-eb70-47be-9e08-38a2c57e6f84 ro quiet splash
SourcePackage: nvidia-graphics-drivers
Title: package nvidia-current 195.36.15-0ubuntu2 failed to install/upgrade: nvidia-current kernel module failed to build
dmi.bios.date: 08/28/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2002
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: P5LD2
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2002:bd08/28/2009:svnstemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5LD2:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: stem manufacturer
glxinfo: Error: [Errno 2] No such file or directory
system:
distro: Ubuntu
codename: lucid
architecture: i686
kernel: 2.6.32-31-generic

Tags:

Revision history for this message

Wesley Schwengle (wesleys) wrote on 2011-11-16:

BootDmesg.txt Edit (41.2 KiB, text/plain; charset="utf-8")
CurrentDmesg.txt Edit (1.2 KiB, text/plain; charset="utf-8")
DKMSBuildLog.txt Edit (977 bytes, text/plain; charset="utf-8")
Dependencies.txt Edit (1.3 KiB, text/plain; charset="utf-8")
Lspci.txt Edit (19.4 KiB, text/plain; charset="utf-8")
Lsusb.txt Edit (460 bytes, text/plain; charset="utf-8")
PciDisplay.txt Edit (1.8 KiB, text/plain; charset="utf-8")
ProcCpuinfo.txt Edit (1.5 KiB, text/plain; charset="utf-8")
ProcInterrupts.txt Edit (1.6 KiB, text/plain; charset="utf-8")
ProcModules.txt Edit (1.9 KiB, text/plain; charset="utf-8")
RelatedPackageVersions.txt Edit (231 bytes, text/plain; charset="utf-8")
UdevDb.txt Edit (110.9 KiB, text/plain; charset="utf-8")
UdevLog.txt Edit (224.5 KiB, text/plain; charset="utf-8")
XorgConf.txt Edit (1.5 KiB, text/plain; charset="utf-8")
XorgLog.txt Edit (12.8 KiB, text/plain; charset="utf-8")
XorgLogOld.txt Edit (13.2 KiB, text/plain; charset="utf-8")
Xrandr.txt Edit (17.0 KiB, text/plain; charset="utf-8")
make.log.txt Edit (977 bytes, text/plain; charset="utf-8")
setxkbmap.txt Edit (233 bytes, text/plain; charset="utf-8")
xdpyinfo.txt Edit (30.5 KiB, text/plain; charset="utf-8")
xkbcomp.txt Edit (44.4 KiB, text/plain; charset="utf-8")

Revision history for this message

Daniel van Vugt (vanvugt) wrote on 2011-11-17:

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.