Difference between revisions of "Intel graphics"

From ArchWiki
Jump to navigation Jump to search
m (→‎Tips and tricks: wikilinks; style: Help:Style#Spelling, rm "here")
 
(579 intermediate revisions by more than 100 users not shown)
Line 1: Line 1:
[[Category: Graphics (English)]][[Category: X Server (English)]]
+
[[Category:Graphics]]
{{i18n|Intel}}
+
[[Category:X server]]
 +
[[cs:Intel graphics]]
 +
[[de:Intel]]
 +
[[es:Intel graphics]]
 
[[fr:Intel]]
 
[[fr:Intel]]
{{Article summary start}}
+
[[hu:Intel graphics]]
{{Article summary text|Information on Intel graphics cards/chipsets and the ''intel'' video driver.}}
+
[[it:Intel graphics]]
{{Article summary heading|Related}}
+
[[ja:Intel Graphics]]
{{Article summary wiki|ATI}}
+
[[pl:Intel graphics]]
{{Article summary wiki|NVIDIA}}
+
[[pt:Intel graphics]]
{{Article summary wiki|Poulsbo}}
+
[[ru:Intel graphics]]
{{Article summary wiki|Xorg}}
+
[[zh-hans:Intel graphics]]
{{Article summary end}}
+
[[zh-hant:Intel graphics]]
 +
{{Related articles start}}
 +
{{Related|Intel GMA 3600}}
 +
{{Related|Xorg}}
 +
{{Related|Kernel mode setting}}
 +
{{Related|Xrandr}}
 +
{{Related|Hybrid graphics}}
 +
{{Related|Vulkan}}
 +
{{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.
  
{{note|For use within the console without [[Xorg|X]], see [[Uvesafb]].}}
+
For a comprehensive list of Intel GPU models and corresponding chipsets and CPUs, see [[Wikipedia:List of Intel graphics processing units]].
  
=== Models ===
+
{{Note|PowerVR-based graphics ([[Intel GMA 3600|GMA 3600]] series) are not supported by open source drivers.}}
It is a popular mistake to think of "Intel 945G" and "Intel GMA 945" as being the same graphics chip with different names. As a matter of fact, the latter does not exist. Intel uses "GMA" to indicate the graphics core, or the GPU. Anything other than that is actually the model of the '''motherboard chipset''', like "915G", "945GM", "G965" or "G45".
 
  
The more common GPUs and their corresponding motherboard chipsets are:
+
== Installation ==
 +
 
 +
[[Install]] the {{Pkg|mesa}} package, which provides the [[wikipedia:Direct_Rendering_Infrastructure|DRI]] driver for 3D acceleration.
 +
 
 +
* 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.
 +
 
 +
Also see [[Hardware video acceleration]].
 +
 
 +
{{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://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].}}
 +
 
 +
== Loading ==
 +
 
 +
The Intel kernel module should load fine automatically on system boot.
 +
 
 +
If it does not happen, then:
 +
 
 +
* 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/}}.
 +
 
 +
=== 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 {{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
 +
}}
 +
 
 +
{{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.}}
 +
 
 +
You can verify both are enabled by using [[dmesg]]:
 +
 
 +
{{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
 +
}}
 +
 
 +
Alternatively, check using:
 +
 
 +
# cat /sys/kernel/debug/dri/0/i915_huc_load_status
 +
# cat /sys/kernel/debug/dri/0/i915_guc_load_status
 +
 
 +
{{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.
 +
{{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)
 +
}}
 +
}}
 +
 
 +
== 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:
 +
 
 +
{{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 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.
 +
}}
  
GPU                Chipset/Northbridge
+
== Module-based options ==
Intel GMA 900        910, 915
 
Intel GMA 950        945
 
  
The "i810" chipset (again, motherboard; not GPU) is actually really old and was manufactured long before the 9xx product line with which the GMA onboard-graphics branding began. Similarly, alternative names for the 910, 915 and 945 chips may include the {{ic|i}} prefix.
+
The {{ic|i915}} kernel module allows for configuration via [[Kernel modules#Setting module options|module options]]. Some of the module options impact power saving.
  
See [[Wikipedia:Intel_GMA#Table_of_GMA_graphics_cores_and_chipsets|this]] for a list.
+
A list of all options along with short descriptions and default values can be generated with the following command:
  
=== Driver ===
+
$ modinfo -p i915
* {{Pkg|xf86-video-intel}}
 
  
== Installation ==
+
To check which options are currently enabled, run
Prerequisite: [[Xorg]]
+
 
   
+
  # systool -m i915 -av
[[pacman|Install]] the {{Pkg|xf86-video-intel}} package which is available in the [[Official Repositories|official repositories]].
 
  
You may need to install {{Pkg|lib32-intel-dri}} in 64-bit systems to use acceleration in 32-bit programs.
+
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]].
  
{{Note|{{Pkg|lib32-intel-dri}} is found in the [[Official_Repositories#.5Bmultilib.5D|[multilib] repository]].}}
+
{{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. }}
  
== Configuration ==
+
=== Framebuffer compression (enable_fbc) ===
  
There is no need for any kind of configuration to get the Xorg running (an {{ic|xorg.conf}} is unneeded, but needs to be configured correctly if present).
+
Making use of Framebuffer compression (FBC) can reduce power consumption while reducing memory bandwidth needed for screen refreshes.
  
One thing that you should have already done from the start (not a configuration step per se) is to add your user to the relevant [[Users and Groups|group]]:
+
To enable FBC, use {{ic|1=i915.enable_fbc=1}} as [[kernel parameter]] or set in {{ic|/etc/modprobe.d/i915.conf}}:
  
# gpasswd -a username video
+
{{hc|/etc/modprobe.d/i915.conf|2=
 +
options i915 enable_fbc=1
 +
}}
  
== KMS (Kernel Mode Setting) ==
+
{{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:
  
[[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, 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.
+
  kernel: drm: not enough stolen space for compressed buffer, disabling.
  
{{Note|When using KMS, you ''must'' remove any references to {{ic|vga}} from the kernel line in {{ic|/boot/grub/menu.lst}}}}
+
Enabling frame buffer compression on pre-Sandy Bridge CPUs results in endless error messages:
  
To proceed, add the {{ic|i915}} module to the {{ic|MODULES}} line in {{ic|/etc/mkinitcpio.conf}}:
+
{{hc|$ dmesg|
MODULES="'''i915'''"
+
[ 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
 +
}}
  
{{Note|If you have a first generation Core i{3,5,7} series processor with an integrated GPU, failure to add {{ic|i915}} to the {{ic|MODULES}} array in {{ic|/etc/mkinitcpio.conf}} will likely cause the error {{ic|kernel: intel ips [...]: failed to get i915 symbols, graphics turbo disabled}}.}}
+
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].}}
  
{{Note|You may need to add the {{ic|intel_agp}} module too if the system complains at boot time.}}
+
=== Fastboot ===
  
Now, regenerate the initramfs:
+
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].
# mkinitcpio -p linux
 
  
and reboot the system.  Everything should work now. If you are having problems, try explicitly enabling KMS by adding {{ic|1=i915.modeset=1}} to your kernel line in {{ic|/boot/grub/menu.lst}}:
+
To enable fastboot, set {{ic|1=i915.fastboot=1}} as [[kernel parameter]] or set in {{ic|/etc/modprobe.d/i915.conf}}:
# (0) Arch Linux
 
title  Arch Linux
 
root  (hd0,0)
 
kernel /boot/vmlinuz-linux root=/dev/... '''i915.modeset=1'''
 
initrd /boot/initramfs-linux.img
 
and make sure that you do not use the {{ic|1=vga=...}} property nor {{ic|nomodeset}}. Now, reboot and Xorg will work.
 
  
If you ever want to disable KMS, you can change the {{ic|i915.modeset}} option to 0 in [[GRUB]]'s {{ic|/boot/grub/menu.lst}}, without rebuilding anything:
+
{{hc|/etc/modprobe.d/i915.conf|2=
# (0) Arch Linux
+
options i915 fastboot=1
title  Arch Linux
+
}}
root  (hd0,0)
 
kernel /boot/vmlinuz-linux root=/dev/... '''i915.modeset=0'''
 
initrd /boot/initramfs-linux.img
 
{{ic|1=i915.modeset=0}} is the Intel equivalent to {{ic|nomodeset}} for other video cards.
 
{{Note|Adding {{ic|nomodeset}} to the kernel boot line might prevent GNOME 3's gnome-shell or KDE's desktop effects from running.}}
 
  
For disabling it without having to edit {{ic|/boot/grub/menu.lst}}, turn on the machine and when you see [[GRUB]]'s screen, hit a key to disable the timeout. Select the kernel you want to boot (probably the one already selected) and hit {{Keypress|e}} for "edit". Now select the line starting with "kernel" and hit {{Keypress|e}} again for editing. You can now add the {{ic|i915.modeset}} option and disable KMS by setting it to 0. Press {{Keypress|Enter}} and then {{Keypress|b}} to boot. Note that this will be temporary, so it will be enabled again upon rebooting.
+
{{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]}}
  
{{Note|Downgrade to kernel 2.6.31.6-1 or disable modesetting with kernel boot parameter if you get a blank screen during boot process with the Intel GMA 950.}}
+
=== Intel GVT-g graphics virtualization support ===
  
=== See also ===
+
See [[Intel GVT-g]] for details.
* [[KMS]] &mdash; Arch wiki article on kernel mode setting
 
* [[Xrandr]] &mdash; If you have problems setting the resolution
 
* Arch Linux forums: [https://bbs.archlinux.org/viewtopic.php?pid=522665#p522665 Intel 945GM, Xorg, Kernel - performance]
 
  
 
== Tips and tricks ==
 
== Tips and tricks ==
Line 94: Line 172:
 
=== Setting scaling mode ===
 
=== Setting scaling mode ===
  
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
+
 
where {{ic|param}} can be
+
  $ xrandr --output LVDS1 --set PANEL_FITTING ''param''
 +
 
 +
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,
 
* {{ic|full}}: scale the resolution so it uses the entire screen or
 
* {{ic|full}}: scale the resolution so it uses the entire screen or
 
* {{ic|full_aspect}}: scale the resolution to the maximum possible but keep the aspect ratio.
 
* {{ic|full_aspect}}: scale the resolution to the maximum possible but keep the aspect ratio.
If it does not work, you can try
 
xrandr --output LVDS1 --set "scaling mode" param
 
where {{ic|param}} is one of {{ic|"Full"}}, {{ic|"Center"}} or {{ic|"Full aspect"}}.
 
  
=== KMS Issue: console is limited to small area ===
+
If it does not work, try:
 +
 
 +
$ 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]}}
 +
 
 +
=== Hardware accelerated H.264 decoding on GMA 4500 ===
 +
 
 +
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].
 +
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/] it is possible to watch hardware accelerated YouTube videos.
 +
 
 +
=== Alternative OpenGL Driver (Iris) ===
 +
 
 +
As of Mesa 19.2, a new OpenGL driver, Iris, is available for testing. Certain applications run faster with it. You may experimentally enable it by setting the {{ic|1=MESA_LOADER_DRIVER_OVERRIDE=iris}} [[environment variable]] before starting any OpenGL application. This setting does not affect Vulkan applications.
 +
 
 +
{{Warning|1=Iris is still experimental - applications might crash or render incorrectly. Use with care and [https://gitlab.freedesktop.org/groups/mesa/-/issues report found bugs/regressions].}}
  
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.
+
=== Overriding reported OpenGL version ===
To fix, explicitly disable the port with an i915 module setting.  For example, add the following to the end of the kernel line in {{ic|/boot/grub/menu.lst}}:
 
  video=SVIDEO-1:d
 
  
If that does not work, you may also try disabling TV1 or VGA1 instead of SVIDEO-1.
+
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.
  
=== Hardware acceleration ===
+
{{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.}}
  
If you want to enable hardware accelerated video decode/encode in multimedia applications (such as VLC or MPlayer) for Intel HD graphics controllers (G45, Sandybridge), [[pacman|install]] the {{pkg|libva-driver-intel}} package, available in the [[Official Repositories]].
+
=== Setting brightness and gamma ===
  
==Supported hardware==
+
See [[Backlight]].
See http://intellinuxgraphics.org/documentation.html.
 
  
 
== Troubleshooting ==
 
== Troubleshooting ==
  
=== Glxgears shows low performance results ===
+
=== Tearing ===
  
If you run glxgears in order to check your system's graphics performance, you may notice that glxgears shows results around '''60 FPS''':
+
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|
311 frames in 5.0 seconds = 61.973 FPS
+
Section "Device"
311 frames in 5.0 seconds = 62.064 FPS
+
  Identifier "Intel Graphics"
  311 frames in 5.0 seconds = 62.026 FPS
+
  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.
 +
}}
 +
 
 +
=== 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 [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>
 +
}}
 +
 
 +
{{Note|Do not use {{AUR|driconf}} to create this file. It is buggy and will set the wrong driver.}}
 +
 
 +
=== SNA issues ===
 +
 
 +
''SNA'' is the default acceleration method in {{Pkg|xf86-video-intel}}. If you 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 [[#Xorg configuration|configuration file]]:
 +
 
 +
Option      "AccelMethod" "uxa"
 +
 
 +
See {{man|4|intel}} under {{ic|Option "AccelMethod"}}.
 +
 
 +
=== 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]]:
 +
 
 +
  Option "DRI" "2"
 +
 
 +
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}}.
 +
 
 +
=== 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:
  
That is happening not because there is a performance regression, but because your system graphics are using vertical sync (vsync), that means, your display's native frames per second.
+
{{hc|/etc/environment|output=
 +
COGL_ATLAS_DEFAULT_BLIT_MODE=framebuffer
 +
}}
  
{{Note|glxgears is not a benchmark for performance comparison between two or more systems.}}
+
See also [https://bugs.freedesktop.org/show_bug.cgi?id=88584 FreeDesktop bug 88584].
{{Note|To disable '''VSync''' just add in your {{ic|/etc/X11/xorg.conf.d/20-intel.conf}} in '''Section "Device"'''  string  '''Option "SwapbuffersWait" "false"''' }}
 
  
 
=== Blank screen during boot, when "Loading modules" ===
 
=== Blank screen during boot, when "Loading modules" ===
  
If you are 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)|KMS]] above.
+
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 parameter]] seems to work as well:
  
Alternatively, appending the following to the kernel command line seems to work as well:
 
 
  video=SVIDEO-1:d
 
  video=SVIDEO-1:d
  
=== External monitor connected to laptop flashes black every 30 seconds ===
+
If you need to output to VGA then try this:
  
If your laptop uses Intel HD graphics and your external LCD is flashing to black every 30 seconds, upgrading your video driver and kernel may help. As of now using {{Pkg|xf86-video-intel}} version 2.14.0-1 and kernel 2.6.37-5 have solved this issue.
+
video=VGA-1:1280x800
  
=== Only a single low-resolution present ===
+
=== X freeze/crash with intel driver ===
  
If Xorg starts with 800x600 and does not find any other resolutions, it may be because you have an {{ic|/etc/X11/xorg.conf}} file left over from your NVIDIA setup. Simply changing the driver from "nvidia" to "intel" is not sufficient when moving from NVIDIA's {{ic|xorg.conf}} to Intel's. Try to delete {{ic|/etc/X11/xorg.conf}}, letting the driver pick the settings itself.
+
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]]:
  
=== Video tearing ===
+
  Option "NoAccel" "True"
Install VA-API support by installing the {{Pkg|libva-driver-intel}} package. Use a VAAPI supported video player. If you use mplayer, install {{Pkg|mplayer-vaapi}}, and use -vo vaapi parameter. To fix tearing on flash videos, try to enable hardware video decoding from {{ic|/etc/adobe/mms.cfg}} and add line {{ic|1=EnableLinuxHWVideoDecode=1}}. If hardware video decoding is still not working, you can also try adding {{ic|1=OverrideGPUValidation = 1}}.
 
  
=== X freeze/crash with intel driver ===
+
Alternatively, try to disable the 3D acceleration only with the {{ic|DRI}} option:
If you have issue with X crashing, or GPU hang, or problem with frozen X, then the fix may be [https://bbs.archlinux.org/viewtopic.php?pid=938004#p938004 to use the "Shadow" option]:
+
 
{{hc|/etc/X11/xorg.conf.d/20-intel.conf|
+
  Option "DRI" "False"
Section "Device"
+
 
    Identifier "old intel stuff"
+
=== Baytrail complete freeze ===
    Driver "intel"
+
 
    Option "Shadow" "True"
+
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.
    Option "DRI" "false"
 
EndSection}}
 
  
Because it disables (most) video acceleration functions, using this fix (Option "Shadow" "True") may cause [https://bbs.archlinux.org/viewtopic.php?pid=973673 problems with gnome-screenshot] and similar programs like {{pkg|gimp}}, or {{pkg|gcolor2}}.
+
intel_idle.max_cstate=1
  
Another option that can help on some implementations is to enable semaphores in the kernel video driver, by adding {{ic|1=i915.semaphores=1}} to the kernel command line. To make this change permanent on [[GRUB2]] installations, changing the kernel command-line entry in {{ic|/etc/default/grub}} and re-running {{ic|grub-mkconfig}} will make that change permanent.
+
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.
  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash i915.semaphores=1"
+
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]].
 +
 
 +
=== 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 [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.
 +
 
 +
=== Corruption/Unresponsiveness in Chromium and Firefox ===
 +
 
 +
If you experience corruption, unresponsiveness, lags or slow performance in Chromium and/or Firefox:
 +
 
 +
* [[#SNA issues|Set the AccelMethod to "uxa"]]
 +
* [[#Disable Vertical Synchronization (VSYNC)|Disable VSYNC]]
 +
 
 +
=== 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 {{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]).
 +
 
 +
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 ==
 +
 
 +
* https://01.org/linuxgraphics/documentation (includes a list of supported hardware)

Latest revision as of 10:03, 5 October 2019

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

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]. 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] it is possible to watch hardware accelerated YouTube videos.

Alternative OpenGL Driver (Iris)

As of Mesa 19.2, a new OpenGL driver, Iris, is available for testing. Certain applications run faster with it. You may experimentally enable it by setting the MESA_LOADER_DRIVER_OVERRIDE=iris environment variable before starting any OpenGL application. This setting does not affect Vulkan applications.

Warning: Iris is still experimental - applications might crash or render incorrectly. Use with care and report found bugs/regressions.

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.

SNA issues

SNA is the default acceleration method in xf86-video-intel. If you 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 intel(4) 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"

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/Unresponsiveness in Chromium and Firefox

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

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