Difference between revisions of "Intel GMA 500"

From ArchWiki
Jump to: navigation, search
(Warning about Xorg 1.13)
(Old fbdev driver (default))
(21 intermediate revisions by 6 users not shown)
Line 2: Line 2:
 
[[Category:X Server]]
 
[[Category:X Server]]
 
[[el:Poulsbo]]
 
[[el:Poulsbo]]
 +
[[it:Poulsbo]]
 
[[ru: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}}
Line 13: Line 14:
 
{{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 opensource [[Intel]] drivers do not work with this hardware.  
+
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.
Line 44: Line 45:
 
  i2c_core              16653  5 drm,drm_kms_helper,i2c_algo_bit,gma500_gfx,videodev
 
  i2c_core              16653  5 drm,drm_kms_helper,i2c_algo_bit,gma500_gfx,videodev
  
== Dual Monitor Setup ==
+
== Modesetting driver and dual monitor Setup ==
To setup different resolution for external monitor using [https://wiki.archlinux.org/index.php/Xrandr xrandr], {{AUR| xf86-video-modesetting-git}} from [[AUR]] is needed. This will replace the {{Pkg|xf86-video-fbdev}} driver.
+
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:
 
+
After installing, an [[Xorg]] file is needed to setup the driver. Use this for device section:
+
  
 
{{hc|/etc/X11/xorg.conf.d/20-gpudriver.conf|
 
{{hc|/etc/X11/xorg.conf.d/20-gpudriver.conf|
Line 56: Line 55:
 
  EndSection
 
  EndSection
 
}}
 
}}
{{Note|1= There have been some [https://bbs.archlinux.org/viewtopic.php?pid=1143717#p1143717 reports] that modesetting causes some anomalies on the screen. Latest git snapshot fixes that.}}
+
{{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}}.}}
{{Note|1= Modesetting doesn't work on latest Xorg server 1.13 as reported on [https://bbs.archlinux.org/viewtopic.php?pid=1170096#p1170096 forum].}}
+
  
 
== Troubleshooting ==
 
== 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:
 +
 +
# 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]])
  
 
=== Fix suspend ===
 
=== 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 {{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.
 
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.
Line 76: Line 85:
  
 
  # pm-suspend -quirk-vbemode-restore  
 
  # 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.}}
 
{{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 {{ic|xrandr}}:
 +
 +
{{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
 +
}}
 +
 +
Edit or create (giving executive permissions) {{ic|/etc/pm/sleep.d/99xrandr}}, writing the correct names and modes for your solution:
 +
 +
{{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>}}
 +
 +
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 {{ic|pm-suspend}} or {{ic|pm-hibernate}} inside [[X]]. If it is called from a daemon or a tty, it won't work.}}
  
 
=== Set backlight brightness ===
 
=== Set backlight brightness ===
Line 104: Line 180:
 
  ./brightness.sh 50
 
  ./brightness.sh 50
  
Sudo may obviously ask for your password, so you have to be in the sudoers file.
+
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}}.}}
 
{{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}}.}}
 
A variation of this script can be found [https://bbs.archlinux.org/viewtopic.php?pid=1143245#p1143245 here].
 
  
 
=== Memory allocation optimization ===
 
=== Memory allocation optimization ===
Line 133: Line 207:
  
 
==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]
 
* [https://wiki.ubuntu.com/HardwareSupportComponentsVideoCardsPoulsbo/ Ubuntu Wiki]
 
* [http://ubuntuforums.org/showthread.php?t=1984236 Ubuntu Forums]
 
* [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)]
 
* [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