Ubuntu
nvidia-graphics-drivers package

package nvidia-current 195.36.24-0ubuntu1~10.04 failed to install/upgrade: nvidia-current kernel module failed to build

Bug #634631 reported by Chadwick on 2010-09-10

This bug report is a duplicate of: Bug #590931: package nvidia-current 195.36.15-0ubuntu3 failed to install/upgrade: nvidia-current kernel module failed to build (nv-linux.h:219: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘nv_spinlock_t’). Edit Remove

This bug affects 1 person

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

Bug Description

looks like it looked for a gdm log that wasnt there. gl hf

ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: nvidia-current 195.36.24-0ubuntu1~10.04
ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-21-generic x86_64
Architecture: amd64
Date: Thu Sep 9 18:30:17 2010
DkmsStatus: nvidia-current, 195.36.24, 2.6.32-21-generic, x86_64: installed
ErrorMessage: nvidia-current kernel module failed to build
GdmLog1: Error: command ['cat', '/var/log/gdm/:0.log.1'] failed with exit code 1: cat: /var/log/gdm/:0.log.1: No such file or directory
GdmLog2: Error: command ['cat', '/var/log/gdm/:0.log.2'] failed with exit code 1: cat: /var/log/gdm/:0.log.2: No such file or directory
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
PackageVersion: 195.36.24-0ubuntu1~10.04
ProcCmdLine: BOOT_IMAGE=/vmlinuz-2.6.32-21-generic root=UUID=2c629d86-07f2-44b9-a586-c407edf21c6b ro quiet splash
SourcePackage: nvidia-graphics-drivers
Title: package nvidia-current 195.36.24-0ubuntu1~10.04 failed to install/upgrade: nvidia-current kernel module failed to build
dmi.bios.date: 11/13/2009
dmi.bios.vendor: Intel Corp.
dmi.bios.version: NBG4310H.86A.0099.2009.1113.1151
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: DG43NB
dmi.board.vendor: Intel Corporation
dmi.board.version: AAE34877-402
dmi.chassis.type: 3
dmi.modalias: dmi:bvnIntelCorp.:bvrNBG4310H.86A.0099.2009.1113.1151:bd11/13/2009:svn:pn:pvr:rvnIntelCorporation:rnDG43NB:rvrAAE34877-402:cvn:ct3:cvr:
glxinfo: Error: [Errno 2] No such file or directory
system:
distro: Ubuntu
codename: lucid
architecture: x86_64
kernel: 2.6.32-21-generic

Tags:

Revision history for this message

Chadwick (lavacano) wrote on 2010-09-10:

BootDmesg.txt Edit (48.7 KiB, text/plain; charset="utf-8")
CurrentDmesg.txt Edit (13.4 KiB, text/plain; charset="utf-8")
DKMSBuildLog.txt Edit (20.5 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (1.3 KiB, text/plain; charset="utf-8")
GdmLog.txt Edit (35.8 KiB, text/plain; charset="utf-8")
Lspci.txt Edit (21.3 KiB, text/plain; charset="utf-8")
Lsusb.txt Edit (736 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.5 KiB, text/plain; charset="utf-8")
ProcModules.txt Edit (5.5 KiB, text/plain; charset="utf-8")
RelatedPackageVersions.txt Edit (231 bytes, text/plain; charset="utf-8")
UdevDb.txt Edit (110.5 KiB, text/plain; charset="utf-8")
UdevLog.txt Edit (239.8 KiB, text/plain; charset="utf-8")
XorgConf.txt Edit (213 bytes, text/plain; charset="utf-8")
XorgLog.txt Edit (38.1 KiB, text/plain; charset="utf-8")
Xrandr.txt Edit (4.7 KiB, text/plain; charset="utf-8")
make.log.txt Edit (20.5 KiB, 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-27:

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 #590931, 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.