Bug#813848: bumblebee: bbswitch will not disable nvidia card after optirun finishes.
Luca Boccassi
luca.boccassi at gmail.com
Sat Feb 6 11:38:06 UTC 2016
Control: tag -1 moreinfo unreproducible
On Fri, 2016-02-05 at 23:05 +0000, Gary Preston wrote:
> Package: bumblebee
> Version: 3.2.1-10~bpo8+1
> Severity: normal
>
> Dear Maintainer,
>
> * What led up to the situation?
>
> Installed nvidia-kernel-dkms 352 from jessie-backports.
>
> * What exactly did you do (or not do) that was effective (or
> ineffective)?
>
> After installation, rebooted and found that after running
> optirun for the first time, /proc/acpi/bbswitch would still
> report ON after optirun had finished.
>
> Stopping the bumblebeed service and "rmmod nvidia" then running
> bumblebeed -vv showed everything was normal during start up,
> however upon quitting optirun the log shows:
>
>
> [ 341.192631] [DEBUG]Socket closed.
> [ 341.192746] [DEBUG]Socket closed.
> [ 341.192751] [INFO]Stopping X server
> [ 341.264275] [DEBUG]Process with PID 3275 returned code 0
> [ 341.264357] [INFO]Unloading nvidia driver
> [ 341.264443] [DEBUG]Process modprobe started, PID 3296.
> modprobe: FATAL: Module nvidia not found.
> [ 341.264997] [DEBUG]Process with PID 3296 returned code 1
> [ 344.270780] [ERROR]Unloading nvidia driver timed out.
> [ 344.270810] [DEBUG]Drivers are still loaded, unable to disable card
> [ 344.270823] [DEBUG][XORG] (II) UnloadModule: "mouse"
> [ 344.270826] [DEBUG][XORG] (II) NVIDIA(GPU-0): Deleting GPU-0
> [ 344.270828] [DEBUG][XORG] (EE) Server terminated successfully (0).
> Closing log file.
>
> The "nvidia" kernel module remained loaded and bbswitch was
> unable to switch the nvidia card to OFF. Running "modprobe -r
> nvidia" manually brought up the same error, instead I had to
> run either:
>
> modprobe -r nvidia-current
>
> or
>
> rmmod nvidia
>
> If I create a sym link from nvidia-current.ko to nvidia.ko and
> from nvidia-current-uvm.ko to nvidia-uvm.ko then run depmod -a
> everything then works as expected.
>
> /etc/nvidia/nvidia-modprobe.conf contains what looks to be
> suitable aliases to allow modprobe -r nvidia to unload
> nvidia-current however I'm not sure if that file is loaded or
> how to check.
>
> Either way, it looks like bumblebee is unable to unload the
> nvidia module that was loaded via nvidia-current and in turn
> that is causing bbswitch to be unable to disable the dedicated
> graphics card.
Hi,
Unfortunately I'm unable to reproduce on my jessie optimus laptop.
You mentioned that you installed "nvidia-kernel-dkms". Why only the DKMS
package and not everything else? Please install nvidia-driver to make
sure everything is correctly pulled down.
If all the packages are from the 352.79 backported version and the
problem still persists, please attach the result of:
reportbug --template nvidia-driver
Kind regards,
Luca Boccassi
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: This is a digitally signed message part
URL: <http://lists.alioth.debian.org/pipermail/pkg-nvidia-devel/attachments/20160206/353a0455/attachment-0001.sig>
More information about the pkg-nvidia-devel
mailing list