Ubuntu
nvidia-graphics-drivers-173-updates package

nvidia-173-updates 173.14.30-0ubuntu5: nvidia-173-updates kernel module failed to build

Bug #909110 reported by john morgan on 2011-12-27

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

Bug Description

invida up dat di not install

ProblemType: Package
DistroRelease: Ubuntu 12.04
Package: nvidia-173-updates 173.14.30-0ubuntu5
ProcVersionSignature: Ubuntu 3.2.0-6.12-generic 3.2.0-rc6
Uname: Linux 3.2.0-6-generic i686
NonfreeKernelModules: nvidia
ApportVersion: 1.90-0ubuntu1
Architecture: i386
DKMSKernelVersion: 3.2.0-7-generic
Date: Wed Dec 28 07:48:14 2011
PackageVersion: 173.14.30-0ubuntu5
SourcePackage: nvidia-graphics-drivers-173-updates
Title: nvidia-173-updates 173.14.30-0ubuntu5: nvidia-173-updates kernel module failed to build
UpgradeStatus: Upgraded to precise on 2011-12-21 (6 days ago)

Tags:

Revision history for this message

john morgan (johnemorgan488) wrote on 2011-12-27:

DKMSBuildLog.txt Edit (980 bytes, text/plain; charset="utf-8")
Dependencies.txt Edit (2.8 KiB, text/plain; charset="utf-8")
DuplicateSignature.txt Edit (951 bytes, text/plain; charset="utf-8")

Revision history for this message

john morgan (johnemorgan488) wrote on 2011-12-27:

download the new update for sysytem

Apport retracing service (apport) on 2011-12-27

tags:

removed: need-duplicate-check

Revision history for this message

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

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.