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 #786008 reported by Alin-Florin Rus-Rebreanu on 2011-05-20

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

fails to build the module for the backport kernel 2.6.35-25-generic yet it builds fine on the .32 kernel

ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: nvidia-173 173.14.22-0ubuntu11
ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-21-generic i686
Architecture: i386
Date: Sat May 21 00:53:14 2011
DkmsStatus: nvidia-173, 173.14.22, 2.6.32-21-generic, i686: installed
ErrorMessage: nvidia-173 kernel module failed to build
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
Lsusb:
Bus 004 Device 002: ID 0e6a:6001 Megawin Technology Co., Ltd
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: MSI MS-6712
PackageVersion: 173.14.22-0ubuntu11
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-21-generic root=UUID=8ab166d4-27ac-4823-b3b4-2c2b59499d25 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/02/01
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: Version 07.00T
dmi.board.name: MS-6712
dmi.board.vendor: MSI
dmi.board.version: 1.0
dmi.chassis.asset.tag: 0123ABC
dmi.chassis.type: 3
dmi.chassis.vendor: Uknown Chassis Manufacture
dmi.chassis.version: Version 1.00
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrVersion07.00T:bd04/02/01:svnMSI:pnMS-6712:pvr1.0:rvnMSI:rnMS-6712:rvr1.0:cvnUknownChassisManufacture:ct3:cvrVersion1.00:
dmi.product.name: MS-6712
dmi.product.version: 1.0
dmi.sys.vendor: MSI
glxinfo: Error: [Errno 2] No such file or directory
system:
distro: Ubuntu
codename: lucid
architecture: i686
kernel: 2.6.32-21-generic

Tags:

Revision history for this message

Alin-Florin Rus-Rebreanu (netblock-deactivatedaccount) wrote on 2011-05-20:

BootDmesg.txt Edit (33.4 KiB, text/plain; charset="utf-8")
CurrentDmesg.txt Edit (4.1 KiB, text/plain; charset="utf-8")
DKMSBuildLog.txt Edit (974 bytes, text/plain; charset="utf-8")
Dependencies.txt Edit (1.3 KiB, text/plain; charset="utf-8")
Lspci.txt Edit (9.3 KiB, text/plain; charset="utf-8")
PciDisplay.txt Edit (1010 bytes, text/plain; charset="utf-8")
ProcCpuinfo.txt Edit (520 bytes, text/plain; charset="utf-8")
ProcInterrupts.txt Edit (1.1 KiB, text/plain; charset="utf-8")
ProcModules.txt Edit (3.0 KiB, text/plain; charset="utf-8")
RelatedPackageVersions.txt Edit (231 bytes, text/plain; charset="utf-8")
UdevDb.txt Edit (77.3 KiB, text/plain; charset="utf-8")
UdevLog.txt Edit (172.6 KiB, text/plain; charset="utf-8")
XorgLog.txt Edit (39.3 KiB, text/plain; charset="utf-8")
Xrandr.txt Edit (4.2 KiB, text/plain; charset="utf-8")
make.log.txt Edit (974 bytes, text/plain; charset="utf-8")
setxkbmap.txt Edit (233 bytes, text/plain; charset="utf-8")
xdpyinfo.txt Edit (17.3 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.