Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP

Loading…

[Nouveau] Failed to set drm interface version #511

Closed
fervi opened this Issue · 7 comments

5 participants

@fervi

Hello!

Few months ago i use Bumblebee with my Nvidia Geforce 310m and Nouveau Driver

I try to use it again (now) and i can't - i got a error

fervi@ThunderStorm:~$ optirun --debug file-roller
[ 749.814721] [DEBUG]optirun version 3.2.1 starting...
[ 749.814795] [DEBUG]Active configuration:
[ 749.814827] [DEBUG] bumblebeed config file: /etc/bumblebee/bumblebee.conf
[ 749.814873] [DEBUG] X display: :8
[ 749.814896] [DEBUG] LD_LIBRARY_PATH:
[ 749.814925] [DEBUG] Socket path: /var/run/bumblebee.socket
[ 749.814955] [DEBUG] Accel/display bridge: auto
[ 749.814983] [DEBUG] VGL Compression: proxy
[ 749.815015] [DEBUG] VGLrun extra options:
[ 749.815040] [DEBUG] Primus LD Path: /usr/lib/x86_64-linux-gnu/primus:/usr/lib/i386-linux-gnu/primus:/usr/lib/primus:/usr/lib32/primus
[ 749.815101] [DEBUG]Using auto-detected bridge virtualgl
[ 749.949348] [INFO]Response: No - error: XORG NOUVEAU(0): [drm] failed to set drm interface version.

[ 749.949377] [ERROR]Cannot access secondary GPU - error: XORG NOUVEAU(0): [drm] failed to set drm interface version.

[ 749.949386] [DEBUG]Socket closed.
[ 749.949414] [ERROR]Aborting because fallback start is disabled.
[ 749.949428] [DEBUG]Killing all remaining processes.

Debian GNU/Linux jessie/sid \n \l

Linux ThunderStorm 3.11-2-amd64 #1 SMP Debian 3.11.10-1 (2013-12-04) x86_64 GNU/Linux

baseboard-manufacturer: ASUSTeK Computer Inc.

baseboard-product-name: K52Jc
baseboard-version : 1.0

system-manufacturer : ASUSTeK Computer Inc.

system-product-name : K52Jc
system-version : 1.0

bios-vendor : American Megatrends Inc.
bios-version : K52Jc.216
bios-release-date : 01/25/2011

optirun (Bumblebee) 3.2.1

If you need any information - write here

Thanks for help

@xarses

I see a similar issue on debian jessie/sid
andreww@aw-linux:~/iso$ optirun --debug file-roller
[ 2069.952961] [DEBUG]optirun version 3.2.1 starting...
[ 2069.952993] [DEBUG]Active configuration:
[ 2069.953008] [DEBUG] bumblebeed config file: /etc/bumblebee/bumblebee.conf
[ 2069.953021] [DEBUG] X display: :8
[ 2069.953032] [DEBUG] LD_LIBRARY_PATH:
[ 2069.953044] [DEBUG] Socket path: /var/run/bumblebee.socket
[ 2069.953055] [DEBUG] Accel/display bridge: auto
[ 2069.953063] [DEBUG] VGL Compression: proxy
[ 2069.953070] [DEBUG] VGLrun extra options:
[ 2069.953077] [DEBUG] Primus LD Path: /usr/lib/x86_64-linux-gnu/primus:/usr/lib/i386-linux-gnu/primus:/usr/lib/primus:/usr/lib32/primus
[ 2069.953129] [DEBUG]Using auto-detected bridge primus
[ 2070.583537] [INFO]Response: No - error: XORG NOUVEAU(0): [drm] failed to set drm interface version.

[ 2070.583556] [ERROR]Cannot access secondary GPU - error: XORG NOUVEAU(0): [drm] failed to set drm interface version.

[ 2070.583560] [DEBUG]Socket closed.
[ 2070.583576] [ERROR]Aborting because fallback start is disabled.
[ 2070.583580] [DEBUG]Killing all remaining processes.

@fervi

Found partially Bug Fix

If we normal run Bumblebee (well, normal run program), we got this error
But if we run first program in console (no in X server, in TTY1) - we got error "No Deviced Detected"

But in we run this program, and run again in X program - program works*

The problem is:

  • You can only run one time program. If you want more, you must in Bumblebee.conf turn off killing X server and Graphics Card (if not - you got error "Server end successfuly"
  • If you turn off this options in bumblebee.conf - you probably lost power managment
  • And if you lost PM, you can also use PRIME technology (faster, but also don't turn off nvidia card)
@gabrielschulhof

I'm also bumping into this issue. Is there any chance it will be fixed?

@amonakov
Collaborator

Is there a reason you can't use PRIME offloading?

(regarding the bug, I think the cause in that the primary X opens nouveau drm device before the secondary X; if that's really the cause, you'd have to configure primary X to bind only to the Intel GPU)

@gabrielschulhof

@amonakov That does indeed seem to be the case. Do you know how to tell the primary X server not to use the nouveau drm?

@amonakov
Collaborator

The same way the secondary X is configured not to touch the Intel gpu: with "AutoAddGPU" "false" and "BusID". See /etc/bumblebee/xorg.conf.*.

Can you answer the question about PRIME? :)

@ArchangeGabriel

Since the opener issue has been resolved, an other workaround has been proposed, and no one answered for month, I’m closing this in my periodically bug triage. Feel free to reopen.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.