intel is the open source graphics driver for Intel GMA onboard graphics cards, starting with the Intel 810.
- 1 Hardware detection
- 2 Feature support
- 3 Installation
- 4 Configuration
- 5 Troubleshooting
- 6 See also
- 7 External resources
- 8 References
To choose the right driver, first detect the graphics card. lspci can be used for this task:
lspci | grep -i VGA
This should show something like this:
lspci | grep -i VGA
00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor Graphics Controller (rev 09)
The lspci output for the graphics controller may refer to CPU generations, whereas the Feature support table below refers to GPU generations. E.g., “3rd Gen” in the example lspci output above corresponds to “Gen7” in the table below.
|Gen 1||810, 815||1.2||No||No||No||intel|
|Gen 2||i830M, 845G, 855GM, 865G||1.3||No||No||No||intel|
|Gen 3||915G/GM, 945G/GM, G/Q33, Atom D4xx/D5xx/N4xx/N5xx||1.4/1.5||No||No||No||intel i915|
|Gen 4||965G/GM/Q, G/Q35, G41, G/Q43, G/GM/Q45||2.1||2.0||No||G/GM45: MPEG2 only[table 1]||intel i965|
|Gen 5||Nehalem (Ironlake)||2.1||2.0||No||Yes||intel i965|
|Gen 6||Sandy Bridge||3.3||3.0||No||Yes||intel i965|
|Gen 7||Ivy Bridge, Valley View, Haswell, Atom Z36xx/Z37xx||3.3||3.0||1.1[table 2]||Yes||intel i965|
|Gen 8||Broadwell, Cherryview (Braswell, Cherry Trail)||3.3||3.0||No||Yes||intel i965|
|Gen 9||Skylake||4.4||3.0||No||Yes||intel i965|
- Experimental H264 support can be enabled. See Enable_hardware_H264_decoding_on_Intel_G/GM45
- A FOSS implementation is in development under the name Beignet
A full list of Intel CPU graphic capabilities can be found here.
If you are using Kabylake, Skylake or Broxton Intel Graphics, install sys-kernel/linux-firmware.
emerge --ask sys-kernel/linux-firmware
Otherwise you might see errors such as
kernel: i915 0000:00:02.0: Direct firmware load for i915/skl_dmc_ver1.bin failed with error -2 kernel: i915 0000:00:02.0: Failed to load DMC firmware [https://01.org/linuxgraphics/intel-linux-graphics-firmwares], disabling runtime power management.
in dmesg. Include the files required for your GPU in the kernel, in this case:
Device Drivers ---> Generic Driver Options ---> -*- Userspace firmware loading support [*] Include in-kernel firmware blobs in kernel binary (i915/skl_dmc_ver1.bin) (/lib/firmware) Firmware blobs root directory
The following kernel options need to be activated:
Processor type and features ---> [*] MTRR (Memory Type Range Register) support Device Drivers ---> Graphics support ---> <*> /dev/agpgart (AGP Support) ---> <*> Intel 440LX/BX/GX, I8xx and E7x05 chipset support <*> Direct Rendering Manager (XFree86 4.1.0 and higher DRI support) ---> <*> Intel 8xx/9xx/G3x/G4x/HD Graphics [*] Enable modesetting on intel by default [*] Enable legacy fbdev support for the modesetting intel driver
The legacy fbdev support is required since kernel 3.14.14 at least for i915 (
For hybrid Intel/AMD system, follow also the steps of radeon (opensource) or fglrx (closed binary) drivers.
Since kernel version 4.4 the driver has been moved and the legacy fbdev support is now
Device Drivers ---> Graphics support ---> <*> /dev/agpgart (AGP Support) ---> --- /dev/agpgart (AGP Support) < > AMD Opteron/Athlon64 on-CPU GART support -*- Intel 440LX/BX/GX, I8xx and E7x05 chipset support < > SiS chipset support < > VIA chipset support [ ] VGA Arbitration [ ] Laptop Hybrid Graphics - GPU switching support <*> Direct Rendering Manager (XFree86 4.1.0 and higher DRI support) ---> --- Direct Rendering Manager (XFree86 4.1.0 and higher DRI support) [*] Enable legacy fbdev support for your modesetting driver [ ] Allow to specify an EDID data set instead of probing for it I2C encoder or helper chips ---> < > 3dfx Banshee/Voodoo3+ < > ATI Rage 128 < > ATI Radeon < > AMD GPU < > Nouveau (NVIDIA) cards < > Intel I810 <*> Intel 8xx/9xx/G3x/G4x/HD Graphics [ ] Enable preliminary support for prerelease Intel hardware by default < > Matrox g200/g400 < > SiS video cards < > Via unichrome video cards < > Savage video cards < > Virtual GEM provider < > DRM driver for VMware Virtual GPU < > Intel GMA5/600 KMS Framebuffer < > DisplayLink < > AST server chips < > Kernel modesetting driver for MGA G200 server engines < > Cirrus driver for QEMU emulated device < > QXL virtual GPU < > DRM Support for bochs dispi vga interface (qemu stdvga) Display Panels ---- Display Interface Bridges ---- Frame buffer Devices ---> -*- Backlight & LCD device support ---> Console display driver support ---> [*] Bootup logo --->
Portage uses the VIDEO_CARDS variable, which expands into the USE_EXPAND variable, for enabling support for various graphics cards in packages. Assuming x11-base/xorg-drivers has already been installed, setting VIDEO_CARDS variable in etc/portage/make.conf will pull in the correct video driver: (see the feature matrix)
Check the USE flags of x11-drivers/xf86-video-intel:
USE flags for x11-drivers/xf86-video-intel X.Org driver for Intel cards
||Enable extra debug codepaths, like asserts and extra output. If you want to get meaningful backtraces see https://wiki.gentoo.org/wiki/Project:Quality_Assurance/Backtraces||global|
||Enable direct rendering: used for accelerated 3D and some 2D, like DMA||global|
||Use DRI3 by default||local|
||Enable SandyBridge's New Acceleration (useful on all chipsets, not just SandyBridge)||local|
||Enable virtual/udev integration (device discovery, power and storage device support, etc)||global|
||Enable UMA Acceleration Architecture||local|
||Enables X-Video Motion Compensation support||local|
After making any changes update the system so the changes take effect by running the emerge command with the
emerge --ask --changed-use --deep @world
Intel GMA X4500HD / G45 / GM45 and newer supports VAAPI hardware video acceleration.
If you have the
acl USE flag enabled globally and are using ConsoleKit (i.e you're using a Desktop profile) permissions to video cards will be handled automatically. You can check the permissions using getfacl:
getfacl /dev/dri/card0 | grep larry
A broader solution is to add the user you want to be able to access the video card to the video group:
gpasswd -a larry video
Note that you will still be able to run X without permission to the DRI subsystem, but usually not with acceleration enabled.
Choose one of the following configuration options:
- Classic Driver -- x11-drivers/xf86-video-intel
- As xorg is not aware of i915 or i965 they will need to be addressed as Driver
Section "Device" Identifier "intel" Driver "intel" EndSection
- Alternate Driver for Gen 4+ -- Modesetting -- Experimental
These instructions are labeled as "Experimental" because they are new. Experiences of this configuration can be found in the Discussion of this page. Add any difficulties there so this section can be improved.
- As of xorg-server-1.17, the modesetting driver was moved into x11-base/xorg-server. This driver has more features than the classic driver, such as GLAMOR.
- xorg-server is easily configured to prefer
modesettingover the older
Section "Device" Identifier "modesetting" Driver "modesetting" EndSection
The X server is designed to work out-of-the-box, with no need to manually edit X.Org's configuration files. It should detect and configure devices such as displays, keyboards, and mice.
However, the main configuration file of the X server is the xorg.conf.
- Gentoo bugtracker: known bugs
- Freedesktop.org bugtracker: known bugs
- Freedesktop.org bugtracker: known bugs
- Guide, how to report bugs upstream
html5/vaapi gpu hangs
If your GPU hangs up when watching vaapi-accelerated video e.g. on youtube, you can try enabling your IOMMU:
Device Drivers ---> [*] IOMMU Hardware Support ---> [*] Support for Intel IOMMU using DMA Remapping Devices [*] Enable Intel DMA Remapping Devices by default
Related upstream bug report.
A workaround is to set
TerminateServer=true in all sections of the file /usr/share/config/kdm/kdmrc, which starts with
KDE's plasma eating CPU
If /usr/bin/plasmashell is always consuming several percent of CPU, perhaps this is related to a vsync problem. QT Quick Animation seem to loop too fast when vsync is not managed by the driver (Reference)
A way to enable vsync with SNA is to enable "TearFree" Option in xorg.conf
Section "Device" Identifier "Device0" Driver "intel" Option "AccelMethod" "SNA" Option "TearFree" "true" EndSection
- According to this Debian wiki, CONFIG_FRAMEBUFFER_CONSOLE must be set to y (aka built-in to the kernel). Otherwise, it is possible to always have a black screen unless nomodeset is passed to the kernel, thus disabling kernel mode setting (KMS).
acpi_osi="Linux"can be passed to the kernel command line to try to solve this kind of issue. This is usually done through the bootloader.
- Kernel with version 4.2 or newer is needed with some gen8 chipsets.
Brightness doesn't change with keyboard shortcuts
First, make sure vendor compatibility is on in the kernel configuration. Toshiba for Toshiba, etc.
If it is, or when the brightness buttons are working, the issue is that the kernel can not detect where the brightness control is located.
Luckily, this is easy enough to modify, as long as the kernel version is >= 3.13.x and < 4.2.Add
to the kernel command line.video.use_native_backlight=1
On kernels >= 4.2, the video.use_native_backlight option is no longer available. You should use one of the following instead (experiment to see which works on your system):
- Xorg/Guide - A guide on how to configure Xorg.
- hprofile - Switching between other graphics drivers and intel.
- Gentoo Forums, "Black screen on boot after kernel upgrade - grub2"
- Gentoo Forums, "Black screen on kernel 3.14.14"
- Gentoo Forums, "N3700 8086:22b1 i915 black screen, works in kernel 4.2.6"
- RedHat Bug 1272633: "video.use_native_backlight=1 doesn't work" (comment 5)