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 #739894 reported by Patrick Walker on 2011-03-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

I installed a new kernel and when the computer booted was given this bug to report.

ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: nvidia-current 195.36.24-0ubuntu1~10.04
ProcVersionSignature: Ubuntu 2.6.32-26.48-generic 2.6.32.24+drm33.11
Uname: Linux 2.6.32-26-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
Date: Mon Mar 21 21:51:28 2011
ErrorMessage: nvidia-current kernel module failed to build
MachineType: System manufacturer System Product Name
PackageVersion: 195.36.24-0ubuntu1~10.04
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-26-generic root=UUID=662790d6-b22c-44c5-aae8-524524d378e4 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: 09/10/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1601
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: M4A78-E
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.:bvr1601:bd09/10/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A78-E:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
system:
distro: Ubuntu
codename: lucid
architecture: x86_64
kernel: 2.6.32-26-generic

Tags:

Revision history for this message

Patrick Walker (phobiac) wrote on 2011-03-22:

BootDmesg.txt Edit (51.2 KiB, text/plain; charset="utf-8")
CurrentDmesg.txt Edit (1.7 KiB, text/plain; charset="utf-8")
DKMSBuildLog.txt Edit (9.9 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (1.3 KiB, text/plain; charset="utf-8")
DkmsStatus.txt Edit (1.0 KiB, text/plain; charset="utf-8")
GdmLog.txt Edit (10.9 KiB, text/plain; charset="utf-8")
GdmLog1.txt Edit (11.2 KiB, text/plain; charset="utf-8")
GdmLog2.txt Edit (11.2 KiB, text/plain; charset="utf-8")
Lspci.txt Edit (28.7 KiB, text/plain; charset="utf-8")
Lsusb.txt Edit (761 bytes, text/plain; charset="utf-8")
PciDisplay.txt Edit (1.9 KiB, text/plain; charset="utf-8")
ProcCpuinfo.txt Edit (3.3 KiB, text/plain; charset="utf-8")
ProcInterrupts.txt Edit (2.2 KiB, text/plain; charset="utf-8")
ProcModules.txt Edit (3.9 KiB, text/plain; charset="utf-8")
RelatedPackageVersions.txt Edit (231 bytes, text/plain; charset="utf-8")
UdevDb.txt Edit (116.2 KiB, text/plain; charset="utf-8")
UdevLog.txt Edit (251.4 KiB, text/plain; charset="utf-8")
XorgConf.txt Edit (1.4 KiB, text/plain; charset="utf-8")
XorgLog.txt Edit (14.1 KiB, text/plain; charset="utf-8")
XorgLogOld.txt Edit (14.6 KiB, text/plain; charset="utf-8")
Xrandr.txt Edit (19.4 KiB, text/plain; charset="utf-8")
glxinfo.txt Edit (24.4 KiB, text/plain; charset="utf-8")
make.log.txt Edit (9.9 KiB, text/plain; charset="utf-8")
setxkbmap.txt Edit (288 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.