Intel GMA 500

From ArchWiki
Revision as of 12:10, 17 October 2012 by Thevoid (Talk | contribs) (Troubleshooting)

Jump to: navigation, search

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 heading Template:Article summary link Template:Article summary end

The Intel Poulsbo Chipset, also known by its official names "GMA 500" and "Intel System Controller Hub US15W", is typically found on boards for the Atom Z processor series. It embeds a PowerVR SGX 535 graphics core developed by Imagination Technologies and then licensed by Intel. Its major advantages include the hardware decoding capability of up to 720p/1080i video content in various state-of-the-art codecs, e.g. H.264.

As the graphics hardware was not developed by Intel themselves, the standard opensource Intel drivers do not work with this hardware.

On this page you find comprehensive information about how to get the best out of your Poulsbo hardware using Arch Linux.

Kernel's gma500_gfx module

With kernel 2.6.39, a new psb_gfx module appeared in the kernel developed by Alan Cox to support Poulsbo hardware. As of kernel 3.3.rc1 the driver has left staging and been renamed gma500_gfx. ([1])

Advantages

  • Native resolution (1366x768) with early KMS (tested on Asus Eee 1101HA)
  • Up to date kernel and Xorg
  • 2D acceleration
  • Works out of the box

Disadvantages

  • Some are unable to get native resolution (e.g 1366x768)
  • No 3D acceleration possible
  • Poor multimedia performance (use mplayer with x11 or sdl so fullscreen video will be quite slow)

To check if the driver is loaded, the output of lsmod | grep gma should look like this:

gma500_gfx            131893  2 
i2c_algo_bit            4615  1 gma500_gfx
drm_kms_helper         29203  1 gma500_gfx
drm                   170883  2 drm_kms_helper,gma500_gfx
i2c_core               16653  5 drm,drm_kms_helper,i2c_algo_bit,gma500_gfx,videodev

Dual Monitor Setup

To setup different resolution for external monitor using xrandr, xf86-video-modesetting-gitAUR from AUR is needed. (or the stable releases xf86-video-modesettingAUR) This will replace the xf86-video-fbdev driver.

After installing, an Xorg file is needed to setup the driver. Use this for device section:

/etc/X11/xorg.conf.d/20-gpudriver.conf
 Section "Device"
    Identifier "gma500_gfx"
    Driver     "modesetting"
    Option     "SWCursor"       "ON" 
 EndSection
Note: There have been some reports that modesetting causes some anomalies on the screen. Latest git snapshot fixes that.

Troubleshooting

Poor video performance

If you have problems playing 720p and 1080p videos, yes, that's normal while there are no accelerated XV drivers. But you can improve it a lot, even to the point of going well and smoothly for most videos (even HD ones) using a little trick. Add this to /etc/rc.local:

pm-powersave false

That will decreese your battery life a little, but will improve the experience, specially with video. Always use mplayer because is the best optimized player in the Linux world.

Also, using the modesetting driver can improve performance.

Fix suspend

If suspend does not work, there are various quirk options you can try. First, make sure that you have pm-utils and pm-quirks installed. See the manpage for pm-suspend for a list of them all. One that has been reported to help is quirk-vbemode-restore, which saves and restores the current VESA mode.

To test it, open a terminal and use the following command

# pm-suspend --quirk-vbemode-restore 

That should suspend your system. If you are able to resume, you'll want to use this option every time you suspend.

# echo "ADD_PARAMETERS='--quirk-vbemode-restore'" > /etc/pm/config.d/gma500 

If you are not able to resume and you get a black screen instead, try the above quirk command with only one dash

# pm-suspend -quirk-vbemode-restore 
Tip: If you stuck with a black screen after resume, be aware that besides the black screen, your system works fine. Instead of hard rebooting, you could try to blindly reboot your system, since the last thing you used before suspend was the terminal. Alternatively, if you have ssh enabled on your machine you could do it remotely.
Note: If you selected modesetting as xserver in the previus section, suspend is probably not going to work with the current driver, so you need to select fbdev driver instead. But with fbdev multiple monitors (xinerama) won't work, so you have to choose.

Set backlight brightness

All that is needed to set the brightness is sending a number (0-100) to /sys/class/backlight/psblvds/brightness. This obviously requires sysfs to be enabled in the kernel, as it is in the Arch Linux kernel. To set display to minimal brightness, issue this command as root:

# echo 0 > /sys/class/backlight/psb-bl/brightness

Or, for full luminosity:

# echo 100 > /sys/class/backlight/psb-bl/brightness

A very short script is available to do this with less typing written by mulenmar.

#! /bin/sh
sudo sh -c "echo $1 > /sys/class/backlight/psb-bl/brightness"

Simply save it as brightness.sh, and give it executable permissions. Then you can use it like so:

Set brightness to minimum:

./brightness.sh 0

Set brightness to half:

./brightness.sh 50

Sudo may obviously ask for your password, so you have to be in the sudoers file.

Note: If changing /sys/class/backlight/psblvds/brightness does not work, you may need to add acpi_osi=Linux acpi_backlight=vendor to your kernel parameters. After rebooting, a new folder will appear under /sys/class/backlight/; making changes to the brightness file in that folder should work. For example, in some Asus netbooks the backlight can be controlled by writing a value (0-10) to /sys/class/backlight/eeepc-wmi/brightness.

A variation of this script can be found here.

Memory allocation optimization

You can often improve performance by limiting the amount of RAM used by the system so that there will be more available for the videocard. If you have 1GB RAM use mem=896mb or if you have 2GB RAM use mem=1920mb. Add the following parameters to your bootloader's configuration file.

Edit /boot/grub/menu.lst

...
kernel /vmlinuz-linux root=/dev/sda2 ro mem=896mb 
...

Edit /etc/default/grub

...
GRUB_CMDLINE_LINUX="mem=896mb"
...

Edit /boot/syslinux/syslinux.cfg

...
APPEND root=/dev/sda2 ro mem=896mb 
...

See also