You are not logged in.
Pages: 1
While installing Arch, I (Correct me, if wrong) installed xf86-video-inetl & xf86-video-ati, because I've a laptop with Intel & AMD GPU. In KInfoCenter, it says that OpenGL vendor is Intel & OpenGL version's 3.0, so it seems that the AMD GPU isn't used. If it's used I'd have OpenGL 3.3 & 4.1, after Mesa 11 is released. What should I do to use AMD GPU?
Note: I tried to install FGLRX, but Linux didn't even load.
Offline
Evil #archlinux@libera.chat channel op and general support dude.
. files on github, Screenshots, Random pics and the rest
Offline
Will removing Intel driver force the use of AMD's one? I want to play games, but I don't want to leave Arch.
Offline
No, it won't.
Radeon chip does not have a direct output to display. It has to offload to intel DGP, which is reponsible for displaying the picture on screen. No matter which driver you use (free or non-free), you absolutely need the intel driver too.
If you wish to use free driver, check the Wiki article for PRIME.
If you wish to use non-free driver, check the Wiki article for AMD Catalyst.
And that's all.
Offline
No, it won't.
Radeon chip does not have a direct output to display. It has to offload to intel DGP, which is reponsible for displaying the picture on screen. No matter which driver you use (free or non-free), you absolutely need the intel driver too.
If you wish to use free driver, check the Wiki article for PRIME.
If you wish to use non-free driver, check the Wiki article for AMD Catalyst.And that's all.
I used
xrandr --setprovideroffloadsink radeon Intel
as normal user & root, but it didn't change what I see in KInfoCenter. What is the problem?
Offline
I forgot to run
DRI_PRIME=1 glxinfo | grep "OpenGL renderer"
It gave the output, I wanted, but why
glxinfo | grep "OpenGL renderer"
shows "OpenGL renderer string: Mesa DRI Intel(R) Ivybridge Mobile" in addition to KInfoCenter & chrome://gpu?
Offline
Think about it.
If you want an application to use discrete radeon card, you add the DRI_PRIME=1 prefix.
Session is started without that prefix, so session uses integrated gpu.
Kinfocenter is started without that prefix, so Kinfocenter uses integrated gpu.
Chrome is started without that prefix, so Chrome uses integrated gpu.
Glxinfo is started without that prefix, so glxinfo uses integrated gpu.
I mean, it is so logical that I am unsure what are you asking?
You have to tell the application which GPU to use.
Offline
Think about it.
If you want an application to use discrete radeon card, you add the DRI_PRIME=1 prefix.
Session is started without that prefix, so session uses integrated gpu.
Kinfocenter is started without that prefix, so Kinfocenter uses integrated gpu.
Chrome is started without that prefix, so Chrome uses integrated gpu.
Glxinfo is started without that prefix, so glxinfo uses integrated gpu.I mean, it is so logical that I am unsure what are you asking?
You have to tell the application which GPU to use.
Do you mean something like $ DRI_PRIME=1 kinfocenter? It crashed, after I had clicked OpenGL.
I tried $ DRI_PRIME=1 glxgears & got much better FPS, but the screen was black. With Chrome, nothing is rendered, but the window existed & I was able to click buttons.
It seems I've this problem with prime. Was it solved?
Will this problem exist with Wayland. How'd I configure which GPU to use with it?
Last edited by sherif8 (2015-09-19 03:03:48)
Offline
Well, problem obviously occurs on X with X applications. Wayland is irrelevant there. When applications start using Wayland instead of X, we can discuss that, in the meantime it's pointless, and applications will use Xwayland (X on Wayland).
Black screen is still an issue. You have two options, either use some Xrender based compositor, like xcompmgr or compton, or compile Intel driver with DRI3 support. I opted for using the mesa-git unofficial repository because of DRI3 and OpenGL improvements in upcoming Mesa, but Mesa 11 is in [testing] now, and will be in [extra] within a day or two. Once it's there, there will be no reason to use git repo, at least not at this moment. You will still have to compile Intel driver with DRI3 enabled.
Offline
Well, problem obviously occurs on X with X applications. Wayland is irrelevant there. When applications start using Wayland instead of X, we can discuss that, in the meantime it's pointless, and applications will use Xwayland (X on Wayland).
Black screen is still an issue. You have two options, either use some Xrender based compositor, like xcompmgr or compton, or compile Intel driver with DRI3 support. I opted for using the mesa-git unofficial repository because of DRI3 and OpenGL improvements in upcoming Mesa, but Mesa 11 is in [testing] now, and will be in [extra] within a day or two. Once it's there, there will be no reason to use git repo, at least not at this moment. You will still have to compile Intel driver with DRI3 enabled.
Is compiling Intel driver better than switching KDE compositor backend to XRender? If yes, how to compile it?
What's the relation between Intel driver and Mesa? What would Mesa 11 do? Will Mesa 11 make it work without comiling the driver or using XRender?
Last edited by sherif8 (2015-09-21 19:57:40)
Offline
https://en.wikipedia.org/wiki/Mesa
https://en.wikipedia.org/wiki/X_Rendering_Extension
https://en.wikipedia.org/wiki/OpenGL
No, DRI (Direct Rendering Interface) version 3 is something that a driver itself has to support in order to be able to use it. DRI3 is not enabled in xf86-video-intel that Arch provides, but you may recompile it and enable DRI3 with --enable-dri3 switch.
Offline
Pages: 1