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 #783026 reported by Billy_bonk621 on 2011-05-15

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

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

Bug Description

I don't know, wont' auto update I assume. I've installed the 260 version of the graphics driver, this is for 11.04.

ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: nvidia-173 173.14.22-0ubuntu11
ProcVersionSignature: Ubuntu 2.6.32-31.61-generic-pae 2.6.32.32+drm33.14
Uname: Linux 2.6.32-31-generic-pae i686
NonfreeKernelModules: nvidia
Architecture: i386
Date: Sun May 15 23:50:14 2011
ErrorMessage: nvidia-173 kernel module failed to build
GdmLog1: X: /tmp/.X11-unix has suspicious mode (not 1777) or is not a directory, aborting.
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
MachineType: Ipex I.T.G. La Crosse series
PackageVersion: 173.14.22-0ubuntu11
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-31-generic-pae root=UUID=42c34099-dced-4aef-a0ff-5f505e709802 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: 02/10/2004
dmi.bios.vendor: Intel Corp.
dmi.bios.version: BF86510A.86A.0056.P14.0402101402
dmi.board.name: D865GLC
dmi.board.vendor: Intel Corporation
dmi.board.version: AAC27499-407
dmi.chassis.type: 2
dmi.chassis.vendor: Ipex I.T.G.
dmi.modalias: dmi:bvnIntelCorp.:bvrBF86510A.86A.0056.P14.0402101402:bd02/10/2004:svnIpexI.T.G.:pnLaCrosseseries:pvrP14:rvnIntelCorporation:rnD865GLC:rvrAAC27499-407:cvnIpexI.T.G.:ct2:cvr:
dmi.product.name: La Crosse series
dmi.product.version: P14
dmi.sys.vendor: Ipex I.T.G.
system:
distro: Ubuntu
codename: lucid
architecture: i686
kernel: 2.6.32-31-generic-pae

Tags:

Revision history for this message

Billy_bonk621 (billy-bonk621) wrote on 2011-05-15:

BootDmesg.txt Edit (37.9 KiB, text/plain; charset="utf-8")
CurrentDmesg.txt Edit (2.1 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 (340 bytes, text/plain; charset="utf-8")
GdmLog.txt Edit (8.4 KiB, text/plain; charset="utf-8")
GdmLog2.txt Edit (8.6 KiB, text/plain; charset="utf-8")
Lspci.txt Edit (10.0 KiB, text/plain; charset="utf-8")
Lsusb.txt Edit (630 bytes, text/plain; charset="utf-8")
PciDisplay.txt Edit (1.1 KiB, text/plain; charset="utf-8")
ProcCpuinfo.txt Edit (1.2 KiB, text/plain; charset="utf-8")
ProcInterrupts.txt Edit (1.5 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 (101.4 KiB, text/plain; charset="utf-8")
UdevLog.txt Edit (223.9 KiB, text/plain; charset="utf-8")
XorgConf.txt Edit (1.7 KiB, text/plain; charset="utf-8")
XorgLog.txt Edit (11.3 KiB, text/plain; charset="utf-8")
XorgLogOld.txt Edit (11.6 KiB, text/plain; charset="utf-8")
Xrandr.txt Edit (3.8 KiB, text/plain; charset="utf-8")
glxinfo.txt Edit (23.4 KiB, 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 (30.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-05-30:

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.