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

Bug #1561802 reported by Luca Osvaldo Mastromatteo
34
This bug affects 8 people
Affects Status Importance Assigned to Milestone
bumblebee (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

I've recently upgraded to Ubuntu 16.04 and I've got some big problems to make bumblebee working.
Basically, every configuration of bumblebee, with the nvidia or nouveau driver, optirun just gives me this error

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

In ubuntu 15.10 was working everything flawlessly

Running the daemon manually:

[ 330.722587] [INFO]bumblebeed 3.2.1 started
[ 337.342647] [ERROR][XORG] (EE)
[ 337.342681] [ERROR][XORG] (EE)
[ 337.342688] [ERROR][XORG] (EE)
[ 337.342692] [ERROR][XORG] (EE)
[ 337.342698] [ERROR][XORG] (EE)
[ 337.342703] [ERROR]X did not start properly

Bumblebee should running correctly, or at least give some configuration-releated problems.

Bumblebee just show in every situation the same error.

I've got no Xorg.8.log in /var/log

I've put an attachment of bumblebee-bugreport contents.

Revision history for this message
Luca Osvaldo Mastromatteo (lukycrociato) wrote :
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in bumblebee (Ubuntu):
status: New → Confirmed
Revision history for this message
Luca Osvaldo Mastromatteo (lukycrociato) wrote :

Solved by forcly removing the Xorg.wrap file, added by the xorg-legacy package which seems it is incompatible with bumblebee, but after the next reboot I am unable to log in into unity desktop. I don't know what is going wrong, in the previously version of ubuntu all was working flawlessly

Revision history for this message
George Vella-King (vellakingg) wrote :

I installed using these steps https://lenovolinux.blogspot.co.nz/2016/05/bumblebee-on-lenovo-t440p-nvidia-gt.html?showComment=1462632338607#c9041142385056286560
You'll have to go into recovery after the first reboot because of a boot loop but if you follow the steps it'll work.
... actually maybe if you just try add nogpumanager to /etc/default/grub step 8 in the link.
I'm guessing the original issue is solved in step 7 with mesa and gl. I'm pritty sure I correctly blacklisted nvidia-361 when I originally had this bug.
I hope this helps.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.