Changing graphics driver in Debian Stretch












0














I have a Debian Stretch laptop with two graphics controllers:



[0]~>lspci | fgrep 'VGA compatible controller' 
00:02.0 VGA compatible controller: Intel Corporation Iris Pro Graphics P580 (rev 09)
01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Venus XTX [Radeon HD 8890M / R9 M275X/M375X] (rev 83)


Now the Intel controller seems to be used for GLX rendering:



[0]~>glxinfo | fgrep Device:
Device: Mesa DRI Intel(R) Iris Pro Graphics P580 (Skylake GT4e) (0x193d)
[0]~>glxgears -info | fgrep GL_RENDERER
GL_RENDERER = Mesa DRI Intel(R) Iris Pro Graphics P580 (Skylake GT4e)
[0]~>glmark2 | fgrep GL_RENDERER:
GL_RENDERER: Mesa DRI Intel(R) Iris Pro Graphics P580 (Skylake GT4e)


These modules are loaded:



[0]~>fgrep LoadModule: /var/log/Xorg.0.log 
[ 10.301] (II) LoadModule: "glx"
[ 10.312] (II) LoadModule: "ati"
[ 10.312] (II) LoadModule: "radeon"
[ 10.314] (II) LoadModule: "modesetting"
[ 10.315] (II) LoadModule: "fbdev"
[ 10.316] (II) LoadModule: "vesa"
[ 10.349] (II) LoadModule: "fbdevhw"
[ 10.350] (II) LoadModule: "glamoregl"
[ 10.987] (II) LoadModule: "fb"
[ 10.988] (II) LoadModule: "fb"
[ 10.988] (II) LoadModule: "dri2"
[ 10.988] (II) LoadModule: "glamoregl"
[ 12.980] (II) LoadModule: "ramdac"
[ 13.195] (II) LoadModule: "libinput"


I have no X.Org configuration file /etc/X11/xorg.conf.



How can I configure X.Org to use the AMD controller?










share|improve this question














bumped to the homepage by Community 23 mins ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.











  • 1




    I see the X server has autodetected the AMD controller, since it has loaded the radeon module. Please post the output of xrandr --listproviders and xrandr with no parameters - let's find out how your laptop display hardware is configured. Also please see: 01.org/linuxgraphics/gfx-docs/drm/gpu/vga-switcheroo.html
    – telcoM
    Jan 25 '18 at 8:45










  • See xrandr results here: pastebin.com/nTvjn6TT
    – haba713
    Jan 25 '18 at 11:01
















0














I have a Debian Stretch laptop with two graphics controllers:



[0]~>lspci | fgrep 'VGA compatible controller' 
00:02.0 VGA compatible controller: Intel Corporation Iris Pro Graphics P580 (rev 09)
01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Venus XTX [Radeon HD 8890M / R9 M275X/M375X] (rev 83)


Now the Intel controller seems to be used for GLX rendering:



[0]~>glxinfo | fgrep Device:
Device: Mesa DRI Intel(R) Iris Pro Graphics P580 (Skylake GT4e) (0x193d)
[0]~>glxgears -info | fgrep GL_RENDERER
GL_RENDERER = Mesa DRI Intel(R) Iris Pro Graphics P580 (Skylake GT4e)
[0]~>glmark2 | fgrep GL_RENDERER:
GL_RENDERER: Mesa DRI Intel(R) Iris Pro Graphics P580 (Skylake GT4e)


These modules are loaded:



[0]~>fgrep LoadModule: /var/log/Xorg.0.log 
[ 10.301] (II) LoadModule: "glx"
[ 10.312] (II) LoadModule: "ati"
[ 10.312] (II) LoadModule: "radeon"
[ 10.314] (II) LoadModule: "modesetting"
[ 10.315] (II) LoadModule: "fbdev"
[ 10.316] (II) LoadModule: "vesa"
[ 10.349] (II) LoadModule: "fbdevhw"
[ 10.350] (II) LoadModule: "glamoregl"
[ 10.987] (II) LoadModule: "fb"
[ 10.988] (II) LoadModule: "fb"
[ 10.988] (II) LoadModule: "dri2"
[ 10.988] (II) LoadModule: "glamoregl"
[ 12.980] (II) LoadModule: "ramdac"
[ 13.195] (II) LoadModule: "libinput"


I have no X.Org configuration file /etc/X11/xorg.conf.



How can I configure X.Org to use the AMD controller?










share|improve this question














bumped to the homepage by Community 23 mins ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.











  • 1




    I see the X server has autodetected the AMD controller, since it has loaded the radeon module. Please post the output of xrandr --listproviders and xrandr with no parameters - let's find out how your laptop display hardware is configured. Also please see: 01.org/linuxgraphics/gfx-docs/drm/gpu/vga-switcheroo.html
    – telcoM
    Jan 25 '18 at 8:45










  • See xrandr results here: pastebin.com/nTvjn6TT
    – haba713
    Jan 25 '18 at 11:01














0












0








0







I have a Debian Stretch laptop with two graphics controllers:



[0]~>lspci | fgrep 'VGA compatible controller' 
00:02.0 VGA compatible controller: Intel Corporation Iris Pro Graphics P580 (rev 09)
01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Venus XTX [Radeon HD 8890M / R9 M275X/M375X] (rev 83)


Now the Intel controller seems to be used for GLX rendering:



[0]~>glxinfo | fgrep Device:
Device: Mesa DRI Intel(R) Iris Pro Graphics P580 (Skylake GT4e) (0x193d)
[0]~>glxgears -info | fgrep GL_RENDERER
GL_RENDERER = Mesa DRI Intel(R) Iris Pro Graphics P580 (Skylake GT4e)
[0]~>glmark2 | fgrep GL_RENDERER:
GL_RENDERER: Mesa DRI Intel(R) Iris Pro Graphics P580 (Skylake GT4e)


These modules are loaded:



[0]~>fgrep LoadModule: /var/log/Xorg.0.log 
[ 10.301] (II) LoadModule: "glx"
[ 10.312] (II) LoadModule: "ati"
[ 10.312] (II) LoadModule: "radeon"
[ 10.314] (II) LoadModule: "modesetting"
[ 10.315] (II) LoadModule: "fbdev"
[ 10.316] (II) LoadModule: "vesa"
[ 10.349] (II) LoadModule: "fbdevhw"
[ 10.350] (II) LoadModule: "glamoregl"
[ 10.987] (II) LoadModule: "fb"
[ 10.988] (II) LoadModule: "fb"
[ 10.988] (II) LoadModule: "dri2"
[ 10.988] (II) LoadModule: "glamoregl"
[ 12.980] (II) LoadModule: "ramdac"
[ 13.195] (II) LoadModule: "libinput"


I have no X.Org configuration file /etc/X11/xorg.conf.



How can I configure X.Org to use the AMD controller?










share|improve this question













I have a Debian Stretch laptop with two graphics controllers:



[0]~>lspci | fgrep 'VGA compatible controller' 
00:02.0 VGA compatible controller: Intel Corporation Iris Pro Graphics P580 (rev 09)
01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Venus XTX [Radeon HD 8890M / R9 M275X/M375X] (rev 83)


Now the Intel controller seems to be used for GLX rendering:



[0]~>glxinfo | fgrep Device:
Device: Mesa DRI Intel(R) Iris Pro Graphics P580 (Skylake GT4e) (0x193d)
[0]~>glxgears -info | fgrep GL_RENDERER
GL_RENDERER = Mesa DRI Intel(R) Iris Pro Graphics P580 (Skylake GT4e)
[0]~>glmark2 | fgrep GL_RENDERER:
GL_RENDERER: Mesa DRI Intel(R) Iris Pro Graphics P580 (Skylake GT4e)


These modules are loaded:



[0]~>fgrep LoadModule: /var/log/Xorg.0.log 
[ 10.301] (II) LoadModule: "glx"
[ 10.312] (II) LoadModule: "ati"
[ 10.312] (II) LoadModule: "radeon"
[ 10.314] (II) LoadModule: "modesetting"
[ 10.315] (II) LoadModule: "fbdev"
[ 10.316] (II) LoadModule: "vesa"
[ 10.349] (II) LoadModule: "fbdevhw"
[ 10.350] (II) LoadModule: "glamoregl"
[ 10.987] (II) LoadModule: "fb"
[ 10.988] (II) LoadModule: "fb"
[ 10.988] (II) LoadModule: "dri2"
[ 10.988] (II) LoadModule: "glamoregl"
[ 12.980] (II) LoadModule: "ramdac"
[ 13.195] (II) LoadModule: "libinput"


I have no X.Org configuration file /etc/X11/xorg.conf.



How can I configure X.Org to use the AMD controller?







linux debian xorg amd-graphics radeon






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Jan 25 '18 at 8:03









haba713

1065




1065





bumped to the homepage by Community 23 mins ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.







bumped to the homepage by Community 23 mins ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.










  • 1




    I see the X server has autodetected the AMD controller, since it has loaded the radeon module. Please post the output of xrandr --listproviders and xrandr with no parameters - let's find out how your laptop display hardware is configured. Also please see: 01.org/linuxgraphics/gfx-docs/drm/gpu/vga-switcheroo.html
    – telcoM
    Jan 25 '18 at 8:45










  • See xrandr results here: pastebin.com/nTvjn6TT
    – haba713
    Jan 25 '18 at 11:01














  • 1




    I see the X server has autodetected the AMD controller, since it has loaded the radeon module. Please post the output of xrandr --listproviders and xrandr with no parameters - let's find out how your laptop display hardware is configured. Also please see: 01.org/linuxgraphics/gfx-docs/drm/gpu/vga-switcheroo.html
    – telcoM
    Jan 25 '18 at 8:45










  • See xrandr results here: pastebin.com/nTvjn6TT
    – haba713
    Jan 25 '18 at 11:01








1




1




I see the X server has autodetected the AMD controller, since it has loaded the radeon module. Please post the output of xrandr --listproviders and xrandr with no parameters - let's find out how your laptop display hardware is configured. Also please see: 01.org/linuxgraphics/gfx-docs/drm/gpu/vga-switcheroo.html
– telcoM
Jan 25 '18 at 8:45




I see the X server has autodetected the AMD controller, since it has loaded the radeon module. Please post the output of xrandr --listproviders and xrandr with no parameters - let's find out how your laptop display hardware is configured. Also please see: 01.org/linuxgraphics/gfx-docs/drm/gpu/vga-switcheroo.html
– telcoM
Jan 25 '18 at 8:45












See xrandr results here: pastebin.com/nTvjn6TT
– haba713
Jan 25 '18 at 11:01




See xrandr results here: pastebin.com/nTvjn6TT
– haba713
Jan 25 '18 at 11:01










1 Answer
1






active

oldest

votes


















0














Cool, both your GPU drivers can handle both output source/sink and render offload source/sink operations. So... try this:



xrandr --setprovideroffloadsink "VERDE @ pci:0000:01:00.0" "modesetting"


or by using provider numbers:



xrandr --setprovideroffloadsink 1 0


This tells the Intel controller to offload its rendering tasks to the AMD GPU. It is not as efficient as switching the outputs to the AMD GPU, but it's the easiest way to make use of both your GPUs with your current configuration.



If it works for you, put that command into a script in /etc/X11/Xsession.d directory, for example /etc/X11/Xsession.d/15custom_xrandr:



#!/bin/sh
xrandr -setprovideroffloadsink "VERDE @ pci:0000:01:00.0" "modesetting"


If you have the debugfs virtual filesystem mounted at /sys/kernel/debug and /sys/kernel/debug/vgaswitcheroo/ directory exists, you may be able to switch the outputs to the AMD GPU's control, if your hardware includes the required multiplexer chip. It should be as easy as arranging something to run



echo "DIS" >>/sys/kernel/debug/vgaswitcheroo/switch


before starting the X server. Then the X server should automatically detect that all the active displays are now on the AMD GPU, and should leave the Intel GPU alone.






share|improve this answer





















  • I've tried all of these with X restart and pc reboot: xrandr --setprovideroffloadsink ..., xrandr --setprovideroffloadsink 1 0 and /etc/X11/Xsession.d/15custom_xrandr (with double hyphen in xrandr switch). However, glxgears -info always reports using Intel GL renderer.
    – haba713
    Jan 28 '18 at 13:06










  • I decided to disable Intel graphics from BIOS. Now glxgears -info reports using GL renderer Gallium 0.4 on AMD CAPE VERDE (DRM 2.49.0 / 4.9.0-5-amd64, LLVM 3.9.1).
    – haba713
    Jan 29 '18 at 7:28











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
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f419534%2fchanging-graphics-driver-in-debian-stretch%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























1 Answer
1






active

oldest

votes








1 Answer
1






active

oldest

votes









active

oldest

votes






active

oldest

votes









0














Cool, both your GPU drivers can handle both output source/sink and render offload source/sink operations. So... try this:



xrandr --setprovideroffloadsink "VERDE @ pci:0000:01:00.0" "modesetting"


or by using provider numbers:



xrandr --setprovideroffloadsink 1 0


This tells the Intel controller to offload its rendering tasks to the AMD GPU. It is not as efficient as switching the outputs to the AMD GPU, but it's the easiest way to make use of both your GPUs with your current configuration.



If it works for you, put that command into a script in /etc/X11/Xsession.d directory, for example /etc/X11/Xsession.d/15custom_xrandr:



#!/bin/sh
xrandr -setprovideroffloadsink "VERDE @ pci:0000:01:00.0" "modesetting"


If you have the debugfs virtual filesystem mounted at /sys/kernel/debug and /sys/kernel/debug/vgaswitcheroo/ directory exists, you may be able to switch the outputs to the AMD GPU's control, if your hardware includes the required multiplexer chip. It should be as easy as arranging something to run



echo "DIS" >>/sys/kernel/debug/vgaswitcheroo/switch


before starting the X server. Then the X server should automatically detect that all the active displays are now on the AMD GPU, and should leave the Intel GPU alone.






share|improve this answer





















  • I've tried all of these with X restart and pc reboot: xrandr --setprovideroffloadsink ..., xrandr --setprovideroffloadsink 1 0 and /etc/X11/Xsession.d/15custom_xrandr (with double hyphen in xrandr switch). However, glxgears -info always reports using Intel GL renderer.
    – haba713
    Jan 28 '18 at 13:06










  • I decided to disable Intel graphics from BIOS. Now glxgears -info reports using GL renderer Gallium 0.4 on AMD CAPE VERDE (DRM 2.49.0 / 4.9.0-5-amd64, LLVM 3.9.1).
    – haba713
    Jan 29 '18 at 7:28
















0














Cool, both your GPU drivers can handle both output source/sink and render offload source/sink operations. So... try this:



xrandr --setprovideroffloadsink "VERDE @ pci:0000:01:00.0" "modesetting"


or by using provider numbers:



xrandr --setprovideroffloadsink 1 0


This tells the Intel controller to offload its rendering tasks to the AMD GPU. It is not as efficient as switching the outputs to the AMD GPU, but it's the easiest way to make use of both your GPUs with your current configuration.



If it works for you, put that command into a script in /etc/X11/Xsession.d directory, for example /etc/X11/Xsession.d/15custom_xrandr:



#!/bin/sh
xrandr -setprovideroffloadsink "VERDE @ pci:0000:01:00.0" "modesetting"


If you have the debugfs virtual filesystem mounted at /sys/kernel/debug and /sys/kernel/debug/vgaswitcheroo/ directory exists, you may be able to switch the outputs to the AMD GPU's control, if your hardware includes the required multiplexer chip. It should be as easy as arranging something to run



echo "DIS" >>/sys/kernel/debug/vgaswitcheroo/switch


before starting the X server. Then the X server should automatically detect that all the active displays are now on the AMD GPU, and should leave the Intel GPU alone.






share|improve this answer





















  • I've tried all of these with X restart and pc reboot: xrandr --setprovideroffloadsink ..., xrandr --setprovideroffloadsink 1 0 and /etc/X11/Xsession.d/15custom_xrandr (with double hyphen in xrandr switch). However, glxgears -info always reports using Intel GL renderer.
    – haba713
    Jan 28 '18 at 13:06










  • I decided to disable Intel graphics from BIOS. Now glxgears -info reports using GL renderer Gallium 0.4 on AMD CAPE VERDE (DRM 2.49.0 / 4.9.0-5-amd64, LLVM 3.9.1).
    – haba713
    Jan 29 '18 at 7:28














0












0








0






Cool, both your GPU drivers can handle both output source/sink and render offload source/sink operations. So... try this:



xrandr --setprovideroffloadsink "VERDE @ pci:0000:01:00.0" "modesetting"


or by using provider numbers:



xrandr --setprovideroffloadsink 1 0


This tells the Intel controller to offload its rendering tasks to the AMD GPU. It is not as efficient as switching the outputs to the AMD GPU, but it's the easiest way to make use of both your GPUs with your current configuration.



If it works for you, put that command into a script in /etc/X11/Xsession.d directory, for example /etc/X11/Xsession.d/15custom_xrandr:



#!/bin/sh
xrandr -setprovideroffloadsink "VERDE @ pci:0000:01:00.0" "modesetting"


If you have the debugfs virtual filesystem mounted at /sys/kernel/debug and /sys/kernel/debug/vgaswitcheroo/ directory exists, you may be able to switch the outputs to the AMD GPU's control, if your hardware includes the required multiplexer chip. It should be as easy as arranging something to run



echo "DIS" >>/sys/kernel/debug/vgaswitcheroo/switch


before starting the X server. Then the X server should automatically detect that all the active displays are now on the AMD GPU, and should leave the Intel GPU alone.






share|improve this answer












Cool, both your GPU drivers can handle both output source/sink and render offload source/sink operations. So... try this:



xrandr --setprovideroffloadsink "VERDE @ pci:0000:01:00.0" "modesetting"


or by using provider numbers:



xrandr --setprovideroffloadsink 1 0


This tells the Intel controller to offload its rendering tasks to the AMD GPU. It is not as efficient as switching the outputs to the AMD GPU, but it's the easiest way to make use of both your GPUs with your current configuration.



If it works for you, put that command into a script in /etc/X11/Xsession.d directory, for example /etc/X11/Xsession.d/15custom_xrandr:



#!/bin/sh
xrandr -setprovideroffloadsink "VERDE @ pci:0000:01:00.0" "modesetting"


If you have the debugfs virtual filesystem mounted at /sys/kernel/debug and /sys/kernel/debug/vgaswitcheroo/ directory exists, you may be able to switch the outputs to the AMD GPU's control, if your hardware includes the required multiplexer chip. It should be as easy as arranging something to run



echo "DIS" >>/sys/kernel/debug/vgaswitcheroo/switch


before starting the X server. Then the X server should automatically detect that all the active displays are now on the AMD GPU, and should leave the Intel GPU alone.







share|improve this answer












share|improve this answer



share|improve this answer










answered Jan 25 '18 at 11:27









telcoM

16k12143




16k12143












  • I've tried all of these with X restart and pc reboot: xrandr --setprovideroffloadsink ..., xrandr --setprovideroffloadsink 1 0 and /etc/X11/Xsession.d/15custom_xrandr (with double hyphen in xrandr switch). However, glxgears -info always reports using Intel GL renderer.
    – haba713
    Jan 28 '18 at 13:06










  • I decided to disable Intel graphics from BIOS. Now glxgears -info reports using GL renderer Gallium 0.4 on AMD CAPE VERDE (DRM 2.49.0 / 4.9.0-5-amd64, LLVM 3.9.1).
    – haba713
    Jan 29 '18 at 7:28


















  • I've tried all of these with X restart and pc reboot: xrandr --setprovideroffloadsink ..., xrandr --setprovideroffloadsink 1 0 and /etc/X11/Xsession.d/15custom_xrandr (with double hyphen in xrandr switch). However, glxgears -info always reports using Intel GL renderer.
    – haba713
    Jan 28 '18 at 13:06










  • I decided to disable Intel graphics from BIOS. Now glxgears -info reports using GL renderer Gallium 0.4 on AMD CAPE VERDE (DRM 2.49.0 / 4.9.0-5-amd64, LLVM 3.9.1).
    – haba713
    Jan 29 '18 at 7:28
















I've tried all of these with X restart and pc reboot: xrandr --setprovideroffloadsink ..., xrandr --setprovideroffloadsink 1 0 and /etc/X11/Xsession.d/15custom_xrandr (with double hyphen in xrandr switch). However, glxgears -info always reports using Intel GL renderer.
– haba713
Jan 28 '18 at 13:06




I've tried all of these with X restart and pc reboot: xrandr --setprovideroffloadsink ..., xrandr --setprovideroffloadsink 1 0 and /etc/X11/Xsession.d/15custom_xrandr (with double hyphen in xrandr switch). However, glxgears -info always reports using Intel GL renderer.
– haba713
Jan 28 '18 at 13:06












I decided to disable Intel graphics from BIOS. Now glxgears -info reports using GL renderer Gallium 0.4 on AMD CAPE VERDE (DRM 2.49.0 / 4.9.0-5-amd64, LLVM 3.9.1).
– haba713
Jan 29 '18 at 7:28




I decided to disable Intel graphics from BIOS. Now glxgears -info reports using GL renderer Gallium 0.4 on AMD CAPE VERDE (DRM 2.49.0 / 4.9.0-5-amd64, LLVM 3.9.1).
– haba713
Jan 29 '18 at 7:28


















draft saved

draft discarded




















































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.





Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


Please pay close attention to the following guidance:


  • 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.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f419534%2fchanging-graphics-driver-in-debian-stretch%23new-answer', 'question_page');
}
);

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







Popular posts from this blog

CARDNET

Boot-repair Failure: Unable to locate package grub-common:i386

濃尾地震