Ubuntu
nvidia-graphics-drivers-173 package

package nvidia-173 (not installed) failed to install/upgrade: nvidia-173 kernel module failed to build

Bug #696746 reported by Aleksandr on 2011-01-03

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

in synaptic delete all with nvidia, but nvyu Nothing helped.

ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: nvidia-173 (not installed)
ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4
Uname: Linux 2.6.35-22-generic i686
NonfreeKernelModules: ne2k_pci 8390 floppy usbhid hid
Architecture: i386
CurrentDmesg:
[ 29.728049] eth0: no IPv6 routers present
[ 625.352645] show_signal_msg: 9 callbacks suppressed
[ 625.352655] glxinfo[1671]: segfault at 0 ip 0804ad91 sp bfdbe990 error 4 in glxinfo[8048000+5000]
[ 5889.880823] glxinfo[1914]: segfault at 0 ip 0804ad91 sp bf8ac360 error 4 in glxinfo[8048000+5000]
[ 5889.945950] glxinfo[1915]: segfault at 0 ip 0804ad91 sp bfdfdf60 error 4 in glxinfo[8048000+5000]
Date: Mon Jan 3 12:24:30 2011
DkmsStatus:

ErrorMessage: nvidia-173 kernel module failed to build
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
PackageVersion: 173.14.22-0ubuntu11
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-22-generic root=UUID=50b62fb1-39ab-4284-ad2d-1a1c067c4e82 ro quiet splash
ProcModules:
ne2k_pci 6349 0 - Live 0xf8158000
8390 8429 1 ne2k_pci, Live 0xf814a000
floppy 54311 0 - Live 0xf812e000
usbhid 36882 0 - Live 0xf8093000
hid 67742 1 usbhid, Live 0xf8057000
SourcePackage: nvidia-graphics-drivers-173
Title: package nvidia-173 (not installed) failed to install/upgrade: nvidia-173 kernel module failed to build
dmi.bios.date: 07/31/2007
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P1.40
dmi.board.name: P4i65G
dmi.board.version: 1.00
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.40:bd07/31/2007:svn:pnP4i65G:pvr1.00:rvn:rnP4i65G:rvr1.00:
dmi.product.name: P4i65G
dmi.product.version: 1.00
system:
distro: Ubuntu
codename: lucid
architecture: i686
kernel: 2.6.35-22-generic

Tags:

Revision history for this message

Aleksandr (sca-inbox) wrote on 2011-01-03:

BootDmesg.txt Edit (35.2 KiB, text/plain; charset="utf-8")
DKMSBuildLog.txt Edit (973 bytes, text/plain; charset="utf-8")
GdmLog.txt Edit (39.2 KiB, text/plain; charset="utf-8")
GdmLog1.txt Edit (39.5 KiB, text/plain; charset="utf-8")
GdmLog2.txt Edit (39.6 KiB, text/plain; charset="utf-8")
Lspci.txt Edit (8.7 KiB, text/plain; charset="utf-8")
Lsusb.txt Edit (425 bytes, text/plain; charset="utf-8")
PciDisplay.txt Edit (937 bytes, text/plain; charset="utf-8")
ProcCpuinfo.txt Edit (549 bytes, text/plain; charset="utf-8")
ProcInterrupts.txt Edit (1.1 KiB, text/plain; charset="utf-8")
RelatedPackageVersions.txt Edit (231 bytes, text/plain; charset="utf-8")
UdevDb.txt Edit (88.8 KiB, text/plain; charset="utf-8")
UdevLog.txt Edit (167.0 KiB, text/plain; charset="utf-8")
XorgConf.txt Edit (1.2 KiB, text/plain; charset="utf-8")
XorgLog.txt Edit (42.9 KiB, text/plain; charset="utf-8")
XorgLogOld.txt Edit (43.3 KiB, text/plain; charset="utf-8")
Xrandr.txt Edit (12.9 KiB, text/plain; charset="utf-8")
glxinfo.txt Edit (669 bytes, text/plain; charset="utf-8")
setxkbmap.txt Edit (299 bytes, text/plain; charset="utf-8")
xdpyinfo.txt Edit (2.7 KiB, text/plain; charset="utf-8")
xkbcomp.txt Edit (57.5 KiB, text/plain; charset="utf-8")

Revision history for this message

Daniel van Vugt (vanvugt) wrote on 2011-06-01:

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.