Difference between revisions of "Intel graphics"

From ArchWiki
Jump to: navigation, search
m (Tear-free video: style, see Help:Style#Notes, Warnings, Tips)
(Don't mention removed powersave option (as of Linux 4.1, see ab585dea120fa20313b1b5a3be2b3d614f094678))
 
(279 intermediate revisions by 79 users not shown)
Line 1: Line 1:
 
[[Category:Graphics]]
 
[[Category:Graphics]]
[[Category:X Server]]
+
[[Category:X server]]
[[cs:Intel]]
+
[[cs:Intel graphics]]
[[es:Intel]]
+
[[de:Intel]]
 +
[[es:Intel graphics]]
 
[[fr:Intel]]
 
[[fr:Intel]]
[[hu:Intel]]
+
[[hu:Intel graphics]]
[[it:Intel]]
+
[[it:Intel graphics]]
 
[[ja:Intel Graphics]]
 
[[ja:Intel Graphics]]
[[pl:Intel]]
+
[[pl:Intel graphics]]
[[ru:Intel]]
+
[[ru:Intel graphics]]
[[zh-CN:Intel Graphics]]
+
[[zh-cn:Intel graphics]]
[[zh-TW:Intel]]
+
[[zh-tw:Intel graphics]]
{{Article summary start}}
+
{{Related articles start}}
{{Article summary text|Information on Intel graphics cards/chipsets and the ''intel'' video driver.}}
+
{{Related|Intel GMA 500}}
{{Article summary heading|Related}}
+
{{Related|Intel GMA 3600}}
{{Article summary wiki|Intel GMA3600}}
+
{{Related|Xorg}}
{{Article summary wiki|Poulsbo}}
+
{{Related|Kernel mode setting}}
{{Article summary wiki|Xorg}}
+
{{Related|Xrandr}}
{{Article summary end}}
+
{{Related|Hybrid graphics}}
 +
{{Related articles end}}
  
Since Intel provides and supports open source drivers, Intel graphics are now essentially plug-and-play.
+
Since Intel provides and supports open source drivers, Intel graphics are essentially plug-and-play.
  
 
For a comprehensive list of Intel GPU models and corresponding chipsets and CPUs, see [[Wikipedia:Comparison of Intel graphics processing units|this comparison on Wikipedia]].
 
For a comprehensive list of Intel GPU models and corresponding chipsets and CPUs, see [[Wikipedia:Comparison of Intel graphics processing units|this comparison on Wikipedia]].
  
{{Note|PowerVR-based graphics ([[Poulsbo|GMA 500]] and [[Intel GMA3600|GMA 3600]] series) are not supported by open source drivers.}}
+
{{Note|1=<nowiki></nowiki>
 +
* Some recommend not installing the Intel driver, and instead falling back on the modesetting driver. See [https://packages.debian.org/sid/x11/xserver-xorg-video-intel], [https://www.reddit.com/r/archlinux/comments/4cojj9/it_is_probably_time_to_ditch_xf86videointel/], [[Xorg#Installation]], and {{man|4|modesetting|url=http://linux.die.net/man/4/modesetting}}. However, the modesetting driver can cause problems such as [https://bugs.chromium.org/p/chromium/issues/detail?id=370022 Chromium Issue 370022].
 +
* PowerVR-based graphics ([[Intel GMA 500|GMA 500]] and [[Intel GMA 3600|GMA 3600]] series) are not supported by open source drivers.}}
  
 
== Installation ==
 
== Installation ==
 
Prerequisite: [[Xorg]].
 
 
   
 
   
[[pacman|Install]] the {{Pkg|xf86-video-intel}} package which is available in the [[Official Repositories|official repositories]]. It provides the DDX driver for 2D acceleration and an [[XvMC]] driver for video decoding on older GPUs. It pulls in {{Pkg|intel-dri}} as a dependency, providing the DRI driver for 3D acceleration.
+
[[Install]] the {{Pkg|xf86-video-intel}} package. It provides the DDX driver for 2D acceleration and it pulls in {{Pkg|mesa}} as a dependency, providing the DRI driver for 3D acceleration.
  
Hardware accelerated video decoding/encoding on newer GPUs is possible through the [[VA-API]] driver provided by {{Pkg|libva-intel-driver}} package also, available in the official repositories.
+
To enable OpenGL support, also install {{Pkg|mesa-libgl}}. If you are on x86_64 and need 32-bit support, also install {{Pkg|lib32-mesa-libgl}} from the [[multilib]] repository.
  
{{Note|User ''may'' need to install {{Pkg|lib32-intel-dri}} in 64-bit systems to use 3D acceleration in 32-bit programs.}}
+
Also see [[Hardware video acceleration]].
 +
 
 +
For [[Vulkan]] support, install {{Pkg|vulkan-intel}} on Ivy-Bridge or newer GPUs.
  
 
== Configuration ==
 
== Configuration ==
  
There is no need for any kind of configuration to get the X.Org running (an {{ic|xorg.conf}} is unneeded, but needs to be configured correctly if present).
+
There is no need for any configuration to run [[Xorg]].
  
For the list of options, type {{ic|man intel}}.
+
{{Note|The latest generation of integrated GPUs (Skylake/HD 530 for instance) may require additional configuration, see [[#Skylake support]]}}
  
== KMS (Kernel Mode Setting) ==
+
However, to take advantage of some driver options, you will need to create a Xorg configuration file similar to the one below:
  
{{Tip|If you have problems with the resolution, check [[Kernel_Mode_Setting#Forcing_modes_and_EDID|this page]].}}
+
{{hc|/etc/X11/xorg.conf.d/20-intel.conf|
 +
Section "Device"
 +
  Identifier  "Intel Graphics"
 +
  Driver      "intel"
 +
EndSection}}
  
[[KMS]] is required in order to run X and a desktop environment such as [[GNOME]], [[KDE]], [[Xfce]], [[LXDE]], etc. KMS is supported by Intel chipsets that use the i915 DRM driver and is enabled by default as of kernel v2.6.32. Versions 2.10 and newer of the {{Pkg|xf86-video-intel}} driver no longer support UMS (except for the very old 810 chipset family), making the use of KMS mandatory<sup>[https://www.archlinux.org/news/484/]</sup>. KMS is typically initialized after the kernel is bootstrapped. It is possible, however, to enable KMS during bootstrap itself, allowing the entire boot process to run at the native resolution.
+
Additional options are added by the user on new lines below {{ic|Driver}}.
  
{{Note|Users '''must''' remove any deprecated references to {{ic|vga}} or {{ic|nomodeset}} from boot configuration.}}
+
{{Note|
 +
*You may need to indicate {{ic|Option "AccelMethod"}} when creating a configuration file, even just to set it to the default method (currently {{ic|"sna"}}); otherwise, X may crash.
 +
*You might need to add more device sections than the one listed above. This will be indicated where necessary.}}  
  
To proceed, add the {{ic|i915}} module to the {{ic|MODULES}} line in {{ic|/etc/mkinitcpio.conf}}:
+
For the full list of options, see the [[man page]] for {{ic|intel}}.
  
MODULES="'''i915'''"
+
== Loading ==
  
If you are using a custom EDID file, you should embed it into initramfs as well:
+
The Intel kernel module should load fine automatically on system boot.
  
{{hc|/etc/mkinitcpio.conf|
+
If it does not happen, then:
2=FILES="/lib/firmware/edid/your_edid.bin"}}
+
  
Now, regenerate the initramfs:
+
* Make sure you do '''not''' have {{ic|nomodeset}} or {{ic|1=vga=}} as a [[kernel parameter]], since Intel requires kernel mode-setting.
 +
* Also, check that you have not disabled Intel by using any modprobe blacklisting within {{ic|/etc/modprobe.d/}} or {{ic|/usr/lib/modprobe.d/}}.
  
# mkinitcpio -p linux
+
=== Enable early KMS ===
  
and reboot the system. Everything should work now.
+
[[Kernel mode setting]] (KMS) is supported by Intel chipsets that use the i915 DRM driver and is mandatory and enabled by default.
 +
 
 +
Refer to [[Kernel mode setting#Early KMS start]] for instuctions on how to enable KMS as soon as possible at the boot process.
  
 
== Module-based Powersaving Options ==
 
== Module-based Powersaving Options ==
  
The '''i915''' kernel module allows for configuration via {{ic|/etc/modprobe.d/i915.conf}} wherein users can define powersavings options. A listing of options is available via the following command:
+
The {{ic|i915}} kernel module allows for configuration via [[Kernel modules#Setting module options|module options]]. Some of the module options impact power saving.
  
$ modinfo i915 | grep power
+
A list of all options along with short descriptions and default values can be generated with the following command:
  
An example {{ic|/etc/modprobe.d/i915.conf}}:
+
$ modinfo -p i915
options i915 i915_enable_rc6=7 i915_enable_fbc=1 lvds_downclock=1
+
 
 +
To check which options are currently enabled, run
 +
 
 +
# systool -m i915 -av
 +
 
 +
You will note that many options default to -1, resulting in per-chip powersaving defaults. It is however possible to configure more aggressive powersaving by using [[Kernel modules#Setting module options|module options]].
 +
 
 +
{{Warning|1=Diverting from the defaults will mark the kernel as [https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=fc9740cebc3ab7c65f3c5f6ce0caf3e4969013ca tainted] from Linux 3.18 onwards. This basically implies using other options than the per-chip defaults is considered experimental and not supported by the developers. }}
 +
 
 +
The following set of options should be generally safe to enable:
 +
 
 +
{{hc|/etc/modprobe.d/i915.conf|<nowiki>
 +
options i915 enable_rc6=1 enable_fbc=1 semaphores=1
 +
</nowiki>}}
 +
 
 +
=== RC6 sleep modes (enable_rc6) ===
 +
 
 +
You can experiment with higher values for {{ic|enable_rc6}}, but your GPU may not support them or the activation of the other options [https://wiki.archlinux.org/index.php?title=Talk:Intel_Graphics&oldid=327547#Kernel_Module_options].
 +
 
 +
The available {{ic|enable_rc6}} values are a bitmask with bit values RC6=1, RC6p=2, RC6pp=4[https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/drivers/gpu/drm/i915/intel_pm.c#n34] - where "RC6p" and "RC6pp" are lower power states.
 +
 
 +
To confirm the current running RC6 level, you can look in sysfs:
 +
 
 +
# cat /sys/class/drm/card0/power/rc6_enable
 +
 
 +
... if the value read is a lower number than expected, the other RC6 level are probably not supported. Passing {{ic|1=drm.debug=0xe}} will add DRM debugging information to the kernel log - possibly including a line like this:
 +
 
 +
[drm:sanitize_rc6_option] Adjusting RC6 mask to 1 (requested 7, valid 1)
 +
 
 +
=== Framebuffer compression (enable_fbc) ===
 +
 
 +
Framebuffer compression may be unreliable or unavailable on Intel GPU generations before Sandy Bridge (generation 6). This results in messages logged to the system journal similar to this one:
 +
kernel: drm: not enough stolen space for compressed buffer, disabling.
  
 
== Tips and tricks ==
 
== Tips and tricks ==
  
=== Choose acceleration method ===
+
=== Tear-free video ===
*UXA - (Unified Acceleration Architecture) is the mature backend that was introduced to support the GEM driver model.
+
*SNA - (Sandybridge's New Acceleration) is the faster successor for hardware supporting it.
+
  
The default method is SNA(as of 2013-08-05[https://projects.archlinux.org/svntogit/packages.git/commit/trunk?h=packages/xf86-video-intel&id=d03f5fb77df413017821f492aa81e5d68def7e48]), which is less stable but faster than UXA. Check benchmarks done by Phoronix [http://www.phoronix.com/scan.php?page=news_item&px=MTEzOTE]. These can be found [http://www.phoronix.com/scan.php?page=article&item=intel_glamor_first&num=1 here for Sandy Bridge] and [http://www.phoronix.com/scan.php?page=article&item=intel_ivy_glamor&num=1 here for Ivy Bridge]. UXA is still a solid option, if experiencing trouble with SNA.
+
The SNA acceleration method causes tearing for some people. To fix this, enable the {{ic|"TearFree"}} option in the driver by adding the following line to your [[#Configuration|configuration file]]:
 +
Option      "TearFree"    "true"
  
To use the old UXA method, create {{ic|/etc/X11/xorg.conf.d/20-intel.conf}} with the following content:
+
See the [https://bugs.freedesktop.org/show_bug.cgi?id=37686 original bug report] for more info.
  
{{hc|/etc/X11/xorg.conf.d/20-intel.conf|
+
{{Note|
Section "Device"
+
* This option may not work when {{ic|SwapbuffersWait}} is {{ic|false}}.
  Identifier  "Intel Graphics"
+
* This option is problematic for applications that are very picky about vsync timing, like [[Wikipedia:Super Meat Boy|Super Meat Boy]].
  Driver      "intel"
+
* This option does not work with UXA acceleration method, only with SNA.
  Option      "AccelMethod" "uxa"
+
* This option should not be needed with DRI3 enabled.
EndSection}}
+
}}
 +
 
 +
=== Disable Vertical Synchronization (VSYNC) ===
 +
The intel-driver uses [http://www.intel.com/support/graphics/sb/CS-004527.htm Triple Buffering] for vertical synchronization, this allows for full performance and avoids tearing. To turn vertical synchronization off (e.g. for benchmarking) use this {{ic|.drirc}} in your home directory:
 +
 
 +
{{hc|~/.drirc|
 +
<device screen&#61;"0" driver&#61;"dri2">
 +
<application name&#61;"Default">
 +
<option name&#61;"vblank_mode" value&#61;"0"/>
 +
</application>
 +
</device>}}
 +
 
 +
{{Warning|Do not use {{Pkg|driconf}} to create this file, it is buggy and will set the wrong driver.}}
  
 
=== Setting scaling mode ===
 
=== Setting scaling mode ===
Line 94: Line 149:
 
This can be useful for some full screen applications:
 
This can be useful for some full screen applications:
  
  $ xrandr --output LVDS1 --set PANEL_FITTING param
+
  $ xrandr --output LVDS1 --set PANEL_FITTING ''param''
  
where {{ic|param}} can be:
+
where {{ic|''param''}} can be:
  
 
* {{ic|center}}: resolution will be kept exactly as defined, no scaling will be made,
 
* {{ic|center}}: resolution will be kept exactly as defined, no scaling will be made,
Line 104: Line 159:
 
If it does not work, try:
 
If it does not work, try:
  
  $ xrandr --output LVDS1 --set "scaling mode" param
+
  $ xrandr --output LVDS1 --set "scaling mode" ''param''
  
where {{ic|param}} is one of {{ic|"Full"}}, {{ic|"Center"}} or {{ic|"Full aspect"}}.
+
where {{ic|''param''}} is one of {{ic|"Full"}}, {{ic|"Center"}} or {{ic|"Full aspect"}}.
  
 
=== KMS Issue: console is limited to small area ===
 
=== KMS Issue: console is limited to small area ===
Line 116: Line 171:
 
=== H.264 decoding on GMA 4500 ===
 
=== H.264 decoding on GMA 4500 ===
  
The {{Pkg|libva-intel-driver}} package provides MPEG-2 decoding only for GMA 4500 series GPUs. The H.264 decoding support is maintained in a separated g45-h264 branch, which can be used by installing {{AUR|libva-driver-intel-g45-h264}} package, available in the [[Arch User Repository]]. Note however that this support is experimental and not currently in active development. Using the VA-API with this driver on a GMA 4500 series GPU will offload the CPU but may not result in as smooth a playback as non-accelerated playback. Tests using mplayer showed that using vaapi to play back an H.264 encoded 1080p video halved the CPU load (compared to the XV overlay) but resulted in very choppy playback, while 720p worked reasonably well [https://bbs.archlinux.org/viewtopic.php?id=150550]. This is echoed by other experiences [http://www.emmolution.org/?p=192&cpage=1#comment-12292].
+
The {{Pkg|libva-intel-driver}} package provides MPEG-2 decoding only for GMA 4500 series GPUs. The H.264 decoding support is maintained in a separated g45-h264 branch, which can be used by installing {{AUR|libva-intel-driver-g45-h264}} package. Note however that this support is experimental and its development has been abandoned. Using the VA-API with this driver on a GMA 4500 series GPU will offload the CPU but may not result in as smooth a playback as non-accelerated playback. Tests using mplayer showed that using vaapi to play back an H.264 encoded 1080p video halved the CPU load (compared to the XV overlay) but resulted in very choppy playback, while 720p worked reasonably well [https://bbs.archlinux.org/viewtopic.php?id=150550]. This is echoed by other experiences [http://www.emmolution.org/?p=192&cpage=1#comment-12292].
 +
Setting the preallocated video ram size higher in bios results in much better hardware decoded playback. Even 1080p h264 works well if this is done.
  
=== Setting gamma and brightness ===
+
=== Setting brightness and gamma ===
  
Intel offers no way to adjust these at the driver level. Luckily these can be set with {{ic|xgamma}} and {{ic|xrandr}}.
+
See [[Backlight]].
  
Gamma can be set with:
+
== Troubleshooting ==
  
$ xgamma -gamma 1.0
+
=== SNA issues ===
  
or:
+
''SNA'' is the default acceleration method in {{Pkg|xf86-video-intel}}. If you are experience issues with ''SNA'' (e.g. pixelated graphics, corrupt text, etc.), try using ''UXA'' instead, which can be done by adding the following line to your [[#Configuration|configuration file]]:
 +
Option      "AccelMethod"  "uxa"
  
$ xrandr --output VGA1 --gamma 1.0:1.0:1.0
+
See {{ic|man 4 intel}} under {{ic|Option "AccelMethod"}}.
  
Brightness can be set with:
+
=== DRI3 issues ===
  
$ xrandr --output VGA1 --brightness 1.0
+
''DRI3'' is the default DRI version in {{Pkg|xf86-video-intel}}. On some systems this can cause issues such as [https://bugs.chromium.org/p/chromium/issues/detail?id=370022 this]. To switch back to ''DRI2'' add the following line to your [[#Configuration|configuration file]]:
 +
Option "DRI" "2"
  
== Troubleshooting ==
+
=== Font and screen corruption in GTK+ applications (missing glyphs after suspend/resume) ===
 +
 
 +
Should you experience missing font glyphs in GTK+ applications, the following workaround might help. [[textedit|Edit]] {{ic|/etc/environment}} to add the following line:
 +
 
 +
{{hc|/etc/environment|output=
 +
COGL_ATLAS_DEFAULT_BLIT_MODE=framebuffer
 +
}}
 +
 
 +
See also [https://bugs.freedesktop.org/show_bug.cgi?id=88584 FreeDesktop bug 88584].
  
 
=== Blank screen during boot, when "Loading modules" ===
 
=== Blank screen during boot, when "Loading modules" ===
  
If using "late start" KMS and the screen goes blank when "Loading modules", it may help to add {{ic|i915}} and {{ic|intel_agp}} to the initramfs. See [[Intel#KMS (Kernel Mode Setting)|the above]] KMS section.
+
If using "late start" KMS and the screen goes blank when "Loading modules", it may help to add {{ic|i915}} and {{ic|intel_agp}} to the initramfs. See [[Kernel mode setting#Early KMS start]] section.
  
Alternatively, appending the following [[Kernel parameters|kernel parameter]] seems to work as well:
+
Alternatively, appending the following [[kernel parameter]] seems to work as well:
  
 
  video=SVIDEO-1:d
 
  video=SVIDEO-1:d
Line 147: Line 213:
  
 
  video=VGA-1:1280x800
 
  video=VGA-1:1280x800
 
=== Tear-free video ===
 
 
If using the SNA acceleration method, ablate video tearing by adding the following to the {{ic|Device}} section of {{ic|/etc/X11/xorg.conf.d/20-intel.conf}}:
 
 
Option "TearFree" "true"
 
 
{{Note|
 
* This option may not work when {{ic|SwapbuffersWait}} is {{ic|false}}.
 
* This option is problematic for applications that are very picky about vsync timing, like [[Wikipedia:Super Meat Boy|Super Meat Boy]].
 
}}
 
  
 
=== X freeze/crash with intel driver ===
 
=== X freeze/crash with intel driver ===
  
Some issues with X crashing, GPU hanging, or problems with X freezing, can be fixed by disabling the GPU usage with the {{ic|NoAccel}} option:
+
Some issues with X crashing, GPU hanging, or problems with X freezing, can be fixed by disabling the GPU usage with the {{ic|NoAccel}} option - add the following lines to your [[#Configuration|configuration file]]:
 
+
{{hc|/etc/X11/xorg.conf.d/20-intel.conf|
+
Section "Device"
+
  Identifier "Intel Graphics"
+
  Driver "intel"
+
 
   Option "NoAccel" "True"
 
   Option "NoAccel" "True"
EndSection}}
 
  
 
Alternatively, try to disable the 3D acceleration only with the {{ic|DRI}} option:
 
Alternatively, try to disable the 3D acceleration only with the {{ic|DRI}} option:
{{hc|/etc/X11/xorg.conf.d/20-intel.conf|
 
Section "Device"
 
  Identifier "Intel Graphics"
 
  Driver "intel"
 
 
   Option "DRI" "False"
 
   Option "DRI" "False"
EndSection}}
 
  
 
If you experience crashes and have
 
If you experience crashes and have
Line 183: Line 227:
 
  Option "AccelMethod" "sna"
 
  Option "AccelMethod" "sna"
  
in your config file, in most cases these can be fixed by adding
+
in your configuration file, in most cases these can be fixed by adding
  
 
  i915.semaphores=1
 
  i915.semaphores=1
Line 189: Line 233:
 
to your boot parameters.
 
to your boot parameters.
  
=== Adding undetected resolutions ===
+
If you are using kernel 4.0.X or above on Baytrail architecture and frequently encounter complete system freezes (especially when watching video or using GFX intensivelly), you should try adding the following kernel option as a workaround, until [https://bugzilla.kernel.org/show_bug.cgi?id=109051 this bug] will be fixed permanently.
  
This issue is covered on the [[Xrandr#Adding_undetected_resolutions|Xrandr page]].
+
  intel_idle.max_cstate=1
  
=== Slowness after an upgrade to libGL 9 and Intel-DRI 9 ===
+
=== Adding undetected resolutions ===
  
[https://wiki.archlinux.org/index.php/Downgrading_Packages#ARM Downgrade] to Intel-DRI 8 and libGL 8.
+
This issue is covered on the [[Xrandr#Adding undetected resolutions|Xrandr page]].
  
=== Black textures in video games ===
+
=== Weathered colors (color range problem) ===
  
Users experiencing black textures in video games may find a solution by enabling S3TC texture compression support. 
+
{{Note|This problem is related to the [http://lists.freedesktop.org/archives/dri-devel/2013-January/033576.html changes] in the kernel 3.9. This problem still remains in kernel 4.1.}}
It can be enabled through {{Pkg|driconf}} or by installing {{Pkg|libtxc_dxtn}}.
+
Kernel 3.9 contains a new default "Automatic" mode for the "Broadcast RGB" property in the Intel driver. It is almost equivalent to "Limited 16:235" (instead of the old default "Full") whenever an HDMI/DP output is in a [http://raspberrypi.stackexchange.com/questions/7332/what-is-the-difference-between-cea-and-dmt CEA mode]. If a monitor does not support signal in limited color range, it will cause weathered colors.
  
This "issue" will be fixed very soon in the [http://www.phoronix.com/scan.php?page=news_item&px=MTIwOTg newer drivers].
+
{{Note|Some monitors/TVs support both color range. In that case an option often known as ''Black Level'' may need to be adjusted to make them handle the signal correctly. Some TVs can handle signal in limited range only. Setting Broadcast RGB to "Full" will cause color clipping. You may need to set it to "Limited 16:235" manually to avoid the clipping.}}
  
Read more about S3TC at:
+
One can force mode e.g. {{ic|xrandr --output <HDMI> --set "Broadcast RGB" "Full"}} (replace {{ic|<HDMI>}} with the appropriate output device, verify by running {{ic|xrandr}}).
* http://dri.freedesktop.org/wiki/S3TC
+
* http://en.wikipedia.org/wiki/S3_Texture_Compression
+
  
One of the games that is affected by this issue is [http://www.phoronix.com/scan.php?page=article&item=unigine_oilrush_gold&num=2 Oil Rush] and World of Warcraft using Wine.
+
Unfortunately, the Intel driver does not support setting the color range through an {{ic|xorg.conf.d}} configuration file.
  
=== Weathered colors (colorspace problem) ===
+
A [https://bugzilla.kernel.org/show_bug.cgi?id=94921 bug report] is filed and a patch can be found in the attachment.
 
+
{{Note|This problem is related to the changes in the kernel 3.9. This problem still remains in kernel 3.10}}
+
Kernel 3.9 contains the Intel driver changes allowing easy RGB Limited range settings which can cause weathered colors in some cases. It is related to the new "Automatic" mode for the "Broadcast RGB" property.
+
One can force mode e.g. {{ic|xrandr --output <HDMI> --set "Broadcast RGB" "Full"}} (replace {{ic|<HDMI>}} with the appropriate output device, verify by running {{ic|xrandr}}). You can add it into your {{ic |.xprofile}}, make it executable to run the command before it will start the graphical mode.
+
{{Note|Some TVs can only display colors from 16-255 so setting to Full will cause color clipping in the 0-15 range so it's best to leave it at Automatic which will automatically detect whether it needs to compress the colorspace for your TV.}}
+
  
 
Also there are other related problems which can be fixed editing GPU registers. More information can be found [http://lists.freedesktop.org/archives/intel-gfx/2012-April/016217.html] and [http://github.com/OpenELEC/OpenELEC.tv/commit/09109e9259eb051f34f771929b6a02635806404c].
 
Also there are other related problems which can be fixed editing GPU registers. More information can be found [http://lists.freedesktop.org/archives/intel-gfx/2012-April/016217.html] and [http://github.com/OpenELEC/OpenELEC.tv/commit/09109e9259eb051f34f771929b6a02635806404c].
  
=== Backlight not fully adjusting, or adjusting at all after resume. ===
+
=== Backlight is not adjustable===
  
If you are using Intel graphics and have no control over your manufacturer suplied hotkeys for changing screen brightness, try booting the kernel parameter:
+
If after resuming from suspend, the hotkeys for changing the screen brightness do not take effect, check your configuration against the [[Backlight]] article.
+
acpi_backlight=vendor
+
  
If that doesnt solve the problem, many folks have gotten mileage from either:
+
If the problem persists, try one of the following [[kernel parameters]]:
  
 
  acpi_osi=Linux
 
  acpi_osi=Linux
 +
acpi_osi="!Windows 2012"
 +
acpi_osi=
  
or
+
=== Disabling frame buffer compression ===
  
acpi_osi="!Windows 2012"
+
Enabling frame buffer compression on pre-Sandy Bridge CPUs results in endless error messages:
  
in addition to the earlier mentioned parameter.
+
$ dmesg |tail
 +
[ 2360.475430] [drm] not enough stolen space for compressed buffer (need 4325376 bytes), disabling
 +
[ 2360.475437] [drm] hint: you may be able to increase stolen memory size in the BIOS to avoid this
  
If neither of those solve your problem, you should edit/create {{ic|/etc/X11/xorg.conf.d/20-intel.conf}} with the following content:
+
The solution is to disable frame buffer compression which will imperceptibly increase power consumption (around 0.06 W). In order to disable it add {{ic|i915.enable_fbc&#61;0}} to the kernel line parameters. More information on the results of disabled compression can be found [http://kernel.ubuntu.com/~cking/power-benchmarking/background-colour-and-framebuffer-compression/ here].
  
{{hc|/etc/X11/xorg.conf.d/20-intel.conf|
+
=== Corruption/Unresponsiveness in Chromium and Firefox ===
Section "Device"
+
        Identifier  "card0"
+
        Driver      "intel"
+
        Option      "Backlight"  "intel_backlight"
+
        BusID      "PCI:0:2:0"
+
  
EndSection}}
+
If you experience corruption or unresponsiveness in Chromium and/or Firefox [[#SNA issues|set the AccelMethod to "uxa"]].
 +
 
 +
=== Kernel crashing w/kernels 4.0+ on Broadwell/Core-M chips ===
 +
 
 +
A few seconds after X/Wayland loads the machine will freeze and journalctl will log a kernel crash referencing the Intel graphics as below:
 +
 
 +
Jun 16 17:54:03 hostname kernel: BUG: unable to handle kernel NULL pointer dereference at          (null)
 +
Jun 16 17:54:03 hostname kernel: IP: [<          (null)>]          (null)
 +
...
 +
Jun 16 17:54:03 hostname kernel: CPU: 0 PID: 733 Comm: gnome-shell Tainted: G    U    O    4.0.5-1-ARCH #1
 +
...
 +
Jun 16 17:54:03 hostname kernel: Call Trace:
 +
Jun 16 17:54:03 hostname kernel:  [<ffffffffa055cc27>] ? i915_gem_object_sync+0xe7/0x190 [i915]
 +
Jun 16 17:54:03 hostname kernel:  [<ffffffffa0579634>] intel_execlists_submission+0x294/0x4c0 [i915]
 +
Jun 16 17:54:03 hostname kernel:  [<ffffffffa05539fc>] i915_gem_do_execbuffer.isra.12+0xabc/0x1230 [i915]
 +
Jun 16 17:54:03 hostname kernel:  [<ffffffffa055d349>] ? i915_gem_object_set_to_cpu_domain+0xa9/0x1f0 [i915]
 +
Jun 16 17:54:03 hostname kernel:  [<ffffffff811ba2ae>] ? __kmalloc+0x2e/0x2a0
 +
Jun 16 17:54:03 hostname kernel:  [<ffffffffa0555471>] i915_gem_execbuffer2+0x141/0x2b0 [i915]
 +
Jun 16 17:54:03 hostname kernel:  [<ffffffffa042fcab>] drm_ioctl+0x1db/0x640 [drm]
 +
Jun 16 17:54:03 hostname kernel:  [<ffffffffa0555330>] ? i915_gem_execbuffer+0x450/0x450 [i915]
 +
Jun 16 17:54:03 hostname kernel:  [<ffffffff8122339b>] ? eventfd_ctx_read+0x16b/0x200
 +
Jun 16 17:54:03 hostname kernel:  [<ffffffff811ebc36>] do_vfs_ioctl+0x2c6/0x4d0
 +
Jun 16 17:54:03 hostname kernel:  [<ffffffff811f6452>] ? __fget+0x72/0xb0
 +
Jun 16 17:54:03 hostname kernel:  [<ffffffff811ebec1>] SyS_ioctl+0x81/0xa0
 +
Jun 16 17:54:03 hostname kernel:  [<ffffffff8157a589>] system_call_fastpath+0x12/0x17
 +
Jun 16 17:54:03 hostname kernel: Code:  Bad RIP value.
 +
Jun 16 17:54:03 hostname kernel: RIP  [<          (null)>]          (null)
 +
 
 +
This can be fixed by disabling execlist support which was changed to default on with kernel 4.0. Add the following kernel parameter:
 +
i915.enable_execlists=0
 +
 
 +
This is known to be broken to at least kernel 4.0.5.
 +
 
 +
===Skylake support===
 +
 
 +
For Linux kernels older than 4.3.x, {{ic|i915.preliminary_hw_support&#61;1}} must be added to your boot parameters for the driver to work on the new Intel Skylake (6th gen.) GPUs. On a fully updated system running kernel 4.3.x and up, this step is unnecessary.
 +
 
 +
{{Note|Fixes for the GPU/DRM bugs are pending in kernel 4.6. The following steps are unnecessary if you have [[testing]] repository enabled, or once 4.6 lands in [[Official_repositories#core|core]].}}
 +
 
 +
The i915 DRM driver is known to cause various GPU hangs, crashes and even full system freezes. It might be necessary to disable hardware acceleration to workaround these issues. One solution is to use the following Xorg configuration.
  
If you are using the SNA acceleration as mentioned above, create the file as follows:
 
 
{{hc|/etc/X11/xorg.conf.d/20-intel.conf|
 
{{hc|/etc/X11/xorg.conf.d/20-intel.conf|
 
Section "Device"
 
Section "Device"
        Identifier  "card0"
+
Identifier  "Intel Graphics"
        Driver      "intel"
+
Driver      "intel"
        Option     "AccelMethod" "sna"
+
Option     "DRI" "false"
        Option      "Backlight"    "intel_backlight"
+
EndSection
        BusID      "PCI:0:2:0"
+
}}
  
EndSection}}
+
Otherwise, specific applications such as Chromium and Firefox browsers can be instructed to disable hardware rendering directly.
  
=== Disabling frame buffer compression ===
+
Another option that seems to work for some users is to add the {{ic|1=i915.enable_rc6=0}} kernel boot parameter, which will cause the CPU/GPU to remain in high-power modes, but seems to resolve most cases of GPU hangs and system freezes.
  
On some cards such as Intel Corporation Mobile 4 Series Chipsets, enabled and forced frame buffer compression results in endless error messages:
+
{{Note|If the system appears to hang after "Loading Initial Ramdisk", make sure that the IGD aperture size in BIOS is less than 4GB.}}
  
$ dmesg |tail
+
=== Lag in Windows guests ===
[ 2360.475430] [drm] not enough stolen space for compressed buffer (need 4325376 bytes), disabling
+
 
[ 2360.475437] [drm] hint: you may be able to increase stolen memory size in the BIOS to avoid this
+
The video output of a Windows guest in VirtualBox sometimes hangs until the host forces a screen update (e.g. by moving the mouse cursor). Removing the {{ic|1=enable_fbc=1}} option fixes this issue.
 +
 
 +
=== Screen flickering ===
  
The solution is to disable frame buffer compression which will slightly increase power consumption. In order to disable it add {{ic|i915.i915_enable_fbc&#61;0}} to the kernel line parameters. More information on the results of disabled compression can be found [http://zinc.canonical.com/~cking/power-benchmarking/background-colour-and-framebuffer-compression/results.txt here].
+
A temporary solution is to add the {{ic|1=i915.enable_rc6=0}} [[Kernel_parameters|kernel boot parameter ]].
  
 
== See also ==
 
== See also ==
  
 
* https://01.org/linuxgraphics/documentation (includes a list of supported hardware)
 
* https://01.org/linuxgraphics/documentation (includes a list of supported hardware)
* [[KMS]] - Arch wiki article on kernel mode setting
 
* [[Xrandr]] - Problems setting the resolution
 
* Arch Linux forums: [https://bbs.archlinux.org/viewtopic.php?pid=522665#p522665 Intel 945GM, Xorg, Kernel - performance]
 

Latest revision as of 00:55, 24 September 2016

Since Intel provides and supports open source drivers, Intel graphics are essentially plug-and-play.

For a comprehensive list of Intel GPU models and corresponding chipsets and CPUs, see this comparison on Wikipedia.

Note:

Installation

Install the xf86-video-intel package. It provides the DDX driver for 2D acceleration and it pulls in mesa as a dependency, providing the DRI driver for 3D acceleration.

To enable OpenGL support, also install mesa-libgl. If you are on x86_64 and need 32-bit support, also install lib32-mesa-libgl from the multilib repository.

Also see Hardware video acceleration.

For Vulkan support, install vulkan-intel on Ivy-Bridge or newer GPUs.

Configuration

There is no need for any configuration to run Xorg.

Note: The latest generation of integrated GPUs (Skylake/HD 530 for instance) may require additional configuration, see #Skylake support

However, to take advantage of some driver options, you will need to create a Xorg configuration file similar to the one below:

/etc/X11/xorg.conf.d/20-intel.conf
Section "Device"
   Identifier  "Intel Graphics"
   Driver      "intel"
EndSection

Additional options are added by the user on new lines below Driver.

Note:
  • You may need to indicate Option "AccelMethod" when creating a configuration file, even just to set it to the default method (currently "sna"); otherwise, X may crash.
  • You might need to add more device sections than the one listed above. This will be indicated where necessary.

For the full list of options, see the man page for intel.

Loading

The Intel kernel module should load fine automatically on system boot.

If it does not happen, then:

  • Make sure you do not have nomodeset or vga= as a kernel parameter, since Intel requires kernel mode-setting.
  • Also, check that you have not disabled Intel by using any modprobe blacklisting within /etc/modprobe.d/ or /usr/lib/modprobe.d/.

Enable early KMS

Kernel mode setting (KMS) is supported by Intel chipsets that use the i915 DRM driver and is mandatory and enabled by default.

Refer to Kernel mode setting#Early KMS start for instuctions on how to enable KMS as soon as possible at the boot process.

Module-based Powersaving Options

The i915 kernel module allows for configuration via module options. Some of the module options impact power saving.

A list of all options along with short descriptions and default values can be generated with the following command:

$ modinfo -p i915

To check which options are currently enabled, run

# systool -m i915 -av

You will note that many options default to -1, resulting in per-chip powersaving defaults. It is however possible to configure more aggressive powersaving by using module options.

Warning: Diverting from the defaults will mark the kernel as tainted from Linux 3.18 onwards. This basically implies using other options than the per-chip defaults is considered experimental and not supported by the developers.

The following set of options should be generally safe to enable:

/etc/modprobe.d/i915.conf
options i915 enable_rc6=1 enable_fbc=1 semaphores=1

RC6 sleep modes (enable_rc6)

You can experiment with higher values for enable_rc6, but your GPU may not support them or the activation of the other options [3].

The available enable_rc6 values are a bitmask with bit values RC6=1, RC6p=2, RC6pp=4[4] - where "RC6p" and "RC6pp" are lower power states.

To confirm the current running RC6 level, you can look in sysfs:

# cat /sys/class/drm/card0/power/rc6_enable

... if the value read is a lower number than expected, the other RC6 level are probably not supported. Passing drm.debug=0xe will add DRM debugging information to the kernel log - possibly including a line like this:

[drm:sanitize_rc6_option] Adjusting RC6 mask to 1 (requested 7, valid 1)

Framebuffer compression (enable_fbc)

Framebuffer compression may be unreliable or unavailable on Intel GPU generations before Sandy Bridge (generation 6). This results in messages logged to the system journal similar to this one:

kernel: drm: not enough stolen space for compressed buffer, disabling.

Tips and tricks

Tear-free video

The SNA acceleration method causes tearing for some people. To fix this, enable the "TearFree" option in the driver by adding the following line to your configuration file:

Option      "TearFree"    "true"

See the original bug report for more info.

Note:
  • This option may not work when SwapbuffersWait is false.
  • This option is problematic for applications that are very picky about vsync timing, like Super Meat Boy.
  • This option does not work with UXA acceleration method, only with SNA.
  • This option should not be needed with DRI3 enabled.

Disable Vertical Synchronization (VSYNC)

The intel-driver uses Triple Buffering for vertical synchronization, this allows for full performance and avoids tearing. To turn vertical synchronization off (e.g. for benchmarking) use this .drirc in your home directory:

~/.drirc
<device screen="0" driver="dri2">
	<application name="Default">
		<option name="vblank_mode" value="0"/>
	</application>
</device>
Warning: Do not use driconf to create this file, it is buggy and will set the wrong driver.

Setting scaling mode

This can be useful for some full screen applications:

$ xrandr --output LVDS1 --set PANEL_FITTING param

where param can be:

  • center: resolution will be kept exactly as defined, no scaling will be made,
  • full: scale the resolution so it uses the entire screen or
  • full_aspect: scale the resolution to the maximum possible but keep the aspect ratio.

If it does not work, try:

$ xrandr --output LVDS1 --set "scaling mode" param

where param is one of "Full", "Center" or "Full aspect".

KMS Issue: console is limited to small area

One of the low-resolution video ports may be enabled on boot which is causing the terminal to utilize a small area of the screen. To fix, explicitly disable the port with an i915 module setting with video=SVIDEO-1:d in the kernel command line parameter in the bootloader. See Kernel parameters for more info.

If that does not work, try disabling TV1 or VGA1 instead of SVIDEO-1.

H.264 decoding on GMA 4500

The libva-intel-driver package provides MPEG-2 decoding only for GMA 4500 series GPUs. The H.264 decoding support is maintained in a separated g45-h264 branch, which can be used by installing libva-intel-driver-g45-h264AUR package. Note however that this support is experimental and its development has been abandoned. Using the VA-API with this driver on a GMA 4500 series GPU will offload the CPU but may not result in as smooth a playback as non-accelerated playback. Tests using mplayer showed that using vaapi to play back an H.264 encoded 1080p video halved the CPU load (compared to the XV overlay) but resulted in very choppy playback, while 720p worked reasonably well [5]. This is echoed by other experiences [6]. Setting the preallocated video ram size higher in bios results in much better hardware decoded playback. Even 1080p h264 works well if this is done.

Setting brightness and gamma

See Backlight.

Troubleshooting

SNA issues

SNA is the default acceleration method in xf86-video-intel. If you are experience issues with SNA (e.g. pixelated graphics, corrupt text, etc.), try using UXA instead, which can be done by adding the following line to your configuration file:

Option      "AccelMethod"  "uxa"

See man 4 intel under Option "AccelMethod".

DRI3 issues

DRI3 is the default DRI version in xf86-video-intel. On some systems this can cause issues such as this. To switch back to DRI2 add the following line to your configuration file:

Option "DRI" "2"

Font and screen corruption in GTK+ applications (missing glyphs after suspend/resume)

Should you experience missing font glyphs in GTK+ applications, the following workaround might help. Edit /etc/environment to add the following line:

/etc/environment
COGL_ATLAS_DEFAULT_BLIT_MODE=framebuffer

See also FreeDesktop bug 88584.

Blank screen during boot, when "Loading modules"

If using "late start" KMS and the screen goes blank when "Loading modules", it may help to add i915 and intel_agp to the initramfs. See Kernel mode setting#Early KMS start section.

Alternatively, appending the following kernel parameter seems to work as well:

video=SVIDEO-1:d

If you need to output to VGA then try this:

video=VGA-1:1280x800

X freeze/crash with intel driver

Some issues with X crashing, GPU hanging, or problems with X freezing, can be fixed by disabling the GPU usage with the NoAccel option - add the following lines to your configuration file:

  Option "NoAccel" "True"

Alternatively, try to disable the 3D acceleration only with the DRI option:

  Option "DRI" "False"

If you experience crashes and have

Option "TearFree" "true"
Option "AccelMethod" "sna"

in your configuration file, in most cases these can be fixed by adding

i915.semaphores=1

to your boot parameters.

If you are using kernel 4.0.X or above on Baytrail architecture and frequently encounter complete system freezes (especially when watching video or using GFX intensivelly), you should try adding the following kernel option as a workaround, until this bug will be fixed permanently.

 intel_idle.max_cstate=1

Adding undetected resolutions

This issue is covered on the Xrandr page.

Weathered colors (color range problem)

Note: This problem is related to the changes in the kernel 3.9. This problem still remains in kernel 4.1.

Kernel 3.9 contains a new default "Automatic" mode for the "Broadcast RGB" property in the Intel driver. It is almost equivalent to "Limited 16:235" (instead of the old default "Full") whenever an HDMI/DP output is in a CEA mode. If a monitor does not support signal in limited color range, it will cause weathered colors.

Note: Some monitors/TVs support both color range. In that case an option often known as Black Level may need to be adjusted to make them handle the signal correctly. Some TVs can handle signal in limited range only. Setting Broadcast RGB to "Full" will cause color clipping. You may need to set it to "Limited 16:235" manually to avoid the clipping.

One can force mode e.g. xrandr --output <HDMI> --set "Broadcast RGB" "Full" (replace <HDMI> with the appropriate output device, verify by running xrandr).

Unfortunately, the Intel driver does not support setting the color range through an xorg.conf.d configuration file.

A bug report is filed and a patch can be found in the attachment.

Also there are other related problems which can be fixed editing GPU registers. More information can be found [7] and [8].

Backlight is not adjustable

If after resuming from suspend, the hotkeys for changing the screen brightness do not take effect, check your configuration against the Backlight article.

If the problem persists, try one of the following kernel parameters:

acpi_osi=Linux
acpi_osi="!Windows 2012"
acpi_osi=

Disabling frame buffer compression

Enabling frame buffer compression on pre-Sandy Bridge CPUs results in endless error messages:

$ dmesg |tail 
[ 2360.475430] [drm] not enough stolen space for compressed buffer (need 4325376 bytes), disabling
[ 2360.475437] [drm] hint: you may be able to increase stolen memory size in the BIOS to avoid this

The solution is to disable frame buffer compression which will imperceptibly increase power consumption (around 0.06 W). In order to disable it add i915.enable_fbc=0 to the kernel line parameters. More information on the results of disabled compression can be found here.

Corruption/Unresponsiveness in Chromium and Firefox

If you experience corruption or unresponsiveness in Chromium and/or Firefox set the AccelMethod to "uxa".

Kernel crashing w/kernels 4.0+ on Broadwell/Core-M chips

A few seconds after X/Wayland loads the machine will freeze and journalctl will log a kernel crash referencing the Intel graphics as below:

Jun 16 17:54:03 hostname kernel: BUG: unable to handle kernel NULL pointer dereference at           (null)
Jun 16 17:54:03 hostname kernel: IP: [<          (null)>]           (null)
...
Jun 16 17:54:03 hostname kernel: CPU: 0 PID: 733 Comm: gnome-shell Tainted: G     U     O    4.0.5-1-ARCH #1
...
Jun 16 17:54:03 hostname kernel: Call Trace:
Jun 16 17:54:03 hostname kernel:  [<ffffffffa055cc27>] ? i915_gem_object_sync+0xe7/0x190 [i915]
Jun 16 17:54:03 hostname kernel:  [<ffffffffa0579634>] intel_execlists_submission+0x294/0x4c0 [i915]
Jun 16 17:54:03 hostname kernel:  [<ffffffffa05539fc>] i915_gem_do_execbuffer.isra.12+0xabc/0x1230 [i915]
Jun 16 17:54:03 hostname kernel:  [<ffffffffa055d349>] ? i915_gem_object_set_to_cpu_domain+0xa9/0x1f0 [i915]
Jun 16 17:54:03 hostname kernel:  [<ffffffff811ba2ae>] ? __kmalloc+0x2e/0x2a0
Jun 16 17:54:03 hostname kernel:  [<ffffffffa0555471>] i915_gem_execbuffer2+0x141/0x2b0 [i915]
Jun 16 17:54:03 hostname kernel:  [<ffffffffa042fcab>] drm_ioctl+0x1db/0x640 [drm]
Jun 16 17:54:03 hostname kernel:  [<ffffffffa0555330>] ? i915_gem_execbuffer+0x450/0x450 [i915]
Jun 16 17:54:03 hostname kernel:  [<ffffffff8122339b>] ? eventfd_ctx_read+0x16b/0x200
Jun 16 17:54:03 hostname kernel:  [<ffffffff811ebc36>] do_vfs_ioctl+0x2c6/0x4d0
Jun 16 17:54:03 hostname kernel:  [<ffffffff811f6452>] ? __fget+0x72/0xb0
Jun 16 17:54:03 hostname kernel:  [<ffffffff811ebec1>] SyS_ioctl+0x81/0xa0
Jun 16 17:54:03 hostname kernel:  [<ffffffff8157a589>] system_call_fastpath+0x12/0x17
Jun 16 17:54:03 hostname kernel: Code:  Bad RIP value.
Jun 16 17:54:03 hostname kernel: RIP  [<          (null)>]           (null)

This can be fixed by disabling execlist support which was changed to default on with kernel 4.0. Add the following kernel parameter:

i915.enable_execlists=0

This is known to be broken to at least kernel 4.0.5.

Skylake support

For Linux kernels older than 4.3.x, i915.preliminary_hw_support=1 must be added to your boot parameters for the driver to work on the new Intel Skylake (6th gen.) GPUs. On a fully updated system running kernel 4.3.x and up, this step is unnecessary.

Note: Fixes for the GPU/DRM bugs are pending in kernel 4.6. The following steps are unnecessary if you have testing repository enabled, or once 4.6 lands in core.

The i915 DRM driver is known to cause various GPU hangs, crashes and even full system freezes. It might be necessary to disable hardware acceleration to workaround these issues. One solution is to use the following Xorg configuration.

/etc/X11/xorg.conf.d/20-intel.conf
Section "Device"
	Identifier  "Intel Graphics"
	Driver      "intel"
	Option	    "DRI"	"false"
EndSection

Otherwise, specific applications such as Chromium and Firefox browsers can be instructed to disable hardware rendering directly.

Another option that seems to work for some users is to add the i915.enable_rc6=0 kernel boot parameter, which will cause the CPU/GPU to remain in high-power modes, but seems to resolve most cases of GPU hangs and system freezes.

Note: If the system appears to hang after "Loading Initial Ramdisk", make sure that the IGD aperture size in BIOS is less than 4GB.

Lag in Windows guests

The video output of a Windows guest in VirtualBox sometimes hangs until the host forces a screen update (e.g. by moving the mouse cursor). Removing the enable_fbc=1 option fixes this issue.

Screen flickering

A temporary solution is to add the i915.enable_rc6=0 kernel boot parameter .

See also