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 #727235 reported by Alexander Zikal on 2011-03-01

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

error is coming every update

ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: nvidia-current 195.36.24-0ubuntu1~10.04
ProcVersionSignature: Ubuntu 2.6.32-28.55-generic 2.6.32.27+drm33.12
Uname: Linux 2.6.32-28-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
Date: Tue Mar 1 16:55:24 2011
ErrorMessage: nvidia-current kernel module failed to build
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100427.1)
MachineType: Gigabyte Technology Co., Ltd. EP45-UD3LR
PackageVersion: 195.36.24-0ubuntu1~10.04
ProcCmdLine: BOOT_IMAGE=/vmlinuz-2.6.32-28-generic root=UUID=a78601da-5f0b-44d5-b65f-c74e34d3792a ro crashkernel=384M-2G:64M,2G-:128M 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: 04/22/2010
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F11
dmi.board.name: EP45-UD3LR
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF11:bd04/22/2010:svnGigabyteTechnologyCo.,Ltd.:pnEP45-UD3LR:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnEP45-UD3LR:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
dmi.product.name: EP45-UD3LR
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
glxinfo: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden
system:
distro: Ubuntu
codename: lucid
architecture: x86_64
kernel: 2.6.32-28-generic

Tags:

Revision history for this message

Alexander Zikal (alexander-zikal) wrote on 2011-03-01:

BootDmesg.txt Edit (74.1 KiB, text/plain; charset="utf-8")
CurrentDmesg.txt Edit (2.9 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 (931 bytes, text/plain; charset="utf-8")
GdmLog.txt Edit (13.8 KiB, text/plain; charset="utf-8")
GdmLog1.txt Edit (14.2 KiB, text/plain; charset="utf-8")
GdmLog2.txt Edit (14.2 KiB, text/plain; charset="utf-8")
Lspci.txt Edit (24.5 KiB, text/plain; charset="utf-8")
Lsusb.txt Edit (1.2 KiB, text/plain; charset="utf-8")
PciDisplay.txt Edit (1.9 KiB, text/plain; charset="utf-8")
ProcCpuinfo.txt Edit (3.0 KiB, text/plain; charset="utf-8")
ProcInterrupts.txt Edit (2.1 KiB, text/plain; charset="utf-8")
ProcModules.txt Edit (3.8 KiB, text/plain; charset="utf-8")
RelatedPackageVersions.txt Edit (231 bytes, text/plain; charset="utf-8")
UdevDb.txt Edit (183.2 KiB, text/plain; charset="utf-8")
UdevLog.txt Edit (317.3 KiB, text/plain; charset="utf-8")
XorgConf.txt Edit (213 bytes, text/plain; charset="utf-8")
XorgLog.txt Edit (17.6 KiB, text/plain; charset="utf-8")
XorgLogOld.txt Edit (18.2 KiB, text/plain; charset="utf-8")
Xrandr.txt Edit (18.7 KiB, text/plain; charset="utf-8")
make.log.txt Edit (9.9 KiB, text/plain; charset="utf-8")
setxkbmap.txt Edit (265 bytes, text/plain; charset="utf-8")
xdpyinfo.txt Edit (22.0 KiB, text/plain; charset="utf-8")
xkbcomp.txt Edit (47.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.