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 #856288 reported by dino99 on 2011-09-22

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

get the same issue with several kernels

ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: nvidia-current 195.36.24-0ubuntu1~10.04
ProcVersionSignature: Ubuntu 2.6.38-11.49~lucid1-generic-pae 2.6.38.8
Uname: Linux 2.6.38-11-generic-pae i686
Architecture: i386
Date: Thu Sep 22 12:40:37 2011
DkmsStatus: nvidia-current, 195.36.24: added
ErrorMessage: nvidia-current kernel module failed to build
MachineType: ASUSTEK COMPUTER INC P5W DH Deluxe
PackageVersion: 195.36.24-0ubuntu1~10.04
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-11-generic-pae root=UUID=0eea5390-114c-4ee2-815f-a3cfca716c04 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: 10/22/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 3001
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: P5W DH Deluxe
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3001:bd10/22/2009:svnASUSTEKCOMPUTERINC:pnP5WDHDeluxe:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WDHDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: P5W DH Deluxe
dmi.product.version: System Version
dmi.sys.vendor: ASUSTEK COMPUTER INC
glxinfo: Error: [Errno 2] Aucun fichier ou dossier de ce type
system:
distro: Ubuntu
codename: lucid
architecture: i686
kernel: 2.6.38-11-generic-pae

Tags:

Revision history for this message

dino99 (9d9) wrote on 2011-09-22:

BootDmesg.txt Edit (54.2 KiB, text/plain; charset="utf-8")
CurrentDmesg.txt Edit (4.9 KiB, 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")
GdmLog.txt Edit (18.5 KiB, text/plain; charset="utf-8")
GdmLog1.txt Edit (18.7 KiB, text/plain; charset="utf-8")
GdmLog2.txt Edit (18.7 KiB, text/plain; charset="utf-8")
Lspci.txt Edit (14.6 KiB, text/plain; charset="utf-8")
Lsusb.txt Edit (407 bytes, text/plain; charset="utf-8")
PciDisplay.txt Edit (823 bytes, text/plain; charset="utf-8")
ProcCpuinfo.txt Edit (3.1 KiB, text/plain; charset="utf-8")
ProcInterrupts.txt Edit (2.3 KiB, text/plain; charset="utf-8")
ProcModules.txt Edit (3.1 KiB, text/plain; charset="utf-8")
RelatedPackageVersions.txt Edit (204 bytes, text/plain; charset="utf-8")
UdevDb.txt Edit (133.8 KiB, text/plain; charset="utf-8")
UdevLog.txt Edit (256.8 KiB, text/plain; charset="utf-8")
XorgLog.txt Edit (22.0 KiB, text/plain; charset="utf-8")
XorgLogOld.txt Edit (22.2 KiB, text/plain; charset="utf-8")
Xrandr.txt Edit (575 bytes, text/plain; charset="utf-8")
make.log.txt Edit (10.6 KiB, text/plain; charset="utf-8")
setxkbmap.txt Edit (258 bytes, text/plain; charset="utf-8")
xdpyinfo.txt Edit (2.5 KiB, text/plain; charset="utf-8")
xkbcomp.txt Edit (58.4 KiB, text/plain; charset="utf-8")

Revision history for this message

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

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.