bumblebee on ubuntu13.04 没检测到图形设备的解决方法[双显卡同样]
2013-07-13 14:44
543 查看
情况:
[ERROR]Cannot access secondary GPU - error: [XORG] (EE) No devices detected.[ERROR]Aborting because fallback start is disabled.
nvidia驱动的情况下:
root@crper-Aspire-5755G:~# lspci | grep VGA 00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09) 01:00.0 VGA compatible controller: NVIDIA Corporation GF108M [GeForce GT 630M] (rev ff)
获取到你的独显的BUSID...就是那个01:00.0
接下来修改 vim /etc/bumblebee/xorg.conf.nvidia
Section "ServerLayout" Identifier "Layout0" Option "AutoAddDevices" "false" Option "AutoAddGPU" "false" EndSection Section "Device" Identifier "DiscreteNvidia" Driver "nvidia" VendorName "NVIDIA Corporation" # If the X server does not automatically detect your VGA device, # you can manually set it here. # To get the BusID prop, run `lspci | egrep 'VGA|3D'` and input the data # as you see in the commented example. # This Setting may be needed in some platforms with more than one # nvidia card, which may confuse the proprietary driver (e.g., # trying to take ownership of the wrong device). Also needed on Ubuntu 13.04. BusID "PCI:01:00:0" # Setting ProbeAllGpus to false prevents the new proprietary driver # instance spawned to try to control the integrated graphics card, # which is already being managed outside bumblebee. # This option doesn't hurt and it is required on platforms running # more than one nvidia graphics card with the proprietary driver. # (E.g. Macbook Pro pre-2010 with nVidia 9400M + 9600M GT). # If this option is not set, the new Xorg may blacken the screen and # render it unusable (unless you have some way to run killall Xorg). Option "ProbeAllGpus" "false" Option "NoLogo" "true" Option "UseEDID" "false" Option "UseDisplayDevice" "none" EndSection
把BusID这一行的注释去掉,修改里面的PCI号(你获取到独显BUSID号码),值得注意的是,获取到的ID号最后一位必须为冒号.
也就是PCI:01:00:0
修改bumblebee的主要配置文件
# Configuration file for Bumblebee. Values should **not** be put between quotes ## Server options. Any change made in this section will need a server restart # to take effect. [bumblebeed] # The secondary Xorg server DISPLAY number VirtualDisplay=:8 # Should the unused Xorg server be kept running? Set this to true if waiting # for X to be ready is too long and don't need power management at all. KeepUnusedXServer=false # The name of the Bumbleblee server group name (GID name) ServerGroup=bumblebee # Card power state at exit. Set to false if the card shoud be ON when Bumblebee # server exits. TurnCardOffAtExit=false # The default behavior of '-f' option on optirun. If set to "true", '-f' will # be ignored. NoEcoModeOverride=false # The Driver used by Bumblebee server. If this value is not set (or empty), # auto-detection is performed. The available drivers are nvidia and nouveau # (See also the driver-specific sections below) Driver=nvidia # Directory with a dummy config file to pass as a -configdir to secondary X XorgConfDir=/etc/bumblebee/xorg.conf.d ## Client options. Will take effect on the next optirun executed. [optirun] # Acceleration/ rendering bridge, possible values are auto, virtualgl and # primus. Bridge=auto # The method used for VirtualGL to transport frames between X servers. # Possible values are proxy, jpeg, rgb, xv and yuv. VGLTransport=proxy # List of paths which are searched for the primus libGL.so.1 when using # the primus bridge PrimusLibraryPath=/usr/lib/x86_64-linux-gnu/primus:/usr/lib/i386-linux-gnu/primus # Should the program run under optirun even if Bumblebee server or nvidia card # is not available? AllowFallbackToIGC=false # Driver-specific settings are grouped under [driver-NAME]. The sections are # parsed if the Driver setting in [bumblebeed] is set to NAME (or if auto- # detection resolves to NAME). # PMMethod: method to use for saving power by disabling the nvidia card, valid # values are: auto - automatically detect which PM method to use # bbswitch - new in BB 3, recommended if available # switcheroo - vga_switcheroo method, use at your own risk # none - disable PM completely # https://github.com/Bumblebee-Project/Bumblebee/wiki/Comparison-of-PM-methods ## Section with nvidia driver specific options, only parsed if Driver=nvidia [driver-nvidia] # Module name to load, defaults to Driver if empty or unset KernelDriver=nvidia-current PMMethod=auto # colon-separated path to the nvidia libraries LibraryPath=/usr/lib/nvidia-current:/usr/lib32/nvidia-current # comma-separated path of the directory containing nvidia_drv.so and the # default Xorg modules path XorgModulePath=/usr/lib/nvidia-current/xorg,/usr/lib/xorg/modules XorgConfFile=/etc/bumblebee/xorg.conf.nvidia ## Section with nouveau driver specific options, only parsed if Driver=nouveau [driver-nouveau] KernelDriver=nouveau PMMethod=auto XorgConfFile=/etc/bumblebee/xorg.conf.nouveau修改
Driver=nvidia KernelDriver=nvidia-current Module=nvidia-current Module=nvidia
相关文章推荐
- bumblebee on ubuntu13.04 没检测到图形设备的解决方法[双显卡同样]
- Ubuntu 14.04双显卡设备出现未知显示器解决方法
- ubuntu安装nvidia官方驱动(安装CUDA7.5之后,找不到TITAN显卡的解决方法)
- 解决"OCC图形设备初始化失败"的方法
- Ubuntu每次开机后提示:检测到系统程序出现问题的解决方法
- Ubuntu12.04解决集成HD3000显卡安装后系统详情显示图形 驱动 未知的方法
- ubuntu安装显卡驱动后无法进入图形界面的解决方法
- Ubuntu 下Eclipse不识别Android设备 的解决方法
- ubuntu 13.04无线网无法使用解决方法
- ubuntu 10.04 i5 2300 显卡解决方法
- ubuntu 16.04系统下GTX970显卡不支持导致无法开机或开机黑屏解决方法
- Ubuntu 14.04双显卡设备出现未知显示器问题解决
- Ubuntu下Adb调试Android找不到设备的解决方法
- 我的Android进阶之旅------>Ubuntu下不能识别Android设备的解决方法
- 虚拟机VMware下的UbuntuUSB设备识别问题的解决方法
- Ubuntu 15.04 开机无法进入图形界面,自动进入emergency mode解决方法
- Rails on Ubuntu常见问题及解决方法
- ubuntu 不是 识别 android 设备 解决方法
- Ubuntu下解决不能识别外部设备的方法
- android 设备在linux(ubuntu) 下无法被adb device发现 解决方法