optirun-Cannot access secondary GPU
After installing bumblebee on debian 9 by sudo apt-get install bumblebee primus as described in debian-bumblebee webpage to use intel and nvidia (Geforce 940MX) gpu in my ASUS computer and running optirun glxgears to test it, I got this message
[ 2478.780360] [ERROR]Cannot access secondary GPU - error: [XORG] (EE) [drm] Failed to open DRM device for pci:0000:01:00.0: -19
[ 2478.780506] [ERROR]Aborting because fallback start is disabled.
If I entered optirun -vv glxgears to see errors, I got
[ 2488.811395] [DEBUG]Reading file: /etc/bumblebee/bumblebee.conf
[ 2488.812317] [DEBUG]optirun version 3.2.1 starting...**
[ 2488.812349] [DEBUG]Active configuration:
[ 2488.812360] [DEBUG] bumblebeed config file: /etc/bumblebee/bumblebee.conf
[ 2488.812370] [DEBUG] X display: :8
[ 2488.812380] [DEBUG] LD_LIBRARY_PATH:
[ 2488.812390] [DEBUG] Socket path: /var/run/bumblebee.socket
[ 2488.812405] [DEBUG] Accel/display bridge: auto
[ 2488.812428] [DEBUG] VGL Compression: proxy
[ 2488.812449] [DEBUG] VGLrun extra options:
[ 2488.812474] [DEBUG] Primus LD Path: /usr/lib/x86_64-linux-gnu/primus:/usr/lib/i386-linux-gnu/primus:/usr/lib/primus:/usr/lib32/primus
[ 2488.812613] [DEBUG]Using auto-detected bridge primus
[ 2488.952035] [INFO]Response: No - error: [XORG] (EE) [drm] Failed to open DRM device for pci:0000:01:00.0: -19
[ 2488.952080] [ERROR]Cannot access secondary GPU - error: [XORG] (EE) [drm] Failed to open DRM device for pci:0000:01:00.0: -19
[ 2488.952102] [DEBUG]Socket closed.
[ 2488.952142] [ERROR]Aborting because fallback start is disabled.
[ 2488.952160] [DEBUG]Killing all remaining processes.
I have already appended the following section to /etc/bumblebee/xorg.conf.nvidia
Section "Screen"
Identifier "Default Screen"
Device "DiscreteNvidia"
EndSection
and changed this line "KernelDriver=nvidia" to "KernelDriver=nvidia-current" in /etc/bumblebee/bumblebee.conf. However, I still get same message. What should I do?
debian nvidia bumblebee
asked 26 mins ago
Onur ÇakıroğluOnur Çakıroğlu
1
New contributor
Onur Çakıroğlu is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
After installing bumblebee on debian 9 by sudo apt-get install bumblebee primus as described in debian-bumblebee webpage to use intel and nvidia (Geforce 940MX) gpu in my ASUS computer and running optirun glxgears to test it, I got this message
[ 2478.780360] [ERROR]Cannot access secondary GPU - error: [XORG] (EE) [drm] Failed to open DRM device for pci:0000:01:00.0: -19
[ 2478.780506] [ERROR]Aborting because fallback start is disabled.
If I entered optirun -vv glxgears to see errors, I got
[ 2488.811395] [DEBUG]Reading file: /etc/bumblebee/bumblebee.conf
[ 2488.812317] [DEBUG]optirun version 3.2.1 starting...**
[ 2488.812349] [DEBUG]Active configuration:
[ 2488.812360] [DEBUG] bumblebeed config file: /etc/bumblebee/bumblebee.conf
[ 2488.812370] [DEBUG] X display: :8
[ 2488.812380] [DEBUG] LD_LIBRARY_PATH:
[ 2488.812390] [DEBUG] Socket path: /var/run/bumblebee.socket
[ 2488.812405] [DEBUG] Accel/display bridge: auto
[ 2488.812428] [DEBUG] VGL Compression: proxy
[ 2488.812449] [DEBUG] VGLrun extra options:
[ 2488.812474] [DEBUG] Primus LD Path: /usr/lib/x86_64-linux-gnu/primus:/usr/lib/i386-linux-gnu/primus:/usr/lib/primus:/usr/lib32/primus
[ 2488.812613] [DEBUG]Using auto-detected bridge primus
[ 2488.952035] [INFO]Response: No - error: [XORG] (EE) [drm] Failed to open DRM device for pci:0000:01:00.0: -19
[ 2488.952080] [ERROR]Cannot access secondary GPU - error: [XORG] (EE) [drm] Failed to open DRM device for pci:0000:01:00.0: -19
[ 2488.952102] [DEBUG]Socket closed.
[ 2488.952142] [ERROR]Aborting because fallback start is disabled.
[ 2488.952160] [DEBUG]Killing all remaining processes.
I have already appended the following section to /etc/bumblebee/xorg.conf.nvidia
Section "Screen"
Identifier "Default Screen"
Device "DiscreteNvidia"
EndSection
and changed this line "KernelDriver=nvidia" to "KernelDriver=nvidia-current" in /etc/bumblebee/bumblebee.conf. However, I still get same message. What should I do?
debian nvidia bumblebee
asked 26 mins ago
Onur ÇakıroğluOnur Çakıroğlu
1
New contributor
Onur Çakıroğlu is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
After installing bumblebee on debian 9 by sudo apt-get install bumblebee primus as described in debian-bumblebee webpage to use intel and nvidia (Geforce 940MX) gpu in my ASUS computer and running optirun glxgears to test it, I got this message
[ 2478.780360] [ERROR]Cannot access secondary GPU - error: [XORG] (EE) [drm] Failed to open DRM device for pci:0000:01:00.0: -19
[ 2478.780506] [ERROR]Aborting because fallback start is disabled.
If I entered optirun -vv glxgears to see errors, I got
[ 2488.811395] [DEBUG]Reading file: /etc/bumblebee/bumblebee.conf
[ 2488.812317] [DEBUG]optirun version 3.2.1 starting...**
[ 2488.812349] [DEBUG]Active configuration:
[ 2488.812360] [DEBUG] bumblebeed config file: /etc/bumblebee/bumblebee.conf
[ 2488.812370] [DEBUG] X display: :8
[ 2488.812380] [DEBUG] LD_LIBRARY_PATH:
[ 2488.812390] [DEBUG] Socket path: /var/run/bumblebee.socket
[ 2488.812405] [DEBUG] Accel/display bridge: auto
[ 2488.812428] [DEBUG] VGL Compression: proxy
[ 2488.812449] [DEBUG] VGLrun extra options:
[ 2488.812474] [DEBUG] Primus LD Path: /usr/lib/x86_64-linux-gnu/primus:/usr/lib/i386-linux-gnu/primus:/usr/lib/primus:/usr/lib32/primus
[ 2488.812613] [DEBUG]Using auto-detected bridge primus
[ 2488.952035] [INFO]Response: No - error: [XORG] (EE) [drm] Failed to open DRM device for pci:0000:01:00.0: -19
[ 2488.952080] [ERROR]Cannot access secondary GPU - error: [XORG] (EE) [drm] Failed to open DRM device for pci:0000:01:00.0: -19
[ 2488.952102] [DEBUG]Socket closed.
[ 2488.952142] [ERROR]Aborting because fallback start is disabled.
[ 2488.952160] [DEBUG]Killing all remaining processes.
I have already appended the following section to /etc/bumblebee/xorg.conf.nvidia
Section "Screen"
Identifier "Default Screen"
Device "DiscreteNvidia"
EndSection
and changed this line "KernelDriver=nvidia" to "KernelDriver=nvidia-current" in /etc/bumblebee/bumblebee.conf. However, I still get same message. What should I do?
debian nvidia bumblebee
asked 26 mins ago
Onur ÇakıroğluOnur Çakıroğlu
1
New contributor
Onur Çakıroğlu is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
After installing bumblebee on debian 9 by sudo apt-get install bumblebee primus as described in debian-bumblebee webpage to use intel and nvidia (Geforce 940MX) gpu in my ASUS computer and running optirun glxgears to test it, I got this message
[ 2478.780360] [ERROR]Cannot access secondary GPU - error: [XORG] (EE) [drm] Failed to open DRM device for pci:0000:01:00.0: -19
[ 2478.780506] [ERROR]Aborting because fallback start is disabled.
If I entered optirun -vv glxgears to see errors, I got
[ 2488.811395] [DEBUG]Reading file: /etc/bumblebee/bumblebee.conf
[ 2488.812317] [DEBUG]optirun version 3.2.1 starting...**
[ 2488.812349] [DEBUG]Active configuration:
[ 2488.812360] [DEBUG] bumblebeed config file: /etc/bumblebee/bumblebee.conf
[ 2488.812370] [DEBUG] X display: :8
[ 2488.812380] [DEBUG] LD_LIBRARY_PATH:
[ 2488.812390] [DEBUG] Socket path: /var/run/bumblebee.socket
[ 2488.812405] [DEBUG] Accel/display bridge: auto
[ 2488.812428] [DEBUG] VGL Compression: proxy
[ 2488.812449] [DEBUG] VGLrun extra options:
[ 2488.812474] [DEBUG] Primus LD Path: /usr/lib/x86_64-linux-gnu/primus:/usr/lib/i386-linux-gnu/primus:/usr/lib/primus:/usr/lib32/primus
[ 2488.812613] [DEBUG]Using auto-detected bridge primus
[ 2488.952035] [INFO]Response: No - error: [XORG] (EE) [drm] Failed to open DRM device for pci:0000:01:00.0: -19
[ 2488.952080] [ERROR]Cannot access secondary GPU - error: [XORG] (EE) [drm] Failed to open DRM device for pci:0000:01:00.0: -19
[ 2488.952102] [DEBUG]Socket closed.
[ 2488.952142] [ERROR]Aborting because fallback start is disabled.
[ 2488.952160] [DEBUG]Killing all remaining processes.
I have already appended the following section to /etc/bumblebee/xorg.conf.nvidia
Section "Screen"
Identifier "Default Screen"
Device "DiscreteNvidia"
EndSection
and changed this line "KernelDriver=nvidia" to "KernelDriver=nvidia-current" in /etc/bumblebee/bumblebee.conf. However, I still get same message. What should I do?
debian nvidia bumblebee
debian nvidia bumblebee
asked 26 mins ago
Onur ÇakıroğluOnur Çakıroğlu
1
New contributor
Onur Çakıroğlu is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked 26 mins ago
Onur ÇakıroğluOnur Çakıroğlu
1
New contributor
Onur Çakıroğlu is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked 26 mins ago
Onur ÇakıroğluOnur Çakıroğlu
1
New contributor
Onur Çakıroğlu is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked 26 mins ago
Onur ÇakıroğluOnur Çakıroğlu
1
asked 26 mins ago
Onur ÇakıroğluOnur Çakıroğlu
1
1
New contributor
Onur Çakıroğlu is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
Onur Çakıroğlu is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Onur Çakıroğlu is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Onur Çakıroğlu is a new contributor. Be nice, and check out our Code of Conduct.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f494751%2foptirun-cannot-access-secondary-gpu%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Onur Çakıroğlu is a new contributor. Be nice, and check out our Code of Conduct.
Onur Çakıroğlu is a new contributor. Be nice, and check out our Code of Conduct.
Onur Çakıroğlu is a new contributor. Be nice, and check out our Code of Conduct.
Onur Çakıroğlu is a new contributor. Be nice, and check out our Code of Conduct.
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f494751%2foptirun-cannot-access-secondary-gpu%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
