Intel graphics - ArchWiki

# Intel graphics

Related articles

- Intel GMA3600
- Poulsbo
- Xorg
- Kernel mode setting
- Xrandr
- Hybrid graphics

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

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

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

## Installation

Prerequisite: Xorg.

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

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

Install the VA-API driver and library provided by the libva-intel-driver and libva packages respectively. On older GPUs, this is provided instead by the XvMC driver, which is included with the DDX driver.

## Configuration

There is no need for any configuration to run X.

For the full list of options, see `$ man intel`.

## Loading

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

If it does not happen, then:

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

### Enable early KMS

Tip: If you have problems with the resolution, you can check whether 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.

KMS is typically initialized after the initramfs stage. It is possible, however, to enable KMS during the initramfs stage. To do this, add the `i915` module to the `MODULES` line in `/etc/mkinitcpio.conf`:

    MODULES="... i915 ..."

Tip: Users might need to add `intel_agp` before `i915` to suppress the ACPI errors. The order matters because the modules are activated in sequence.

If you are using a custom EDID file, you should embed it into initramfs as well:

    /etc/mkinitcpio.conf

    FILES="/lib/firmware/edid/your_edid.bin"

Now, regenerate the initramfs:

    # mkinitcpio -p linux

The change takes effect at the next reboot.

## Module-based Powersaving Options

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

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

    $ modinfo -p i915

To check which options are currently enabled, run

    # systool -m i915 -av

You will note that the `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 module options.

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

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

    /etc/modprobe.d/i915.conf

    options i915 enable_rc6=1 enable_fbc=1 lvds_downclock=1

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

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.

## Tips and tricks

### Disable Vertical Synchronization (VSYNC)

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

    ~/.drirc

    <device screen="0" driver="dri2">
    	<application name="Default">
    		<option name="vblank_mode" value="0"/>
    	</application>
    </device>

Do not use driconf to create this file, it is buggy and will set the wrong driver.

### Setting scaling mode

This can be useful for some full screen applications:

    $ xrandr --output LVDS1 --set PANEL_FITTING param

where `param` can be:

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

If it does not work, try:

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

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

### KMS Issue: console is limited to small area

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

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

### H.264 decoding on GMA 4500

The libva-intel-driver package provides MPEG-2 decoding only for GMA 4500 series GPUs. The H.264 decoding support is maintained in a separated g45-h264 branch, which can be used by installing libva-intel-driver-g45-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 [2]. This is echoed by other experiences [3].

### Setting brightness and gamma

The following example demonstrates using using the `/sys` virtual file system to set brightness at the driver level. The maximum brightness is indicated in the file `/sys/class/backlight/intel_backlight/max_brightness`. Note that its value may differ across different hardware configurations.

    # cd /sys/class/backlight/intel_backlight
    # cat max_brightness
    4437
    # echo 2200 > brightness

Brightness can alternatively be set using the xorg-xbacklight package.

    $ xbacklight -set 50  # sets brightness to 50% of maximum

Increments can be used instead of absolute values, for example:

    $ xbacklight -inc 10  # increase brightness by 10%
    $ xbacklight -dec 10  # decrease brightness by 10%

Gamma can be set using either the xorg-xrandr or xorg-xgamma package. The following commands create the same effect.

    $ xrandr --output LVDS1 --gamma 1.0:1.0:1.0
    $ xgamma -rgamma 1 -ggamma 1 -bgamma 1

## Troubleshooting

### SNA issues

From `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 xf86-video-intel. If you are experience issues with SNA, try using UXA instead, which can be done by creating an X configuration file containing the following:

    /etc/X11/xorg.conf.d/20-intel.conf

    Section "Device"
       Identifier  "Intel Graphics"
       Driver      "intel"
       Option      "AccelMethod"  "uxa"
    EndSection

Glamor can be used instead:

    /etc/X11/xorg.conf.d/20-intel.conf

    Section "Device"
       Identifier  "Intel Graphics"
       Driver      "intel"
       Option      "AccelMethod"  "glamor"
    EndSection

### 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 section above. [dead link 2014-12-18]

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

### Tear-free video

The SNA acceleration method causes tearing for some people. To fix this, enable the `"TearFree"` option in the driver:

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

### 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:

    /etc/X11/xorg.conf.d/20-intel.conf

    Section "Device"
       Identifier "Intel Graphics"
       Driver "intel"
       Option "NoAccel" "True"
    EndSection

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

    /etc/X11/xorg.conf.d/20-intel.conf

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

If you experience crashes and have

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

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

    i915.semaphores=1

to your boot parameters.

### Adding undetected resolutions

This issue is covered on the Xrandr page.

### Weathered colors (colorspace problem)

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

Kernel 3.9 contains the Intel driver changes allowing easy RGB Limited range settings which can cause weathered colors in some cases. It is related to the new "Automatic" mode for the "Broadcast RGB" property. One can force mode e.g. `xrandr --output <HDMI> --set "Broadcast RGB" "Full"` (replace `<HDMI>` with the appropriate output device, verify by running `xrandr`). You can add it into your `.xprofile`, make it executable to run the command before it will start the graphical mode.

Note: Some TVs can only display colors from 16-255 so setting to Full will cause color clipping in the 0-15 range so it is best to leave it at Automatic which will automatically detect whether it needs to compress the colorspace for your TV.

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

Unfortunately, the intel driver does not support setting the colorspace through an xorg.conf.d file.

#### Intel Color Range (Auto) Workaround

This article or section needs expansion.

Reason: The following method to patch was added to have color space set in vt already. As the author describes in talk already, it would be preferable to use a systemd unit for setting the desired above xrandr configuration on boot instead of patching. Idea? See: (Discuss)

A longer term workaround (which restricts the use to full color space displays) is to manually patch and recompile the kernel sources in `drivers/gpu/drm/i915/intel_hdmi.c`

    --- drivers/gpu/drm/i915/intel_hdmi.c	2014-11-08 19:25:27.813734911 +0800
    +++ drivers/gpu/drm/i915/intel_hdmi.c	2014-11-08 19:28:12.886143545 +0800
    @@ -1103,7 +1103,8 @@ intel_hdmi_set_property(struct drm_conne

     		switch (val) {
     		case INTEL_BROADCAST_RGB_AUTO:
    			intel_hdmi->color_range_auto = true;
    +			intel_hdmi->color_range_auto = false;
    +			intel_hdmi->color_range = 0;
     			break;
     		case INTEL_BROADCAST_RGB_FULL:
     			intel_hdmi->color_range_auto = false;

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

Either in addition to the above mentioned parameter, or on its own, add one of the following two parameters:

    acpi_osi=Linux
    acpi_osi="!Windows 2012"

Another parameter available:

    video.use_native_backlight=1

If neither of those solve the problem, edit or create `/etc/X11/xorg.conf.d/20-intel.conf` with the following content:

    /etc/X11/xorg.conf.d/20-intel.conf

    Section "Device"
            Identifier  "card0"
            Driver      "intel"
        Option      "Backlight"  "intel_backlight"
            BusID       "PCI:0:2:0"

    EndSection

If using the UXA acceleration as mentioned above, create the file as follows:

    /etc/X11/xorg.conf.d/20-intel.conf

    Section "Device"
            Identifier  "card0"
            Driver      "intel"
            Option      "AccelMethod"  "uxa"
            Option      "Backlight"    "intel_backlight"
            BusID       "PCI:0:2:0"

    EndSection

### Disabling frame buffer compression

On some cards such as Intel Corporation Mobile 4 Series Chipsets, enabling frame buffer compression 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 `i915.enable_fbc=0` to the kernel line parameters. More information on the results of disabled compression can be found here.

### Corruption/Unresponsiveness in Chromium and Firefox

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

### GPU hangs with Haswell's and Ivy Bridge's HD Graphics

A recently fixed bug in drm-intel causing GPU hangs with Haswell's HD Graphics, known as GT1, which can be found in the ULV and regular (37 W) dual-core CPU models of Haswell, the bug was confirmed to affect also Ivy Bridge ULV CPUs (thus also Ivy Bridge's HD Graphics).

This bug will result in a temporary hang of an application or Xorg, that might be recoverable or not, which will be logged as `[drm] stuck on render ring`.

The bug is fixed in rc2 of kernel 3.19, the relevant patches are: [6], [7].

## See also

- https://01.org/linuxgraphics/documentation (includes a list of supported hardware)

Categories:

- Graphics
- X Server