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 #862856 reported by Tiago Correia on 2011-09-29

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

o drive deixou de funcionar e apareceu um relatorio que dizia que era impossível instalar o pacote

ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: nvidia-current 195.36.24-0ubuntu1~10.04
ProcVersionSignature: Ubuntu 2.6.38-11.50~lucid1-virtual 2.6.38.8
Uname: Linux 2.6.38-11-virtual i686
Architecture: i386
Date: Thu Sep 29 23:52:00 2011
DkmsStatus:
nvidia-current, 195.36.24: added
multitouch, 1.5, 2.6.32-34-generic-pae, i686: installed
multitouch, 1.5, 2.6.32-33-generic-pae, i686: installed
multitouch, 1.5, 2.6.32-34-386, i686: installed
multitouch, 1.5, 2.6.32-34-generic, i686: installed
ErrorMessage: nvidia-current kernel module failed to build
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
MachineType: Packard Bell oneTwo M3351
PackageVersion: 195.36.24-0ubuntu1~10.04
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-11-virtual root=UUID=80f96d4f-b1b0-4e42-8f36-dbbed00c8cd3 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: 05/17/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P01-A1
dmi.board.name: oneTwo M3351
dmi.board.vendor: Packard Bell
dmi.chassis.type: 3
dmi.chassis.vendor: Packard Bell
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP01-A1:bd05/17/2010:svnPackardBell:pnoneTwoM3351:pvr:rvnPackardBell:rnoneTwoM3351:rvr:cvnPackardBell:ct3:cvr:
dmi.product.name: oneTwo M3351
dmi.sys.vendor: Packard Bell
glxinfo: Error: [Errno 2] Ficheiro ou directoria inexistente
system:
distro: Ubuntu
codename: lucid
architecture: i686
kernel: 2.6.38-11-virtual

Tags:

Revision history for this message

Tiago Correia (tsilvacorreia) wrote on 2011-09-29:

BootDmesg.txt Edit (54.5 KiB, text/plain; charset="utf-8")
CurrentDmesg.txt Edit (5.5 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 (23.7 KiB, text/plain; charset="utf-8")
GdmLog1.txt Edit (24.0 KiB, text/plain; charset="utf-8")
GdmLog2.txt Edit (434 bytes, text/plain; charset="utf-8")
Lspci.txt Edit (26.2 KiB, text/plain; charset="utf-8")
Lsusb.txt Edit (582 bytes, text/plain; charset="utf-8")
PciDisplay.txt Edit (1.9 KiB, text/plain; charset="utf-8")
ProcCpuinfo.txt Edit (1.7 KiB, text/plain; charset="utf-8")
ProcInterrupts.txt Edit (1.5 KiB, text/plain; charset="utf-8")
ProcModules.txt Edit (2.1 KiB, text/plain; charset="utf-8")
RelatedPackageVersions.txt Edit (231 bytes, text/plain; charset="utf-8")
UdevDb.txt Edit (146.1 KiB, text/plain; charset="utf-8")
UdevLog.txt Edit (309.4 KiB, text/plain; charset="utf-8")
XorgLog.txt Edit (27.3 KiB, text/plain; charset="utf-8")
XorgLogOld.txt Edit (28.0 KiB, text/plain; charset="utf-8")
Xrandr.txt Edit (575 bytes, text/plain; charset="utf-8")
make.log.txt Edit (780 bytes, 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 (47.3 KiB, text/plain; charset="utf-8")

Revision history for this message

Daniel van Vugt (vanvugt) wrote on 2011-09-30:

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.