Comment 8 for bug 1231725

Sorry for the delay…

I meant, it’s recommended only when you don’t use bumblebeed, but do you think it can cause any harm if installed for everyone? For instance, can this conflict with the setting in bumblebeed?

Currently, bumblebeed starts, loads bbswitch, and shutdown the card. Right? On exit (with "TurnCardOffAtExit=false" which is the default and that I suspect to be set like that in above case, without preventing the issue to happen for an unknown reason)

If I have /etc/modprobe.d/bbswitch.conf with "options bbswitch load_state=1 unload_state=1" and I start bumblebeed, bbswitch won’t turn off the card on start, then bumblebeed will ask him to do so, and the card will still be disabled on bumblebeed start, right?

With load_state=0, bbswitch will disable the card when modprobed for bumblebeed, then bumblebeed will see the card is already disabled and won’t ask bbswitch to turn it off, correct?

Next, if I stop bumblebeed, it will turn on the card and remove bbswitch, which will do nothing since the card is already ON. Does bumblebee remove bbswitch if I set "TurnCardOffAtExit=true"? If so, it seems to me to be an issue because then the card won’t be powered on again before shutdown, and even if not, having the modprobe conf file seems needed, else on shut down when bbswitch will be removed, it won’t turn ON the card, right?

Finally, similarly to this latest case, what if bumblebee get killed for any reason? Does it handle correctly bbswitch and PM in this case before being killed? I suppose not, because a killed program is not supposed to do anything, right?

So if I’m all right, I think we might ship /etc/modprobe.d/bbswitch.conf with "options bbswitch load_state=0 unload_state=1" in bbswitch-dkms package.