Bug#763272: workaround

Vincent Cheng vcheng at debian.org
Sun Oct 5 10:17:16 UTC 2014

Control: forwarded -1 https://github.com/Bumblebee-Project/Bumblebee/issues/592

On Sun, Sep 28, 2014 at 2:05 PM, Robert Lange <rcl24 at drexel.edu> wrote:
> I found a reference to the same issue from an Arch user:
> https://github.com/Bumblebee-Project/Bumblebee/issues/592
> The workaround given was to append acpi_osi=\"!Windows 2013\" to the
> GRUB_CMDLINE_LINUX_DEFAULT variable in /etc/default/grub and run
> update-grub.
> After doing this, bumblebee is again able to toggle the discrete chip on and
> off.

If it's really a kernel/ACPI issue like the above bug report suggests,
then there's nothing I can do as bbswitch/bumblebee maintainer to fix
this, sorry. Consider filing a bug report against the kernel.


More information about the pkg-nvidia-devel mailing list