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 #653869 reported by oldwierdal on 2010-10-03

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

The nvidia-graphics-driver (version current) is installed and works perfectly. I don't use 3D graphics, so, frankly, I don't much care if this nvidia-173 driver works or not.
I did just compile and install a custom kernel, but this driver wasn't the one being used on the standard 2.6.32-25-generic kernel either, I don't think.

ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: nvidia-173 173.14.22-0ubuntu11
ProcVersionSignature: Ubuntu 2.6.35-9.14~lucid1-core2 2.6.35-rc5
Uname: Linux 2.6.35-9-core2 x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
Date: Sat Oct 2 17:01:05 2010
ErrorMessage: nvidia-173 kernel module failed to build
MachineType: MSI MS-7309
PackageVersion: 173.14.22-0ubuntu11
ProcCmdLine: root=/dev/sda2 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: 04/09/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: V9.5
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: MS-7309
dmi.board.vendor: MSI
dmi.board.version: 1.0
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV9.5:bd04/09/2009:svnMSI:pnMS-7309:pvr1.0:rvnMSI:rnMS-7309:rvr1.0:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: MS-7309
dmi.product.version: 1.0
dmi.sys.vendor: MSI
system:
distro: Ubuntu
codename: lucid
architecture: x86_64
kernel: 2.6.35-9-core2

Tags:

Revision history for this message

oldwierdal (owaugly) wrote on 2010-10-03:

BootDmesg.txt Edit (49.6 KiB, text/plain; charset="utf-8")
CurrentDmesg.txt Edit (4.3 KiB, text/plain; charset="utf-8")
DKMSBuildLog.txt Edit (972 bytes, text/plain; charset="utf-8")
Dependencies.txt Edit (1.3 KiB, text/plain; charset="utf-8")
DkmsStatus.txt Edit (2.7 KiB, text/plain; charset="utf-8")
GdmLog.txt Edit (10.0 KiB, text/plain; charset="utf-8")
GdmLog1.txt Edit (22.9 KiB, text/plain; charset="utf-8")
GdmLog2.txt Edit (32.7 KiB, text/plain; charset="utf-8")
Lspci.txt Edit (22.1 KiB, text/plain; charset="utf-8")
Lsusb.txt Edit (576 bytes, text/plain; charset="utf-8")
PciDisplay.txt Edit (3.0 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 (3.6 KiB, text/plain; charset="utf-8")
RelatedPackageVersions.txt Edit (231 bytes, text/plain; charset="utf-8")
UdevDb.txt Edit (122.8 KiB, text/plain; charset="utf-8")
UdevLog.txt Edit (262.8 KiB, text/plain; charset="utf-8")
XorgConf.txt Edit (1.5 KiB, text/plain; charset="utf-8")
XorgLog.txt Edit (13.0 KiB, text/plain; charset="utf-8")
XorgLogOld.txt Edit (26.1 KiB, text/plain; charset="utf-8")
Xrandr.txt Edit (5.5 KiB, text/plain; charset="utf-8")
glxinfo.txt Edit (24.2 KiB, text/plain; charset="utf-8")
make.log.txt Edit (21.2 KiB, text/plain; charset="utf-8")
setxkbmap.txt Edit (233 bytes, text/plain; charset="utf-8")
xdpyinfo.txt Edit (22.0 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-05-27:

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.