intel is the open source graphics driver for Intel GMA onboard graphics cards, starting with the Intel 810.
To choose the right driver, first detect the graphics card. You can use lspci for this task:
|Gen2||i830M, 845G, 855GM, 865G||1.3||No||No||No||intel|
|Gen3||915G/GM, 945G/GM, G/Q33||1.4/1.5||No||No||No||intel i915|
|Gen4||965G/GM/Q, G/Q35, G41, G/Q43, G/GM/Q45||2.1||2.0||No||G/GM45: MPEG2 only||intel i965|
|Gen6||Sandy Bridge||3.1||2.0 (3.0)1||No||Yes||intel i965|
|Gen7||Ivy Bridge, Valley View, Haswell||3.1||2.0 (3.0)1||1.12||Yes||intel i965|
- 1) Needs testing packages: >=mesa-9.1
- 2) A FOSS implementation is in development under the name Beignet
You need to activate the following kernel options:
Portage uses the variable VIDEO_CARDS for enabling support for various graphics cards in packages. Setting VIDEO_CARDS 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:
|dri||Yes||Yes||Enable direct rendering: used for accelerated 3D and some 2D, like DMA|
|glamor||No||Enable Glamor OpenGL 2D acceleration|
|sna||Yes||Yes||Enable SandyBridge's New Acceleration (useful on all chipsets, not just SandyBridge)|
|udev||Yes||Yes||Enable sys-fs/udev integration (device discovery, power and storage device support, etc)|
|uxa||No||Enable UMA Acceleration Architecture|
|xvmc||No||Enables X-Video Motion Compensation support|
After setting this you want to update your system so the changes take effect:
Intel GMA X4500HD / G45 / GM45 and newer supports VAAPI hardware video acceleration.
If you have the USE flag acl 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:
A broader solution is to add the user you want to be able to access the video card to the video group:
Note that you will still be able to run X without permission to the DRI subsystem, but usually not with acceleration enabled.
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
- fdo bugtracker: known bugs
- fdo bugtracker: known bugs
- Guide, how to report bugs upstream
A workaround is to set TerminateServer=true in all sections of the file /usr/share/config/kdm/kdmrc, which starts with X-.
According to this Debian wiki, CONFIG_FRAMEBUFFER_CONSOLE must be set to y (aka built-in). Otherwise, it is possible to always have a black screen unless nomodeset is passed to the kernel, thus disabling KMS.
You can also try to pass acpi_osi="Linux" to the kernel line to try to solve this kind of issue
Brightness doesn't change with keyboard shortcuts
First, make sure your vendor compatibility is on in the kernel configuration, toshiba for toshiba and so on. If it is, or if you're sure that the brightness buttons are working, it's probably that your kernel can't detect where the brightness is. Luckily, this is easy enough to modify, as long as your kernel version is 3.13.x +.Simply add to your kernel command line.