splitting off nvidia-graphics-drivers-legacy-340xx

[Luca Boccassi]

On Mon, 2015-08-03 at 11:07 +0100, Luca Boccassi wrote:
> On Mon, 2015-08-03 at 11:23 +0200, Andreas Beckmann wrote:
> > On 2015-08-03 02:26, Luca Boccassi wrote:
> > 
> > >> * renaming the nvidia-uvm.ko module
> > >>
> > >> These shouldn't be cherry-picked into experimental until they are
> > >> finished and working. Especially for renaming the kernel module I could
> > >> need some help for testing that this works properly ...
> > > 
> > > I'll gladly help out, I have 2 machines with Nvidia hardware and one
> > > is a laptop,
> > > so very handy for testing the nvidia uvm + cuda + bumblebee combination.
> > 
> > I commited something, that could (should) work theoretically :-)
> > 
> > To be tested would be 'modprobe' and 'modprobe -r' on the real and alias
> > names of the modules:
> > * nvidia
> > * nvidia-current
> > * nvidia-uvm
> > * nvidia-current-uvm
> > Check with lsmod whether that causes the correct module(s) to be loaded.
> > Despite of the filename that was changed to nvidia-current{,-uvm}.ko the
> > internal name of the module has not been changed (that would break
> > expectations elsewhere) [note to self: document this :-)], so lsmod will
> > only show 'nvidia' and 'nvidia-uvm'.
> 
> Perfect, will try later tonight or tomorrow night.

So installed 340.76-4 on my desktop, and everything seemed fine.

The new module can be loaded and unloaded just fine:

$ lsmod | grep nvidia
nvidia              10514432  53 
drm                   274432  5 i915,drm_kms_helper,nvidia
$ sudo modprobe nvidia-current-uvm 
[sudo] password for luca: 
$ lsmod | grep nvidia
nvidia_uvm             36864  0 
nvidia              10514432  54 nvidia_uvm
drm                   274432  5 i915,drm_kms_helper,nvidia 
$ sudo modprobe -r nvidia_uvm 
$ lsmod | grep nvidia
nvidia              10514432  53 
drm                   274432  5 i915,drm_kms_helper,nvidia
$ sudo modprobe nvidia-current-uvm 
$ sudo modprobe -r nvidia-current-uvm
$ lsmod | grep nvidia
nvidia              10514432  53 
drm                   274432  5 i915,drm_kms_helper,nvidia

I do not have a CUDA setup here, tomorrow evening I'll try on my laptop.

Any more tests you would like to see done?

> > Which raises the question: on non-uvm architectures (e.g. experimental
> > driver (or just >= 346) on i386), does the modprobe remove hook cause
> > errors since it tries to rmmod a module that's not loaded?
> 
> Very good point. I do not have an i386 install with Nvidia HW. I have
> never tried, can the modules be loaded in a VM where there is no HW
> available? I'll give it a try later tonight or tomorrow.

I tried with some random modules, and the same test works just fine:
modprobe random_mod ; modprobe -r random_not_loaded_mod random_mod

An error is printed, but random_mod is removed nonetheless.

> > BTW, can the kernel module even be built on armhf in jessie?
> 
> I have tried on a Sid chroot only, where the 4.0 module builds fine
> (after the CONFIG_XEN hack). I will create a Jessie one and try again
> later tonight or tomorrow and report back, but building for 3.16 on Sid
> does not work due to this error:
> 
> FATAL: modpost: GPL-incompatible module nvidia.ko uses GPL-only symbol
> 'xen_start_info'

The workaround for this error is to remove CONFIG_XEN altogether. Then
the armhf module builds fine in a Sid chroot with 3.16 too.

Kind regards,
Luca Boccassi
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: This is a digitally signed message part
URL: <http://lists.alioth.debian.org/pipermail/pkg-nvidia-devel/attachments/20150803/19d6b889/attachment.sig>