Intel Graphics Media Accelerator 950

From ThinkWiki
Jump to: navigation, search

Intel video driver

The Intel opensource videodriver is maintained by Intel at Intel releases a new driver once per quarter. The latest stable release is 2.10.

Kernel mode setting (KMS)

KMS (Kernel Mode Setting) as the name suggests moves some video setup functions to the kernel. This should have the following benefits over legacy mode setting

  • increased stability, because it removes the current contention between the X server and the kernel
  • ability to show kernel dump screens even when the X server was running
  • rapid mode switching
  • in theory should not allow the X video driver to hang the system
  • early graphical boot display with seamless login
  • should in the future allow for the X server to run without root privileges
  • larger virtual display size (4096x4096) allowing extended desktop configs (2048x2048 without KMS)

Note that KMS does not eliminate the need for the Intel Xorg driver, it just frees that driver from the hardware setup functions.


Right now KMS is still in heavy development, and officially requires at least kernel 2.6.29 with version 2.7 of the Intel driver. But in reality you should really be running at least the kernel and version 2.8 of the Intel driver.


The chip has hardware limitations when the display area exceeds 2048 pixels (horizontally or vertically), which is why earlier versions of the driver did not even try to support it. Here are the limitations you may run into when running dual-display Extended desktop.

  • 3D acceleration is limited (compiz will crash, or with some older software stacks may even freeze the system) [1]
  • Xvideo does not work (black or empty video window) [2]

For the Xvideo issue a workaround in the driver is technically possible but not yet implemented.

For now you can work around the Xvideo driver issue by either enabling Metacity compositing or disabling XV overlay.

Enable Metacity Compositing

gconftool-2 --type bool --set /apps/metacity/general/compositing_manager true

This will result in a slower desktop. It can be turned off again with

gconftool-2 --type bool --set /apps/metacity/general/compositing_manager false

Disable XV
This will cause much higher CPU usage, but only during video playback. For Gstreamer enabled apps this can be set globally, for other apps you will have to dig into their settings.

gconftool-2 --type string --set /system/gstreamer/0.10/default/videosink ximagesink

To set it back to the default setting

gconftool-2 --type string --set /system/gstreamer/0.10/default/videosink autovideosink

Here is a script I wrote that automatically sets the correct video output option based on configured displays. It could be launched from a dock hotplug event script (although that would not take care of all the use cases, such as booting with external display already attached)

# This script is to work around an annoying issue on Intel 945 video chips
# Basically you cannot have video acceleration if desktop size >2048 pixels in either way
# unless you use Metacity compositing, which is rather slow.
# So there are 2 ways to work around the bug, either use Compositing or disable XV.
# We do the later, but only if the current display size > 2048

for output in $(/usr/bin/xrandr -d :0.0 --verbose| \
                /bin/grep "Screen 0"| \
                /usr/bin/awk '{print $8} {print $10}'| \
                /usr/bin/awk -F, '{print $1}')
   if [ "$output" -gt "2048" ]; then

if [ "$disablexv" -eq "1" ]
    /usr/bin/gconftool-2 --type string --set /system/gstreamer/0.10/default/videosink ximagesink
    /usr/bin/gconftool-2 --type string --set /system/gstreamer/0.10/default/videosink autovideosink


In this mode, ideally you do not configure any settings through xorg.conf but by using xrandr, or a graphical front-end to RandR such as gnome-display-settings.

Disabling KMS

If KMS causes you problems, you can disable it and return to user mode setting (UMS) by booting with the nomodeset kernel boot option. Note that this is no longer an option starting with version 2.10 of the Intel Xorg driver as UMS support has been dropped.

User mode setting (UMS)

User mode setting means the Intel Xorg driver does the mode setting. This is how mode setting worked before KMS was introduced. Note that starting with the 2.10 version of the Intel Xorg driver UMS support has been removed, leaving just KMS support.

There are two ways to configure the driver, either the 'old fashion' way through xorg.conf, or using xrandr (either from the cmd line or through a display utility such as gnome-display-properties).


The basic working starting point for the sections relevant to graphics (excluding any manually loaded modules) is:

Section "Device"
        Identifier "Intel Graphics Adapter"
        Driver     "intel"

Section "Screen"
        Identifier "Default Screen"
        Device "Intel Graphics Adapter"

But with modern distributions even the above is not necessarily needed as the video chipset, resolution, refresh rate, etc will be auto-detected. If you don't like the auto-detected settings, you can use the XRandR command line utility to adjust them dynamically without having to restart the X server! You can always of course get more sophisticated with the xorg.conf file. Just type man intel or read Intel's documentation for more info.

External display with XRandR

Unfortunately, given all the radical changes to the Intel driver, and especially now with KMS, external display support has been rather in flux.

One of the issues encountered is that the maximum virtual screensize depending on driver version (or in the case of KMS, the kernel). This is important if you want to have an extended desktop (dual-display), but not for Mirror mode. If your using KMS, depending on what patches made it into the kernel the maximum virtual screensize is either 2048x2048 or 4096x4096. If your not using KMS, depending on the Intel driver version it will be either 1280x1280 or 2048x2048. 4096x4096 is not possible without KMS, and even then you might have to add this patch to your kernel to enable it.

To see what your virtual screensize is, simply run xrandr from a cmdline and look for something like this

Screen 0: minimum 320 x 200, current 1400 x 1050, maximum 4096 x 4096

As you can see in the above example the maximum virtual screensize is 4096x4096 which is ideal, and again, only possible in combination with KMS. If your getting 1280x1280 instead, your running an older Intel driver and have to add the Virtual line as shown below to your xorg.conf

Section "Screen"
     Identifier      "Default Screen"
     Device          "Intel Graphics Adapter"
     SubSection "Display"
            Virtual         2048 2048

Once you have started X, you should find that your multiple monitors are automatically activated and mirror each other to the extent allowed by their potentially different geometries. If you want them to appear as a "large desktop", you need to adjust their relative position with the XRandR utility. You can get an idea of what you're working with by typing

xrandr -q

This will give you a list of outputs and tell you which ones are connected. The external display port should be called "VGA" or "DVI" (or "VGA1" or "DVI1" in case of KMS) while the builtin LCD should be called "LVDS". (or "LVDS1" in case of KMS). If, for example you want to stack your desktops vertically, you might do something like

xrandr --output LVDS --below VGA


xrandr --output VGA --below LVDS

your window manager may treat the two cases differently in terms of where it decides to put things like the toolbar. Ideally, you probably want to put the desired xrandr command someplace that it might get executed before your window manager starts. For example in your ~/.xsession or ~/.xinitrc file.

External VGA port with xorg.conf

While XRandR eliminates the need to deal with xorg.conf in posititioning your screens, you may just want them to be laid out correctly from the outset. In this case, you can specify the default orientation of the displays in the xorg.conf file (which you can still change later with XRandR). This involves adding a "Monitor" section for each physical display output specifying its position. You must also tell the driver which "Monitor" belongs to which output (VGA,LVDS,etc) with the associated "monitor-..." option.

Section "Device"
        Identifier "Intel 945GM"
        Driver     "intel"
	Option     "monitor-VGA"  "External VGA"
	Option     "monitor-LVDS" "Builtin LCD"

Section "Monitor"
     Identifier "Builtin LCD"
     Option "Below" "External VGA"

Section "Monitor"
     Identifier "External VGA"
     Option "Above" "Builtin LCD"

Section "Screen"
        Identifier "Screen Dual"
        Device "Intel 945GM"
	SubSection "Display"
                Virtual 2048 2048

More info can be found at

VESA (console) resolution

Largest video resolution, supported by VESA for T60 is 1280x1024. You can set that for console in grub or lilo by adding vga=794 option.

SVideo port

The SVideo Port can be activated using xrandr. run

xrandr --verbose

to see if there is a TV section. The supported TV_FORMATs and other options are listed. The parameters TOP, RIGHT, BOTTOM ans LEFT are used to control the TV-overscan.

#set the TV format
xrandr --output TV --set TV_FORMAT PAL
#set the overscan (adjust fitting your TV)
xrandr --output TV --set TOP 20
xrandr --output TV --set RIGHT 20
xrandr --output TV --set BOTTOM 0
xrandr --output TV --set LEFT 40
#turn on the TV output
xrandr --output TV --auto
#turn off...
xrandr --output TV --off

This works for my Thinkpad R60, running Debian Lenny

DVI port

DVI passthrough is only supported on the T60 in combination with a docking station. Maximum resolution is 2048x1536

Suspend behaviour

  • Required kernel parameters for suspend to ram: none
  • Additional notes:
    • switch to/from X11 to reinitialize display properly (stays black)
    • DO NOT use vbetool to save/restore the video mode, this breakes resume!

ThinkPads this chip may be found in