Intel graphics

From ArchWiki
Revision as of 02:38, 18 September 2011 by James Eder (talk | contribs) (assorted fixes)
Jump to: navigation, search

This template has only maintenance purposes. For linking to local translations please use interlanguage links, see Help:i18n#Interlanguage links.

Local languages: Català – Dansk – English – Español – Esperanto – Hrvatski – Indonesia – Italiano – Lietuviškai – Magyar – Nederlands – Norsk Bokmål – Polski – Português – Slovenský – Česky – Ελληνικά – Български – Русский – Српски – Українська – עברית – العربية – ไทย – 日本語 – 正體中文 – 简体中文 – 한국어

External languages (all articles in these languages should be moved to the external wiki): Deutsch – Français – Română – Suomi – Svenska – Tiếng Việt – Türkçe – فارسی

Template:Article summary start

Template:Article summary text Template:Article summary heading Template:Article summary wiki Template:Article summary wiki Template:Article summary wiki Template:Article summary wiki Template:Article summary end

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

Note: For use within the console without X, see Uvesafb.


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:

  • 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 i prefix.

See this for a list.



Prerequisite: Xorg

# pacman -S xf86-video-intel

You may need to install lib32-intel-dri in 64-bit systems to use acceleration in 32-bit programs.

Note: lib32-intel-dri is found in the [multilib] repository.


There is no need for any kind of configuration to get the Xorg running (an Template:Filename is unneeded).

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

# gpasswd -a username video

KMS (Kernel Mode Setting)

KMS is required in order to run X (Gnome, KDE, etc).

KMS is supported by Intel chipsets that use the i915 DRM driver and is now enabled by default as of kernel v2.6.32. Since xf86-video-intel 2.10, using KMS is mandatory. 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 native resolution.

Note: When using KMS, you must remove any references to "vga" or "video" from the kernel line in Template:Filename

Add the Template:Codeline module to the Template:Codeline line in Template:Filename:

Note: Failing to add Template:Codeline to the Template:Codeline array in Template:Filename will likely cause the error Template:Codeline on (at least) the first generation Core i{3,5,7} series processors with integrated GPUs.

Now, regenerate the initramfs:

# mkinitcpio -p linux

Everything should work now. If you are having problems, try explicitly enabling KMS by adding Template:Codeline to your kernel line in Template:Filename:

# (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 Template:Codeline property nor Template:Codeline. Now, reboot and Xorg will work.

If you ever want to disable KMS, you can change the Template:Codeline option to 0 in GRUB's Template:Filename, without rebuilding anything:

# (0) Arch Linux
title  Arch Linux
root   (hd0,0)
kernel /boot/vmlinuz-linux root=/dev/... i915.modeset=0
initrd /boot/initramfs-linux.img

Template:Codeline is the Intel equivalent to Template:Codeline for other video cards.

Note: Adding Template:Codeline 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 Template:Filename, 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 "e" for "edit". Now select the line starting with "kernel" and hit again "e" for editing. You can now add the Template:Codeline option and disable KMS by setting it to 0. Press enter and then "b" to boot. Note that this will be temporary, so it will be enabled again upon rebooting.

Note: Downgrade to kernel or disable modesetting with kernel boot parameter if you get a blank screen during boot process with Intel GMA 950

See also

Tips and tricks

Setting scaling mode

This can be useful for some full screen applications.

xrandr --output LVDS1 --set PANEL_FITTING param

where Template:Codeline can be

If it does not work, you can try

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

where Template:Codeline is one of Template:Codeline, Template:Codeline or Template:Codeline.

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. For example, add the following to the end of the kernel line in Template:Filename:


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

Supported hardware



Glxgears shows low performance results

If you run glxgears in order to check your system's graphics' performance, you may notice that glxgears shows results around 60 FPS:

311 frames in 5.0 seconds = 61.973 FPS
311 frames in 5.0 seconds = 62.064 FPS
311 frames in 5.0 seconds = 62.026 FPS

That is happening not because there is a performance regression, but because your system graphics are using VSync, that means, your screen's native frames per second.

Note: glxgears is not a benchmark for performance comparison between two or more systems.

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 i915 and intel_agp to the initramfs. See KMS above.

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


External monitor connected to laptop flashes black every 30 seconds

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 xf86-video-intel version 2.14.0-1 and kernel 2.6.37-5 have solved this issue.

X freeze/crash with intel driver

If you have issue with X crashing, or GPU hang, or problem with frozen X, then the fix may be to use the "Shadow" option: Template:File

Using this fix (Option "Shadow" "True") may cause problems with gnome-screenshot and similar programs like gimp, or gcolor2.