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 #941191 reported by Andrea on 2012-02-26

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

After trying the Kenel 3.0.0-16

ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: nvidia-173 173.14.22-0ubuntu11
ProcVersionSignature: Ubuntu 3.0.0-16.29~lucid1-generic 3.0.20
Uname: Linux 3.0.0-16-generic x86_64
Architecture: amd64
Date: Sat Feb 25 19:36:15 2012
ErrorMessage: nvidia-173 kernel module failed to build
InstallationMedia: Ubuntu 10.04.3 LTS "Lucid Lynx" - Release amd64 (20110720.1)
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
PackageVersion: 173.14.22-0ubuntu11
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-16-generic root=UUID=7c84ee36-889c-40a0-866c-f9ed936a4fd1 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: 09/02/2005
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1012.001
dmi.board.name: K8V
dmi.board.vendor: ASUSTeK Computer Inc.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1012.001:bd09/02/2005:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASUSTeKComputerInc.:rnK8V:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.
glxinfo: Error: [Errno 2] File o directory non esistente
system:
distro: Ubuntu
codename: lucid
architecture: x86_64
kernel: 3.0.0-16-generic

Tags:

Revision history for this message

Andrea (andreik2900) wrote on 2012-02-26:

BootDmesg.txt Edit (44.0 KiB, text/plain; charset="utf-8")
CurrentDmesg.txt Edit (9.5 KiB, text/plain; charset="utf-8")
DKMSBuildLog.txt Edit (977 bytes, text/plain; charset="utf-8")
Dependencies.txt Edit (1.3 KiB, text/plain; charset="utf-8")
DkmsStatus.txt Edit (341 bytes, text/plain; charset="utf-8")
GdmLog.txt Edit (434 bytes, text/plain; charset="utf-8")
GdmLog1.txt Edit (4.7 KiB, text/plain; charset="utf-8")
GdmLog2.txt Edit (434 bytes, text/plain; charset="utf-8")
Lspci.txt Edit (14.9 KiB, text/plain; charset="utf-8")
Lsusb.txt Edit (596 bytes, text/plain; charset="utf-8")
PciDisplay.txt Edit (998 bytes, text/plain; charset="utf-8")
ProcCpuinfo.txt Edit (549 bytes, text/plain; charset="utf-8")
ProcInterrupts.txt Edit (1.3 KiB, text/plain; charset="utf-8")
ProcModules.txt Edit (3.3 KiB, text/plain; charset="utf-8")
RelatedPackageVersions.txt Edit (233 bytes, text/plain; charset="utf-8")
UdevDb.txt Edit (104.1 KiB, text/plain; charset="utf-8")
UdevLog.txt Edit (243.1 KiB, text/plain; charset="utf-8")
XorgConf.txt Edit (213 bytes, text/plain; charset="utf-8")
XorgLog.txt Edit (6.4 KiB, text/plain; charset="utf-8")
XorgLogOld.txt Edit (6.4 KiB, text/plain; charset="utf-8")
Xrandr.txt Edit (575 bytes, text/plain; charset="utf-8")
make.log.txt Edit (977 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 2012-02-26:

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.