Ubuntu
nvidia-graphics-drivers-96 package

package nvidia-96 96.43.17-0ubuntu1.1 failed to install/upgrade: nvidia-96 kernel module failed to build

Bug #990333 reported by Staff on 2012-04-28

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-96 (Ubuntu)	New	Undecided	Unassigned

Bug Description

10.04 LTS -> update kernel to 3.3

ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: nvidia-96 96.43.17-0ubuntu1.1
ProcVersionSignature: Ubuntu 2.6.32-41.88-generic 2.6.32.59+drm33.24
Uname: Linux 2.6.32-41-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
Date: Sat Apr 28 10:21:24 2012
DkmsStatus:
nvidia-current, 195.36.24, 2.6.32-41-generic, x86_64: installed
nvidia-173, 173.14.22, 2.6.32-41-generic, x86_64: installed
nvidia-96, 96.43.17, 2.6.32-41-generic, x86_64: installed
ErrorMessage: nvidia-96 kernel module failed to build
InstallationMedia:

MachineType: ASUSTeK Computer Inc. M50Vc
PackageVersion: 96.43.17-0ubuntu1.1
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-41-generic root=UUID=4e9fb43c-d291-4ddd-b22a-2b28ef04042f ro quiet splash
SourcePackage: nvidia-graphics-drivers-96
Title: package nvidia-96 96.43.17-0ubuntu1.1 failed to install/upgrade: nvidia-96 kernel module failed to build
dmi.bios.date: 07/24/2008
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 206
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: M50Vc
dmi.board.vendor: ASUSTeK Computer Inc.
dmi.board.version: 1.0
dmi.chassis.asset.tag: ATN12345678901234567
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK Computer Inc.
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr206:bd07/24/2008:svnASUSTeKComputerInc.:pnM50Vc:pvr1.0:rvnASUSTeKComputerInc.:rnM50Vc:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
dmi.product.name: M50Vc
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK Computer Inc.
glxinfo: Error: [Errno 2] Toks failas ar aplankas neegzistuoja
system:
distro: Ubuntu
codename: lucid
architecture: x86_64
kernel: 2.6.32-41-generic

Tags:

Revision history for this message

Staff (xfaily) wrote on 2012-04-28:

BootDmesg.txt Edit (54.0 KiB, text/plain; charset="utf-8")
CurrentDmesg.txt Edit (11.7 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")
GdmLog.txt Edit (12.6 KiB, text/plain; charset="utf-8")
GdmLog1.txt Edit (13.2 KiB, text/plain; charset="utf-8")
GdmLog2.txt Edit (12.9 KiB, text/plain; charset="utf-8")
Lspci.txt Edit (32.9 KiB, text/plain; charset="utf-8")
Lsusb.txt Edit (742 bytes, text/plain; charset="utf-8")
PciDisplay.txt Edit (1.9 KiB, text/plain; charset="utf-8")
ProcCpuinfo.txt Edit (1.4 KiB, text/plain; charset="utf-8")
ProcInterrupts.txt Edit (1.6 KiB, text/plain; charset="utf-8")
ProcModules.txt Edit (4.6 KiB, text/plain; charset="utf-8")
RelatedPackageVersions.txt Edit (233 bytes, text/plain; charset="utf-8")
UdevDb.txt Edit (133.4 KiB, text/plain; charset="utf-8")
UdevLog.txt Edit (265.2 KiB, text/plain; charset="utf-8")
XorgConf.txt Edit (1.3 KiB, text/plain; charset="utf-8")
XorgLog.txt Edit (15.9 KiB, text/plain; charset="utf-8")
XorgLogOld.txt Edit (16.7 KiB, text/plain; charset="utf-8")
Xrandr.txt Edit (12.3 KiB, text/plain; charset="utf-8")
make.log.txt Edit (977 bytes, text/plain; charset="utf-8")
setxkbmap.txt Edit (267 bytes, text/plain; charset="utf-8")
xdpyinfo.txt Edit (22.0 KiB, text/plain; charset="utf-8")
xkbcomp.txt Edit (56.3 KiB, text/plain; charset="utf-8")

Revision history for this message

Daniel van Vugt (vanvugt) wrote on 2012-04-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.