Ubuntu
nvidia-graphics-drivers package

nvidia-current 195.x failed to install/upgrade: nvidia-current kernel module failed to build with 3.0.0.8 kernel

Bug #850224 reported by joe of loatj on 2011-09-14

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

Upgraded to latest kernel using kernel PPA, nvidia drivers failed to install.

ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: nvidia-current 195.36.24-0ubuntu1~10.04
ProcVersionSignature: Ubuntu 3.0.0-8.11~lucid1-generic 3.0.1
Uname: Linux 3.0.0-8-generic x86_64
Architecture: amd64
Date: Wed Sep 14 19:00:58 2011
ErrorMessage: nvidia-current kernel module failed to build
InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.1)
MachineType: MICRO-STAR INTERNATIONAL CO.,LTD MS-7599
PackageVersion: 195.36.24-0ubuntu1~10.04
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-8-generic root=UUID=668e371b-d8de-4d04-be31-b2d0b50b31d1 ro quiet splash
SourcePackage: nvidia-graphics-drivers
Title: package nvidia-current 195.36.24-0ubuntu1~10.04 failed to install/upgrade: nvidia-current kernel module failed to build
dmi.bios.date: 08/04/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: V1.12
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: 870-C45 (MS-7599)
dmi.board.vendor: MICRO-STAR INTERNATIONAL CO.,LTD
dmi.board.version: 1.0
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: MICRO-STAR INTERNATIONAL CO.,LTD
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV1.12:bd08/04/2010:svnMICRO-STARINTERNATIONALCO.,LTD:pnMS-7599:pvr1.0:rvnMICRO-STARINTERNATIONALCO.,LTD:rn870-C45(MS-7599):rvr1.0:cvnMICRO-STARINTERNATIONALCO.,LTD:ct3:cvr1.0:
dmi.product.name: MS-7599
dmi.product.version: 1.0
dmi.sys.vendor: MICRO-STAR INTERNATIONAL CO.,LTD
glxinfo: Error: [Errno 2] No such file or directory
system:
distro: Ubuntu
codename: lucid
architecture: x86_64
kernel: 3.0.0-8-generic

Tags:

Revision history for this message

joe of loatj (monkeyofasia) wrote on 2011-09-14:

BootDmesg.txt Edit (55.0 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")
DkmsStatus.txt Edit (576 bytes, text/plain; charset="utf-8")
Lspci.txt Edit (25.8 KiB, text/plain; charset="utf-8")
Lsusb.txt Edit (552 bytes, text/plain; charset="utf-8")
PciDisplay.txt Edit (1.9 KiB, text/plain; charset="utf-8")
ProcCpuinfo.txt Edit (3.4 KiB, text/plain; charset="utf-8")
ProcInterrupts.txt Edit (2.1 KiB, text/plain; charset="utf-8")
ProcModules.txt Edit (2.2 KiB, text/plain; charset="utf-8")
RelatedPackageVersions.txt Edit (197 bytes, text/plain; charset="utf-8")
UdevDb.txt Edit (124.4 KiB, text/plain; charset="utf-8")
UdevLog.txt Edit (227.5 KiB, text/plain; charset="utf-8")
XorgConf.txt Edit (1.3 KiB, text/plain; charset="utf-8")
XorgLog.txt Edit (4.8 KiB, text/plain; charset="utf-8")
XorgLogOld.txt Edit (13.3 KiB, text/plain; charset="utf-8")
Xrandr.txt Edit (751 bytes, text/plain; charset="utf-8")
make.log.txt Edit (973 bytes, text/plain; charset="utf-8")
setxkbmap.txt Edit (233 bytes, text/plain; charset="utf-8")
xdpyinfo.txt Edit (2.5 KiB, text/plain; charset="utf-8")
xkbcomp.txt Edit (47.3 KiB, text/plain; charset="utf-8")

Revision history for this message

Daniel van Vugt (vanvugt) wrote on 2011-09-15:

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.