Bug#717687: bumblebee: cannot activate the discrete nvidia card

[LOMBARD Maxime]

The driver 304.88-6 in Sid has the same kernel 3.10 patch than the
experimental driver. I don't think that the kernel has the cause but only
the module rename.
I'll open a bug report about this module rename.


2013/8/5 Maurizio Avogadro <mavoga at gmail.com>

> Hi,
>
> interestingly enough, I experienced the same issue only when I upgraded
> from 319.32-1 to 319.32-2; one of the main  differences between these 2
> versions (while not documented in the Debian changelog AFAICS: is it one
> of the changes merged from 304.88-7?) is the module rename: that is,
> very likely, the reason of the issue. I now reinstalled the 319.32-1 and
> bumblebee now works again even with kernel 3.10 (I'm manually applying
> the patch at http://pastebin.com/JDpkR3kt, which I strongly suggest
> since the other patches don't remove the /proc/driver/nvidia upon module
> removal, which causes a kernel oops when the nvidia module is loaded the
> next time).
>
>
> Maurizio
>
>
> Il 04/08/2013 18:19, LOMBARD Maxime ha scritto:
> > Hi guys, I found something.
> >
> > If you install Nvidia 304.88 package, the module is named : nvidia.ko
> > but the module for the Nvidia 319.32 package is named : nvidia-current.ko
> >
> > Even if i modify "/etc/bumblebee/bumblebee.conf" to replace
> > "KernelDriver=nvidia" by "KernelDriver=nvidia-current", this bug
> > always exist.
> >
> > I create a bug report on bumblebee github :
> > https://github.com/Bumblebee-Project/Bumblebee/issues/452 and for
> > them, it's a kernel 3.10 problem.
> >
> > So, i tried the experimental Nvidia driver + Kernel 3.9 from Testing
> > and the same bug exist.
> >
> > Andreas, if you read this bug report, it can be possible to re-package
> > Nvidia 319.32 driver to modify the module name ?
> >
> > Thanks,
> > Max
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/pkg-nvidia-devel/attachments/20130805/19582b28/attachment.html>