On Thu, 21 Nov 2019 at 15:30, Andreas Beckmann <a...@debian.org> wrote: > > Hi Luca, > > On Sun, 08 Sep 2019 11:50:28 +0100 Luca Boccassi <bl...@debian.org> wrote: > > Ok scratch that, I can reproduce - it's because of the non-glvnd > > libraries. With the glvnd one there's no issue, and that's why 435 > > works - non-glvnd was removed. > > Can you check 430.64-1? If that still does not work, I'll remove the > non-glvnd binaries like in 435. And with the RC bugs gone, I might do a > buster-backports upload as well. > > Could you also verify that the latest 418.xx releases still do work in > non-glvnd mode? > > https://people.debian.org/~anbe/418.113/amd64/ > > That's the latest 418.xx upstream release. (branch 418) > > https://people.debian.org/~anbe/418.87.01/amd64/ > > That's the latest tesla driver release packaged as a regular 418.xx > release (i.e. without any "*-tesla-*" package renaming that may still > have some bugs in corner cases) (branch 418-tesla) > > > Andreas
Hi, Sorry, didn't have time till now. I've done some work to make bumblebee+primus viable with either glvnd or non-glvnd (for the legacy drivers), based on a suggestion from Felipe. See: https://github.com/Bumblebee-Project/Bumblebee/pull/1050 https://salsa.debian.org/nvidia-team/bumblebee/merge_requests/2 There are many ways to approach this, I picked the separate package with a different config file and a systemd drop-in to use it. I don't particularly mind which solution we choose and have time over the holidays to do some more work and testing if required. Thanks! Kind regards, Luca Boccassi
