Difference between revisions of "Intel GMA 500"

From ArchWiki
Jump to: navigation, search
m (fix gaps)
(Old fbdev driver (default))
(44 intermediate revisions by 11 users not shown)
Line 1: Line 1:
[[Category: Graphics (English)]]
+
[[Category:Graphics]]
[[Category: X Server (English)]]
+
[[Category:X Server]]
{{i18n|Poulsbo}}
+
[[el:Poulsbo]]
 +
[[it:Poulsbo]]
 +
[[ru:Poulsbo]]
 
{{Article summary start}}
 
{{Article summary start}}
 
{{Article summary text|The current state of Intel GMA500/Poulsbo hardware support under Arch Linux.}}
 
{{Article summary text|The current state of Intel GMA500/Poulsbo hardware support under Arch Linux.}}
 
{{Article summary heading|Related}}
 
{{Article summary heading|Related}}
{{Article summary wiki|Intel}}
+
{{Article summary wiki|Intel Graphics}}
 
{{Article summary wiki|Xorg}}
 
{{Article summary wiki|Xorg}}
{{Article summary wiki|Mplayer}}
+
{{Article summary wiki|MPlayer}}
 
{{Article summary heading|Resources}}
 
{{Article summary heading|Resources}}
 
{{Article summary link|Poulsbo Discussion in Arch BBS|https://bbs.archlinux.org/viewtopic.php?pid=746439}}
 
{{Article summary link|Poulsbo Discussion in Arch BBS|https://bbs.archlinux.org/viewtopic.php?pid=746439}}
 
{{Article summary end}}
 
{{Article summary end}}
  
The Intel Poulsbo Chipset, also known by its official names "GMA 500" and "[http://ark.intel.com/Product.aspx?id=35444 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.
+
The '''Intel GMA 500''' series, also known by it's codename '''Poulsbo''' or '''[http://ark.intel.com/Product.aspx?id=35444 Intel System Controller Hub US15W]''', is a family of integrated video adapters based on the PowerVR SGX 535 graphics core. It is typically found on boards for the Atom Z processor series. Features include 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 Intel drivers do not work with this hardware. Furthermore, at least two different accelerated Linux drivers for this hardware exist, each of which have major problems. Alternatively, [[Poulsbo#FBDEV Driver|there is a generic framebuffer driver solution]], but this is unaccelerated.
+
As the PowerVR SGX 535 graphics core was developed by Imagination Technologies and then licensed by Intel, 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.
 
On this page you find comprehensive information about how to get the best out of your Poulsbo hardware using Arch Linux.
  
== Drivers: Advantages and Disadvantages ==
+
== Kernel's gma500_gfx module ==
  
=== Kernel's psb-gfx module ===
+
With kernel 2.6.39, a new psb_gfx module appeared in the kernel developed by [http://en.wikipedia.org/wiki/Alan_Cox Alan Cox] to support Poulsbo hardware. As of kernel 3.3.rc1 the driver has left staging and been renamed gma500_gfx. ([http://blog.bodhizazen.net/linux/linux-gma500-poulsbo-driver-moved-out-of-staging/])
With kernel 2.6.39, a new psb_gfx module appeared in the kernel developed by Alan Cox to support Poulsbo hardware. Currently this is very rudimentary but the development is very active and this should get better and better with upcoming kernels.
+
  
 
'''Advantages'''
 
'''Advantages'''
  
 +
* Native resolution (1366x768) with early KMS (tested on Asus Eee 1101HA)
 
* Up to date kernel and Xorg
 
* Up to date kernel and Xorg
 
* 2D acceleration
 
* 2D acceleration
* Nothing to do to make it work
+
* Works out of the box
  
 
'''Disadvantages'''
 
'''Disadvantages'''
  
* Did not manage to get native resolution (e.g 1366x768)
+
* Some are unable to get native resolution (e.g 1366x768)
* Buggy backlight control (Fixed in Linux 3.0.0)
+
 
* No 3D acceleration possible
 
* No 3D acceleration possible
* Poor performances (use mplayer with x11 or sdl so fullscreen video will be quite slow)
+
* Poor multimedia performance (use mplayer with x11 or sdl so fullscreen video will be quite slow)
  
=== PSB/GMA500 Driver ===
+
To check if the driver is loaded, the output of <code>lsmod | grep gma</code> should look like this:
'''Advantages'''
+
     
 +
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
  
* Native resolution
+
== Modesetting driver and dual monitor Setup ==
* 2D acceleration
+
To setup different resolution for external monitor using [https://wiki.archlinux.org/index.php/Xrandr xrandr], {{Pkg|xf86-video-modesetting}} from official repo is needed. If you choose to use the git package ({{AUR| xf86-video-modesetting-git}}), remember to recompile it after a new version of [[Xorg]]. After installing, an [[Xorg]] file is needed to setup the driver. Use this for device section:
* Possible 3D acceleration with work and luck - Fedora, as well as Ubuntu, have this [http://ubuntuforums.org/showthread.php?t=1229345]
+
* Backlight control possible
+
  
'''Disadvantages'''
+
{{hc|/etc/X11/xorg.conf.d/20-gpudriver.conf|
 +
Section "Device"
 +
    Identifier "gma500_gfx"
 +
    Driver    "modesetting"
 +
    Option    "SWCursor"      "ON"
 +
EndSection
 +
}}
 +
{{Note|1= The above configuration file will replace the {{Pkg|xf86-video-fbdev}} driver. If you want to revert back, just replace {{ic|modesetting}} with {{ic|fbdev}}.}}
  
* Performance not on par with IEGD (Youtube videos play smoothly at 360p, perhaps 480p, but no higher)
+
== Troubleshooting ==
* Not supported through official packages. Use of AUR required.
+
* Needs kernel <=2.6.37 and Xorg 1.9
+
  
=== PSB/GMA500 Driver with FBDEV ===  
+
=== Poor video performance ===
'''Advantages'''
+
  
* Up to date Xorg without hacking libdrm
+
If you have problems playing 720p and 1080i videos, yes, that's normal while there are not accelerated XV drivers. But you can improve it up to the point of going well and smoothly for most videos (even HD ones) with these tricks:
* Native resolution
+
* 2D acceleration
+
* Backlight control possible
+
  
'''Disadvantages'''
+
# add <code>pm-powersave false</code> to <code>/etc/rc.local</code>. <code>man pm-powersave</code> for more info.
 +
# use {{AUR| xf86-video-modesetting-git}} as indicated above.
 +
# always use [[mplayer]] or any variant/gui. [[VLC]] and others are usually much more slower.
 +
# substitute the normal mplayer with {{AUR| mplayer-minimal-svn}}, and compile with aggressive optimizations: <code>-march=native -fomit-frame-pointer -O3 -ffast-math'</code>. ([[Makepkg|About makepkg]])
 +
# use {{AUR | linux-lqx}} as it is a very good performance kernel. Edit PKGBUILD so you can do <code>menuconfig</code> and make sure you select your processor and remove generic optimizations for other processors. ([[kernel |About kernels]])
  
* Needs kernel <=2.6.37
+
=== Fix suspend ===
* Performance comparable to FBDEV solution
+
==== Old fbdev driver (default) ====
* Not supported through official packages. Use of AUR required.
+
  
=== IEGD Driver ===
+
If suspend does not work, there are various quirk options you can try. First, make sure that you have {{Pkg|pm-utils}} and {{Pkg|pm-quirks}} [[pacman|installed]]. See the manpage for pm-suspend for a list of them all. One that has been reported to help is <code>quirk-vbemode-restore</code>, which saves and restores the current VESA mode.
'''Advantages'''
+
  
* X works
+
To test it, open a terminal and use the following command
* Native resolution
+
* Basic OpenGl Capabilities
+
* 2D acceleration
+
* HD video playback without stuttering
+
  
'''Disadvantages'''
+
# pm-suspend --quirk-vbemode-restore
As of August 12 2010:
+
  
* Artifacts in video playback
+
That should suspend your system. If you are able to resume, you'll want to use this option every time you suspend.
* Suspend states are broken
+
* Works only for kernel <= 2.6.31 & Xorg server <= 1.6
+
* Lengthy process to install
+
* Not supported through official packages.
+
  
=== FBDEV Driver ===
+
# echo "ADD_PARAMETERS='--quirk-vbemode-restore'" > /etc/pm/config.d/gma500
'''Advantages'''
+
  
* Combined with 915resolution-static and Uvesafb, allows native resolution
+
If you are not able to resume and you get a black screen instead, try the above quirk command with only '''one dash'''
* Up to date kernel and Xorg
+
* No recompiling needed on kernel updates
+
  
'''Disadvantages'''
+
# pm-suspend -quirk-vbemode-restore
  
* Video playback may not be smooth
+
If this also fails, you might try removing pm-utils's video resume script, so that it's not run when you resume the machine.
* Flash video playback, such as on YouTube, not smooth above 360p
+
* Full-screen Flash video playback useless
+
* No Xv video acceleration whatsoever
+
  
Installation and configuration procedure is [[Poulsbo#FBDEV Driver (xf86-video-fbdev)|is discussed later.]]
+
# cd /usr/lib/pm-utils/sleep.d
 +
# mv 99video ~
  
=== VESA Driver ===
+
{{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.}}
'''Advantages'''
+
  
* Combined with 915resolution-static and Uvesafb, possibly allows native resolution (untested)
+
==== modesetting xorg driver ====
* Up to date kernel and Xorg
+
* No recompiling needed on kernel updates
+
  
'''Disadvantages'''
+
On some machines, when using modesetting driver the screen gets messed up with random data. Although the computer still works, you must go to a console and kill X or reboot "blindly". This is not optimal, so here is a solution:
  
* Video playback may not be smooth
+
First, see your available screens and modes running {{ic|xrandr}}:
* Full-screen Flash video playback useless
+
* Slower than the FBDEV driver
+
* Not supported through official packages. Use of AUR required.
+
  
== Do I Need To Downgrade? ==
+
{{bc|
 +
# xrandr
 +
Screen 0: minimum 320 x 200, current 1280 x 720, maximum 2048 x 2048
 +
LVDS-0 connected 1280x720+0+0 222mm x 125mm
 +
  1280x720      60.0*+
 +
HDMI-0 connected 1280x720+0+0 531mm x 298mm
 +
  1920x1080      60.0 +
 +
  1680x1050      59.9 
 +
  1680x945      60.0 
 +
  1400x1050      74.9    59.9 
 +
  1600x900      60.0 
 +
  1280x1024      75.0    60.0 
 +
  1440x900      75.0    59.9 
 +
  1280x960      60.0 
 +
  1366x768      60.0 
 +
  1360x768      60.0 
 +
  1280x800      74.9    59.9 
 +
  1152x864      75.0 
 +
  1280x768      74.9    60.0 
 +
  1280x720      60.0*
 +
  1024x768      75.1    70.1    60.0 
 +
  1024x576      60.0 
 +
  832x624        74.6 
 +
  800x600        72.2    75.0    60.3    56.2 
 +
  848x480        60.0 
 +
  640x480        72.8    75.0    60.0 
 +
  720x400        70.1
 +
}}
  
As of November, 2011 you do not need to downgrade anything to use the psb-gfx, FBDEV, or VESA Xorg video drivers.
+
Edit or create (giving executive permissions) {{ic|/etc/pm/sleep.d/99xrandr}}, writing the correct names and modes for your solution:
  
However, if you wish to experiment with the PSB or IEGD driver, you will need to downgrade your kernel and maybe xorg-server, along with several other packages.
+
{{bc|<nowiki>
 +
#!/bin/sh
 +
#
 +
# turn off and on the screens so we force to clean video data
 +
case "$1" in
 +
hibernate|||suspend)
 +
xrandr --output LVDS-0 --off
 +
xrandr --output HDMI-0 --off
 +
;;
 +
thaw|||resume)
 +
xrandr --output LVDS-0 --off
 +
xrandr --output HDMI-0 --off
 +
xrandr --output LVDS-0 --mode 1280x720
 +
/usr/local/bin/brillo-
 +
;;
 +
*) exit $NA
 +
;;
 +
esac
 +
</nowiki>}}
  
== Xorg-server 1.7 or higher (current Arch) ==
+
In my case, I turn off both screens, and turn on only the main screen upon awakening. Feel free to customize to your needs.
 +
On some machines, the screen turns on by default even when the system was put to sleep with the screen turned off, so you need to turn it off twice.
  
=== Kernel's psb-gfx module ===
+
{{Note| This only works if you call {{ic|pm-suspend}} or {{ic|pm-hibernate}} inside [[X]]. If it is called from a daemon or a tty, it won't work.}}
 
+
If you have a kernel newer than 2.6.39, then it should work out of the box.
+
 
+
The module is psb_gfx:
+
$ modprobe -l | grep psb
+
kernel/drivers/staging/gma500/psb_gfx.ko.gz
+
 
+
And xorg should use fbdev by default. You can check it in /var/log/Xorg.0.log.
+
 
+
=== PSB/GMA500 Driver ===
+
 
+
You need kernel <=2.6.37 to use the PSB-Driver
+
 
+
==== Install from custom repository ====
+
 
+
Add the following repository to your {{ic|/etc/pacman.conf}}
+
[poulsbo-old]
+
Server = http://kissmyarch.eu/gma500/poulsbo-old/
+
and install the psb driver with
+
# pacman -Syu xorg-x11-drv-psb
+
 
+
==== Build and Install from AUR (xorg 1.9) ====
+
Build and install the following packages in this exact order
+
 
+
1) {{AUR|psb-firmware}}
+
2) {{AUR|psb-kmod}}
+
3) {{AUR|libdrm-poulsbo}}
+
4) {{AUR|xpsb-glx}}
+
5) {{AUR|xorg-x11-drv-psb}}
+
 
+
==== Configure xorg.conf ====
+
 
+
To tell Xorg to use this driver, change the Driver line in <code>/etc/X11/xorg.conf</code> to read as:
+
Driver "psb"
+
 
+
You can also try adding a couple options to try improving acceleration or stability:
+
 
+
with:
+
Option "ShadowFB" "true"
+
and possibly:
+
Option      "MigrationHeuristic" "greedy"
+
 
+
Cross fingers and restart X.
+
 
+
==== Hardware accelerated video playback ====
+
 
+
In order to have video acceleration, you must
+
* Install {{AUR|xorg-x11-drv-psb}}
+
* Install {{AUR|libva-freeworld}} from the [[Arch User Repository|AUR]] or from [https://wiki.archlinux.org/index.php/Poulsbo#Install_from_custom_repository above] given repository
+
* Install {{pkg|mplayer-vaapi}} from [community]
+
* Run
+
mplayer -vo vaapi -va vaapi videofile
+
 
+
=== PSB/GMA500 Driver with FBDEV ===
+
 
+
The advantage of this solution is that you just add a kernel module
+
but you do not need to bother about specific Xorg version or libdrm
+
while keeping backlight control.
+
 
+
It makes it simpler to manage than the PSB/GMA500 Driver and FBDEV Driver solutions.
+
 
+
==== Build and Install from AUR (xorg 1.9) ====
+
Build and install the following packages in this exact order
+
 
+
1) {{AUR|psb-firmware}}
+
2) {{AUR|psb-kmod}}
+
 
+
You can either download these packages from the repository given [https://wiki.archlinux.org/index.php/Poulsbo#Install_from_custom_repository above].
+
 
+
==== Install the fbdev Xorg driver ====
+
 
+
# pacman -S xf86-video-fbdev
+
 
+
==== Configure your system ====
+
 
+
Load the module at startup by adding "psb" to you MODULES in <code>/etc/rc.conf</code>.
+
To avoid an unnecessary reboot, as root perform to get your module loaded:
+
# modprobe psb
+
 
+
 
+
To tell Xorg to use the framebuffer driver, change the Driver line in <code>/etc/X11/xorg.conf</code> to read as:
+
Driver "fbdev"
+
 
+
Restart X and you are done !
+
 
+
=== FBDEV Driver (xf86-video-fbdev) ===
+
 
+
Download <code>v86d</code> and <code>xf86-video-fbdev</code>:
+
pacman -S v86d xf86-video-fbdev
+
 
+
You will also need to install {{AUR|915resolution-static}} from the [[Arch User Repository|AUR]] or the repository given [https://wiki.archlinux.org/index.php/Poulsbo#Install_from_custom_repository above].
+
 
+
Create the file <code>/etc/modprobe.d/uvesafb.conf</code>, if it does not exist, and change it so the only non-comment line is this:
+
options uvesafb mode_option=1280x800-32 scroll=ywrap
+
 
+
Make sure you use the right resolution for your setup -- if you have a 1366x768 screen, for example, change the "mode_option=" number to "1366x768-32".
+
 
+
Edit <code>/lib/initcpio/hooks/915resolution</code> and make sure it has the right resolution for your setup -- the same resolution as specified in <code>/etc/modprobe.d/uvesafb.conf</code>.
+
 
+
Next, edit <code>/etc/mkinitcpio.conf</code> and add <code>915resolution</code> and <code>v86d</code> to the "HOOKS", like this:
+
HOOKS="base udev 915resolution v86d ..."
+
 
+
Make sure you run mkinitcpio:
+
mkinitcpio -p linux
+
 
+
Edit <code>/etc/X11/xorg.conf</code> and change driver to fbdev:
+
Driver "fbdev"
+
 
+
See the [[Uvesafb|Uvesafb article]] for more information.
+
 
+
=== VESA Driver ===
+
 
+
Download <code>xf86-video-vesa</code> and install.
+
 
+
# pacman -S xf86-video-vesa
+
 
+
Then edit <code>/etc/X11/xorg.conf</code> to use it.
+
 
+
Driver "vesa"
+
 
+
== Xorg-server 1.6 ==
+
 
+
'''Please note that Kernel 2.6.31 and Xorg server 1.6 are no longer supported by the Arch Linux team.'''
+
 
+
=== Installing Xorg-server 1.6 ===
+
 
+
Add to your <code>/etc/pacman.conf</code> the following custom repository and make sure it is higher than the others.
+
 
+
[xorg16]
+
Server = http://catalyst.apocalypsus.net/repo/xorg16/i686/
+
 
+
Then uninstall old packages if any, and install xorg
+
 
+
# pacman -R xorg-server xf86-input-evdev xf86-input-mouse xf86-input-synaptics xf86-input-keyboard
+
            xf86-video-vesa xf86-video-fbdev
+
# pacman -S xf86-evdev xorg-server xf86-input-keyboard xf86-input-mouse xf86-input-synaptics
+
            xf86-video-vesa openssl-compatibility
+
 
+
 
+
An older version of <code>libssl</code> is required. This can be fulfilled using the {{AUR|openssl-compatibility}} package from the [[Arch User Repository|AUR]].
+
 
+
mkdir openssl-compatibility
+
cd openssl-compatibility
+
wget https://aur.archlinux.org/packages/openssl-compatibility/PKGBUILD
+
makepkg -s
+
# pacman -U openssl-compatibility*.pkg.tar.xz
+
 
+
Once this is done, you may reboot the computer. Alternatively, kill all instances of Xorg and restart.
+
 
+
The Xorg 1.6 server should start without issue.
+
 
+
=== FBDEV Driver using xorg-server-1.6.3.901 ===
+
 
+
The <code>xf86-video-fbdev</code> driver is not currently in the Chakra Project's repositories. Download and install from here
+
 
+
$ wget http://dl.dropbox.com/u/6228981/poulsbo/i686/fbdev/xf86-video-fbdev-0.4.1-1-i686.pkg.tar.gz
+
# pacman -U xf86-video-fbdev-0.4.1-1-i686.pkg.tar.gz
+
 
+
=== Installing IEGD-enabled kernel ===
+
 
+
This process is still under development. Some info may be found [http://org.bonfus.it/wiki/doku.php?id=en:argo#ubuntu_kernel_patches_for_fitpc here.]
+
 
+
=== Installing IEGD binary drivers ===
+
 
+
tbd
+
 
+
=== Troubleshooting Xorg 1.6 ===
+
==== Driver cannot be found ====
+
 
+
If X complains that the driver cannot be found, you may have the FBDEV driver specified in xorg.conf file, but the FBDEV driver is not installed as described in [[Poulsbo#Installing the FBDEV Xorg framebuffer driver|above]]. Revert back to "vesa" by finding the line with the video driver - fbdev - and alter it,
+
 
+
Driver "fbdev"
+
 
+
to
+
 
+
Driver "vesa"
+
 
+
Then make sure to follow the steps in the aforementioned section on installing FBDEV.
+
 
+
== Taking Advantage of non-FBDEV/VESA Driver ==
+
  
 
=== Set backlight brightness ===
 
=== Set backlight brightness ===
  
'''This has only been tested with the PSB driver'''
+
All that is needed to set the brightness is sending a number (0-100) to {{ic|/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:
 
+
''This is pertinent to machines with built-in LCD screens, not to devices such as the Fit-PC''
+
 
+
With a driver installed and loaded (via modprobe or at boot), 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.
+
 
+
An example: to set display to minimal brightness, issue this command as root:
+
  
  echo 0 > /sys/class/backlight/psb-bl/brightness
+
  # echo 0 > /sys/class/backlight/psb-bl/brightness
  
 
Or, for full luminosity:
 
Or, for full luminosity:
  
  echo 100 > /sys/class/backlight/psb-bl/brightness
+
  # echo 100 > /sys/class/backlight/psb-bl/brightness
  
 
A very short script is available to do this with less typing written by [https://bbs.archlinux.org/viewtopic.php?pid=813074#p813074 mulenmar].
 
A very short script is available to do this with less typing written by [https://bbs.archlinux.org/viewtopic.php?pid=813074#p813074 mulenmar].
Line 331: Line 174:
 
Set brightness to minimum:
 
Set brightness to minimum:
  
    ./brightness.sh 0
+
./brightness.sh 0
  
 
Set brightness to half:
 
Set brightness to half:
  
    ./brightness.sh 50
+
./brightness.sh 50
 +
 
 +
Sudo may obviously ask for your password, so you have to be in the sudoers file. A variation of this script can be found [https://bbs.archlinux.org/viewtopic.php?pid=1143245#p1143245 here].
 +
 
 +
{{Note|If changing {{ic|/sys/class/backlight/psblvds/brightness}} does not work, you may need to add {{ic|acpi_osi&#61;Linux acpi_backlight&#61;vendor}} to your [[kernel parameters]].  After rebooting, a new folder will appear under {{ic|/sys/class/backlight/}}; making changes to the {{ic|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 {{ic|/sys/class/backlight/eeepc-wmi/brightness}}.}}
 +
 
 +
=== 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 <code>mem=896mb</code> or if you have 2GB RAM use <code>mem=1920mb</code>. Add the following parameters to your bootloader's configuration file.
 +
 
 +
*[[Grub-legacy]]
 +
Edit {{ic|/boot/grub/menu.lst}}
 +
...
 +
kernel /vmlinuz-linux root=/dev/sda2 ro mem=896mb
 +
...
 +
 
 +
*[[Grub]]
 +
Edit {{ic|/etc/default/grub}}
 +
...
 +
GRUB_CMDLINE_LINUX="mem=896mb"
 +
...
  
Sudo may obviously ask for your password, so you have to be in the sudoers file.
+
*[[Syslinux]]
 +
Edit {{ic|/boot/syslinux/syslinux.cfg}}
 +
...
 +
APPEND root=/dev/sda2 ro mem=896mb
 +
...
  
 
==See also==
 
==See also==
* [http://www.kriptopolis.org/arch-linux-03#comment-66066 An experience about configuring Poulsbo (spanish)]
+
* [http://www.kriptopolis.org/arch-linux-03#comment-66066 An experience about configuring Poulsbo (Spanish)]
 +
* [https://wiki.ubuntu.com/HardwareSupportComponentsVideoCardsPoulsbo/ Ubuntu Wiki]
 +
* [http://ubuntuforums.org/showthread.php?t=1984236 Ubuntu Forums]
 +
* [http://blog.bodhizazen.net/linux/ubuntu-12-04-gma500-poulsbo-boot-options/ Ubuntu 12.04 gma500 (poulsbo) boot options (blog post)]

Revision as of 02:06, 9 January 2013

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 GMA 500 series, also known by it's codename Poulsbo or Intel System Controller Hub US15W, is a family of integrated video adapters based on the PowerVR SGX 535 graphics core. It is typically found on boards for the Atom Z processor series. Features include hardware decoding capability of up to 720p/1080i video content in various state-of-the-art codecs, e.g. H.264.

As the PowerVR SGX 535 graphics core was developed by Imagination Technologies and then licensed by Intel, 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

Modesetting driver and dual monitor Setup

To setup different resolution for external monitor using xrandr, xf86-video-modesetting from official repo is needed. If you choose to use the git package (xf86-video-modesetting-gitAUR), remember to recompile it after a new version of Xorg. 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: The above configuration file will replace the xf86-video-fbdev driver. If you want to revert back, just replace modesetting with fbdev.

Troubleshooting

Poor video performance

If you have problems playing 720p and 1080i videos, yes, that's normal while there are not accelerated XV drivers. But you can improve it up to the point of going well and smoothly for most videos (even HD ones) with these tricks:

  1. add pm-powersave false to /etc/rc.local. man pm-powersave for more info.
  2. use xf86-video-modesetting-gitAUR as indicated above.
  3. always use mplayer or any variant/gui. VLC and others are usually much more slower.
  4. substitute the normal mplayer with mplayer-minimal-svnAUR, and compile with aggressive optimizations: -march=native -fomit-frame-pointer -O3 -ffast-math'. (About makepkg)
  5. use linux-lqxAUR as it is a very good performance kernel. Edit PKGBUILD so you can do menuconfig and make sure you select your processor and remove generic optimizations for other processors. (About kernels)

Fix suspend

Old fbdev driver (default)

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 

If this also fails, you might try removing pm-utils's video resume script, so that it's not run when you resume the machine.

# cd /usr/lib/pm-utils/sleep.d
# mv 99video ~
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.

modesetting xorg driver

On some machines, when using modesetting driver the screen gets messed up with random data. Although the computer still works, you must go to a console and kill X or reboot "blindly". This is not optimal, so here is a solution:

First, see your available screens and modes running xrandr:

 # xrandr
 Screen 0: minimum 320 x 200, current 1280 x 720, maximum 2048 x 2048
 LVDS-0 connected 1280x720+0+0 222mm x 125mm
   1280x720       60.0*+
 HDMI-0 connected 1280x720+0+0 531mm x 298mm
   1920x1080      60.0 +
   1680x1050      59.9  
   1680x945       60.0  
   1400x1050      74.9     59.9  
   1600x900       60.0  
   1280x1024      75.0     60.0  
   1440x900       75.0     59.9  
   1280x960       60.0  
   1366x768       60.0  
   1360x768       60.0  
   1280x800       74.9     59.9  
   1152x864       75.0  
   1280x768       74.9     60.0  
   1280x720       60.0* 
   1024x768       75.1     70.1     60.0  
   1024x576       60.0  
   832x624        74.6  
   800x600        72.2     75.0     60.3     56.2  
   848x480        60.0  
   640x480        72.8     75.0     60.0  
   720x400        70.1

Edit or create (giving executive permissions) /etc/pm/sleep.d/99xrandr, writing the correct names and modes for your solution:

 #!/bin/sh
 #
 # turn off and on the screens so we force to clean video data
 case "$1" in
 hibernate|||suspend)
 xrandr --output LVDS-0 --off
 xrandr --output HDMI-0 --off
 ;;
 thaw|||resume)
 xrandr --output LVDS-0 --off
 xrandr --output HDMI-0 --off
 xrandr --output LVDS-0 --mode 1280x720
 /usr/local/bin/brillo-
 ;;
 *) exit $NA
 ;;
 esac

In my case, I turn off both screens, and turn on only the main screen upon awakening. Feel free to customize to your needs. On some machines, the screen turns on by default even when the system was put to sleep with the screen turned off, so you need to turn it off twice.

Note: This only works if you call pm-suspend or pm-hibernate inside X. If it is called from a daemon or a tty, it won't work.

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. A variation of this script can be found here.

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.

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