FS#47140 - [bumblebee] can not handle nvidia-modeset.ko
Attached to Project:
Community Packages
Opened by Tomasz Przybył (FadeMind) - Saturday, 21 November 2015, 19:53 GMT
Last edited by Sven-Hendrik Haase (Svenstaro) - Friday, 15 April 2016, 13:41 GMT
Opened by Tomasz Przybył (FadeMind) - Saturday, 21 November 2015, 19:53 GMT
Last edited by Sven-Hendrik Haase (Svenstaro) - Friday, 15 April 2016, 13:41 GMT
|
Details
If nvidia-modeset.ko is installed then bbswitch can't unload
a nvidia-modeset module and turn off NVIDIA GPU cause
nvidia-modeset is used instead of nvidia module.
Normal nvidia package don't have installed nvidia-modeset.ko and it is NOT AFFECTED. Commit: https://projects.archlinux.org/svntogit/packages.git/commit/trunk?h=packages/nvidia-lts&id=8d09af1d2085ce990358200ad9a74cc475ae1694 I will report this upstream on github. NVIDIA 358.16. BBSWITCH upstream 0.8 release. |
This task depends upon
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
https://github.com/Bumblebee-Project/Bumblebee/issues/699
Working for me dmesg: https://pastebin.com/raw.php?i=MbWrYV0y
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
Please see PKGBUILD and patches: https://github.com/FadeMind/archpkgbuilds/tree/master/AUR/nvidia-optimus/bumblebee
Working for me like a charm.
FS#47140.It seems that the GPU is never turned off due to that new module not being unloaded.
Patches credits: Abuzer Rafey (arafey)
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.
REVISION 2 included https://github.com/arafey/Bumblebee/commit/fcfe596eb13f62ca9dd7de272a5a87ae843b2a00 PATCH
Patches credits: Abuzer Rafey (arafey)
TESTED ON MY DEVICE = ALL IS FINE
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?
Download tarball and compile own.
I don't see any news from maintainer bumblebee in Arch Repo for official fix way.