bumblebee-nvidia stuff

Andreas Beckmann anbe at debian.org
Mon Oct 19 14:32:47 UTC 2015


Hi,

looking at nvidia-bumblebee again, I don't see support for the legacy
drivers we have in Debian ...

Depends: ${shlibs:Depends}, ${misc:Depends}, bumblebee (=
${binary:Version}),
# proprietary NVIDIA packages in Debian
 nvidia-driver | nvidia-glx | nvidia-kernel-dkms | nvidia-kernel-amd64 |
 nvidia-kernel-686-pae | nvidia-kernel-486 |

Also I don't understand why there is a list of kernel module packages
here, don't you need both
 * the nvidia.ko kernel module (or however it is named currently) and
 * the nvidia lib*GL* libraries (but not in the default searchpath)
to run bumblebee stuff with the proprietary nvidia driver backend?

Should /etc/modprobe.d/bumblebee.conf be integrated with the glx
alternative (via the nvidia/bumblebee variant)? So switching
bumblebee(-nvidia) on and off could also happen via the glx alternative
(+ some trigger activation+processing).

Maybe the modprobe configuration should be split into
  bumblebee-blacklists-nouveau.conf
  bumblebee-blacklists-nvidia.conf
and be moved to /etc/bumblebee with symlinks being placed in modprobe.d
via some alternative :-) (see glx-alternative-nvidia/fglrx if the actual
file (and not a dangling symlink) is required to be present in the
initrd). That would also solve the leaves-a-conffile in modprobe.d after
purge issues. I doubt LP: #1242785 is fixed with the current postinst ...

No clue how bumblebee with nouveau as backend works.
I don't know much about bumblebee, having no hardware that requires it
:-)

Andreas



More information about the pkg-nvidia-devel mailing list