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 #905685 reported by buvi85@free.fr on 2011-12-17

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

rien

ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: nvidia-173 173.14.22-0ubuntu11
ProcVersionSignature: Ubuntu 2.6.38-13.53~lucid1-generic 2.6.38.8
Uname: Linux 2.6.38-13-generic i686
NonfreeKernelModules: nvidia
Architecture: i386
Date: Tue Dec 13 23:58:30 2011
ErrorMessage: nvidia-173 kernel module failed to build
GdmLog1: Error: command ['cat', '/var/log/gdm/:0.log.1'] failed with exit code 1: cat: /var/log/gdm/:0.log.1: No such file or directory
GdmLog2: Error: command ['cat', '/var/log/gdm/:0.log.2'] failed with exit code 1: cat: /var/log/gdm/:0.log.2: No such file or directory
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-2.6.38-13-generic root=UUID=8e5316b2-f042-40cb-940c-7df709b7c07c 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/30/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P2.30
dmi.board.name: K10N78FullHD-hSLI..
dmi.board.vendor: ASRock
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.:bvrP2.30:bd04/30/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnK10N78FullHD-hSLI..:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
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.
system:
distro: Ubuntu
codename: lucid
architecture: i686
kernel: 2.6.38-13-generic

Tags:

Revision history for this message

buvi85@free.fr (buvi85) wrote on 2011-12-17:

BootDmesg.txt Edit (50.7 KiB, text/plain; charset="utf-8")
CurrentDmesg.txt Edit (616 bytes, text/plain; charset="utf-8")
DKMSBuildLog.txt Edit (990 bytes, text/plain; charset="utf-8")
Dependencies.txt Edit (1.3 KiB, text/plain; charset="utf-8")
DkmsStatus.txt Edit (1.3 KiB, text/plain; charset="utf-8")
GdmLog.txt Edit (9.4 KiB, text/plain; charset="utf-8")
Lspci.txt Edit (24.2 KiB, text/plain; charset="utf-8")
Lsusb.txt Edit (371 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.5 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 (116.6 KiB, text/plain; charset="utf-8")
UdevLog.txt Edit (245.2 KiB, text/plain; charset="utf-8")
XorgConf.txt Edit (213 bytes, text/plain; charset="utf-8")
XorgLog.txt Edit (12.4 KiB, text/plain; charset="utf-8")
Xrandr.txt Edit (6.8 KiB, text/plain; charset="utf-8")
glxinfo.txt Edit (24.6 KiB, text/plain; charset="utf-8")
make.log.txt Edit (990 bytes, text/plain; charset="utf-8")
setxkbmap.txt Edit (238 bytes, text/plain; charset="utf-8")
xdpyinfo.txt Edit (22.0 KiB, text/plain; charset="utf-8")
xkbcomp.txt Edit (48.6 KiB, text/plain; charset="utf-8")

Revision history for this message

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

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.