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 #799242 reported by slmb on 2011-06-18

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

SystemError: installArchives() failed

ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: nvidia-current 195.36.24-0ubuntu1~10.04
ProcVersionSignature: Ubuntu 2.6.38-1.27~lucid1-generic 2.6.38-rc2
Uname: Linux 2.6.38-1-generic i686
Architecture: i386
Date: Sat Jun 18 23:27:44 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)
MachineType: ACER Aspire M5640
PackageVersion: 195.36.24-0ubuntu1~10.04
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-1-generic root=UUID=c4b7c82d-b23c-4aa0-8492-64c8e3317a82 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
XorgConf:

dmi.bios.date: 01/29/2008
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: R01-A3
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: MCP73
dmi.board.vendor: ACER
dmi.board.version: NVIDIA MCP73
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.:bvrR01-A3:bd01/29/2008:svnACER:pnAspireM5640:pvrR01-A3:rvnACER:rnMCP73:rvrNVIDIAMCP73:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: Aspire M5640
dmi.product.version: R01-A3
dmi.sys.vendor: ACER
glxinfo: Error: [Errno 2] No such file or directory
system:
distro: Ubuntu
codename: lucid
architecture: i686
kernel: 2.6.38-1-generic

Tags:

Revision history for this message

slmb (fqa101) wrote on 2011-06-18:

BootDmesg.txt Edit (56.2 KiB, text/plain; charset="utf-8")
CurrentDmesg.txt Edit (2.8 KiB, text/plain; charset="utf-8")
DKMSBuildLog.txt Edit (10.4 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (1.3 KiB, text/plain; charset="utf-8")
GdmLog.txt Edit (19.4 KiB, text/plain; charset="utf-8")
GdmLog1.txt Edit (3.1 MiB, text/plain; charset="utf-8")
GdmLog2.txt Edit (19.3 KiB, text/plain; charset="utf-8")
Lspci.txt Edit (21.0 KiB, text/plain; charset="utf-8")
Lsusb.txt Edit (515 bytes, text/plain; charset="utf-8")
PciDisplay.txt Edit (1.0 KiB, text/plain; charset="utf-8")
ProcCpuinfo.txt Edit (1.5 KiB, text/plain; charset="utf-8")
ProcInterrupts.txt Edit (1.5 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 (127.2 KiB, text/plain; charset="utf-8")
UdevLog.txt Edit (275.4 KiB, text/plain; charset="utf-8")
XorgLog.txt Edit (23.0 KiB, text/plain; charset="utf-8")
XorgLogOld.txt Edit (3.1 MiB, text/plain; charset="utf-8")
Xrandr.txt Edit (578 bytes, text/plain; charset="utf-8")
make.log.txt Edit (10.4 KiB, text/plain; charset="utf-8")
setxkbmap.txt Edit (285 bytes, text/plain; charset="utf-8")
xdpyinfo.txt Edit (17.2 KiB, text/plain; charset="utf-8")
xkbcomp.txt Edit (47.3 KiB, text/plain; charset="utf-8")

Revision history for this message

Daniel van Vugt (vanvugt) wrote on 2011-06-19:

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.