Ubuntu
nvidia-graphics-drivers-173 package

package nvidia-173 173.14.22-0ubuntu11 failed to install/upgrade: nvidia-173 kernel module failed to build after linux-header update

Bug #620835 reported by Guru R on 2010-08-20

This bug report is a duplicate of: Bug #581045: package nvidia-* failed to install/upgrade: nvidia-* kernel module failed to build (FATAL: modpost: GPL-incompatible module nvidia.ko uses GPL-only symbol 'xen_features') [Lucid on kernel 2.6.32-22]. 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 seems to crash everytime i update the linux-headers. It happened the last time i update it & this time too.

I am using Ubuntu release 10.04 LTS - the Lucid Lynx Current driver installed is 195.36.24-0ubuntu1~10.04.

ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: nvidia-173 173.14.22-0ubuntu11
ProcVersionSignature: Ubuntu 2.6.32-24.39-generic 2.6.32.15+drm33.5
Uname: Linux 2.6.32-24-generic i686
NonfreeKernelModules: nvidia
Architecture: i386
Date: Fri Aug 20 10:28:40 2010
ErrorMessage: nvidia-173 kernel module failed to build
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100427.1)
MachineType: Dell Inc. Latitude E6500
PackageVersion: 173.14.22-0ubuntu11
PccardctlIdent:
Socket 0:
no product info available
PccardctlStatus:
Socket 0:
no card
ProcCmdLine: BOOT_IMAGE=/vmlinuz-2.6.32-24-generic root=/dev/mapper/hostname-root 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: 05/06/2010
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A22
dmi.board.name: 0X564R
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvrA22:bd05/06/2010:svnDellInc.:pnLatitudeE6500:pvr:rvnDellInc.:rn0X564R:rvr:cvnDellInc.:ct8:cvr:
dmi.product.name: Latitude E6500
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-24-generic

Tags:

Revision history for this message

Guru R (rguru76) wrote on 2010-08-20:

BootDmesg.txt Edit (56.7 KiB, text/plain; charset="utf-8")
CurrentDmesg.txt Edit (4.2 KiB, text/plain; charset="utf-8")
DKMSBuildLog.txt Edit (84.6 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (1.3 KiB, text/plain; charset="utf-8")
DkmsStatus.txt Edit (423 bytes, text/plain; charset="utf-8")
GdmLog.txt Edit (14.1 KiB, text/plain; charset="utf-8")
GdmLog1.txt Edit (20.2 KiB, text/plain; charset="utf-8")
GdmLog2.txt Edit (13.5 KiB, text/plain; charset="utf-8")
Lspci.txt Edit (28.5 KiB, text/plain; charset="utf-8")
Lsusb.txt Edit (1.0 KiB, text/plain; charset="utf-8")
PciDisplay.txt Edit (1.9 KiB, text/plain; charset="utf-8")
ProcCpuinfo.txt Edit (1.6 KiB, text/plain; charset="utf-8")
ProcInterrupts.txt Edit (1.6 KiB, text/plain; charset="utf-8")
ProcModules.txt Edit (4.9 KiB, text/plain; charset="utf-8")
RelatedPackageVersions.txt Edit (231 bytes, text/plain; charset="utf-8")
UdevDb.txt Edit (146.5 KiB, text/plain; charset="utf-8")
UdevLog.txt Edit (295.0 KiB, text/plain; charset="utf-8")
XorgConf.txt Edit (213 bytes, text/plain; charset="utf-8")
XorgLog.txt Edit (17.6 KiB, text/plain; charset="utf-8")
XorgLogOld.txt Edit (24.2 KiB, text/plain; charset="utf-8")
Xrandr.txt Edit (18.9 KiB, text/plain; charset="utf-8")
make.log.txt Edit (97.2 KiB, text/plain; charset="utf-8")
setxkbmap.txt Edit (253 bytes, text/plain; charset="utf-8")
xdpyinfo.txt Edit (22.0 KiB, text/plain; charset="utf-8")
xkbcomp.txt Edit (44.3 KiB, text/plain; charset="utf-8")

Revision history for this message

Daniel van Vugt (vanvugt) wrote on 2011-05-27:

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 #581045, 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.