There are many similar errors on here, but none quite seemed to match my issue.

[ERROR]Cannot access secondary GPU - error: [XORG] (EE)

I have PRIME running, and I can use the PRIME profile to switch between my Intel and my NVIDIA 970M successfully. I've got nvidia-375 drivers installed (latest).

The only piece of the puzzle that doesn't work is bumblebee now.

My error:

davidparks21@ghostmint ~ $ vblank_mode=0 optirun -vv /opt/VirtualGL/bin/glxspheres64 -v
[ 1011.616264] [DEBUG]Reading file: /etc/bumblebee/bumblebee.conf
[ 1011.616435] [INFO]Configured driver: nvidia
[ 1011.616528] [DEBUG]optirun version 3.2.1 starting...
[ 1011.616534] [DEBUG]Active configuration:
[ 1011.616535] [DEBUG] bumblebeed config file: /etc/bumblebee/bumblebee.conf
[ 1011.616543] [DEBUG] X display: :8
[ 1011.616547] [DEBUG] LD_LIBRARY_PATH: /usr/lib/nvidia-375:/usr/lib32/nvidia-375
[ 1011.616550] [DEBUG] Socket path: /var/run/bumblebee.socket
[ 1011.616555] [DEBUG] Accel/display bridge: auto
[ 1011.616561] [DEBUG] VGL Compression: proxy
[ 1011.616565] [DEBUG] VGLrun extra options: 
[ 1011.616569] [DEBUG] Primus LD Path: /usr/lib/x86_64-linux-gnu/primus:/usr/lib/i386-linux-gnu/primus
[ 1011.616603] [DEBUG]Using auto-detected bridge virtualgl
[ 1011.617953] [INFO]Response: No - error: [XORG] (EE) 

[ 1011.617963] [ERROR]Cannot access secondary GPU - error: [XORG] (EE) 

[ 1011.617966] [DEBUG]Socket closed.
[ 1011.617978] [ERROR]Aborting because fallback start is disabled.
[ 1011.617984] [DEBUG]Killing all remaining processes.

My bumblebee config file:

# 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.
# The secondary Xorg server DISPLAY number
# 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.
# The name of the Bumbleblee server group name (GID name)
# Card power state at exit. Set to false if the card shoud be ON when Bumblebee
# server exits.
# The default behavior of '-f' option on optirun. If set to "true", '-f' will
# be ignored.
# 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)
# Directory with a dummy config file to pass as a -configdir to secondary X

## Client options. Will take effect on the next optirun executed.
# Acceleration/ rendering bridge, possible values are auto, virtualgl and
# primus.
# The method used for VirtualGL to transport frames between X servers.
# Possible values are proxy, jpeg, rgb, xv and yuv.
# List of paths which are searched for the primus libGL.so.1 when using
# the primus bridge
# Should the program run under optirun even if Bumblebee server or nvidia card
# is not available?

# 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
# Module name to load, defaults to Driver if empty or unset
# colon-separated path to the nvidia libraries
# comma-separated path of the directory containing nvidia_drv.so and the
# default Xorg modules path

## Section with nouveau driver specific options, only parsed if Driver=nouveau


Section "ServerLayout"
    Identifier  "Layout0"
    Option      "AutoAddDevices" "false"
    Option      "AutoAddGPU" "false"

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"

Verify PCI bus:

lspci -vnn | grep '\''[030[02]\]'
00:02.0 VGA compatible controller [0300]: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller])
01:00.0 3D controller [0302]: NVIDIA Corporation GM204M [GeForce GTX 970M] [10de:13d8] (rev a1)


The answer was finally there, uninstall xserver-xorg-legacy

sudo apt remove xserver-xorg-legacy

Here are the main resources I used to crack this:

(understand what in the !@#$ is going on here)

(this will get you 90% of the way there)

(solves a bunch of little gotchas you might have missed) Bumblebee: Cannot access secondary GPU - error: [XORG] (EE) No devices detected

(the official bumblebee troubleshooting page) https://github.com/Bumblebee-Project/Bumblebee/wiki/Troubleshooting

(the final active bug, remove xserver-org-legacy) https://github.com/Bumblebee-Project/Bumblebee/issues/749

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.