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 #903533 reported by Norman Higginbotham on 2011-12-13

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 failed to load. Ubuntu running in low grade graphics mode

ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: nvidia-173 173.14.22-0ubuntu11
ProcVersionSignature: Ubuntu 3.0.0-14.23~lucid1-generic-pae 3.0.9
Uname: Linux 3.0.0-14-generic-pae i686
Architecture: i386
Date: Mon Dec 12 21:33:02 2011
DkmsStatus:
nvidia-current, 195.36.24: added
nvidia-173, 173.14.22: added
ErrorMessage: nvidia-173 kernel module failed to build
InstallationMedia: Ubuntu 10.04.2 LTS "Lucid Lynx" - Release i386 (20110211.1)
MachineType: System manufacturer System Product Name
PackageVersion: 173.14.22-0ubuntu11
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-14-generic-pae root=UUID=2935698e-c480-49a7-b1ee-ef26c4c690b4 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: 06/11/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0506
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: P5G41-M LE
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0506:bd06/11/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5G41-MLE:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
system:
distro: Ubuntu
codename: lucid
architecture: i686
kernel: 3.0.0-14-generic-pae

Tags:

Revision history for this message

Norman Higginbotham (nhigginbotham01) wrote on 2011-12-13:

BootDmesg.txt Edit (44.7 KiB, text/plain; charset="utf-8")
CurrentDmesg.txt Edit (4.0 KiB, text/plain; charset="utf-8")
DKMSBuildLog.txt Edit (976 bytes, text/plain; charset="utf-8")
Dependencies.txt Edit (1.3 KiB, text/plain; charset="utf-8")
GdmLog.txt Edit (434 bytes, text/plain; charset="utf-8")
GdmLog1.txt Edit (4.1 KiB, text/plain; charset="utf-8")
GdmLog2.txt Edit (11.0 KiB, text/plain; charset="utf-8")
Lspci.txt Edit (18.3 KiB, text/plain; charset="utf-8")
Lsusb.txt Edit (494 bytes, text/plain; charset="utf-8")
PciDisplay.txt Edit (2.0 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.6 KiB, text/plain; charset="utf-8")
RelatedPackageVersions.txt Edit (231 bytes, text/plain; charset="utf-8")
UdevDb.txt Edit (104.4 KiB, text/plain; charset="utf-8")
UdevLog.txt Edit (218.5 KiB, text/plain; charset="utf-8")
XorgLog.txt Edit (5.3 KiB, text/plain; charset="utf-8")
XorgLogOld.txt Edit (14.3 KiB, text/plain; charset="utf-8")
Xrandr.txt Edit (576 bytes, text/plain; charset="utf-8")
glxinfo.txt Edit (602 bytes, text/plain; charset="utf-8")
make.log.txt Edit (976 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 (44.4 KiB, text/plain; charset="utf-8")

Revision history for this message

Daniel van Vugt (vanvugt) wrote on 2011-12-14:

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.