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 #795547 reported by craig hill on 2011-06-10

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 update, window opened on restart asking to reconfig nvidia. Was unable to perform reconfig

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 i686
Architecture: i386
Date: Thu Jun 9 16:47:26 2011
ErrorMessage: nvidia-current kernel module failed to build
Lsusb:
Bus 002 Device 003: ID 04b4:0033 Cypress Semiconductor Corp.
Bus 002 Device 002: ID 1a86:7584 Unknown
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 004: ID 058f:6362 Alcor Micro Corp. Hi-Speed 21-in-1 Flash Card Reader/Writer (Internal/External)
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: BIOSTAR Group N61PB-M2S
PackageVersion: 195.36.24-0ubuntu1~10.04
ProcCmdLine: root=UUID=fa537162-2b71-4928-b484-bea7a9a4a4d5 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/16/2008
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: 6.00 PG
dmi.board.name: N61PB-M2S
dmi.board.vendor: BIOSTAR Group
dmi.board.version: 1.0
dmi.chassis.type: 3
dmi.chassis.vendor: BIOSTAR Group
dmi.chassis.version: N61PB-M2S
dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd06/16/2008:svnBIOSTARGroup:pnN61PB-M2S:pvr6.0:rvnBIOSTARGroup:rnN61PB-M2S:rvr1.0:cvnBIOSTARGroup:ct3:cvrN61PB-M2S:
dmi.product.name: N61PB-M2S
dmi.product.version: 6.0
dmi.sys.vendor: BIOSTAR Group
system:
distro: Ubuntu
codename: lucid
architecture: i686
kernel: 2.6.38-10-generic

Tags:

Revision history for this message

craig hill (bfuzzled) wrote on 2011-06-10:

BootDmesg.txt Edit (53.4 KiB, text/plain; charset="utf-8")
CurrentDmesg.txt Edit (7.1 KiB, text/plain; charset="utf-8")
DKMSBuildLog.txt Edit (10.5 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (1.3 KiB, text/plain; charset="utf-8")
DkmsStatus.txt Edit (691 bytes, text/plain; charset="utf-8")
GdmLog.txt Edit (19.0 KiB, text/plain; charset="utf-8")
GdmLog1.txt Edit (19.0 KiB, text/plain; charset="utf-8")
GdmLog2.txt Edit (19.1 KiB, text/plain; charset="utf-8")
Lspci.txt Edit (24.0 KiB, text/plain; charset="utf-8")
PciDisplay.txt Edit (2.8 KiB, text/plain; charset="utf-8")
ProcCpuinfo.txt Edit (1.5 KiB, text/plain; charset="utf-8")
ProcInterrupts.txt Edit (1.4 KiB, text/plain; charset="utf-8")
ProcModules.txt Edit (2.7 KiB, text/plain; charset="utf-8")
RelatedPackageVersions.txt Edit (231 bytes, text/plain; charset="utf-8")
UdevDb.txt Edit (111.2 KiB, text/plain; charset="utf-8")
UdevLog.txt Edit (239.0 KiB, text/plain; charset="utf-8")
XorgLog.txt Edit (22.4 KiB, text/plain; charset="utf-8")
XorgLogOld.txt Edit (22.4 KiB, text/plain; charset="utf-8")
Xrandr.txt Edit (575 bytes, text/plain; charset="utf-8")
glxinfo.txt Edit (602 bytes, text/plain; charset="utf-8")
make.log.txt Edit (10.5 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 (54.1 KiB, text/plain; charset="utf-8")

Revision history for this message

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

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.