Bug#718774: Nvidia module rename patch break bumblebee

Vincent Cheng vincentc1208 at gmail.com
Tue Aug 6 07:14:18 UTC 2013


Hi Andreas,

On Mon, Aug 5, 2013 at 12:26 PM, Andreas Beckmann <anbe at debian.org> wrote:
> On 2013-08-05 12:16, LOMBARD Maxime wrote:
>> With this new module name, bumblebee can't activate the nvidia driver
>> because it can't load GPU driver. See Bug #717687
>
> How does bumblebee load the nvidia module?

It uses a bunch of settings in /etc/bumblebee/bumblebee.conf, i.e.

# The Driver used by Bumblebee server. If this value is not set (or empty),
# auto-detection is performed. The available drivers are nvidia and nouveau
# (See also the driver-specific sections below)
Driver=

## Section with nvidia driver specific options, only parsed if Driver=nvidia
[driver-nvidia]
# Module name to load, defaults to Driver if empty or unset
KernelDriver=nvidia

"Driver" is left unset by upstream to automatically detect whether to
load nvidia or nouveau (I have no idea how autodetection is done), and
"KernelDriver" specifies the name of the module to load.

For what it's worth, it seems that Ubuntu's Nvidia packages ship
renamed modules as well following the branch version, but bumblebee
(unchanged in Ubuntu) still works there.

Regards,
Vincent



More information about the pkg-nvidia-devel mailing list