glx-alternative and bumblebee in jessie-backports
luca.boccassi at gmail.com
Sun Jun 26 20:22:13 UTC 2016
On Thu, 2016-06-23 at 18:01 +0200, Andreas Beckmann wrote:
> On 2016-06-19 19:21, Luca Boccassi wrote:
> > Andreas, Vincent,
> > bumblebee 3.1.2-13 has migrated to testing yesterday, and today I've
> > uploaded it to jessie-backports. This will hide false negative error
> > logs, fix all kernel module loading problems, and fix compatibility with
> > the legacy-YYYxx drivers.
> > When you have time and if you don't mind, could you please either upload
> > to backports glx-alternative or whitelist my GPG key so that I can take
> > care of it myself? I have added a trigger to glx-alternative-nvidia to
> > restart bumblebee when switching the nvidia provider, as bumblebee needs
> > to restart to pick up the change to libGLX and the kernel module.
> I'll be offline for the weekend. if you have some time, could you test
> some of the glvnd reorganization I did for 361? no guarantee that it
> works at all, it just builds :-)
Just tried it, looks good to me.
Shall we push it up to experimental? Seeing how long it's taking for
355.11-3 to get through the NEW queue, I'm beginning to be quite worried
that if we wait for 355.11-3 to be accepted first and then have to wait
another 6 months to get the new binary packages in 361 approved
separately we might miss the Stretch deadline...
> PS: is there anything we may have to patch for Linux 4.7?
Pushed a couple patches for 361, 364 and 367 (will have to merged up).
304, 340 and 352 are OK as they are.
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 819 bytes
Desc: This is a digitally signed message part
More information about the pkg-nvidia-devel