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 #794238 reported by oebarg76 on 2011-06-07

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 make a update, and my problem start there, now i am usin the standart driver of ubuntu.

ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: nvidia-current 195.36.24-0ubuntu1~10.04
ProcVersionSignature: Ubuntu 2.6.38-10.44-generic 2.6.38.7
Uname: Linux 2.6.38-10-generic x86_64
Architecture: amd64
Date: Tue Jun 7 16:35:01 2011
ErrorMessage: nvidia-current kernel module failed to build
InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.1)
MachineType: Gigabyte Technology Co., Ltd. GA-MA78GM-S2H
PackageVersion: 195.36.24-0ubuntu1~10.04
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-10-generic root=UUID=8b3e64aa-1550-4be2-a3f9-1d9b2678e245 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: 06/18/2008
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F5
dmi.board.name: GA-MA78GM-S2H
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.:bvrF5:bd06/18/2008:svnGigabyteTechnologyCo.,Ltd.:pnGA-MA78GM-S2H:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-MA78GM-S2H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
dmi.product.name: GA-MA78GM-S2H
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
glxinfo: Error: [Errno 2] No existe el fichero o el directorio
system:
distro: Ubuntu
codename: lucid
architecture: x86_64
kernel: 2.6.38-10-generic

Tags:

Revision history for this message

oebarg76 (oebarg76) wrote on 2011-06-07:

BootDmesg.txt Edit (53.5 KiB, text/plain; charset="utf-8")
CurrentDmesg.txt Edit (1.7 KiB, text/plain; charset="utf-8")
DKMSBuildLog.txt Edit (9.8 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (1.3 KiB, text/plain; charset="utf-8")
DkmsStatus.txt Edit (378 bytes, text/plain; charset="utf-8")
GdmLog.txt Edit (19.3 KiB, text/plain; charset="utf-8")
GdmLog1.txt Edit (434 bytes, text/plain; charset="utf-8")
GdmLog2.txt Edit (3.6 KiB, text/plain; charset="utf-8")
Lspci.txt Edit (20.5 KiB, text/plain; charset="utf-8")
Lsusb.txt Edit (647 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 (2.4 KiB, text/plain; charset="utf-8")
RelatedPackageVersions.txt Edit (231 bytes, text/plain; charset="utf-8")
UdevDb.txt Edit (121.9 KiB, text/plain; charset="utf-8")
UdevLog.txt Edit (258.4 KiB, text/plain; charset="utf-8")
XorgLog.txt Edit (22.6 KiB, text/plain; charset="utf-8")
XorgLogOld.txt Edit (4.9 KiB, text/plain; charset="utf-8")
Xrandr.txt Edit (574 bytes, text/plain; charset="utf-8")
make.log.txt Edit (9.8 KiB, text/plain; charset="utf-8")
setxkbmap.txt Edit (233 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-08:

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.