Ubuntu
nvidia-graphics-drivers-173 package

package nvidia-173 173.14.22-0ubuntu11 failed to install/upgrade: nvidia-173 kernel module failed to build

Bug #731945 reported by PKZ on 2011-03-09

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-173 (Ubuntu)	New	Undecided	Unassigned

Bug Description

nvidia-173 173.14.22-0ubuntu11 failed to install
nvidia-173 kernel module failed to build

ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: nvidia-173 173.14.22-0ubuntu11
ProcVersionSignature: Ubuntu 2.6.32-30.59-generic 2.6.32.29+drm33.13
Uname: Linux 2.6.32-30-generic i686
NonfreeKernelModules: nvidia
Architecture: i386
Date: Wed Mar 9 14:31:07 2011
ErrorMessage: nvidia-173 kernel module failed to build
Lsusb:
Bus 002 Device 003: ID 0b39:0d04 Omnidirectional Control Technology, Inc.
Bus 002 Device 002: ID 05e3:0604 Genesys Logic, Inc. USB 1.1 Hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: MSI MS-7309
PackageVersion: 173.14.22-0ubuntu11
ProcCmdLine: root=UUID=8a50e724-c237-4ec6-8004-c439f5c42e01 ro quiet splash
SourcePackage: nvidia-graphics-drivers-173
Title: package nvidia-173 173.14.22-0ubuntu11 failed to install/upgrade: nvidia-173 kernel module failed to build
dmi.bios.date: 12/10/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: V2.3
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: K9N6PGM2-V2 (MS-7309)
dmi.board.vendor: MSI
dmi.board.version: 2.0
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: MSI
dmi.chassis.version: 2.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV2.3:bd12/10/2009:svnMSI:pnMS-7309:pvr2.0:rvnMSI:rnK9N6PGM2-V2(MS-7309):rvr2.0:cvnMSI:ct3:cvr2.0:
dmi.product.name: MS-7309
dmi.product.version: 2.0
dmi.sys.vendor: MSI
system:
distro: Ubuntu
codename: lucid
architecture: i686
kernel: 2.6.32-30-generic

Tags:

Revision history for this message

PKZ (aikido) wrote on 2011-03-09:

BootDmesg.txt Edit (40.7 KiB, text/plain; charset="utf-8")
CurrentDmesg.txt Edit (900 bytes, text/plain; charset="utf-8")
DKMSBuildLog.txt Edit (973 bytes, text/plain; charset="utf-8")
Dependencies.txt Edit (1.3 KiB, text/plain; charset="utf-8")
DkmsStatus.txt Edit (647 bytes, text/plain; charset="utf-8")
GdmLog.txt Edit (10.4 KiB, text/plain; charset="utf-8")
GdmLog1.txt Edit (10.0 KiB, text/plain; charset="utf-8")
GdmLog2.txt Edit (9.5 KiB, text/plain; charset="utf-8")
Lspci.txt Edit (20.7 KiB, text/plain; charset="utf-8")
PciDisplay.txt Edit (1.1 KiB, text/plain; charset="utf-8")
ProcCpuinfo.txt Edit (1.7 KiB, text/plain; charset="utf-8")
ProcInterrupts.txt Edit (1.4 KiB, text/plain; charset="utf-8")
ProcModules.txt Edit (2.0 KiB, text/plain; charset="utf-8")
RelatedPackageVersions.txt Edit (231 bytes, text/plain; charset="utf-8")
UdevDb.txt Edit (88.6 KiB, text/plain; charset="utf-8")
UdevLog.txt Edit (193.5 KiB, text/plain; charset="utf-8")
XorgLog.txt Edit (13.3 KiB, text/plain; charset="utf-8")
XorgLogOld.txt Edit (13.0 KiB, text/plain; charset="utf-8")
Xrandr.txt Edit (9.1 KiB, text/plain; charset="utf-8")
glxinfo.txt Edit (26.5 KiB, text/plain; charset="utf-8")
make.log.txt Edit (973 bytes, text/plain; charset="utf-8")
setxkbmap.txt Edit (307 bytes, text/plain; charset="utf-8")
xdpyinfo.txt Edit (30.5 KiB, text/plain; charset="utf-8")
xkbcomp.txt Edit (51.8 KiB, text/plain; charset="utf-8")

Revision history for this message

Daniel van Vugt (vanvugt) wrote on 2011-06-02:

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.