Difference between revisions of "Intel graphics"

From ArchWiki
Jump to navigation Jump to search
(→‎Backlight is not adjustable: Samsung devices need another kernel parameter to get intel_backlight working)
 
(292 intermediate revisions by 88 users not shown)
Line 9: Line 9:
 
[[ja:Intel Graphics]]
 
[[ja:Intel Graphics]]
 
[[pl:Intel graphics]]
 
[[pl:Intel graphics]]
 +
[[pt:Intel graphics]]
 
[[ru:Intel graphics]]
 
[[ru:Intel graphics]]
[[zh-cn:Intel graphics]]
+
[[zh-hans:Intel graphics]]
[[zh-tw:Intel graphics]]
+
[[zh-hant:Intel graphics]]
 
{{Related articles start}}
 
{{Related articles start}}
{{Related|Intel GMA3600}}
+
{{Related|Intel GMA 3600}}
{{Related|Poulsbo}}
 
 
{{Related|Xorg}}
 
{{Related|Xorg}}
 
{{Related|Kernel mode setting}}
 
{{Related|Kernel mode setting}}
 
{{Related|Xrandr}}
 
{{Related|Xrandr}}
 
{{Related|Hybrid graphics}}
 
{{Related|Hybrid graphics}}
 +
{{Related|Vulkan}}
 +
{{Related|GPGPU}}
 
{{Related articles end}}
 
{{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:List of Intel graphics processing units]].
  
{{Note|PowerVR-based graphics ([[GMA 500]] and [[Intel GMA3600|GMA 3600]] series) are not supported by open source drivers.}}
+
{{Note|PowerVR-based graphics ([[Intel GMA 3600|GMA 3600]] series) are not supported by open source drivers.}}
  
 
== Installation ==
 
== Installation ==
  
Prerequisite: [[Xorg]].
+
[[Install]] the {{Pkg|mesa}} package, which provides the [[wikipedia:Direct_Rendering_Infrastructure|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.
 
  
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.
+
* For 32-bit application support, also install the {{Pkg|lib32-mesa}} package from the [[multilib]] repository.
 +
* For the [[wikipedia:X.Org_Server#DDX|DDX]] driver (which provides 2D acceleration in [[Xorg]]), [[install]] the {{Pkg|xf86-video-intel}} package. (Often not recommended, see note below.)
 +
* For [[Vulkan]] support (''Ivy Bridge'' and newer), install the {{Pkg|vulkan-intel}} package.
  
Install the [[VA-API]] driver and library provided by the {{Pkg|libva-intel-driver}} and {{Pkg|libva}} packages respectively. On older GPUs, this is provided instead by the [[XvMC]] driver, which is included with the DDX driver.
+
Also see [[Hardware video acceleration]].
  
== Configuration ==
+
{{Note|1=Some ([http://www.phoronix.com/scan.php?page=news_item&px=Ubuntu-Debian-Abandon-Intel-DDX Debian & Ubuntu], [http://www.phoronix.com/scan.php?page=news_item&px=Fedora-Xorg-Intel-DDX-Switch Fedora], [https://community.kde.org/Plasma/5.9_Errata#Intel_GPUs KDE]) recommend not installing the {{Pkg|xf86-video-intel}} driver, and instead falling back on the modesetting driver for Gen4 and newer GPUs (GMA 3000 from 2006 and newer). See [https://web.archive.org/web/20160714232204/https://www.reddit.com/r/archlinux/comments/4cojj9/it_is_probably_time_to_ditch_xf86videointel/], [http://www.phoronix.com/scan.php?page=article&item=intel-modesetting-2017&num=1], [[Xorg#Installation]], and {{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].}}
 
 
There is no need for any configuration to run [[X]].
 
 
 
For the full list of options, see the [[man page]] for {{ic|intel}}.
 
  
 
== Loading ==
 
== Loading ==
Line 54: Line 52:
 
=== Enable early KMS ===
 
=== Enable early KMS ===
  
{{Tip|If you have problems with the resolution, you can check whether [[Kernel mode setting#Forcing modes and EDID|enforcing the mode]] helps.}}
+
[[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 instructions on how to enable KMS as soon as possible at the boot process.
 +
 
 +
=== Enable GuC / HuC firmware loading ===
 +
 
 +
For Skylake and newer processors, some video features (e.g. CBR rate control on SKL low-power encoding mode) may require the use of an updated GPU firmware, which is currently (as of 4.16) not enabled by default. Enabling GuC/HuC firmware loading can cause issues on some systems; disable it if you experience freezing (for example, after resuming from hibernation).
 +
 
 +
{{Note|See [[Gentoo:Intel#Feature support]] for an overview of Intel processor generations.}}
 +
 
 +
For those processors it is necessary to add {{ic|1=i915.enable_guc=2}} to the [[kernel parameters]] to enable both GuC and HuC firmware loading. Alternatively, if the [[initramfs]] already includes the {{ic|i915}} module (see [[Kernel mode setting#Early KMS start]]), you can set these options through a file in {{ic|/etc/modprobe.d/}}, e.g.:
 +
 
 +
{{hc|/etc/modprobe.d/i915.conf|2=
 +
options i915 enable_guc=2
 +
}}
 +
 
 +
{{Out of date|GuC submission has been [https://patchwork.kernel.org/patch/10904591 completely disabled] for the kernel 5.4 and later, due to it reducing performance and causing bugs. Setting {{ic|1=enable_guc=3}} has no effect.}}
  
[[Kernel mode setting]] (KMS) is supported by Intel chipsets that use the i915 DRM driver and is mandatory and enabled by default.  
+
{{Note|It is possible to enable both GuC/HuC firmware loading and GuC submission by using the {{ic|1=enable_guc=3}} module parameter, although this is generally discouraged and may even negatively affect your system stability.}}
  
KMS is typically initialized after the [[Arch boot process#initramfs|initramfs stage]]. It is possible, however, to enable KMS during the initramfs stage. To do this, add the {{ic|i915}} module to the {{ic|MODULES}} line in {{ic|/etc/mkinitcpio.conf}}:
+
You can verify both are enabled by using [[dmesg]]:
  
MODULES="... i915 ..."
+
{{hc|$ dmesg|2=
 +
[drm] HuC: Loaded firmware i915/kbl_huc_ver02_00_1810.bin (version 2.0)
 +
[drm] GuC: Loaded firmware i915/kbl_guc_ver9_39.bin (version 9.39)
 +
i915 0000:00:02.0: GuC firmware version 9.39
 +
i915 0000:00:02.0: GuC submission enabled
 +
i915 0000:00:02.0: HuC enabled
 +
}}
  
{{Tip|
+
Alternatively, check using:
Users might need to add {{Ic|intel_agp}} before {{Ic|i915}} to suppress the ACPI errors. The order matters because the modules are activated in sequence.}}
 
  
If you are using a custom [[Wikipedia:Extended display identification data|EDID]] file, you should embed it into initramfs as well:
+
# cat /sys/kernel/debug/dri/0/i915_huc_load_status
 +
# cat /sys/kernel/debug/dri/0/i915_guc_load_status
  
{{hc|/etc/mkinitcpio.conf|
+
{{Warning|1=Using [[Intel GVT-g|GVT-g graphics virtualization]] by setting {{ic|1=enable_gvt=1}} is not supported as of linux 4.20.11 when GuC/HuC is also enabled. The i915 module would fail to initialize as shown in system journal.
2=FILES="/lib/firmware/edid/your_edid.bin"}}
+
{{hc|$ journalctl|
 +
... kernel: [drm:intel_gvt_init [i915]] *ERROR* i915 GVT-g loading failed due to Graphics virtualization is not yet supported with GuC submission
 +
... kernel: i915 0000:00:02.0: [drm:i915_driver_load [i915]] Device initialization failed (-5)
 +
... kernel: i915: probe of 0000:00:02.0 failed with error -5
 +
... kernel: snd_hda_intel 0000:00:1f.3: failed to add i915 component master (-19)
 +
}}
 +
}}
  
Now, regenerate the initramfs:
+
== Xorg configuration ==
  
# mkinitcpio -p linux
+
There may be no need for any configuration to run [[Xorg]].
  
The change takes effect at the next reboot.
+
However, if [[Xorg]] does not start, and to take advantage of some driver options, you can create an Xorg configuration file similar to the one below:
  
== Module-based Powersaving Options ==
+
{{hc|/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 {{ic|Driver}}.
 +
For the full list of options, see the {{man|4|intel}} man page.
 +
 
 +
{{Note|
 +
*You might need to add more device sections than the one listed above. This will be indicated where necessary.
 +
}}
 +
 
 +
=== AccelMethod ===
 +
 
 +
You may need to indicate {{ic|Option "AccelMethod"}} when creating a configuration file, the classical options are {{ic|UXA}}, {{ic|SNA}} (default) and {{ic|BLT}}.
 +
 
 +
If you experience issues with default {{ic|SNA}} (e.g. pixelated graphics, corrupt text, etc.), try using {{ic|UXA}} instead, which can be done by adding the following line to your [[#Xorg configuration|configuration file]]:
 +
 
 +
Option      "AccelMethod"  "uxa"
 +
 
 +
See {{man|4|intel}} under {{ic|Option "AccelMethod"}}.
 +
 
 +
== Module-based options ==
  
 
The {{ic|i915}} kernel module allows for configuration via [[Kernel modules#Setting module options|module options]]. Some of the module options impact power saving.
 
The {{ic|i915}} kernel module allows for configuration via [[Kernel modules#Setting module options|module options]]. Some of the module options impact power saving.
Line 88: Line 137:
 
  # systool -m i915 -av
 
  # systool -m i915 -av
  
You will note that the {{ic|i915.powersave}} option which "enable[s] powersavings, fbc, downclocking, etc." is enabled by default, resulting in per-chip powersaving defaults. It is however possible to configure more aggressive powersaving by using [[Kernel modules#Setting module options|module options]].
+
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. }}
 
{{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:
+
=== Framebuffer compression (enable_fbc) ===
  
{{hc|/etc/modprobe.d/i915.conf|<nowiki>
+
Making use of Framebuffer compression (FBC) can reduce power consumption while reducing memory bandwidth needed for screen refreshes.
options i915 enable_rc6=1 enable_fbc=1 lvds_downclock=1
+
 
</nowiki>}}
+
To enable FBC, use {{ic|1=i915.enable_fbc=1}} as [[kernel parameter]] or set in {{ic|/etc/modprobe.d/i915.conf}}:
 +
 
 +
{{hc|/etc/modprobe.d/i915.conf|2=
 +
options i915 enable_fbc=1
 +
}}
  
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].
+
{{Note|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:
  
Framebuffer compression, for example, 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.
 
  kernel: drm: not enough stolen space for compressed buffer, disabling.
  
== Tips and tricks ==
+
Enabling frame buffer compression on pre-Sandy Bridge CPUs results in endless error messages:
 +
 
 +
{{hc|$ dmesg|
 +
[ 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
 +
}}
  
=== Tear-free video ===
+
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|1=i915.enable_fbc=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].}}
  
The SNA acceleration method causes tearing for some people. To fix this, enable the {{ic|"TearFree"}} option in the driver:
+
=== Fastboot ===
  
{{hc|/etc/X11/xorg.conf.d/20-intel.conf|
+
The goal of Intel Fastboot is to preserve the frame-buffer as setup by the BIOS or [[bootloader]] to avoid any flickering until [[Xorg]] has started [https://www.phoronix.com/scan.php?page=news_item&px=MTEwNzc].
Section "Device"
 
  Identifier  "Intel Graphics"
 
  Driver      "intel"
 
  Option      "AccelMethod"  "sna"
 
  Option      "TearFree"    "true"
 
EndSection}}
 
  
See the [https://bugs.freedesktop.org/show_bug.cgi?id=37686 original bug report] for more info.
+
To enable fastboot, set {{ic|1=i915.fastboot=1}} as [[kernel parameter]] or set in {{ic|/etc/modprobe.d/i915.conf}}:
  
{{Note|
+
{{hc|/etc/modprobe.d/i915.conf|2=
* This option may not work when {{ic|SwapbuffersWait}} is {{ic|false}}.
+
options i915 fastboot=1
* This option is problematic for applications that are very picky about vsync timing, like [[Wikipedia:Super Meat Boy|Super Meat Boy]].
 
* This option does not work with UXA acceleration method, only with SNA.
 
 
}}
 
}}
  
=== Disable Vertical Synchronization (VSYNC) ===
+
{{Warning|1=This parameter is not enabled by default and may cause issues on some older (pre-Skylake) systems.[https://www.phoronix.com/scan.php?page=news_item&px=Intel-Fastboot-Default-2019-Try]}}
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:
+
 
 +
=== Intel GVT-g graphics virtualization support ===
  
{{hc|~/.drirc|
+
See [[Intel GVT-g]] for details.
<device screen&#61;"0" driver&#61;"dri2">
 
<application name&#61;"Default">
 
<option name&#61;"vblank_mode" value&#61;"0"/>
 
</application>
 
</device>}}
 
  
Do not use {{Pkg|driconf}} to create this file, it is buggy and will set the wrong driver.
+
== Tips and tricks ==
  
 
=== Setting scaling mode ===
 
=== Setting scaling mode ===
Line 141: Line 186:
 
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 151: Line 196:
 
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"}}.
 +
 
 +
{{Note|1=This option currently does not work for external displays (e.g. VGA, DVI, HDMI, DP). [https://bugs.freedesktop.org/show_bug.cgi?id=90989]}}
  
where {{ic|param}} is one of {{ic|"Full"}}, {{ic|"Center"}} or {{ic|"Full aspect"}}.
+
=== Hardware accelerated H.264 decoding on GMA 4500 ===
  
=== KMS Issue: console is limited to small area ===
+
The {{Pkg|libva-intel-driver}} package only provides hardware accelerated MPEG-2 decoding 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]{{Dead link|2020|03|29|status=domain name not resolved}}.
 +
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.
 +
Smooth playback (1080p/720p) works also with {{AUR|mpv-git}} in combination with {{AUR|ffmpeg-git}} and {{AUR|libva-intel-driver-g45-h264}}. With MPV and the Firefox plugin "Watch with MPV"[https://addons.mozilla.org/de/firefox/addon/watch-with-mpv/]{{Dead link|2020|03|29|status=404}} it is possible to watch hardware accelerated YouTube videos.
 +
 
 +
=== Old OpenGL Driver (i965) ===
 +
 
 +
As of Mesa 19.2, a new OpenGL driver, Iris, is available for testing. In Mesa 20.0, the Iris driver is promoted to be the default for Gen8+. Certain applications run faster with it. You may disable it and revert to use the old i965 driver by setting the {{ic|1=MESA_LOADER_DRIVER_OVERRIDE=i965}} [[environment variable]] before starting any OpenGL application. This setting does not affect Vulkan applications.
  
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 {{ic|1=video=SVIDEO-1:d}} in the kernel command line parameter in the bootloader. See [[Kernel parameters]] for more info.
+
{{Warning|1=Report bugs and regressions regarding the Iris driver [https://gitlab.freedesktop.org/mesa/mesa/issues here].}}
  
If that does not work, try disabling TV1 or VGA1 instead of SVIDEO-1.
+
=== Overriding reported OpenGL version ===
  
=== H.264 decoding on GMA 4500 ===
+
The {{ic|MESA_GL_VERSION_OVERRIDE}} [[environment variable]] can be used to override the reported OpenGL version to any application. For example, setting {{ic|1=MESA_GL_VERSION_OVERRIDE=4.5}} will report OpenGL 4.5.
  
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, 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].
+
{{Warning|You can use this variable to report any known OpenGL version, even if it is not supported by the GPU. Some applications might no longer crash, some may start crashing - you probably do not want to set this variable globally.}}
  
 
=== Setting brightness and gamma ===
 
=== Setting brightness and gamma ===
  
The following example demonstrates using using the {{ic|/sys}} [[Wikipedia:Virtual file system|virtual file system]] to set brightness at the driver level. The maximum brightness is indicated in the file {{ic|/sys/class/backlight/intel_backlight/max_brightness}}. Note that its value may differ across different hardware configurations.
+
See [[Backlight]].
  
{{bc|
+
== Troubleshooting ==
# cd /sys/class/backlight/intel_backlight
+
 
# cat max_brightness
+
=== Tearing ===
4437
+
 
# echo 2200 > brightness
+
The SNA acceleration method causes tearing on some machines. To fix this, enable the {{ic|"TearFree"}} option in the driver by adding the following line to your [[#Xorg configuration|configuration file]]:
 +
 
 +
{{hc|/etc/X11/xorg.conf.d/20-intel.conf|
 +
Section "Device"
 +
  Identifier "Intel Graphics"
 +
  Driver "intel"
 +
 
 +
  Option "TearFree" "true"
 +
EndSection}}
 +
 
 +
See the [https://bugs.freedesktop.org/show_bug.cgi?id=37686 original bug report] for more info.
 +
 
 +
{{Note|1=<nowiki></nowiki>
 +
* This option may not work when {{ic|SwapbuffersWait}} is {{ic|false}}.
 +
* This option may increase memory allocation considerably and reduce performance. [https://bugs.freedesktop.org/show_bug.cgi?id=37686#c123]
 +
* This option is problematic for applications that are very picky about vsync timing, like [[Wikipedia:Super Meat Boy|Super Meat Boy]].
 +
* This option does not work with UXA acceleration method, only with SNA.
 
}}
 
}}
  
Brightness can alternatively be set using the {{Pkg|xorg-xbacklight}} package.
+
=== Disable Vertical Synchronization (VSYNC) ===
  
$ xbacklight -set 50  # sets brightness to 50% of maximum
+
Useful when:
  
Increments can be used instead of absolute values, for example:
+
* Chomium/Chrome has lags and slow performance due to GPU and runs smoothly with --disable-gpu switch
 +
* glxgears test does not show desired performance
  
$ xbacklight -inc 10  # increase brightness by 10%
+
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:
$ xbacklight -dec 10  # decrease brightness by 10%
 
  
Gamma can be set using either the {{Pkg|xorg-xrandr}} or {{Pkg|xorg-xgamma}} package. The following commands create the same effect.
+
{{hc|~/.drirc|
 +
<device screen&#61;"0" driver&#61;"dri2">
 +
<application name&#61;"Default">
 +
<option name&#61;"vblank_mode" value&#61;"0"/>
 +
</application>
 +
</device>
 +
}}
 +
 
 +
{{Note|Do not use {{AUR|driconf}} to create this file. It is buggy and will set the wrong driver.}}
 +
 
 +
=== DRI3 issues ===
 +
 
 +
''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 [[#Xorg configuration|configuration file]]:
  
  $ xrandr --output LVDS1 --gamma 1.0:1.0:1.0
+
  Option "DRI" "2"
$ xgamma -rgamma 1 -ggamma 1 -bgamma 1
 
  
== Troubleshooting ==
+
For the {{ic|modesetting}} driver, this method of disabling DRI3 does not work.  Instead, one can set the environment variable {{ic|1=LIBGL_DRI3_DISABLE=1}}.
  
=== SNA issues ===
+
=== Font and screen corruption in GTK applications (missing glyphs after suspend/resume) ===
From {{ic|man 4 intel}}:
 
:''There are a couple of backends available for accelerating the DDX. "UXA" (Unified Acceleration Architecture) is the mature backend that was introduced to support the GEM driver model. It is in the process of being superseded by "SNA" (Sandybridge's New Acceleration). Until that process is complete, the ability to choose which backend to use remains for backwards compatibility.''
 
  
''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 creating an [[X]] configuration file containing the following:
+
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/X11/xorg.conf.d/20-intel.conf|
+
{{hc|/etc/environment|output=
Section "Device"
+
COGL_ATLAS_DEFAULT_BLIT_MODE=framebuffer
  Identifier  "Intel Graphics"
 
  Driver      "intel"
 
  Option      "AccelMethod"  "uxa"
 
EndSection
 
 
}}
 
}}
 +
 +
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" ===
Line 220: Line 298:
 
=== 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 [[#Xorg 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
 
  
Option "TearFree" "true"
+
=== Baytrail complete freeze ===
Option "AccelMethod" "sna"
 
  
in your config file, in most cases these can be fixed by adding
+
If you are using kernel > 3.16 on Baytrail architecture and randomly encounter total system freezes, the following kernel option is a workaround until [https://bugzilla.kernel.org/show_bug.cgi?id=109051 this bug] is fixed in the linux kernel.
  
  i915.semaphores=1
+
  intel_idle.max_cstate=1
  
to your boot parameters.
+
This is originally an Intel CPU bug that can be triggered by certain c-state transitions. It can also happen with Linux kernel 3.16 or Windows, though apparently much more rarely.
 +
The kernel option will prevent the freeze by avoiding c-state transitions but will also increase power consumption.
  
 
=== Adding undetected resolutions ===
 
=== Adding undetected resolutions ===
  
 
This issue is covered on the [[Xrandr#Adding undetected resolutions|Xrandr page]].
 
This issue is covered on the [[Xrandr#Adding undetected resolutions|Xrandr page]].
 
=== Weathered colors (color range problem) ===
 
 
{{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.}}
 
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.
 
 
{{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.}}
 
 
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 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.}}
 
 
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].
 
 
Unfortunately, the Intel driver does not support setting the color range through an {{ic|xorg.conf.d}} configuration file.
 
 
A [https://bugzilla.kernel.org/show_bug.cgi?id=94921 bug report] is filed and a patch can be found in the attachment.
 
  
 
=== Backlight is not adjustable===
 
=== Backlight is not adjustable===
After resuming from suspend, the hotkeys for changing the screen brightness do not take effect. Using the following kernel parameters can potentially solve the problem.
 
 
acpi_backlight=vendor
 
  
Samsung devices with hybrid graphics (like 770Z5E) need acpi_backlight=video as a kernel parameter when using kernel >= 3.17
+
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=video
+
If the problem persists, try one of the following [[kernel parameters]]:
  
Either in addition to the above mentioned parameter, or on its own, add one of the following three parameters:
 
 
  acpi_osi=Linux
 
  acpi_osi=Linux
 
  acpi_osi="!Windows 2012"
 
  acpi_osi="!Windows 2012"
 
  acpi_osi=
 
  acpi_osi=
  
Another parameter available:
+
Also make sure you are not using fastboot mode (i915.fastboot kernel parameter), it is [https://www.phoronix.com/forums/forum/software/mobile-linux/1066447-arch-linux-users-with-intel-graphics-can-begin-enjoying-a-flicker-free-boot known] for breaking backlight controls.
video.use_native_backlight=1
 
  
If neither of those solve the problem, edit or create {{ic|/etc/X11/xorg.conf.d/20-intel.conf}} with the following content:
+
=== Corruption or unresponsiveness in Chromium and Firefox ===
  
{{hc|/etc/X11/xorg.conf.d/20-intel.conf|
+
If you experience corruption, unresponsiveness, lags or slow performance in Chromium and/or Firefox some possible solutions are:
Section "Device"
 
        Identifier  "card0"
 
        Driver      "intel"
 
    Option      "Backlight"  "intel_backlight"
 
        BusID      "PCI:0:2:0"
 
  
EndSection}}
+
* [[#AccelMethod|Set the AccelMethod to "uxa"]]
 
+
* [[#Disable Vertical Synchronization (VSYNC)|Disable VSYNC]]
If using the UXA acceleration as mentioned above, create the file as follows:
+
* [[#Tearing|Enable the TearFree option]]
{{hc|/etc/X11/xorg.conf.d/20-intel.conf|
+
* Disable "DRI" and acceleration method (tested on Intel Iris 10th generation): {{bc|<nowiki>
Section "Device"
+
Option "NoAccel" "True"
        Identifier  "card0"
+
Option "DRI" "False"
        Driver      "intel"
+
</nowiki>}}
        Option      "AccelMethod"uxa"
 
        Option      "Backlight"    "intel_backlight"
 
        BusID      "PCI:0:2:0"
 
 
 
EndSection}}
 
 
 
=== 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 slightly increase power consumption. 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://zinc.canonical.com/~cking/power-benchmarking/background-colour-and-framebuffer-compression/results.txt here].
 
 
 
=== Corruption/Unresponsiveness in Chromium and Firefox ===
 
 
 
If you experience corruption or unresponsiveness in Chromium and/or Firefox [[#SNA issues|set the AccelMethod to "uxa"]].
 
 
 
=== Pink & green artifacts in video or webcam output ===
 
 
 
On Broadwell machines with applications that use ''xv'' output, or Intel Textured Video (notably, Skype and VLC), the video stream exhibits pink and green artifacts. This is a general Broadwell video issue that was fixed upstream on 2015-04-16. [https://bugs.freedesktop.org/show_bug.cgi?id=89807] Update {{pkg|xf86-video-intel}} to fix it.
 
  
 
=== Kernel crashing w/kernels 4.0+ on Broadwell/Core-M chips ===
 
=== Kernel crashing w/kernels 4.0+ on Broadwell/Core-M chips ===
Line 352: Line 369:
 
  Jun 16 17:54:03 hostname kernel: RIP  [<          (null)>]          (null)
 
  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:
+
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
 
  i915.enable_execlists=0
  
 
This is known to be broken to at least kernel 4.0.5.
 
This is known to be broken to at least kernel 4.0.5.
  
===Driver not working for Intel Skylake chips===
+
=== 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 {{ic|1=enable_fbc=1}} option fixes this issue.
 +
 
 +
=== Screen flickering ===
 +
 
 +
Panel Self Refresh (PSR), a power saving feature used by Intel iGPUs is known to cause flickering in some instances {{Bug|49628}} {{Bug|49371}} {{Bug|50605}}. A temporary solution is to disable this feature using the [[kernel parameter]] {{ic|1=i915.enable_psr=0}}.
 +
 
 +
=== OpenGL 2.1 with i915 driver ===
 +
 
 +
The update of {{Pkg|mesa}} from version 13.x to 17 may break support for OpenGL 2.1 on third gen Intel GPUs (GMA3100, see [[wikipedia:List_of_Intel_graphics_processing_units#Third_generation|here]]), as described in this [http://www.phoronix.com/scan.php?page=news_item&px=Mesa-i915-OpenGL-2-Drop article], reverting it back to OpenGL 1.4. However this could be restored manually by setting {{ic|/etc/drirc}} or {{ic|~/.drirc}} options like:
 +
 
 +
{{hc|/etc/drirc|output=
 +
<driconf>
 +
...
 +
    <device driver="i915">
 +
        <application name="Default">
 +
            <option name="'''stub_occlusion_query'''" value="'''true'''" />
 +
            <option name="'''fragment_shader'''" value="'''true'''" />
 +
        </application>
 +
    </device>
 +
...
 +
</driconf>
 +
}}
 +
 
 +
{{Note|the reason of this step back was Chromium and other apps bad experience. If needed, you might edit the drirc file in a "app-specific" style, see [https://dri.freedesktop.org/wiki/ConfigurationInfrastructure/ here], to disable gl2.1 on executable chromium for instance.}}
 +
 
 +
=== 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 {{ic|1=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. Video port names can be listed with [[xrandr]].
 +
 
 +
=== Weathered colors (color range problems) ===
 +
 
 +
The "Broadcast RGB" property in the Intel driver defines the color range which can be used by the display - either "Limited 16:235" (which limits the color range for some displays that can't properly display all colors) and "Full". Since kernel 3.9, the new default property "Automatic" tries to determine whenever the display supports the full color range, and if it doesn't/detection fails, color range falls back to "Limited 16:235". This results in weathered colors and grey blacks. On some displays/connectors, despite the full color range being supported properly, automatic detection fails and falls back to the limited color range ([https://bugs.freedesktop.org/show_bug.cgi?id=108821 upstream bug report, kernels 4.18-4.20]).
  
For the driver to work on the new Intel Skylake (6th gen.) GPUs, {{ic|i915.preliminary_hw_support&#61;1}} must be added to your boot parameters.
+
You can forcefully set the desired color range by running {{ic|xrandr --output <OUT> --set "Broadcast RGB" "Full"}} (replace {{ic|<OUT>}} with the appropriate output device, listed by running {{ic|xrandr}}). There is no way to persist this setting in {{ic|xorg.conf}}.
  
 
== 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)

Latest revision as of 10:42, 4 April 2020

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:List of Intel graphics processing units.

Note: PowerVR-based graphics (GMA 3600 series) are not supported by open source drivers.

Installation

Install the mesa package, which provides the DRI driver for 3D acceleration.

Also see Hardware video acceleration.

Note: Some (Debian & Ubuntu, Fedora, KDE) recommend not installing the xf86-video-intel driver, and instead falling back on the modesetting driver for Gen4 and newer GPUs (GMA 3000 from 2006 and newer). See [1], [2], Xorg#Installation, and modesetting(4). However, the modesetting driver can cause problems such as Chromium Issue 370022.

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 instructions on how to enable KMS as soon as possible at the boot process.

Enable GuC / HuC firmware loading

For Skylake and newer processors, some video features (e.g. CBR rate control on SKL low-power encoding mode) may require the use of an updated GPU firmware, which is currently (as of 4.16) not enabled by default. Enabling GuC/HuC firmware loading can cause issues on some systems; disable it if you experience freezing (for example, after resuming from hibernation).

Note: See Gentoo:Intel#Feature support for an overview of Intel processor generations.

For those processors it is necessary to add i915.enable_guc=2 to the kernel parameters to enable both GuC and HuC firmware loading. Alternatively, if the initramfs already includes the i915 module (see Kernel mode setting#Early KMS start), you can set these options through a file in /etc/modprobe.d/, e.g.:

/etc/modprobe.d/i915.conf
options i915 enable_guc=2

Tango-view-refresh-red.pngThis article or section is out of date.Tango-view-refresh-red.png

Reason: GuC submission has been completely disabled for the kernel 5.4 and later, due to it reducing performance and causing bugs. Setting enable_guc=3 has no effect. (Discuss in Talk:Intel graphics#)
Note: It is possible to enable both GuC/HuC firmware loading and GuC submission by using the enable_guc=3 module parameter, although this is generally discouraged and may even negatively affect your system stability.

You can verify both are enabled by using dmesg:

$ dmesg
[drm] HuC: Loaded firmware i915/kbl_huc_ver02_00_1810.bin (version 2.0)
[drm] GuC: Loaded firmware i915/kbl_guc_ver9_39.bin (version 9.39)
i915 0000:00:02.0: GuC firmware version 9.39
i915 0000:00:02.0: GuC submission enabled
i915 0000:00:02.0: HuC enabled

Alternatively, check using:

# cat /sys/kernel/debug/dri/0/i915_huc_load_status
# cat /sys/kernel/debug/dri/0/i915_guc_load_status
Warning: Using GVT-g graphics virtualization by setting enable_gvt=1 is not supported as of linux 4.20.11 when GuC/HuC is also enabled. The i915 module would fail to initialize as shown in system journal.
$ journalctl
... kernel: [drm:intel_gvt_init [i915]] *ERROR* i915 GVT-g loading failed due to Graphics virtualization is not yet supported with GuC submission
... kernel: i915 0000:00:02.0: [drm:i915_driver_load [i915]] Device initialization failed (-5)
... kernel: i915: probe of 0000:00:02.0 failed with error -5
... kernel: snd_hda_intel 0000:00:1f.3: failed to add i915 component master (-19)

Xorg configuration

There may be no need for any configuration to run Xorg.

However, if Xorg does not start, and to take advantage of some driver options, you can create an 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. For the full list of options, see the intel(4) man page.

Note:
  • You might need to add more device sections than the one listed above. This will be indicated where necessary.

AccelMethod

You may need to indicate Option "AccelMethod" when creating a configuration file, the classical options are UXA, SNA (default) and BLT.

If you experience issues with default 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 intel(4) under Option "AccelMethod".

Module-based 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.

Framebuffer compression (enable_fbc)

Making use of Framebuffer compression (FBC) can reduce power consumption while reducing memory bandwidth needed for screen refreshes.

To enable FBC, use i915.enable_fbc=1 as kernel parameter or set in /etc/modprobe.d/i915.conf:

/etc/modprobe.d/i915.conf
options i915 enable_fbc=1
Note: 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.

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

$ dmesg
[ 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.

Fastboot

The goal of Intel Fastboot is to preserve the frame-buffer as setup by the BIOS or bootloader to avoid any flickering until Xorg has started [3].

To enable fastboot, set i915.fastboot=1 as kernel parameter or set in /etc/modprobe.d/i915.conf:

/etc/modprobe.d/i915.conf
options i915 fastboot=1
Warning: This parameter is not enabled by default and may cause issues on some older (pre-Skylake) systems.[4]

Intel GVT-g graphics virtualization support

See Intel GVT-g for details.

Tips and tricks

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

Note: This option currently does not work for external displays (e.g. VGA, DVI, HDMI, DP). [5]

Hardware accelerated H.264 decoding on GMA 4500

The libva-intel-driver package only provides hardware accelerated MPEG-2 decoding 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 [6]. This is echoed by other experiences [7][dead link 2020-03-29 ⓘ]. 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. Smooth playback (1080p/720p) works also with mpv-gitAUR in combination with ffmpeg-gitAUR and libva-intel-driver-g45-h264AUR. With MPV and the Firefox plugin "Watch with MPV"[8][dead link 2020-03-29 ⓘ] it is possible to watch hardware accelerated YouTube videos.

Old OpenGL Driver (i965)

As of Mesa 19.2, a new OpenGL driver, Iris, is available for testing. In Mesa 20.0, the Iris driver is promoted to be the default for Gen8+. Certain applications run faster with it. You may disable it and revert to use the old i965 driver by setting the MESA_LOADER_DRIVER_OVERRIDE=i965 environment variable before starting any OpenGL application. This setting does not affect Vulkan applications.

Warning: Report bugs and regressions regarding the Iris driver here.

Overriding reported OpenGL version

The MESA_GL_VERSION_OVERRIDE environment variable can be used to override the reported OpenGL version to any application. For example, setting MESA_GL_VERSION_OVERRIDE=4.5 will report OpenGL 4.5.

Warning: You can use this variable to report any known OpenGL version, even if it is not supported by the GPU. Some applications might no longer crash, some may start crashing - you probably do not want to set this variable globally.

Setting brightness and gamma

See Backlight.

Troubleshooting

Tearing

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

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

  Option "TearFree" "true"
EndSection

See the original bug report for more info.

Note:
  • This option may not work when SwapbuffersWait is false.
  • This option may increase memory allocation considerably and reduce performance. [9]
  • 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.

Disable Vertical Synchronization (VSYNC)

Useful when:

  • Chomium/Chrome has lags and slow performance due to GPU and runs smoothly with --disable-gpu switch
  • glxgears test does not show desired performance

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>
Note: Do not use driconfAUR to create this file. It is buggy and will set the wrong driver.

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"

For the modesetting driver, this method of disabling DRI3 does not work. Instead, one can set the environment variable LIBGL_DRI3_DISABLE=1.

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"

Baytrail complete freeze

If you are using kernel > 3.16 on Baytrail architecture and randomly encounter total system freezes, the following kernel option is a workaround until this bug is fixed in the linux kernel.

intel_idle.max_cstate=1

This is originally an Intel CPU bug that can be triggered by certain c-state transitions. It can also happen with Linux kernel 3.16 or Windows, though apparently much more rarely. The kernel option will prevent the freeze by avoiding c-state transitions but will also increase power consumption.

Adding undetected resolutions

This issue is covered on the Xrandr page.

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=

Also make sure you are not using fastboot mode (i915.fastboot kernel parameter), it is known for breaking backlight controls.

Corruption or unresponsiveness in Chromium and Firefox

If you experience corruption, unresponsiveness, lags or slow performance in Chromium and/or Firefox some possible solutions are:

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.

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

Panel Self Refresh (PSR), a power saving feature used by Intel iGPUs is known to cause flickering in some instances FS#49628 FS#49371 FS#50605. A temporary solution is to disable this feature using the kernel parameter i915.enable_psr=0.

OpenGL 2.1 with i915 driver

The update of mesa from version 13.x to 17 may break support for OpenGL 2.1 on third gen Intel GPUs (GMA3100, see here), as described in this article, reverting it back to OpenGL 1.4. However this could be restored manually by setting /etc/drirc or ~/.drirc options like:

/etc/drirc
<driconf>
...
    <device driver="i915">
        <application name="Default">
            <option name="stub_occlusion_query" value="true" />
            <option name="fragment_shader" value="true" />
        </application>
    </device>
...
</driconf>
Note: the reason of this step back was Chromium and other apps bad experience. If needed, you might edit the drirc file in a "app-specific" style, see here, to disable gl2.1 on executable chromium for instance.

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. Video port names can be listed with xrandr.

Weathered colors (color range problems)

The "Broadcast RGB" property in the Intel driver defines the color range which can be used by the display - either "Limited 16:235" (which limits the color range for some displays that can't properly display all colors) and "Full". Since kernel 3.9, the new default property "Automatic" tries to determine whenever the display supports the full color range, and if it doesn't/detection fails, color range falls back to "Limited 16:235". This results in weathered colors and grey blacks. On some displays/connectors, despite the full color range being supported properly, automatic detection fails and falls back to the limited color range (upstream bug report, kernels 4.18-4.20).

You can forcefully set the desired color range by running xrandr --output <OUT> --set "Broadcast RGB" "Full" (replace <OUT> with the appropriate output device, listed by running xrandr). There is no way to persist this setting in xorg.conf.

See also