bumblebee team mailing list archive

[Robin Battey <ubuntu@xxxxxxxxxx>]

Oops, you're quite right, the /etc/init/hybrid-gfx.conf is put there
by nvidia-common, not nvidia-current.  However, it *does* change the
nvidia driver via the alternatives system, which could cause
bumblebeed to (try to) use a different driver than actually used by
the system upon graphical UI invocation, if new drivers have been
installed.  I expect it could also turn on the card, or fail due to it
being off unexpectedly, or a variety of other things if bumblebeed
starts first.

In any case, starting bumblebeed right *after* the graphical UI is
displayed appears to fix all problems.  Thanks for accepting the
patch.  :-)

Cheers!
-robin

On Mon, Oct 29, 2012 at 6:47 AM, Lekensteyn <lekensteyn@xxxxxxxxx> wrote:
> On Monday 29 October 2012 05:09:11 Robin Battey wrote:
>> I was unable to get bumblebeed to function at all on quantal (video driver
>> issues in 3.5), so I can't say. I would be surprised if it was different,
>> though. I believe the change that broke things as they stand was in upstart
>> script from the nvidia-current package, and the x-updates ppa is
>> nearly-official packages intended to be put into quantal proper (so saith
>> the ppa blurb). If it isn't broken in quantal right now, it will be when
>> the new drivers hit main.
> The video driver should not matter since it does not get loaded by bumblebeed
> on boot, it only disables the nvidia card when bumblebeed starts. That could
> cause issues with the hybrid graphics detection script supplied by some
> package (nvidia-common?). I assumed that you were using Quantal, but now I see
> it is just Precise.
>
>> And yes, I've been running with my proposed edit for at least 50 reboots so
>> far (it's amazing how many times you reboot when testing quirky
>> hibernation...), and the issue hasn't resurfaced.
> Thanks for confirming.
>
> Regards,
> Peter