Difference between revisions of "PRIME"

From ArchWiki
Jump to navigation Jump to search
(Glitches/Ghosting synchronization problem on second monitor when using reverse PRIME: Added link)
(Overall revision and added reverse PRIME)
Line 1: Line 1:
 
[[Category:Graphics]]
 
[[Category:Graphics]]
 
[[zh-CN:PRIME]]
 
[[zh-CN:PRIME]]
{{Expansion|The list of drivers that support PRIME is incomplete.}}
+
 
 
PRIME is a technology used to manage hybrid graphics found on recent laptops ([[NVIDIA Optimus|Optimus for NVIDIA]], AMD Dynamic Switchable Graphics for Radeon).
 
PRIME is a technology used to manage hybrid graphics found on recent laptops ([[NVIDIA Optimus|Optimus for NVIDIA]], AMD Dynamic Switchable Graphics for Radeon).
 +
'''PRIME GPU offloading''' and '''Reverse PRIME''' is an attempt to support muxless hybrid graphics in the Linux kernel.
 +
 +
 +
== Installation ==
  
The following drivers support it:
+
=== Open Source Drivers ===
 +
 
 +
Remove any closed-source graphic drivers and replace them with the open source equivalent:
  
 
* {{Pkg|xf86-video-nouveau}}
 
* {{Pkg|xf86-video-nouveau}}
Line 10: Line 16:
 
* {{Pkg|xf86-video-intel}}
 
* {{Pkg|xf86-video-intel}}
  
== Installation ==
+
Reboot and check the list of attached graphic drivers:
 
 
First, check the list of video cards attached to your display:
 
  
 
{{hc|$ xrandr --listproviders|
 
{{hc|$ xrandr --listproviders|
Line 20: Line 24:
 
}}
 
}}
  
We can see that there are two graphic cards: Intel, the integrated card (id 0x7d), and Radeon, the discrete card (id 0x56), which should be used for GPU-intensive applications. We can see that, by default, Intel is always used:
+
 
 +
We can see that there are two graphic cards: Intel, the integrated card (id 0x7d), and Radeon, the discrete card (id 0x56), which should be used for GPU-intensive applications.  
 +
 
 +
By default the Intel card is always used:
  
 
{{hc|<nowiki>$ glxinfo | grep "OpenGL renderer"</nowiki>|
 
{{hc|<nowiki>$ glxinfo | grep "OpenGL renderer"</nowiki>|
Line 26: Line 33:
 
}}
 
}}
  
The command {{ic|xrandr --setprovideroffloadsink provider sink}} can be used to make a render offload provider send its output to the sink provider (the provider which has a display connected). The provider and sink identifiers can be numeric (0x7d, 0x56) or a case-sensitive name (Intel, radeon). Example:
+
 
 +
=== Closed Source Drivers ===
 +
 
 +
{{Expansion|Add article about support and setup of closed-source graphic drivers for PRIME}}
 +
 
 +
 
 +
== PRIME GPU offloading ==
 +
 
 +
GPU-intensive applications should be rendered on the more powerful discrete card. The command {{ic|xrandr --setprovideroffloadsink provider sink}} can be used to make a render offload provider send its output to the sink provider (the provider which has a display connected). The provider and sink identifiers can be numeric (0x7d, 0x56) or a case-sensitive name (Intel, radeon).
 +
 
 +
Example:
  
 
  $ xrandr --setprovideroffloadsink radeon Intel
 
  $ xrandr --setprovideroffloadsink radeon Intel
  
Now, you can use your discrete card for the applications who need it the most (for example games, 3D modellers...):
+
Now, you can use your discrete card for the applications who need it the most (for example games, 3D modellers...) by prepending the {{ic|DRI_PRIME&#61;1}} environment variable:
  
 
{{hc|<nowiki>$ DRI_PRIME=1 glxinfo | grep "OpenGL renderer"</nowiki>|
 
{{hc|<nowiki>$ DRI_PRIME=1 glxinfo | grep "OpenGL renderer"</nowiki>|
Line 37: Line 54:
  
 
Other applications will still use the less power-hungry integrated card. These settings are lost once the X server restarts, you may want to make a script and auto-run it at the startup of your desktop environment (alternatively, put it in {{ic|/etc/X11/xinit/xinitrc.d/}}). This may reduce your battery life and increase heat though.
 
Other applications will still use the less power-hungry integrated card. These settings are lost once the X server restarts, you may want to make a script and auto-run it at the startup of your desktop environment (alternatively, put it in {{ic|/etc/X11/xinit/xinitrc.d/}}). This may reduce your battery life and increase heat though.
 +
 +
 +
== Reverse PRIME ==
 +
 +
If the second GPU has outputs that aren't accessible by the primary GPU, you can use '''Reverse PRIME''' to make use of them. This will involve using the primary GPU to render the images, and then pass them off to the secondary GPU.
 +
 +
In the scenario above, you would do
 +
 +
$ xrandr --setprovideroutputsource radeon Intel
 +
 +
When this is done, the discrete card's outputs (Radeon) should be available in xrandr, and you could do something like:
 +
 +
$ xrandr --output HDMI-1 --auto --above LVDS1
 +
  
 
== Troubleshooting ==
 
== Troubleshooting ==
Line 86: Line 117:
 
  CLUTTER_PAINT=disable-clipped-redraws:disable-culling
 
  CLUTTER_PAINT=disable-clipped-redraws:disable-culling
 
  CLUTTER_VBLANK=True
 
  CLUTTER_VBLANK=True
 +
 +
 +
== See also ==
 +
 +
* [https://wiki.freedesktop.org/nouveau/Optimus/ Nouveau Optimus]

Revision as of 12:45, 5 November 2015

zh-CN:PRIME

PRIME is a technology used to manage hybrid graphics found on recent laptops (Optimus for NVIDIA, AMD Dynamic Switchable Graphics for Radeon). PRIME GPU offloading and Reverse PRIME is an attempt to support muxless hybrid graphics in the Linux kernel.


Installation

Open Source Drivers

Remove any closed-source graphic drivers and replace them with the open source equivalent:

Reboot and check the list of attached graphic drivers:

$ xrandr --listproviders
Providers: number : 2
Provider 0: id: 0x7d cap: 0xb, Source Output, Sink Output, Sink Offload crtcs: 3 outputs: 4 associated providers: 1 name:Intel
Provider 1: id: 0x56 cap: 0xf, Source Output, Sink Output, Source Offload, Sink Offload crtcs: 6 outputs: 1 associated providers: 1 name:radeon


We can see that there are two graphic cards: Intel, the integrated card (id 0x7d), and Radeon, the discrete card (id 0x56), which should be used for GPU-intensive applications.

By default the Intel card is always used:

$ glxinfo | grep "OpenGL renderer"
OpenGL renderer string: Mesa DRI Intel(R) Ivybridge Mobile


Closed Source Drivers

Tango-view-fullscreen.pngThis article or section needs expansion.Tango-view-fullscreen.png

Reason: Add article about support and setup of closed-source graphic drivers for PRIME (Discuss in Talk:PRIME#)


PRIME GPU offloading

GPU-intensive applications should be rendered on the more powerful discrete card. The command xrandr --setprovideroffloadsink provider sink can be used to make a render offload provider send its output to the sink provider (the provider which has a display connected). The provider and sink identifiers can be numeric (0x7d, 0x56) or a case-sensitive name (Intel, radeon).

Example:

$ xrandr --setprovideroffloadsink radeon Intel

Now, you can use your discrete card for the applications who need it the most (for example games, 3D modellers...) by prepending the DRI_PRIME=1 environment variable:

$ DRI_PRIME=1 glxinfo | grep "OpenGL renderer"
OpenGL renderer string: Gallium 0.4 on AMD TURKS

Other applications will still use the less power-hungry integrated card. These settings are lost once the X server restarts, you may want to make a script and auto-run it at the startup of your desktop environment (alternatively, put it in /etc/X11/xinit/xinitrc.d/). This may reduce your battery life and increase heat though.


Reverse PRIME

If the second GPU has outputs that aren't accessible by the primary GPU, you can use Reverse PRIME to make use of them. This will involve using the primary GPU to render the images, and then pass them off to the secondary GPU.

In the scenario above, you would do

$ xrandr --setprovideroutputsource radeon Intel

When this is done, the discrete card's outputs (Radeon) should be available in xrandr, and you could do something like:

$ xrandr --output HDMI-1 --auto --above LVDS1


Troubleshooting

Tango-inaccurate.pngThe factual accuracy of this article or section is disputed.Tango-inaccurate.png

Reason: No sources to motivate the workarounds in this section (Discuss in Talk:PRIME#)

XRandR specifies only 1 output provider

Delete/move /etc/X11/xorg.conf file and any other files relating to GPUs in /etc/X11/xorg.conf.d/. Restart the X server after this change.

If the video driver is blacklisted in /etc/modprobe.d/, load the module and restart X. This may be the case if you use the bbswitch module for Nvidia GPUs.

Since kernel version 3.19.0 the nouveau kernel module cannot be loaded under certain circumstances. Dmesg will throw an error with invalid rom content. The bug as has been patched, but hasnt yet reached mainline. Freedesktop Bug Thread In the meantime, applying the patches to a custom kernel before compiling seems to be the only fix.

When an application is rendered with the discrete card, it only renders a black screen

In some cases PRIME needs a composition manager to properly work. If your window manager doesn’t do compositing, you can use xcompmgr on top of it.

If you use Xfce, you can go to Menu->Settings->Window Manager Tweaks->Compositor and enable compositing, then try again your application.

Black screen with GL-based compositors

Currently there are issues with GL-based compositors and PRIME offloading. While Xrender-based compositors (xcompmgr, xfwm, compton's default backend, cairo-compmgr, and a few others) will work without issue, GL-based compositors (Mutter/muffin, Compiz, compton with GLX backend, Kwin's OpenGL backend, etc) will initially show a black screen, as if there was no compositor running. While you can force an image to appear by resizing the offloaded window, this is not a practical solution as it will not work for things such as full screen Wine applications. This means that desktop environments such as GNOME3 and Cinnamon have issues with using PRIME offloading.

Additionally if you are using an Intel IGP you might be able to fix the GL Compositing issue by running the IGP as UXA instead of SNA, however this may cause issues with the offloading process (ie, xrandr --listproviders may not list the discrete GPU).

For details see FDO Bug #69101.

Kernel crash/oops when using PRIME and switching windows/workspaces

Note: this has been tested on a system with Intel+AMD

Using DRI3 WITH a config file for the integrated card seems to fix this issue.

To enable DRI3, you need to recompile mesa with --enable-dri3 in the configure flags[1] and create a config for the integrated card adding the DRI3 option:

Section "Device"
    Identifier "Intel Graphics"
    Driver "intel"
    Option "DRI" "3"
EndSection

After this you can use DRI_PRIME=1 WITHOUT having to run xrandr --setprovideroffloadsink radeon Intel as DRI3 will take care of the offloading.

Glitches/Ghosting synchronization problem on second monitor when using reverse PRIME

This problem users when not using a composite manager, such as with i3. [2]

If you experience this problem under Gnome, then a possible fix is to set some environment variables in /etc/environment [3]

CLUTTER_PAINT=disable-clipped-redraws:disable-culling
CLUTTER_VBLANK=True


See also