Ubuntu
nvidia-graphics-drivers-96 package

NVIDIA 96 driver doesn't work on Ubuntu 10.04 running over Linux 2.6.32-38-generic image

Bug #930685 reported by Caleb Howland (Menzador) on 2012-02-11

This bug report is a duplicate of: Bug #552286: package nvidia-* failed to install/upgrade: nvidia-* kernel module failed to build (Failed CC sanity check). Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	nvidia-graphics-drivers-96 (Ubuntu)	New	Undecided	Unassigned

Bug Description

For some reason when I upgrade the Linux image from 2.6.32-37 to 2.6.32-38, the NVIDIA driver doesn't function AT ALL. Please fix whatever it is that's causing this.

ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: nvidia-96 96.43.17-0ubuntu1.1
ProcVersionSignature: Ubuntu 2.6.32-38.83-generic 2.6.32.52+drm33.21
Uname: Linux 2.6.32-38-generic i686
Architecture: i386
Date: Sat Feb 11 10:48:49 2012
DkmsStatus: nvidia-96, 96.43.17: added
ErrorMessage: nvidia-96 kernel module failed to build
InstallationMedia: Ubuntu 10.04.3 LTS "Lucid Lynx" - Release i386 (20110720.1)
Lsusb:
Bus 002 Device 003: ID 152e:2507 LG (HLDS)
Bus 002 Device 002: ID 8086:1122 Intel Corp.
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 002: ID 0763:1010 Midiman MidiSport 1x1
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: Gateway E-3600
PackageVersion: 96.43.17-0ubuntu1.1
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-38-generic root=/dev/sda1 loop=/hostname/disks/root.disk 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: 12/05/2001
dmi.bios.vendor: Intel Corp.
dmi.bios.version: PT84510A.15A.0004.P02.0112051220
dmi.board.name: D845PT
dmi.board.vendor: Intel Corporation
dmi.board.version: AAA65253-303
dmi.chassis.type: 3
dmi.chassis.vendor: Gateway
dmi.chassis.version: HV02A04
dmi.modalias: dmi:bvnIntelCorp.:bvrPT84510A.15A.0004.P02.0112051220:bd12/05/2001:svnGateway:pnE-3600:pvr4000777:rvnIntelCorporation:rnD845PT:rvrAAA65253-303:cvnGateway:ct3:cvrHV02A04:
dmi.product.name: E-3600
dmi.product.version: 4000777
dmi.sys.vendor: Gateway
glxinfo: Error: [Errno 2] No such file or directory
system:
distro: Ubuntu
codename: lucid
architecture: i686
kernel: 2.6.32-38-generic

Tags:

Revision history for this message

Caleb Howland (Menzador) (menzador) wrote on 2012-02-11:

BootDmesg.txt Edit (30.8 KiB, text/plain; charset="utf-8")
CurrentDmesg.txt Edit (2.9 KiB, text/plain; charset="utf-8")
DKMSBuildLog.txt Edit (354 bytes, text/plain; charset="utf-8")
Dependencies.txt Edit (1.3 KiB, text/plain; charset="utf-8")
GdmLog.txt Edit (434 bytes, text/plain; charset="utf-8")
GdmLog1.txt Edit (4.0 KiB, text/plain; charset="utf-8")
GdmLog2.txt Edit (4.0 KiB, text/plain; charset="utf-8")
Lspci.txt Edit (7.6 KiB, text/plain; charset="utf-8")
PciDisplay.txt Edit (1.0 KiB, text/plain; charset="utf-8")
ProcCpuinfo.txt Edit (538 bytes, text/plain; charset="utf-8")
ProcInterrupts.txt Edit (1.2 KiB, text/plain; charset="utf-8")
ProcModules.txt Edit (2.1 KiB, text/plain; charset="utf-8")
RelatedPackageVersions.txt Edit (233 bytes, text/plain; charset="utf-8")
UdevDb.txt Edit (79.4 KiB, text/plain; charset="utf-8")
UdevLog.txt Edit (171.8 KiB, text/plain; charset="utf-8")
XorgLog.txt Edit (5.5 KiB, text/plain; charset="utf-8")
XorgLogOld.txt Edit (5.5 KiB, text/plain; charset="utf-8")
Xrandr.txt Edit (2.3 KiB, text/plain; charset="utf-8")
make.log.txt Edit (354 bytes, text/plain; charset="utf-8")
setxkbmap.txt Edit (233 bytes, text/plain; charset="utf-8")
xdpyinfo.txt Edit (2.7 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 2012-02-12:

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 552286, 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.