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 #702699 reported by Cip Santoss on 2011-01-14

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 2 people

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

Bug Description

Nvidia driver does not work when I installed kernel 2.6.37-12

ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: nvidia-current 195.36.24-0ubuntu1~10.04
ProcVersionSignature: Ubuntu 2.6.32-27.49-generic 2.6.32.26+drm33.12
Uname: Linux 2.6.32-27-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
Date: Thu Jan 13 11:35:14 2011
ErrorMessage: nvidia-current kernel module failed to build
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
PackageVersion: 195.36.24-0ubuntu1~10.04
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-27-generic root=UUID=e810d75a-d5a4-46bb-ae90-29b511acd92f 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: 05/28/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P1.90
dmi.board.name: G31M-S.
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.90:bd05/28/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnG31M-S.:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.
glxinfo: Error: [Errno 2] No such file or directory
system:
distro: Ubuntu
codename: lucid
architecture: x86_64
kernel: 2.6.32-27-generic

Tags:

Revision history for this message

Cip Santoss (cipsantos) wrote on 2011-01-14:

BootDmesg.txt Edit (39.7 KiB, text/plain; charset="utf-8")
CurrentDmesg.txt Edit (3.6 KiB, text/plain; charset="utf-8")
DKMSBuildLog.txt Edit (8.9 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (1.3 KiB, text/plain; charset="utf-8")
DkmsStatus.txt Edit (1.1 KiB, text/plain; charset="utf-8")
GdmLog.txt Edit (9.2 KiB, text/plain; charset="utf-8")
GdmLog1.txt Edit (44.6 KiB, text/plain; charset="utf-8")
GdmLog2.txt Edit (9.5 KiB, text/plain; charset="utf-8")
Lspci.txt Edit (19.0 KiB, text/plain; charset="utf-8")
Lsusb.txt Edit (400 bytes, 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.4 KiB, text/plain; charset="utf-8")
ProcModules.txt Edit (2.7 KiB, text/plain; charset="utf-8")
RelatedPackageVersions.txt Edit (197 bytes, text/plain; charset="utf-8")
UdevDb.txt Edit (99.6 KiB, text/plain; charset="utf-8")
UdevLog.txt Edit (201.9 KiB, text/plain; charset="utf-8")
XorgConf.txt Edit (2.3 KiB, text/plain; charset="utf-8")
XorgLog.txt Edit (12.2 KiB, text/plain; charset="utf-8")
XorgLogOld.txt Edit (47.8 KiB, text/plain; charset="utf-8")
Xrandr.txt Edit (578 bytes, text/plain; charset="utf-8")
make.log.txt Edit (8.9 KiB, text/plain; charset="utf-8")
setxkbmap.txt Edit (233 bytes, text/plain; charset="utf-8")
xdpyinfo.txt Edit (22.0 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-26:

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.