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)

Bug #627022 reported by martyfelker
760
This bug affects 87 people
Affects Status Importance Assigned to Milestone
Gentoo Linux
Fix Released
Medium
nvidia-graphics-drivers (Ubuntu)
Fix Released
Undecided
Daniel van Vugt
Lucid
Fix Released
Undecided
Daniel van Vugt
nvidia-graphics-drivers-96 (Ubuntu)
Fix Released
Undecided
Daniel van Vugt
Lucid
Fix Released
Undecided
Daniel van Vugt

Bug Description

IMPACT:

The NVIDIA driver fails to build on Ubuntu 10.04 LTS if you have upgraded your kernel to >= 2.6.36. The offending kernel change was commit b19dd42faf413b4705d4adb38521e82d73fa4249 in 2.6.36 stable.

TEST CASE:

Starting with a clean Ubuntu 10.04 installation...
    sudo apt-add-repository ppa:kernel-ppa/ppa && sudo apt-get update
    sudo apt-get install linux-image-generic-lts-backport-natty linux-headers-generic-lts-backport-natty
    sudo apt-get install nvidia-current
Installation of nvidia-current will fail for the newer kernel. Now to verify it's the same error at nv.c:417:
    tail /var/lib/dkms/nvidia-current/*/build/make.log
("error: unknown field ‘ioctl’ specified in initializer")

FIX:

ifdef out the deprecated structure field, which is no longer present in Linux kernels >= 2.6.36. NVIDIA have already implemented a similar fix upstream, apparently in driver version ~260.19.06 onward.

NOTES:

This seems to be the same bug in both the 96 and 195 series nvidia drivers:
nv.c:244 (nvidia-96 96.43.17-0ubuntu1) == nv.c:417 (nvidia-current 195.36.24-0ubuntu1~10.04)

REGRESSION POTENTIAL:

Low. We are only #ifdef'ing out a structure member that no longer exists. Its replacement is already present in both newer and older kernels, and is used (redundantly) by the NVIDIA driver source because the removal of the 'ioctl' field had been planned for a long time.

ORIGINAL BUG REPORT:

ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: nvidia-current 195.36.24-0ubuntu1~10.04
ProcVersionSignature: Ubuntu 2.6.35-19.25~lucid1-generic 2.6.35.3
Uname: Linux 2.6.35-19-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
Date: Mon Aug 30 15:20:49 2010
ErrorMessage: nvidia-current kernel module failed to build
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100427.1)
Lsusb:
 Bus 002 Device 002: ID 1241:1503 Belkin Keyboard
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Gigabyte Technology Co., Ltd. M61P-S3
PackageVersion: 195.36.24-0ubuntu1~10.04
ProcCmdLine: BOOT_IMAGE=/vmlinuz-2.6.35-19-generic root=UUID=854b6439-6806-4a32-ae7b-c2024e888b20 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/2009
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F7f
dmi.board.name: M61P-S3
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF7f:bd06/18/2009:svnGigabyteTechnologyCo.,Ltd.:pnM61P-S3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnM61P-S3:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
dmi.product.name: M61P-S3
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
system:
 distro: Ubuntu
 codename: lucid
 architecture: x86_64
 kernel: 2.6.35-19-generic

Related branches

Revision history for this message
martyfelker (martyfelker-gmail) wrote :
Revision history for this message
In , Christian Ruppert (idl0r) wrote :

Latest keyworded drivers doesn't build with >=kernel-2.6.36.
/var/tmp/portage/x11-drivers/nvidia-drivers-256.53/work/kernel/nv.c:426: error: unknown field 'ioctl' specified in initializer
/var/tmp/portage/x11-drivers/nvidia-drivers-256.53/work/kernel/nv.c:426: warning: initialization from incompatible pointer type
make[4]: *** [/var/tmp/portage/x11-drivers/nvidia-drivers-256.53/work/kernel/nv.o] Error 1
make[3]: *** [_module_/var/tmp/portage/x11-drivers/nvidia-drivers-256.53/work/kernel] Error 2

nvidia-drivers-260.19.12 seems to be the latest stable version from nvidia but its still hardmasked as "beta".

Could we fix the mask?

Revision history for this message
In , Brant (brant) wrote :

*** Bug 342021 has been marked as a duplicate of this bug. ***

Revision history for this message
In , Christian Ruppert (idl0r) wrote :

*** Bug 342275 has been marked as a duplicate of this bug. ***

Revision history for this message
In , Stylinae (stylinae) wrote :

is 260 still considered beta? Gentoo portage just released *.36 into ~amd64 so people on testing can't use the driver yet. I know Ubuntu is shipping with version 260, so I wouldn't think it's still in beta.

Revision history for this message
In , Christian Ruppert (idl0r) wrote :

*** Bug 342651 has been marked as a duplicate of this bug. ***

Revision history for this message
In , Deduktionstheorem (deduktionstheorem) wrote :

(In reply to comment #3)
> is 260 still considered beta?

There still are serious issues with nvidia-drivers-260.19.*, see bug #336837

Revision history for this message
In , Kfirufk (kfirufk) wrote :

since new nvidia beta drivers xbmc stopped working.

Revision history for this message
In , Conan (richard-connon) wrote :

x11-drivers/nvidia-drivers-260.19.12 is masked as being beta but it's marked stable on the nvidia website.

Does it still ahve major issues?

Revision history for this message
In , Codez-iccd-99 (codez-iccd-99) wrote :

As it is stated in bug #336837, comment 33 the version 256.53 of nvidia-drivers can be compiled against 2.6.36 (gentoo-sources-)kernel with a patch that was posted to NVidia forums by artem.
So with little tinkering applied for nvidia-drivers-256.53.ebuild, I am able to compile those drivers. (I don't know how they work yet, though.)
The question is, would this patch (and later potential stabilizing of 256.53) be an acceptable alternative for unmasking masked drivers?

Ebuild was modified as per following, shown here only for reference. The .txt extension was removed from the file posted in the forums. I'll post the real deals (ebuild and the patch) if there's any point for doing that.

--- /usr/portage/x11-drivers/nvidia-drivers/nvidia-drivers-256.53.ebuild 2010-08-31 18:57:49.000000000 +0300
+++ /usr/local/portage/x11-drivers/nvidia-drivers/nvidia-drivers-256.53.ebuild 2010-11-05 17:03:37.000000000 +0200
@@ -277,6 +277,10 @@

   # If greater than 2.6.5 use M= instead of SUBDIR=
   convert_to_m "${NV_SRC}"/Makefile.kbuild
+
+ if kernel_is ge 2 6 36; then
+ epatch "${FILESDIR}"/NVIDIA-Linux-x86-256.53-linux-2.6.36.patch
+ fi
  fi
 }

Revision history for this message
In , J.Schlick (josch09) wrote :

(In reply to comment #7)
> x11-drivers/nvidia-drivers-260.19.12 is masked as being beta but it's marked
> stable on the nvidia website.
>
> Does it still ahve major issues?
>

opengl stuff is buggy or at least does not work as expected. In my environment
app-emulation/qemu-kvm-0.13.0-r2 stops with a coredump when trying to start a virtual machine.

Program terminated with signal 11, Segmentation fault.
#0 0x0000003ad109483f in ?? () from //usr/lib64/opengl/nvidia/lib/libGL.so.1
(gdb) bt
#0 0x0000003ad109483f in ?? () from //usr/lib64/opengl/nvidia/lib/libGL.so.1
#1 0x0000003ad1094c39 in ?? () from //usr/lib64/opengl/nvidia/lib/libGL.so.1
#2 0x0000003ad109939b in ?? () from //usr/lib64/opengl/nvidia/lib/libGL.so.1
#3 0x0000003ad109994c in ?? () from //usr/lib64/opengl/nvidia/lib/libGL.so.1
#4 0x0000003ac8c06c3a in start_thread () from /lib/libpthread.so.0
#5 0x0000003ac80d1cad in clone () from /lib/libc.so.6

Revision history for this message
In , Dyadkin (dyadkin) wrote :

(In reply to comment #7)
> x11-drivers/nvidia-drivers-260.19.12 is masked as being beta but it's marked
> stable on the nvidia website.
>
> Does it still ahve major issues?
>

My laptop sony vaio vpccw2s1r with gf 330m does not start xorg with x11-drivers/nvidia-drivers-260.19.12 (just black screen)

Revision history for this message
In , Tdalman (tdalman) wrote :

New driver version 260.19.21 was just released - might be worth a try ?

Revision history for this message
In , Chi-Thanh Christopher Nguyen (chithanh) wrote :

*** Bug 345269 has been marked as a duplicate of this bug. ***

Revision history for this message
In , Dominique Michel (dominique-michel-vtxnet) wrote :

(In reply to comment #7)
> x11-drivers/nvidia-drivers-260.19.12 is masked as being beta but it's marked
> stable on the nvidia website.
>
> Does it still ahve major issues?
>

I get something like "... nvidia.ko Device not found"

with 'modprobe nvidia' on my ~amd64 system.

Revision history for this message
In , Turul16 (turul16) wrote :

Created attachment 254193
nv-256.53_lnx-2.6.36.patch

I had issues with the 260.19.12 and with gvim while using 2.6.36 kernel. (Strange if tracing the gvim process it is working)

I have the 256.53 to compile with 2.6.36 , I have back-ported the config options from the 2.6.36.

Now gvim is working.
I tested OpenArena as well.

Revision history for this message
In , Turul16 (turul16) wrote :

Created attachment 254195
nvidia-drivers-256.53.ebuild

A working ebuild with the nv-256.53_lnx-2.6.36.patch.

Revision history for this message
In , JC Wren (jcwren) wrote :

I'm happy to report that applying the patch and new ebuild has allowed me to once again use KDE on my workstation.

Thank you!

Revision history for this message
In , Xarthisius (xarthisius) wrote :

*** Bug 345707 has been marked as a duplicate of this bug. ***

Revision history for this message
In , Petr Písař (petr-pisar) wrote :

Created attachment 254745
Patch for 96.43.18 driver

The same issue with x11-drivers/nvidia-drivers-96.43.18. This is patch for 260* version transposed for 96.43.18 version. Tested on x86 and Linux 2.6.36-gentoo-r1.

Revision history for this message
In , Limanski (limanski) wrote :

Hi all,

  gentoo-sources-2.6.36-r5 is now stable (bug 348509) on x86. Should this bug be a blocker for 2.6.36 stabilization?

Revision history for this message
In , Tbartdev (tbartdev) wrote :

(In reply to comment #19)
> Hi all,
>
> gentoo-sources-2.6.36-r5 is now stable (bug 348509) on x86. Should this bug
> be a blocker for 2.6.36 stabilization?
>

2.6.35 also has some severe problems. better fix this issue I guess...

Attila, please correct the patch to have the correct name! (36 not 26)

Revision history for this message
In , Tbartdev (tbartdev) wrote :

This bug is related to http://bugs.gentoo.org/show_bug.cgi?id=348865

virtualbox-modules has a similar issue, see my patch above.

Revision history for this message
In , Mike (michael-hammill) wrote :

(In reply to comment #19)
> Hi all,
>
> gentoo-sources-2.6.36-r5 is now stable (bug 348509) on x86. Should this bug
> be a blocker for 2.6.36 stabilization?
>
As someone who just downloaded the stable 2.6.36-r5 and expected stable nvidia-drivers-195.36.31 to work, I would second the notion that something should be done *soon* or alternatively block 2.6.36 as stable. I'll try the patches supplied above for now.

Revision history for this message
In , Codez-iccd-99 (codez-iccd-99) wrote :

As I've stated in comment #8 256.53 can be compiled against 3.6.36. Now I have 3.6.36-r5 kernel running smoothly with nvidia-drivers-256.53, but it is NOT using any patches attached here. Instead the patch (mentioned in my comment) that contains 3 very small changes is used.

Additionally it seems, that some of 260.*-series drivers are not hardmasked anymore so the question is, do we want working older (256.53) drivers beside new cutting-edge drivers, or not?

Revision history for this message
In , Deduktionstheorem (deduktionstheorem) wrote :

I have gentoo-sources-2.6.36-r5 and nvidia-drivers-260.19.29 installed (directly from portage, without any patches). They're running without any problems!

Revision history for this message
In , Christian Ruppert (idl0r) wrote :

(In reply to comment #24)
> I have gentoo-sources-2.6.36-r5 and nvidia-drivers-260.19.29 installed
> (directly from portage, without any patches). They're running without any
> problems!
>

I agree, 260.19.29 is the only version of the 260 series that works fine for me.

Revision history for this message
In , Mike (michael-hammill) wrote :

(In reply to comment #24)
I can second this. I have the same setup. I also tested the corresponding nvidia-setting-260.19.29 and it seems to be working as well. The only minor thing I have found is "nvidia: module license 'NVIDIA' taints kernel" in dmesg. BTW, I'm running a nVidia Corporation G96 [GeForce 9400 GT] (rev a1).

Revision history for this message
In , Christian Ruppert (idl0r) wrote :

*** Bug 349303 has been marked as a duplicate of this bug. ***

Revision history for this message
In , Christian Ruppert (idl0r) wrote :

*** Bug 349616 has been marked as a duplicate of this bug. ***

Revision history for this message
In , Samuli Suominen (ssuominen) wrote :

This should be solved by bug 348186.

summary: package nvidia-current 195.36.24-0ubuntu1~10.04 failed to
- install/upgrade: nvidia-current kernel module failed to build
+ install/upgrade: nvidia-current kernel module failed to build (nv.c:417:
+ error: unknown field ‘ioctl’ specified in initializer)
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Confirmed by dozens of duplicates, with new duplicates every day or two.

Changed in nvidia-graphics-drivers (Ubuntu):
status: New → Confirmed
description: updated
Changed in gentoo:
importance: Unknown → Medium
status: Unknown → Fix Released
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

The root cause of this bug is the final removal of BKL from the Linux kernel:
http://git.kernel.org/?p=linux/kernel/git/stable/linux-2.6.36.y.git;a=commitdiff;h=b19dd42faf413b4705d4adb38521e82d73fa4249

The change first appeared in kernel 2.6.36 and possibly later versions of ubuntu kernel 2.6.35.

NVIDIA have implemented a fix in their later driver versions:
Users of nvidia-96 need version 96.43.19 or later.
Users of nvidia-current need version 260.19.06 or later.

260.19.06 really does seem to be the earliest instance of the fix I can find for nvidia-current. It seems the fix was never implemented in 195.*

Users of Ubuntu 10.04 (lucid) might find success if they can install the maverick version 260.19.06:
http://packages.ubuntu.com/maverick/nvidia-current

Changed in nvidia-graphics-drivers-96 (Ubuntu):
status: New → Confirmed
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Further details:
nvidia-96 is already fixed in maverick-updates and natty. It is not yet fixed in lucid.
nvidia-current is already fixed in maverick and natty. It is not yet fixed in lucid.

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Alternatively, Ubuntu 10.04 (lucid) users could just downgrade to the standard lucid kernel, which is 2.6.32.something. That will fix the bug too, and allow you to install nvidia-*. Upgrading the kernel beyond what lucid is meant to have is what triggers this bug in the first place.

Revision history for this message
Jaster (jastersr) wrote : Re: [Bug 627022] Re: 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)

Consegui resolver o problema após a reinstalação do Ubuntu. O problema
havia ocorrido devido a instalação do driver não ter sido completada e a
atualização dos pacotes ter ocorrido em paralelo, provavelmente gerou
alguma incompatibilidade.

Muito Obrigado.
Jaster

Em Seg, 2011-06-13 às 08:44 +0000, Daniel van Vugt escreveu:
> Alternatively, Ubuntu 10.04 (lucid) users could just downgrade to the
> standard lucid kernel, which is 2.6.32.something. That will fix the bug
> too, and allow you to install nvidia-*. Upgrading the kernel beyond what
> lucid is meant to have is what triggers this bug in the first place.
>

Revision history for this message
Bryce Harrington (bryce) wrote :

Looks like this needs the nvidia-2.6.36-ioctl.patch patch added for these packages.

@Alberto, if this is correct could you include backports of the patch to lucid as well? Would be nice to also update it in x-updates and perhaps xorg-edgers if it isn't already.

Changed in nvidia-graphics-drivers (Ubuntu):
assignee: nobody → Alberto Milone (albertomilone)
Changed in nvidia-graphics-drivers-96 (Ubuntu):
assignee: nobody → Alberto Milone (albertomilone)
description: updated
Changed in nvidia-graphics-drivers (Ubuntu):
assignee: Alberto Milone (albertomilone) → Daniel van Vugt (vanvugt)
status: Confirmed → In Progress
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

nvidia-2.6.36-ioctl.patch is actually slightly wrong, but will still kind of work.

I have now proposed a cleaner solution. If accepted for nvidia-graphics-drivers, then I'm happy to do the same for -96 too.

Changed in nvidia-graphics-drivers-96 (Ubuntu):
assignee: Alberto Milone (albertomilone) → Daniel van Vugt (vanvugt)
status: Confirmed → In Progress
Revision history for this message
Chris Halse Rogers (raof) wrote :

Alberto: are you happy to have this patch in Lucid? The merge request¹ looks good, and given that we've got the LTS-backport kernels in the archive it might be worthwhile to build against them if it's easy enough.

¹: https://code.launchpad.net/~vanvugt/ubuntu/lucid/nvidia-graphics-drivers/fix-627022/+merge/66255

Changed in nvidia-graphics-drivers-96 (Ubuntu Lucid):
assignee: nobody → Daniel van Vugt (vanvugt)
status: New → In Progress
Changed in nvidia-graphics-drivers (Ubuntu Lucid):
assignee: nobody → Daniel van Vugt (vanvugt)
status: New → In Progress
Revision history for this message
Alberto Milone (albertomilone) wrote :

The LTS-backport kernels provide a good use case for adding the patch. Please go on with the upload.

Revision history for this message
dx9s (dx9s) wrote :

I also reported a pretty much duplicate issue with this in #836349 ... looks like this has been ongoing for a while and is stuck on kernel API call changes... I was trying to upgrade to Ubuntu's kernel 2.6.38-10 (really need 2.6.39 as that is known to have USB 3.0 **HUB** support 38-10 might have backported that but I don't know).. I guess the only way to go is to skip to something not LTS that might have a newer / new enough kernel. YES the current kernel I have has xHCI support, and my two hard drives plug in and work (fast) but can't add a third USB 3.0 drive without a USB 3.0 hub and that support isn't added until 2.6.39 . So for me now, it's have USB 3.0 Hub support for nVidia OpenGL (and dual display) support..

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Your patience is appreciated. A fix is ready and waiting, but it has been waiting for review by other developers for about 2 months.

Also note, doing a distribution upgrade to Ubuntu 11.04 or later will also resolve this bug.

tags: added: testcase
description: updated
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Here is the debdiff for nvidia-graphics-drivers (lucid)

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

And here is the debdiff for nvidia-graphics-drivers-96 (lucid)

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

But are the debdiffs really necessary since they're identical to the above merge proposals??

Revision history for this message
Stéphane Graber (stgraber) wrote :

Pushed both to -proposed, once accepted by the SRU team you'll be asked to test them.

Thanks for contributing these.

Changed in nvidia-graphics-drivers-96 (Ubuntu Lucid):
status: In Progress → Fix Committed
Changed in nvidia-graphics-drivers (Ubuntu Lucid):
status: In Progress → Fix Committed
Revision history for this message
Elling Melle (ebmelle-j) wrote : Re: [Bug 627022] Re: 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)
Download full text (4.5 KiB)

All symptoms of problem went away after recent update.
Thanks; Elling

On Thu, Sep 22, 2011 at 4:20 PM, Stéphane Graber <email address hidden>wrote:

> Pushed both to -proposed, once accepted by the SRU team you'll be asked
> to test them.
>
> Thanks for contributing these.
>
> ** Changed in: nvidia-graphics-drivers-96 (Ubuntu Lucid)
> Status: In Progress => Fix Committed
>
> ** Changed in: nvidia-graphics-drivers (Ubuntu Lucid)
> Status: In Progress => Fix Committed
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (796091).
> https://bugs.launchpad.net/bugs/627022
>
> Title:
> 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)
>
> Status in “nvidia-graphics-drivers” package in Ubuntu:
> In Progress
> Status in “nvidia-graphics-drivers-96” package in Ubuntu:
> In Progress
> Status in “nvidia-graphics-drivers” source package in Lucid:
> Fix Committed
> Status in “nvidia-graphics-drivers-96” source package in Lucid:
> Fix Committed
> Status in Gentoo Linux:
> Fix Released
>
> Bug description:
> IMPACT:
>
> The NVIDIA driver fails to build on Ubuntu 10.04 LTS if you have
> upgraded your kernel to >= 2.6.36. The offending kernel change was
> commit b19dd42faf413b4705d4adb38521e82d73fa4249 in 2.6.36 stable.
>
>
> TEST CASE:
>
> Starting with a clean Ubuntu 10.04 installation...
> sudo apt-add-repository ppa:kernel-ppa/ppa && sudo apt-get update
> sudo apt-get install linux-image-generic-lts-backport-natty
> linux-headers-generic-lts-backport-natty
> sudo apt-get install nvidia-current
> Installation of nvidia-current will fail for the newer kernel. Now to
> verify it's the same error at nv.c:417:
> tail /var/lib/dkms/nvidia-current/*/build/make.log
> ("error: unknown field ‘ioctl’ specified in initializer")
>
>
> FIX:
>
> ifdef out the deprecated structure field, which is no longer present
> in Linux kernels >= 2.6.36. NVIDIA have already implemented a similar
> fix upstream, apparently in driver version ~260.19.06 onward.
>
>
> NOTES:
>
> This seems to be the same bug in both the 96 and 195 series nvidia
> drivers:
> nv.c:244 (nvidia-96 96.43.17-0ubuntu1) == nv.c:417 (nvidia-current
> 195.36.24-0ubuntu1~10.04)
>
>
> REGRESSION POTENTIAL:
>
> Low. We are only #ifdef'ing out a structure member that no longer
> exists. Its replacement is already present in both newer and older
> kernels, and is used (redundantly) by the NVIDIA driver source because
> the removal of the 'ioctl' field had been planned for a long time.
>
>
> ORIGINAL BUG REPORT:
>
> ProblemType: Package
> DistroRelease: Ubuntu 10.04
> Package: nvidia-current 195.36.24-0ubuntu1~10.04
> ProcVersionSignature: Ubuntu 2.6.35-19.25~lucid1-generic 2.6.35.3
> Uname: Linux 2.6.35-19-generic x86_64
> NonfreeKernelModules: nvidia
> Architecture: amd64
> Date: Mon Aug 30 15:20:49 2010
> ErrorMessage: nvidia-current kernel module failed to build
> InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64
> (20100427.1)
> Lsusb:
> ...

Read more...

Revision history for this message
Martin Pitt (pitti) wrote : Please test proposed package

Hello martyfelker, or anyone else affected,

Accepted nvidia-graphics-drivers into lucid-proposed, the package will build now and be available in a few hours. Please test and give feedback here. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you in advance!

tags: added: verification-needed
Revision history for this message
Martin Pitt (pitti) wrote :

Hello martyfelker, or anyone else affected,

Accepted nvidia-graphics-drivers-96 into lucid-proposed, the package will build now and be available in a few hours. Please test and give feedback here. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you in advance!

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Verification done using the test case in the description. I downloaded the (i386) packages directly:
https://launchpad.net/ubuntu/lucid/i386/nvidia-current/195.36.24-0ubuntu1~10.04.1
https://launchpad.net/ubuntu/lucid/i386/nvidia-96/96.43.17-0ubuntu1.1

However this was done in a VM as I no longer have nvidia hardware. Someone with actual nvidia hardware needs to test the packages too.

Revision history for this message
Zerin Sakech (zerinsakech) wrote : Re: [Bug 627022] Re: 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)
Download full text (4.9 KiB)

ok, so I reinstalled Ubuntu 10.04.1 64bit (added the pre-released updates
source) and did the all the normal updates, including the 2.6.32-34-generic
kernel upgrade. then I installed the recommended hardware drivers from the
GUI. Everything seemed to work perfectly fine the way a casual user might do
it. It installed the 195.36.24 nvidia drivers for my gts 250 nvidia. If you
need any more info, tell me.

On Mon, Oct 3, 2011 at 11:58 PM, Daniel van Vugt <email address hidden> wrote:

> Verification done using the test case in the description. I downloaded the
> (i386) packages directly:
>
> https://launchpad.net/ubuntu/lucid/i386/nvidia-current/195.36.24-0ubuntu1~10.04.1
> https://launchpad.net/ubuntu/lucid/i386/nvidia-96/96.43.17-0ubuntu1.1
>
> However this was done in a VM as I no longer have nvidia hardware.
> Someone with actual nvidia hardware needs to test the packages too.
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (787838).
> https://bugs.launchpad.net/bugs/627022
>
> Title:
> 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)
>
> Status in “nvidia-graphics-drivers” package in Ubuntu:
> In Progress
> Status in “nvidia-graphics-drivers-96” package in Ubuntu:
> In Progress
> Status in “nvidia-graphics-drivers” source package in Lucid:
> Fix Committed
> Status in “nvidia-graphics-drivers-96” source package in Lucid:
> Fix Committed
> Status in Gentoo Linux:
> Fix Released
>
> Bug description:
> IMPACT:
>
> The NVIDIA driver fails to build on Ubuntu 10.04 LTS if you have
> upgraded your kernel to >= 2.6.36. The offending kernel change was
> commit b19dd42faf413b4705d4adb38521e82d73fa4249 in 2.6.36 stable.
>
>
> TEST CASE:
>
> Starting with a clean Ubuntu 10.04 installation...
> sudo apt-add-repository ppa:kernel-ppa/ppa && sudo apt-get update
> sudo apt-get install linux-image-generic-lts-backport-natty
> linux-headers-generic-lts-backport-natty
> sudo apt-get install nvidia-current
> Installation of nvidia-current will fail for the newer kernel. Now to
> verify it's the same error at nv.c:417:
> tail /var/lib/dkms/nvidia-current/*/build/make.log
> ("error: unknown field ‘ioctl’ specified in initializer")
>
>
> FIX:
>
> ifdef out the deprecated structure field, which is no longer present
> in Linux kernels >= 2.6.36. NVIDIA have already implemented a similar
> fix upstream, apparently in driver version ~260.19.06 onward.
>
>
> NOTES:
>
> This seems to be the same bug in both the 96 and 195 series nvidia
> drivers:
> nv.c:244 (nvidia-96 96.43.17-0ubuntu1) == nv.c:417 (nvidia-current
> 195.36.24-0ubuntu1~10.04)
>
>
> REGRESSION POTENTIAL:
>
> Low. We are only #ifdef'ing out a structure member that no longer
> exists. Its replacement is already present in both newer and older
> kernels, and is used (redundantly) by the NVIDIA driver source because
> the removal of the 'ioctl' field had been planned for a long time.
>
>
> ORIGINAL BUG REPORT:
>
> ProblemType: Package
> DistroRelease: Ubuntu 10.04
> Pac...

Read more...

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Thanks Zerin.

Could you please run this command so we can verify the package version you're using?

    dpkg -l | grep nvidia

And then attach the output to this bug?

Revision history for this message
Zerin Sakech (zerinsakech) wrote :

zerin@zerin-nvidiatest:~$ dpkg -l | grep nvidia
ii nvidia-173-modaliases 173.14.22-0ubuntu11 Modaliases for the NVIDIA binary X.Org drive
ii nvidia-96-modaliases 96.43.17-0ubuntu1.1 Modaliases for the NVIDIA binary X.Org drive
ii nvidia-common 0.2.23 Find obsolete NVIDIA drivers
ii nvidia-current 195.36.24-0ubuntu1~10.04.1 NVIDIA binary Xorg driver, kernel module and
ii nvidia-current-modaliases 195.36.24-0ubuntu1~10.04.1 Modaliases for the NVIDIA binary X.Org drive
ii nvidia-settings 195.36.08-0ubuntu2 Tool of configuring the NVIDIA graphics driv

Here you go, I was also wondering if i need to be on the 2.6.36 kernel for this confirmation to be valid?

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Thanks. Verification done using Nvidia GTS 250 hardware.

I have already tested the fix with kernel 2.6.36 but if you could too then that would be helpful.

tags: added: verification-done
removed: verification-needed
Revision history for this message
Elling Melle (ebmelle-j) wrote :
Download full text (9.6 KiB)

I am in the habit of installing all updates from Canonical as soon as
available, and noted some time ago that the problem no longer seemed to
exist after a routine update. Unfortunately I did not note the date or time
of the update that did the trick.

On Tue, Oct 11, 2011 at 11:09 PM, Zerin Sakech <email address hidden>wrote:

> ok, so I reinstalled Ubuntu 10.04.1 64bit (added the pre-released updates
> source) and did the all the normal updates, including the 2.6.32-34-generic
> kernel upgrade. then I installed the recommended hardware drivers from the
> GUI. Everything seemed to work perfectly fine the way a casual user might
> do
> it. It installed the 195.36.24 nvidia drivers for my gts 250 nvidia. If you
> need any more info, tell me.
>
>
> On Mon, Oct 3, 2011 at 11:58 PM, Daniel van Vugt <email address hidden>
> wrote:
>
> > Verification done using the test case in the description. I downloaded
> the
> > (i386) packages directly:
> >
> >
> https://launchpad.net/ubuntu/lucid/i386/nvidia-current/195.36.24-0ubuntu1~10.04.1
> > https://launchpad.net/ubuntu/lucid/i386/nvidia-96/96.43.17-0ubuntu1.1
> >
> > However this was done in a VM as I no longer have nvidia hardware.
> > Someone with actual nvidia hardware needs to test the packages too.
> >
> > --
> > You received this bug notification because you are subscribed to a
> > duplicate bug report (787838).
> > https://bugs.launchpad.net/bugs/627022
> >
> > Title:
> > 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)
> >
> > Status in “nvidia-graphics-drivers” package in Ubuntu:
> > In Progress
> > Status in “nvidia-graphics-drivers-96” package in Ubuntu:
> > In Progress
> > Status in “nvidia-graphics-drivers” source package in Lucid:
> > Fix Committed
> > Status in “nvidia-graphics-drivers-96” source package in Lucid:
> > Fix Committed
> > Status in Gentoo Linux:
> > Fix Released
> >
> > Bug description:
> > IMPACT:
> >
> > The NVIDIA driver fails to build on Ubuntu 10.04 LTS if you have
> > upgraded your kernel to >= 2.6.36. The offending kernel change was
> > commit b19dd42faf413b4705d4adb38521e82d73fa4249 in 2.6.36 stable.
> >
> >
> > TEST CASE:
> >
> > Starting with a clean Ubuntu 10.04 installation...
> > sudo apt-add-repository ppa:kernel-ppa/ppa && sudo apt-get update
> > sudo apt-get install linux-image-generic-lts-backport-natty
> > linux-headers-generic-lts-backport-natty
> > sudo apt-get install nvidia-current
> > Installation of nvidia-current will fail for the newer kernel. Now to
> > verify it's the same error at nv.c:417:
> > tail /var/lib/dkms/nvidia-current/*/build/make.log
> > ("error: unknown field ‘ioctl’ specified in initializer")
> >
> >
> > FIX:
> >
> > ifdef out the deprecated structure field, which is no longer present
> > in Linux kernels >= 2.6.36. NVIDIA have already implemented a similar
> > fix upstream, apparently in driver version ~260.19.06 onward.
> >
> >
> > NOTES:
> >
> > This seems to be the same bug in both the 96 and 195 series nvidia
> > drivers:
> > nv.c:244 (nvid...

Read more...

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package nvidia-graphics-drivers - 195.36.24-0ubuntu1~10.04.1

---------------
nvidia-graphics-drivers (195.36.24-0ubuntu1~10.04.1) lucid-proposed; urgency=low

  * Fix nv.c build failure with kernels >= 2.6.36 (LP: #627022)
 -- Daniel van Vugt <email address hidden> Wed, 29 Jun 2011 14:48:22 +0800

Changed in nvidia-graphics-drivers (Ubuntu Lucid):
status: Fix Committed → Fix Released
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package nvidia-graphics-drivers-96 - 96.43.17-0ubuntu1.1

---------------
nvidia-graphics-drivers-96 (96.43.17-0ubuntu1.1) lucid-proposed; urgency=low

  * Fix nv.c build failure with kernels >= 2.6.36 (LP: #627022)
 -- Daniel van Vugt <email address hidden> Wed, 29 Jun 2011 17:08:13 +0800

Changed in nvidia-graphics-drivers-96 (Ubuntu Lucid):
status: Fix Committed → Fix Released
Changed in nvidia-graphics-drivers-96 (Ubuntu):
status: In Progress → Fix Released
Changed in nvidia-graphics-drivers (Ubuntu):
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.