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 #720396 reported by Mathilda Young on 2011-02-16

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 the driver for my Belkin F5D8053 (and my sources are set to natty, so, I'm sorry if this bug won't help anyone)

ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: nvidia-current 195.36.24-0ubuntu1~10.04
ProcVersionSignature: Ubuntu 2.6.32-29.58-generic 2.6.32.28+drm33.13
Uname: Linux 2.6.32-29-generic i686
NonfreeKernelModules: nvidia
Architecture: i386
Date: Wed Feb 16 14:19:11 2011
DkmsStatus:
vboxhost, 4.0.2, 2.6.32-29-generic, i686: installed
vboxhost, 4.0.2, 2.6.32-28-generic, i686: installed
nvidia-current, 195.36.24, 2.6.32-29-generic, i686: installed
nvidia-current, 195.36.24, 2.6.32-28-generic, i686: installed
ErrorMessage: nvidia-current kernel module failed to build
InstallationMedia: Ubuntu 10.04.2 LTS "Lucid Lynx" - Release i386 (20110206)
MachineType: eMachines EL1200
PackageVersion: 195.36.24-0ubuntu1~10.04
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-29-generic root=UUID=95d8d891-34d7-4ec2-b2e0-b7a15842b11b 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/23/2008
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: R01-A2
dmi.board.name: WMCP61M
dmi.board.vendor: eMachines
dmi.chassis.asset.tag: 0000000000000000000000
dmi.chassis.type: 3
dmi.chassis.vendor: eMachines
dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvrR01-A2:bd10/23/2008:svneMachines:pnEL1200:pvrR01-A2:rvneMachines:rnWMCP61M:rvr:cvneMachines:ct3:cvr:
dmi.product.name: EL1200
dmi.product.version: R01-A2
dmi.sys.vendor: eMachines
glxinfo: Error: [Errno 2] No such file or directory
system:
distro: Ubuntu
codename: lucid
architecture: i686
kernel: 2.6.32-29-generic

Tags:

Revision history for this message

Mathilda Young (gtrsdk) wrote on 2011-02-16:

BootDmesg.txt Edit (61.6 KiB, text/plain; charset="utf-8")
CurrentDmesg.txt Edit (15.6 KiB, text/plain; charset="utf-8")
DKMSBuildLog.txt Edit (10.5 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (1.3 KiB, text/plain; charset="utf-8")
Lspci.txt Edit (22.0 KiB, text/plain; charset="utf-8")
Lsusb.txt Edit (376 bytes, text/plain; charset="utf-8")
PciDisplay.txt Edit (1.0 KiB, text/plain; charset="utf-8")
ProcCpuinfo.txt Edit (661 bytes, text/plain; charset="utf-8")
ProcInterrupts.txt Edit (1.0 KiB, text/plain; charset="utf-8")
ProcModules.txt Edit (2.3 KiB, text/plain; charset="utf-8")
RelatedPackageVersions.txt Edit (231 bytes, text/plain; charset="utf-8")
UdevDb.txt Edit (99.3 KiB, text/plain; charset="utf-8")
UdevLog.txt Edit (215.2 KiB, text/plain; charset="utf-8")
XorgConf.txt Edit (213 bytes, text/plain; charset="utf-8")
XorgLog.txt Edit (13.4 KiB, text/plain; charset="utf-8")
XorgLogOld.txt Edit (13.7 KiB, text/plain; charset="utf-8")
Xrandr.txt Edit (12.6 KiB, text/plain; charset="utf-8")
make.log.txt Edit (10.5 KiB, text/plain; charset="utf-8")
setxkbmap.txt Edit (233 bytes, text/plain; charset="utf-8")
xdpyinfo.txt Edit (30.5 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.