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 #853786 reported by kumar on 2011-09-19

This bug report is a duplicate of: Bug #627022: package nvidia-current 195.36.24-0ubuntu1~10.04 failed to install/upgrade: nvidia-current kernel module failed to build (nv.c:417: error: unknown field ‘ioctl’ specified in initializer). Edit Remove

This bug affects 1 person

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

Bug Description

Nvidia Graphic Card Driver is not supporting for HD Vedios

ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: nvidia-current 195.36.24-0ubuntu1~10.04
ProcVersionSignature: Ubuntu 2.6.38-11.50~lucid1-generic-pae 2.6.38.8
Uname: Linux 2.6.38-11-generic-pae i686
Architecture: i386
Date: Mon Sep 19 16:29:46 2011
DkmsStatus: nvidia-current, 195.36.24: added
ErrorMessage: nvidia-current kernel module failed to build
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
Lsusb:
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
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: System manufacturer System Product Name
PackageVersion: 195.36.24-0ubuntu1~10.04
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-11-generic-pae root=UUID=b2978303-da11-4319-bd0e-cdc8a7c075ff 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: 01/30/2008
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0312
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: P5GC-MX/1333
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev x.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: ASUSTek Computer INC.
dmi.chassis.version: Rev 1.xx
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0312:bd01/30/2008:svnSystemmanufacturer:pnSystemProductName:pvrRev1.xx:rvnASUSTeKComputerINC.:rnP5GC-MX/1333:rvrRevx.xx:cvnASUSTekComputerINC.:ct3:cvrRev1.xx:
dmi.product.name: System Product Name
dmi.product.version: Rev 1.xx
dmi.sys.vendor: System manufacturer
glxinfo: Error: [Errno 2] No such file or directory
system:
distro: Ubuntu
codename: lucid
architecture: i686
kernel: 2.6.38-11-generic-pae

Tags:

Revision history for this message

kumar (silotum) wrote on 2011-09-19:

BootDmesg.txt Edit (45.8 KiB, text/plain; charset="utf-8")
CurrentDmesg.txt Edit (998 bytes, text/plain; charset="utf-8")
DKMSBuildLog.txt Edit (10.6 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (1.3 KiB, text/plain; charset="utf-8")
Lspci.txt Edit (19.7 KiB, 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.6 KiB, text/plain; charset="utf-8")
ProcModules.txt Edit (2.1 KiB, text/plain; charset="utf-8")
RelatedPackageVersions.txt Edit (231 bytes, text/plain; charset="utf-8")
UdevDb.txt Edit (105.3 KiB, text/plain; charset="utf-8")
UdevLog.txt Edit (223.8 KiB, text/plain; charset="utf-8")
XorgLog.txt Edit (6.2 MiB, text/plain; charset="utf-8")
XorgLogOld.txt Edit (19.2 MiB, text/plain; charset="utf-8")
Xrandr.txt Edit (573 bytes, text/plain; charset="utf-8")
make.log.txt Edit (10.6 KiB, text/plain; charset="utf-8")
setxkbmap.txt Edit (233 bytes, text/plain; charset="utf-8")
xdpyinfo.txt Edit (17.2 KiB, text/plain; charset="utf-8")
xkbcomp.txt Edit (54.1 KiB, text/plain; charset="utf-8")

Revision history for this message

Daniel van Vugt (vanvugt) wrote on 2011-09-20:

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