FS#47150 - With NVIDIA 358.16-2.1 Drivers, Card is not properly turned off afterwards
Attached to Project:
Community Packages
Opened by Jacob S (Gourdcaptain) - Sunday, 22 November 2015, 20:21 GMT
Last edited by Doug Newgard (Scimmia) - Sunday, 22 November 2015, 21:06 GMT
Opened by Jacob S (Gourdcaptain) - Sunday, 22 November 2015, 20:21 GMT
Last edited by Doug Newgard (Scimmia) - Sunday, 22 November 2015, 21:06 GMT
|
Details
Description:
On my laptop with a NVIDIA 950m, after upgrading to 358.16-2.1, Bumblebee fails to unload the modules and turn off the card after the app run with optirun closes. This is due to the new nvidia_modeset module, then the nvidia module, needing to be unloaded before it will allow me to use bbswitch to turn off the card manually. Additional info: bumblebee version: 3.2.1-10 NVIDIA driver: 358.16-2.1 bbswitch version: 0.8-38 Steps to reproduce: optirun glxgears According to the bumblebee bug tracker this has something to do with module aliases? https://github.com/Bumblebee-Project/Bumblebee/issues/565 - Similar issue when the nvidia-uvm issue was new. https://github.com/Bumblebee-Project/Bumblebee/issues/691 - One on nvidia-modset. Sorry, I'm not entirely sure where to submit this one. |
This task depends upon
Closed by Doug Newgard (Scimmia)
Sunday, 22 November 2015, 21:06 GMT
Reason for closing: Duplicate
Additional comments about closing: FS#47140
Sunday, 22 November 2015, 21:06 GMT
Reason for closing: Duplicate
Additional comments about closing: