Arch Linux

Upstream: https://github.com/Bumblebee-Project/bbswitch/issues/116

Setup info:

01:00.0 VGA compatible controller: NVIDIA Corporation GF108M GeForce GT 630M (prog-if ff)
!!! Unknown header type 7f
Kernel modules: nouveau, nvidia

[tomasz@arch ~]$ dmesg |grep bbsw
[ 2.540830] bbswitch: version 0.8
[ 2.540836] bbswitch: Found integrated VGA device 0000:00:02.0: _SB_.PCI0.GFX0
[ 2.540844] bbswitch: Found discrete VGA device 0000:01:00.0: _SB_.PCI0.PEG0.PEGP
[ 2.540951] bbswitch: detected an Optimus _DSM function
[ 2.540968] bbswitch: Succesfully loaded. Discrete card 0000:01:00.0 is on
[ 2.547654] bbswitch: disabling discrete graphics
[ 23.418246] bbswitch: enabling discrete graphics
[ 566.226540] bbswitch: disabling discrete graphics

NOTE: if I manually unload the nvidia-modeset module, then bbswitch will turn off GPU.

I have MANY warnings about

[ 29.372971] ACPI Warning: _SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires Package

but I just ignore this:
THIS is log how new nvidia-modeset module works instead nvidia:

[ 23.418246] bbswitch: enabling discrete graphics
[ 23.904334] nvidia: module license 'NVIDIA' taints kernel.
[ 23.904339] Disabling lock debugging due to kernel taint
[ 23.911959] vgaarb: device changed decodes: PCI:0000:01:00.0,olddecodes=io+mem,decodes=none:owns=none
[ 23.912049] nvidia-nvlink: Nvlink Core is being initialized, major device number 246
[ 23.912146] [drm] Initialized nvidia-drm 0.0.0 20150116 for 0000:01:00.0 on minor 1
[ 23.912150] NVRM: loading NVIDIA UNIX x86_64 Kernel Module 358.16 Mon Nov 16 19:25:55 PST 2015
[ 24.442745] nvidia-modeset: Loading NVIDIA Kernel Mode Setting Driver for UNIX platforms 358.16 Mon Nov 16 18:58:09 PST 2015
[ 24.851888] nvidia-modeset: Allocated GPU:0 (GPU-d6b03ef8-5883-7f16-ebcf-26ba8a9815ca) @ PCI:0000:01:00.0
[ 24.853907] ACPI Warning: _SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires Package
[ 29.348982] nvidia-modeset: Freed GPU:0 (GPU-d6b03ef8-5883-7f16-ebcf-26ba8a9815ca) @ PCI:0000:01:00.0
[ 546.533540] nvidia-modeset: Unloading

In this situation I unload nvidia-modeset module manually via sudo modprobe -r nvidia-modeset

Regards

UPDATE: all nvidia 358.16 install nvidia-modeset module, and bbswitch not working fine with it.

UPDATE: It is a bumblebee issue - not bbswitch.

https://github.com/Bumblebee-Project/Bumblebee/issues/699

The problem is later in that bug report you linked they say it's an issue that needs to be fixed with a udev rule. At this point I'm not sure who should be taking responsibility for fixing this.

Hard FIX patch: https://github.com/arafey/Bumblebee/commit/5636b24fa86a005a5d2e30bd794516db13ccba56
Working for me dmesg: https://pastebin.com/raw.php?i=MbWrYV0y

I updated my patch to detect nvidia_modeset, rather than assuming it's loaded: https://github.com/arafey/Bumblebee/commit/09d537e8e5313cd0f2c7bf6620ca70454de8a04a

In my case, it's not just the nvidia_modeset module that causes issues.
My system also loades a nvidia_uvm module that needs to be unloaded first.

Some guy on github proposed this as a temporary hack:
https://github.com/Bumblebee-Project/Bumblebee/pull/709#issuecomment-167376709

I tested it out, and it works for me.
journalctl output: https://pastebin.com/raw/7uStwwvz

What's the status on this? Upstream still unwilling to fix this upstream? In that case, I will downstream patch this.

@Sven
Please see PKGBUILD and patches: https://github.com/FadeMind/archpkgbuilds/tree/master/AUR/nvidia-optimus/bumblebee

Working for me like a charm.

Tomasz's patches and PKGBUILD he linked are working for me on nvidia driver 361.28-1 with a GTX 950m.

Tomasz's patches and PKGBUILD are working for me too.

Bumblebee PKGBUILD with patches for hard workaround issue  FS#47140 .

Please apply the patch on the Arch package, there is no progress on fixing this upstream. It is annoying to have to unload the module manually every time I boot my computer and every time I use primusrun.

FadeMind, could you please modify your patches to properly unload the new nvidia-drm module that is found in the last version of the nvidia driver, now in testing?
It seems that the GPU is never turned off due to that new module not being unloaded.

AnAkkk (AnAkkk) asking directly https://github.com/arafey about this, He is author of this hard workaround.

I will load the testing version of the Nvidia driver in order to test a new version of the workaround with that driver tonight. I'll post a link here when I upload it to Github.

PKGBUILD bumblebee with patches for handling nvidia-drm nvidia-modeset and nvidia-uvm modules.

Patches credits: Abuzer Rafey (arafey)

Here is the patch to fix issues with nvidia 364.16. You can also pull it from the master branch of https://github.com/arafey/Bumblebee
Let me know how it works.

EDIT: FadeMind, I just saw your new PKGBUILD after refreshing my browser. The new commit I linked is a cleaner version of the one from 2 hours ago.

PKGBUILD bumblebee with patches for handling nvidia-drm nvidia-modeset and nvidia-uvm modules.

REVISION 2 included https://github.com/arafey/Bumblebee/commit/fcfe596eb13f62ca9dd7de272a5a87ae843b2a00 PATCH

Patches credits: Abuzer Rafey (arafey)

TESTED ON MY DEVICE = ALL IS FINE

Hi,

I have the same problem with 364.16 and I see there is a patch for the issue. This patch is going to be added official package or do I have to compile own with the patch?

@Cihat Ertem (fincan) -

Download tarball and compile own.
I don't see any news from maintainer bumblebee in Arch Repo for official fix way.

Thx, I compiled the package with patch and it works perfectly!

I applied the patches to the bumblebee package taken from FadeMind's package. However, the changes to bumblebee.install are unacceptable and will not be added. Please test package rel -11.

JFYI, upstream will be patched, whenever I get time to look at this. That’s probably going to be around may 5th-8th. ;)

Works fine after the update.