我已经为这个问题苦苦挣扎了很长时间了。我刚刚将xubuntu升级到16.04,我的nvidia驱动程序又坏了。因此,像往常一样,我必须卸载所有nvidia驱动程序(我正在使用nvidia-352-updates)以及大黄蜂。因此,我做到了,然后再次执行了相同的过程(此处很少观察:我现在使用的是nvidia-361-updates):
sudo apt-get install nvidia-361-updates -y && sudo apt-get install bumblebee
OK,一切设置和我为首的/etc/bumblebee/bumblebee.conf给点LD_LIBRARY_PATH
和XorgModulePath
进入正确的NVIDIA文件夹,在我的情况nvidia-361
。之后,我只是重新启动计算机并尝试运行:
optirun glxinfo
我得到了答案:
[ranu@ranu-laptop ~]$ optirun glxinfo [ 515.027004] [ERROR]Cannot access secondary GPU, secondary X is not active. [ 515.027105] [ERROR]Aborting because fallback start is disabled.
我很惊讶,然后又跑了一个更冗长的代码(optirun -vv -debug glxinfo
):
[ 334.856357] [DEBUG]Reading file: /etc/bumblebee/bumblebee.conf [ 334.856840] [INFO]Configured driver: nvidia-361 [ 334.857253] [DEBUG]optirun version 3.2.1 starting... [ 334.857290] [DEBUG]Active configuration: [ 334.857298] [DEBUG] bumblebeed config file: /etc/bumblebee/bumblebee.conf [ 334.857305] [DEBUG] X display: ebug [ 334.857311] [DEBUG] LD_LIBRARY_PATH: [ 334.857319] [DEBUG] Socket path: /var/run/bumblebee.socket [ 334.857326] [DEBUG] Accel/display bridge: auto [ 334.857341] [DEBUG] VGL Compression: proxy [ 334.857380] [DEBUG] VGLrun extra options: [ 334.857400] [DEBUG] Primus LD Path: /usr/lib/x86_64-linux-gnu/primus:/usr/lib/i386-linux-gnu/primus [ 334.870268] [DEBUG]Using auto-detected bridge virtualgl [ 337.882765] [INFO]Response: No, secondary X is not active. [ 337.882803] [ERROR]Cannot access secondary GPU, secondary X is not active. [ 337.882817] [DEBUG]Socket closed. [ 337.882869] [ERROR]Aborting because fallback start is disabled. [ 337.882887] [DEBUG]Killing all remaining processes.
奇怪,LD_LIBRARY_PATH
即使在中填充了信息也为空/etc/bumblebee/bumblebee.conf
。所以我跑了:
bumblebeed -vv -debug
并收到输出:
[ 782.329141] [DEBUG]Found card: 01:00.0 (discrete) [ 782.329201] [DEBUG]Found card: 00:02.0 (integrated) [ 782.329236] [DEBUG]Reading file: /etc/bumblebee/bumblebee.conf [ 782.329655] [INFO]Configured driver: nvidia-361 [ 782.329684] [DEBUG]Skipping auto-detection, using configured driver 'nvidia-361' [ 782.329850] [DEBUG]successfully loaded bbswitch [ 782.329866] [INFO]Switching method 'bbswitch' is available and will be used. [ 782.329879] [DEBUG]Active configuration: [ 782.329899] [DEBUG] bumblebeed config file: /etc/bumblebee/bumblebee.conf [ 782.329919] [DEBUG] X display: ebug [ 782.329938] [DEBUG] LD_LIBRARY_PATH: [ 782.329957] [DEBUG] Socket path: /var/run/bumblebee.socket [ 782.329977] [DEBUG] pidfile: /var/run/bumblebeed.pid [ 782.329995] [DEBUG] xorg.conf file: /etc/bumblebee/xorg.conf.DRIVER [ 782.330017] [DEBUG] xorg.conf.d dir: /etc/bumblebee/xorg.conf.d [ 782.330043] [DEBUG] ModulePath: [ 782.330063] [DEBUG] GID name: bumblebee [ 782.330084] [DEBUG] Power method: auto [ 782.330104] [DEBUG] Stop X on exit: 1 [ 782.330123] [DEBUG] Driver: nvidia-361 [ 782.330142] [DEBUG] Driver module: nvidia-361 [ 782.330163] [DEBUG] Card shutdown state: 1 [ 782.330418] [DEBUG]Process /sbin/modprobe started, PID 3094. [ 782.330566] [DEBUG]Hiding stderr for execution of /sbin/modprobe [ 782.333919] [DEBUG]SIGCHILD received, but wait failed with No child processes [ 782.333969] [DEBUG]Configuration test passed. [ 782.334023] [ERROR]Cannot open or write pidfile /var/run/bumblebeed.pid.
好的,这甚至更奇怪,配置测试已经通过,但是也ModulePath
为空,我不知道为什么,最重要的是它无法写入pidfile,权限问题?
看起来Driver
大黄蜂配置文件中的条目应该为nvidia
and not nvidia-361
,尽管大黄蜂说配置测试已经通过,如前所示:
[ 782.333969] [DEBUG]Configuration test passed.
本文收集自互联网,转载请注明来源。
如有侵权,请联系[email protected] 删除。
我来说两句