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 #871050 reported by ken Johnson on 2011-10-09

This bug report is a duplicate of: Bug #552286: package nvidia-* failed to install/upgrade: nvidia-* kernel module failed to build (Failed CC sanity check). Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	nvidia-graphics-drivers-173 (Ubuntu)	New	Undecided	Unassigned

Bug Description

nvidia-graphics-drivers-173 failed to install during upgrade of amarok::error 10. I do not know why.

ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: nvidia-173 173.14.22-0ubuntu11
ProcVersionSignature: Ubuntu 2.6.32-34.77-generic-pae 2.6.32.44+drm33.19
Uname: Linux 2.6.32-34-generic-pae i686
Architecture: i386
Date: Sat Oct 8 20:02:25 2011
DkmsStatus:
nvidia-173, 173.14.22: added
virtualbox-ose-guest, 3.1.6, 2.6.32-34-generic-pae, i686: installed
nvidia-96, 96.43.17, 2.6.35-22-generic-pae, i686: installed
nvidia-96, 96.43.17, 2.6.32-34-generic-pae, i686: installed
ErrorMessage: nvidia-173 kernel module failed to build
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
MachineType: Dell Inc. Inspiron 1545
PackageVersion: 173.14.22-0ubuntu11
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-34-generic-pae root=UUID=4bab52d5-e036-438d-a4a9-6e66079ce990 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/07/2009
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A14
dmi.board.name: 0G848F
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvrA14:bd12/07/2009:svnDellInc.:pnInspiron1545:pvr:rvnDellInc.:rn0G848F:rvr:cvnDellInc.:ct8:cvr:
dmi.product.name: Inspiron 1545
dmi.sys.vendor: Dell Inc.
glxinfo: Error: [Errno 2] No such file or directory
system:
distro: Ubuntu
codename: lucid
architecture: i686
kernel: 2.6.32-34-generic-pae

Tags:

Revision history for this message

ken Johnson (arseenowe) wrote on 2011-10-09:

BootDmesg.txt Edit (47.2 KiB, text/plain; charset="utf-8")
CurrentDmesg.txt Edit (3.4 KiB, text/plain; charset="utf-8")
DKMSBuildLog.txt Edit (360 bytes, text/plain; charset="utf-8")
Dependencies.txt Edit (1.2 KiB, text/plain; charset="utf-8")
GdmLog.txt Edit (26.9 KiB, text/plain; charset="utf-8")
GdmLog1.txt Edit (28.8 KiB, text/plain; charset="utf-8")
GdmLog2.txt Edit (29.7 KiB, text/plain; charset="utf-8")
Lspci.txt Edit (24.0 KiB, text/plain; charset="utf-8")
Lsusb.txt Edit (756 bytes, text/plain; charset="utf-8")
PciDisplay.txt Edit (1.5 KiB, text/plain; charset="utf-8")
ProcCpuinfo.txt Edit (1.5 KiB, text/plain; charset="utf-8")
ProcInterrupts.txt Edit (1.4 KiB, text/plain; charset="utf-8")
ProcModules.txt Edit (3.1 KiB, text/plain; charset="utf-8")
RelatedPackageVersions.txt Edit (231 bytes, text/plain; charset="utf-8")
UdevDb.txt Edit (123.1 KiB, text/plain; charset="utf-8")
UdevLog.txt Edit (271.9 KiB, text/plain; charset="utf-8")
XorgLog.txt Edit (30.2 KiB, text/plain; charset="utf-8")
XorgLogOld.txt Edit (32.6 KiB, text/plain; charset="utf-8")
Xrandr.txt Edit (5.2 KiB, text/plain; charset="utf-8")
make.log.txt Edit (10.8 KiB, text/plain; charset="utf-8")
setxkbmap.txt Edit (233 bytes, text/plain; charset="utf-8")
xdpyinfo.txt Edit (19.2 KiB, text/plain; charset="utf-8")
xkbcomp.txt Edit (44.4 KiB, text/plain; charset="utf-8")

Revision history for this message

ken Johnson (arseenowe) wrote on 2011-10-09:

I have been having problems with my repositories---could not get into, them. Re-installed OP system (Ubuntu 10.04) and (separately) installed Amarok and its ancillary programs. nvidia failed to install ...

Revision history for this message

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

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 552286, 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.