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 #797436 reported by gabriele bianchi on 2011-06-14

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

ubuntu 10.04. the problem appeared while system update, updating linux-headers-generic-pae-lts-backport-maverick (2.6.35.28.37) to 2.6.35.30.38 and
linux-image-generic-pae-lts-backport-maverick (2.6.35.28.37) to 2.6.35.30.38

ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: nvidia-173 173.14.22-0ubuntu11
ProcVersionSignature: Ubuntu 2.6.35-28.50~lucid1-generic-pae 2.6.35.11
Uname: Linux 2.6.35-28-generic-pae i686
NonfreeKernelModules: nvidia
Architecture: i386
Date: Tue Jun 14 23:49:23 2011
ErrorMessage: nvidia-173 kernel module failed to build
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Release Candidate i386 (20100419.1)
MachineType: Acer Aspire 5930
PackageVersion: 173.14.22-0ubuntu11
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-28-generic-pae root=UUID=5e489735-7d4f-4d49-a4cf-4d0185068c80 ro quiet
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: 08/22/2008
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: V1.21
dmi.board.name: Eiger
dmi.board.vendor: Acer
dmi.board.version: Rev
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvrV1.21:bd08/22/2008:svnAcer:pnAspire5930:pvr0100:rvnAcer:rnEiger:rvrRev:cvnAcer:ct10:cvrN/A:
dmi.product.name: Aspire 5930
dmi.product.version: 0100
dmi.sys.vendor: Acer
glxinfo: Error: [Errno 2] File o directory non esistente
system:
distro: Ubuntu
codename: lucid
architecture: i686
kernel: 2.6.35-28-generic-pae

Tags:

Revision history for this message

gabriele bianchi (gabriele-bianchi) wrote on 2011-06-14:

BootDmesg.txt Edit (57.5 KiB, text/plain; charset="utf-8")
CurrentDmesg.txt Edit (3.8 KiB, text/plain; charset="utf-8")
DKMSBuildLog.txt Edit (981 bytes, text/plain; charset="utf-8")
Dependencies.txt Edit (1.2 KiB, text/plain; charset="utf-8")
DkmsStatus.txt Edit (1.3 KiB, text/plain; charset="utf-8")
GdmLog.txt Edit (11.3 KiB, text/plain; charset="utf-8")
GdmLog1.txt Edit (12.7 KiB, text/plain; charset="utf-8")
GdmLog2.txt Edit (12.7 KiB, text/plain; charset="utf-8")
Lspci.txt Edit (29.5 KiB, text/plain; charset="utf-8")
Lsusb.txt Edit (692 bytes, text/plain; charset="utf-8")
PciDisplay.txt Edit (1.9 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.9 KiB, text/plain; charset="utf-8")
RelatedPackageVersions.txt Edit (231 bytes, text/plain; charset="utf-8")
UdevDb.txt Edit (122.0 KiB, text/plain; charset="utf-8")
UdevLog.txt Edit (252.7 KiB, text/plain; charset="utf-8")
XorgConf.txt Edit (213 bytes, text/plain; charset="utf-8")
XorgLog.txt Edit (14.4 KiB, text/plain; charset="utf-8")
XorgLogOld.txt Edit (16.1 KiB, text/plain; charset="utf-8")
Xrandr.txt Edit (9.5 KiB, text/plain; charset="utf-8")
make.log.txt Edit (981 bytes, text/plain; charset="utf-8")
setxkbmap.txt Edit (313 bytes, text/plain; charset="utf-8")
xdpyinfo.txt Edit (22.0 KiB, text/plain; charset="utf-8")
xkbcomp.txt Edit (57.2 KiB, text/plain; charset="utf-8")

Revision history for this message

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

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.