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 #809952 reported by Carlos Puero C. on 2011-07-13

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

After upgrade this error raised

ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: nvidia-current 195.36.24-0ubuntu1~10.04
ProcVersionSignature: Ubuntu 2.6.38-10.46~lucid1-generic 2.6.38.7
Uname: Linux 2.6.38-10-generic x86_64
Architecture: amd64
Date: Wed Jul 13 10:12:08 2011
ErrorMessage: nvidia-current kernel module failed to build
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
MachineType: ASUSTeK Computer INC. Z96S
PackageVersion: 195.36.24-0ubuntu1~10.04
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-10-generic root=UUID=b0e77b8f-f1ed-4ea6-b9e4-718c2b0bc09b ro ipv6.disable=1 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: 06/16/2008
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0803
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: Z96S
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: 1.00
dmi.chassis.asset.tag: 0x00000000
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTek Computer INC.
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0803:bd06/16/2008:svnASUSTeKComputerINC.:pnZ96S:pvr1.0:rvnASUSTeKComputerINC.:rnZ96S:rvr1.00:cvnASUSTekComputerINC.:ct10:cvr1.0:
dmi.product.name: Z96S
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK Computer INC.
glxinfo: Error: [Errno 2] No such file or directory
system:
distro: Ubuntu
codename: lucid
architecture: x86_64
kernel: 2.6.38-10-generic

Tags:

Revision history for this message

Carlos Puero C. (cjoasis) wrote on 2011-07-13:

BootDmesg.txt Edit (55.8 KiB, text/plain; charset="utf-8")
CurrentDmesg.txt Edit (4.6 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.2 KiB, text/plain; charset="utf-8")
GdmLog.txt Edit (434 bytes, text/plain; charset="utf-8")
GdmLog1.txt Edit (3.9 KiB, text/plain; charset="utf-8")
GdmLog2.txt Edit (434 bytes, text/plain; charset="utf-8")
Lspci.txt Edit (26.6 KiB, text/plain; charset="utf-8")
Lsusb.txt Edit (738 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.5 KiB, text/plain; charset="utf-8")
ProcModules.txt Edit (3.1 KiB, text/plain; charset="utf-8")
RelatedPackageVersions.txt Edit (231 bytes, text/plain; charset="utf-8")
UdevDb.txt Edit (125.0 KiB, text/plain; charset="utf-8")
UdevLog.txt Edit (262.9 KiB, text/plain; charset="utf-8")
XorgConf.txt Edit (1.3 KiB, text/plain; charset="utf-8")
XorgLog.txt Edit (5.1 KiB, text/plain; charset="utf-8")
XorgLogOld.txt Edit (5.0 KiB, text/plain; charset="utf-8")
Xrandr.txt Edit (575 bytes, text/plain; charset="utf-8")
make.log.txt Edit (9.9 KiB, text/plain; charset="utf-8")
setxkbmap.txt Edit (233 bytes, text/plain; charset="utf-8")
xdpyinfo.txt Edit (2.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-07-14:

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.