« Poulsbo update: Compiz working on F11!
NetworkManager Test Day on Thursday »

August 10th, 2009

Intel GMA500 (Poulsbo) on Fedora 11: repository (with working 3D / compiz support)

So, finally I bit the bullet and did it. I’ve set up a repository with working packages for Intel GMA500 (Poulsbo) support on Fedora 11. You can just enable the repository and install the driver and it will work.

UPDATE 2

The driver is now available in RPM Fusion. All you need to do is enable the RPM Fusion repositories – you need non-free, that’s where the driver lives – and run:

yum –enablerepo=rpmfusion-nonfree-updates-testing,updates-testing install xorg-x11-drv-psb

then reboot, and all is good. If you want to use an external display alongside the internal one, you’ll need to edit the xorg.conf file and add a Virtual line, as briefly discussed in the old text below. Otherwise, that’s really all you need to do. All installation instructions below are obsolete, though some of the tweaks discussed are still useful (like the kernel parameter for the Vaio P). I will be removing my own repository shortly and maintaining the driver only in RPM Fusion.

UPDATE 1

Since first writing this post, I’ve made several updates to the packages. Video playback acceleration is now available: see this later post for details. libdrm-poulsbo is much cleaner and installs happily alongside regular libdrm. I have just updated the main driver package with a patch which make it default to ignoring ACPI for screen detection purposes. . The package now installs a service which automatically enables the driver and configures the ‘greedy’ EXA migration heuristic rather than ‘always’, which seems to improve performance and reliability for several testers (both here and on the Ubuntu forums), so you don’t need to modify xorg.conf yourself at all unless you want to do spanning across multiple displays.

A couple of gotchas with the packages have also emerged. You need to have the RPM Fusion repository enabled before you can use this repository, it just won’t work otherwise. Depending on your exact hardware – many Poulsbo-sporting machines don’t actually support PAE – you may also need to manually install (with yum) the i586 kernel-devel package instead of the i686-PAE kernel-devel package that the dependencies may pull in. If you’re using a Sony Vaio P, you’ll want the kernel parameters ‘mem=1900MB nohz=off’ to make everything go smoothly.

END UPDATES

To install, as root:

rpm -Uvh http://adamwill.fedorapeople.org/poulsbo/i586/poulsbo-repository-release-11-1.noarch.rpm
yum install xorg-x11-drv-psb

The only thing you’ll have to do manually is set up a /etc/X11/xorg.conf file, as there’s no way I can patch X.org’s auto-detection from outside the X server package. You can just use mine if you like. It has a Screen section which sets up a framebuffer size of 3280×1050, which is what I need to have a 1680×1050 display side-by-side with the 1600×768 panel in my Vaio P; you can adjust that section to your needs, or take it out if you don’t expect to be doing any spanning with an external display. If you create your own xorg.conf, you may still need the line ‘Option “IgnoreACPI”‘ in the Device section, or you may not – I’m not entirely sure if it’s still needed with these latest versions of everything.

There’s some very horrible hackery in the libdrm-poulsbo spec to make it replace the regular libdrm without complaining, but if you don’t look at it, it won’t hurt you :) . Sources are here (of course, this is still the partly-proprietary driver liberated from Ubuntu Netbook Remix, so there’s still no sources for the ‘firmware’ or xpsb-glx parts). Let me know if you have any trouble.

This is for F11, i586 only. I don’t believe any x86-64 system has a Poulsbo chipset, and I don’t have an F10 system so I can’t easily build F10 packages any more.

Posted by adamw in Red Hat, Technical | 100 Comments »

100 Responses to “Intel GMA500 (Poulsbo) on Fedora 11: repository (with working 3D / compiz support)”

  • Adam,

    I’m wondering why isn’t this in an official Fedora repository?

    By lkundrak August 10th, 2009 at 8:42 pm

  • Yay. I will try to find some time in the next week to finally upgrade my aborted F10 beta install to F11 and use these packages to finally make my CF-U1 into something more useful than a paperweight! Much Thanks!!! :)

    By hubick August 10th, 2009 at 9:46 pm

  • Because it’s still completely dependent on proprietary code, so it can’t go in the official repos. And frankly I’m not entirely sure the redistribution situation is safe enough to even submit it for RPM Fusion.

    By adamw August 10th, 2009 at 10:30 pm

  • Nice work, I’ve been waiting for this for quite a long time, as I don’t have too much time for this..

    Thank’s a lot for this stuff. I’ll send feedback if I encounter any problems.

    By Michael M August 11th, 2009 at 12:33 am

  • I agree that adamw’s idea. If Poulsbo does not open-sourced,i believe that submitting it for RPM Fusion is the best choice. Some netbook users whose netbook is based on GMA500 are Fedora fans. They have no reason to give up Fedora due to graphic driver.

    By liangsuilong August 11th, 2009 at 10:08 am

  • I’ve checked the licenses, and it is legally safe to go in RPM Fusion (redistribution of the binary stuff is allowed). I’ve adjusted the packages to be much less baby-eating today, too – thanks to a suggestion from lkundrak to use a subdirectory for the libdrm variant. So I’ll probably submit them for RPM Fusion soon. You can update the packages from the repository, if you like. Now libdrm-poulsbo and libdrm (and their -devel packages) can all co-exist, you can have all four installed at once and stuff should work.

    By adamw August 11th, 2009 at 10:22 am

  • Nice work indeed. Thank you!
    However on a stock F11 install I get this:

    - – - – - – - – - -
    Error: Missing Dependency: /usr/bin/kmodtool is needed by package akmod-psb-4.41.1-3.fc11.i586 (poulsbo)
    Error: Missing Dependency: akmods is needed by package akmod-psb-4.41.1-3.fc11.i586 (poulsbo)
    Error: Missing Dependency: kmodtool is needed by package akmod-psb-4.41.1-3.fc11.i586 (poulsbo)
    - – - – - – - – - -

    Any ideas? I’m not familiar with Fedora unfortunately.

    By Kmt August 11th, 2009 at 1:29 pm

  • Oops! You’re quite right, I didn’t think about that. You need to have the RPM Fusion repositories enabled – http://www.rpmfusion.org/ . The kmod stuff is packaged there, not in main Fedora.

    By adamw August 11th, 2009 at 1:45 pm

  • hi im haveing many problems with this. im am curently useing a acer apire one 751h with intel gma 500 graphics and running f11. first off i am a very new to fedora……linux in genaral. when i try to get this pakage this is the error i get.

    Retrieving http://adamwill.fedorapeople.org/poulsbo/i586/poulsbo-repository-release-11-1.noarch.rpm
    error: Failed dependencies:
    rpmlib(PayloadIsXz) <= 5.2-1 is needed by poulsbo-repository-release-11-1.noarch
    i have absalutely no idea what that means. also i get this error

    Loaded plugins: fastestmirror, presto, refresh-packagekit
    Loading mirror speeds from cached hostfile
    * fedora: http://ftp.linux.ncsu.edu
    * rpmfusion-free: lordmorgul.net
    * rpmfusion-free-updates: lordmorgul.net
    * rpmfusion-nonfree: lordmorgul.net
    * rpmfusion-nonfree-updates: lordmorgul.net
    * updates: distro.ibiblio.org
    Setting up Install Process
    No package xorg-x11-drv-psb available.
    Nothing to do

    i have no idea what is causing that…. and also im not intirely sure how to edit a xorg.conf dile so if someone can walk me throuh that it would be greatly apriciated….. thanks

    ps please forgive my spelling errors my netbook is running very slowly and i figure without the driver it is hard for it to eep up with my typeing…… i asure u though all the errors i get in the termanel are corectly posted. i hope u can help me

    By samusishere August 12th, 2009 at 11:28 am

  • I’m sorry, that’s my fault, I didn’t do a clean rebuild of the repository package it seems. The second problem is caused by the first: installing the first package sets up the repository from which the other packages will come, so since the first package installation failed for you, the repository is not configured, and the packages can’t be found.

    I’ll upload a properly rebuilt copy of the package now. Try again in a few hours and it should be OK.

    By adamw August 12th, 2009 at 11:38 am

  • thank you! but as of this very moment its downloading the one you originally posted. all i needed to do was download the rpm fusion packages to get it to download…… my only problem now is that i do not know if this will succseed but if it does how do i set up a /etc/X11/xorg.conf file. if u can tell me how to do that and the download being made by yum is sucsessful then i asume all will be good……… thank you sooo much for the help….

    By samusishere August 12th, 2009 at 12:03 pm

  • ok it just finished downloading and both were succsessful but after rebooting my system and trying to enable desktop effects i was unable to do so. so now i need to know what i need to do to enable desktop effects with the new driver??

    By samusishere August 12th, 2009 at 12:26 pm

  • Thanks Adam, that did it!

    2D performance is slightly better than what I had on Ubuntu, but overall
    performance is still quite horrible (compared to Windows 7) :-( Did someone
    ever try to get Intel’s latest embedded drivers to work on Linux (IEGD 10.1)?
    It looks like it supports the GMA500 and reasonable new versions of x.org
    servers (1.5/1.6).

    http://edc.intel.com/Software/Downloads/IEGD/#compatibility

    By Kmt August 12th, 2009 at 12:40 pm

  • samusishere: you’ll need the xorg.conf file before the driver will load. Without an xorg.conf, the new driver is not being loaded, you’re still using the default ‘vesa’ fallback driver.

    All you need to do is take a copy of the xorg.conf file I linked to in the post, and put it on your system as /etc/X11/xorg.conf . Save it in your home directory, open a console, become root with ’su’, and then copy the file to /etc/X11, and you should be fine.

    kmt: I haven’t really looked at getting the IEGD stream of the driver to work. I think it’s really the same driver in a different wrapping, but I haven’t fully confirmed that yet.

    By adamw August 12th, 2009 at 1:09 pm

  • ok………. im so sorry but im really infamiler with fedora. so what im very confused on is
    1. when u say all i need to do is take a copy of the xorg.conf file u linked in the post, and put it on my system as /etc/X11/xorg.conf . Save it in my home directory, open a console, become root with ’su’, and then copy the file to /etc/X11. now how exactly do i do that…. as far as putting the copy i took from the page and putting it on my system as /etc/X11/xorg.conf. and i have no clue how to get to and save the copy to my home directory. and last once im in a termanal and loged in as root how do i get the file i need to save to the directory into /etc/X11. as i also dont know what that is or how to accsess or edit it………. im sorry but as i said before i just started using fedora comeing from windows……(very hard switch) and as u probley already know it was nothing like this and most of what you wanted or needed to do could be done via a program. i really do appricate the help as ive went to many diffrent sites and none have given me a answer.

    By samusishere August 12th, 2009 at 2:04 pm

  • Hi, I am trying to run Fedora11+poulsbo on Axiomtek eBox530 powered by an Atom 1,1GHz with 2Go RAM. Once poulsbo driver installed according to your procedure, X doesn’t start.

    I get the following errors messages in dmesg:

    psb 0000:00:02.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
    psb 0000:00:02.0: setting latency timer to 64
    [drm] psb – 5.0.1.0046
    [drm:psb_do_init] *ERROR* Debug is 0×00000000
    psb 0000:00:02.0: firmware: requesting msvdx_fw.bin
    [drm:psb_do_init] *ERROR* Gatt must be 256M aligned. This is a bug.
    set the msvdx clock to 0 in the psb_msvdx_uninit
    DRM: fill_in_dev failed
    psb 0000:00:02.0: PCI INT A disabled
    DRM: drm_get_dev failed.
    psb: probe of 0000:00:02.0 failed with error -22

    And also some errors messages in Xorg.0.log:

    (II) PSB(0): Debug: MMIO virtual address is 0xb7fa3000
    (–) PSB(0): Mapped PCI MMIO at physical address 0xfdf00000
    with size 512 kiB
    (EE) PSB(0): the stolenBase is:0×7f800000
    (–) PSB(0): Detected 8060 kiB of “stolen” memory set aside as video RAM.
    (EE) PSB(0): screnIndex is:0;fbPhys is:0×7f800000; fbsize is:0×007df000
    (–) PSB(0): Mapped graphics aperture at physical address 0×7f800000
    with size 7 MiB

    Any idea? Thanks in advance for your support.

    By fabdim August 13th, 2009 at 4:47 am

  • Not sure. What happens exactly? Does the system hang or just X won’t start and dumps you at a console? Can you pastebin the whole Xorg.0.log?

    By adamw August 13th, 2009 at 7:29 am

  • Hello!

    Hmmm. I’ve just installed a fresh F11 KDE (didn’t even run ‘yum upgrade’), added the rpmfusion and your poulsbo repos, the ‘yum install xorg-x11-drv-psb’ command finished without any errors, but the ‘psb’ kernel module didn’t appear at all (and Xorg fails to start saying it was unable to find the kernel module too).

    When I run ‘akmods’ (though i’m not sure what does this tool actually do :S ), it says:

    directories are missing:
    /usr/src/kernels/2.6.29.4-167.fc11.i586/
    /lib/modules/2.6.29.4-167.fc11.i586/build/

    But I have 2.6.29.6-217.2.3.fc11.i686.PAE instead.

    What should I do?
    I have an Acer Aspire One AO751h.

    By dergachev August 13th, 2009 at 11:24 pm

  • ah, looks like the auto-dep solver preferred the PAE kernel :/. Try manually installing the appropriate i586 kernel-devel package (you will likely have to remove the i686.PAE one).

    By adamw August 13th, 2009 at 11:33 pm

  • Thanks, it worked. I’ve installed the latest kernel.i586, ran akmods and rebooted, and was proudly met by the kdm greeting. You saved me a lot of time, thanks :)

    But kwin4 desktop effects still don’t work for me: they start with no errors, but then the desktop and all windows become black (only white windows borders are visible), though popup-menus are ok. But i’ve had the same problem on UNR 9.04 (with kubuntu-desktop installed), so it’s probably a kde problem (?)

    By dergachev August 14th, 2009 at 12:16 am

  • X doesn’t start and dumps me to a console… Here the full content of Xorg.0.log:

    X.Org X Server 1.6.1.901 (1.6.2 RC 1)
    Release Date: 2009-5-8
    X Protocol Version 11, Revision 0
    Build Operating System: Linux 2.6.18-128.1.6.el5 i686
    Current Operating System: Linux localhost.localdomain 2.6.29.4-167.fc11.i686.PAE #1 SMP Wed May 27 17:28:22 EDT 2009 i686
    Kernel command line: ro root=UUID=f7e16440-54cd-4da3-9cdb-ad3808a9c9a3 rhgb quiet
    Build Date: 18 May 2009 02:47:59PM
    Build ID: xorg-x11-server 1.6.1.901-1.fc11
    Before reporting problems, check http://wiki.x.org
    to make sure that you have the latest version.
    Markers: (–) probed, (**) from config file, (==) default setting,
    (++) from command line, (!!) notice, (II) informational,
    (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
    (==) Log file: “/var/log/Xorg.0.log”, Time: Thu Aug 13 14:31:06 2009
    (==) Using config file: “/etc/X11/xorg.conf”
    (==) No Layout section. Using the first Screen section.
    (==) No screen section available. Using defaults.
    (**) |–>Screen “Default Screen Section” (0)
    (**) | |–>Monitor “”
    (==) No device specified for screen “Default Screen Section”.
    Using the first device section listed.
    (**) | |–>Device “Videocard0″
    (==) No monitor specified for screen “Default Screen Section”.
    Using a default monitor configuration.
    (==) Automatically adding devices
    (==) Automatically enabling devices
    (==) FontPath set to:
    catalogue:/etc/X11/fontpath.d,
    built-ins
    (==) ModulePath set to “/usr/lib/xorg/modules”
    (II) Cannot locate a core pointer device.
    (II) Cannot locate a core keyboard device.
    (II) The server relies on HAL to provide the list of input devices.
    If no devices become available, reconfigure HAL or disable AllowEmptyInput.
    (II) Loader magic: 0×640
    (II) Module ABI versions:
    X.Org ANSI C Emulation: 0.4
    X.Org Video Driver: 5.0
    X.Org XInput driver : 4.0
    X.Org Server Extension : 2.0
    (II) Loader running on linux
    (–) using VT number 7

    (–) PCI:*(0@0:2:0) Intel Corporation System Controller Hub (SCH Poulsbo) Graphics Controller rev 7, Mem @ 0xfdf00000/524288, 0xd8000000/134217728, 0xfdfc0000/131072, I/O @ 0×0000ff00/8, BIOS @ 0x????????/131072
    (II) No APM support in BIOS or kernel
    (II) System resource ranges:
    [0] -1 0 0xffffffff – 0xffffffff (0×1) MX[B]
    [1] -1 0 0×000f0000 – 0×000fffff (0×10000) MX[B]
    [2] -1 0 0×000c0000 – 0×000effff (0×30000) MX[B]
    [3] -1 0 0×00000000 – 0×0009ffff (0xa0000) MX[B]
    [4] -1 0 0×0000ffff – 0×0000ffff (0×1) IX[B]
    [5] -1 0 0×00000000 – 0×00000000 (0×1) IX[B]
    (II) LoadModule: “extmod”
    (II) Loading /usr/lib/xorg/modules/extensions//libextmod.so
    (II) Module extmod: vendor=”X.Org Foundation”
    compiled for 1.6.1.901, module version = 1.0.0
    Module class: X.Org Server Extension
    ABI class: X.Org Server Extension, version 2.0
    (II) Loading extension SELinux
    (II) Loading extension MIT-SCREEN-SAVER
    (II) Loading extension XFree86-VidModeExtension
    (II) Loading extension XFree86-DGA
    (II) Loading extension DPMS
    (II) Loading extension XVideo
    (II) Loading extension XVideo-MotionCompensation
    (II) Loading extension X-Resource
    (II) LoadModule: “dbe”
    (II) Loading /usr/lib/xorg/modules/extensions//libdbe.so
    (II) Module dbe: vendor=”X.Org Foundation”
    compiled for 1.6.1.901, module version = 1.0.0
    Module class: X.Org Server Extension
    ABI class: X.Org Server Extension, version 2.0
    (II) Loading extension DOUBLE-BUFFER
    (II) LoadModule: “glx”
    (II) Loading /usr/lib/xorg/modules/extensions//libglx.so
    (II) Module glx: vendor=”X.Org Foundation”
    compiled for 1.6.1.901, module version = 1.0.0
    ABI class: X.Org Server Extension, version 2.0
    (==) AIGLX enabled
    (II) Loading extension GLX
    (II) LoadModule: “record”
    (II) Loading /usr/lib/xorg/modules/extensions//librecord.so
    (II) Module record: vendor=”X.Org Foundation”
    compiled for 1.6.1.901, module version = 1.13.0
    Module class: X.Org Server Extension
    ABI class: X.Org Server Extension, version 2.0
    (II) Loading extension RECORD
    (II) LoadModule: “dri”
    (II) Loading /usr/lib/xorg/modules/extensions//libdri.so
    (II) Module dri: vendor=”X.Org Foundation”
    compiled for 1.6.1.901, module version = 1.0.0
    ABI class: X.Org Server Extension, version 2.0
    (II) Loading extension XFree86-DRI
    (II) LoadModule: “dri2″
    (II) Loading /usr/lib/xorg/modules/extensions//libdri2.so
    (II) Module dri2: vendor=”X.Org Foundation”
    compiled for 1.6.1.901, module version = 1.0.0
    ABI class: X.Org Server Extension, version 2.0
    (II) Loading extension DRI2
    (II) LoadModule: “psb”
    (II) Loading /usr/lib/xorg/modules/drivers//psb_drv.so
    (II) Module psb: vendor=”X.Org Foundation”
    compiled for 1.6.1.901, module version = 0.29.0
    Module class: X.Org Video Driver
    ABI class: X.Org Video Driver, version 5.0
    (II) Debug: psbSetup
    (II) PSB: driver for Intel GMA500 chipsets: Intel GMA500
    (II) Primary Device is: PCI 00@00:02:0
    (WW) Falling back to old probe method for psb
    (II) Debug: psbProbe
    (WW) PSB: No matching Device section for instance (BusID PCI:0@0:0:0) found
    (–) Assigning device section with no busID to primary device
    (WW) PSB: No matching Device section for instance (BusID PCI:0@0:28:0) found
    (WW) PSB: No matching Device section for instance (BusID PCI:0@0:28:1) found
    (WW) PSB: No matching Device section for instance (BusID PCI:0@0:31:0) found
    (–) Chipset Intel GMA500 found
    (II) resource ranges after xf86ClaimFixedResources() call:
    [0] -1 0 0xffffffff – 0xffffffff (0×1) MX[B]
    [1] -1 0 0×000f0000 – 0×000fffff (0×10000) MX[B]
    [2] -1 0 0×000c0000 – 0×000effff (0×30000) MX[B]
    [3] -1 0 0×00000000 – 0×0009ffff (0xa0000) MX[B]
    [4] -1 0 0×0000ffff – 0×0000ffff (0×1) IX[B]
    [5] -1 0 0×00000000 – 0×00000000 (0×1) IX[B]
    (II) PSB(0): Debug: Allocating new device
    (II) resource ranges after probing:
    [0] -1 0 0xffffffff – 0xffffffff (0×1) MX[B]
    [1] -1 0 0×000f0000 – 0×000fffff (0×10000) MX[B]
    [2] -1 0 0×000c0000 – 0×000effff (0×30000) MX[B]
    [3] -1 0 0×00000000 – 0×0009ffff (0xa0000) MX[B]
    [4] 0 0 0×000a0000 – 0×000affff (0×10000) MS[B]
    [5] 0 0 0×000b0000 – 0×000b7fff (0×8000) MS[B]
    [6] 0 0 0×000b8000 – 0×000bffff (0×8000) MS[B]
    [7] -1 0 0×0000ffff – 0×0000ffff (0×1) IX[B]
    [8] -1 0 0×00000000 – 0×00000000 (0×1) IX[B]
    [9] 0 0 0×000003b0 – 0×000003bb (0xc) IS[B]
    [10] 0 0 0×000003c0 – 0×000003df (0×20) IS[B]
    (II) PSB(0): Debug: psbPreInit
    (II) PSB(0): psb_drv – 2.2.0.32L.0027
    (II) Loading sub module “vbe”
    (II) LoadModule: “vbe”
    (II) Loading /usr/lib/xorg/modules//libvbe.so
    (II) Module vbe: vendor=”X.Org Foundation”
    compiled for 1.6.1.901, module version = 1.1.0
    ABI class: X.Org Video Driver, version 5.0
    (II) PSB(0): Creating default Display subsection in Screen section
    “Default Screen Section” for depth/fbbpp 24/32
    (==) PSB(0): Depth 24, (–) framebuffer bpp 32
    (II) Loading sub module “fb”
    (II) LoadModule: “fb”
    (II) Loading /usr/lib/xorg/modules//libfb.so
    (II) Module fb: vendor=”X.Org Foundation”
    compiled for 1.6.1.901, module version = 1.0.0
    ABI class: X.Org ANSI C Emulation, version 0.4
    (–) PSB(0): Linear framebuffer at 0×0
    (==) PSB(0): RGB weight 888
    (==) PSB(0): Default visual is TrueColor
    (**) PSB(0): Option “IgnoreACPI”
    (==) PSB(0): Use hardware cursor.
    (**) PSB(0): Not using ACPI for LVDS detection.
    (II) Loading sub module “dri”
    (II) LoadModule: “dri”
    (II) Reloading /usr/lib/xorg/modules/extensions//libdri.so
    (II) PSB(0): Debug: psbPreinitXpsb
    (II) Loading sub module “Xpsb”
    (II) LoadModule: “Xpsb”
    (II) Loading /usr/lib/xorg/modules/drivers//Xpsb.so
    (II) Module Xpsb: vendor=”Tungsten Graphics Inc.”
    compiled for 1.6.0, module version = 0.1.0
    (II) PSB(0): Debug: psbDeviceScreenInit
    (II) PSB(0): Debug: Initializing device
    (II) Loading sub module “vgahw”
    (II) LoadModule: “vgahw”
    (II) Loading /usr/lib/xorg/modules//libvgahw.so
    (II) Module vgahw: vendor=”X.Org Foundation”
    compiled for 1.6.1.901, module version = 0.1.0
    ABI class: X.Org Video Driver, version 5.0
    (II) PSB(0): Debug: MMIO virtual address is 0xb7fa3000
    (–) PSB(0): Mapped PCI MMIO at physical address 0xfdf00000
    with size 512 kiB
    (EE) PSB(0): the stolenBase is:0×7f800000
    (–) PSB(0): Detected 8060 kiB of “stolen” memory set aside as video RAM.
    (EE) PSB(0): screnIndex is:0;fbPhys is:0×7f800000; fbsize is:0×007df000
    (–) PSB(0): Mapped graphics aperture at physical address 0×7f800000
    with size 7 MiB
    (II) PSB(0): Debug: DRM device init
    (II) PSB(0): Poulsbo MemClock 400, CoreClock 200
    (II) PSB(0): Poulsbo Latencies 540 1240 350 750
    (II) PSB(0): sku_value is 0×00800000, sku_bSDVOEnable is 1, sku_bMaxResEnableInt is 0
    (II) PSB(0): Debug: psbInitOutputs
    (II) PSB(0): Debug: psbLVDSInit
    (II) PSB(0): Output LVDS0 has no monitor section
    (II) Debug: i830_psbOutputInit
    (II) PSB(0): I2C bus “LVDSBLC_B” initialized.
    (II) PSB(0): I2C bus “LVDSDDC_C” initialized.
    (II) PSB(0): I2C device “LVDSBLC_B:BLC Control” registered at address 0×58.
    (II) PSB(0): Debug: i830_psbDDCGetModes
    (II) PSB(0): I2C device “LVDSDDC_C:E-EDID segment register” registered at address 0×60.
    (II) PSB(0): I2C device “LVDSDDC_C:ddc2″ registered at address 0xA0.
    (II) Loading sub module “int10″
    (II) LoadModule: “int10″
    (II) Loading /usr/lib/xorg/modules//libint10.so
    (II) Module int10: vendor=”X.Org Foundation”
    compiled for 1.6.1.901, module version = 1.0.0
    ABI class: X.Org Video Driver, version 5.0
    (II) PSB(0): initializing int10
    (II) PSB(0): Bad V_BIOS checksum
    (II) PSB(0): Primary V_BIOS segment is: 0xc000
    (II) PSB(0): VESA BIOS detected
    (II) PSB(0): VESA VBE Version 3.0
    (II) PSB(0): VESA VBE Total Mem: 8000 kB
    (II) PSB(0): VESA VBE OEM: Intel(r)Poulsbo Graphics Chip Accelerated VGA BIOS
    (II) PSB(0): VESA VBE OEM Software Rev: 1.0
    (II) PSB(0): VESA VBE OEM Vendor: Intel Corporation
    (II) PSB(0): VESA VBE OEM Product: Intel(r)Poulsbo Graphics Controller
    (II) PSB(0): VESA VBE OEM Product Rev: Hardware Version 0.0
    (II) PSB(0): Found panel mode in BIOS VBT tables:
    (II) PSB(0): Modeline “1024×768″x0.0 65.00 1024 1048 1184 1344 768 771 777 806 (48.4 kHz)
    (II) PSB(0): BLC Data in BIOS VBT tables: datasize=0 paneltype=2 type=0×02 pol=0×01 freq=0×00c8 minlevel=0×00 i2caddr=0×58 cmd=0xaa
    (II) PSB(0): Lid state timer is enabled!
    (II) Debug: i830_psbPtrAddToList
    (II) PSB(0): Debug: i830_psbSDVOInit
    (II) PSB(0): I2C bus “SDVOCTRL_E for SDVOB” initialized.
    (II) PSB(0): I2C device “SDVOCTRL_E for SDVOB:SDVO Controller B” registered at address 0×70.
    (II) PSB(0): I2C bus “SDVOB DDC Bus” initialized.
    (II) PSB(0): Debug: SDVO: W: 02 (i830_SDVO_CMD_GET_DEVICE_CAPS)
    (II) PSB(0): SDVO: R: 02 42 02 01 01 3D 3E 00 (Success)
    (II) PSB(0): Debug: sdvo_get_capabilities, caps.output_flags=3e
    (II) PSB(0): Debug: SDVO: W: 0B (i830_SDVO_CMD_GET_ATTACHED_DISPLAYS)
    (II) PSB(0): SDVO: R: 02 00 (Pending)
    (II) PSB(0): SDVO: R: 02 00 (Pending)
    (II) PSB(0): SDVO: R: 02 00 (Pending)
    (II) PSB(0): SDVO: R: 02 00 (Pending)
    (II) PSB(0): SDVO: R: 02 00 (Pending)
    (II) PSB(0): SDVO: R: 02 00 (Pending)
    (II) PSB(0): SDVO: R: 02 00 (Success)
    (II) PSB(0): Debug: SDVO: W: 0B (i830_SDVO_CMD_GET_ATTACHED_DISPLAYS)
    (II) PSB(0): SDVO: R: 02 00 (Pending)
    (II) PSB(0): SDVO: R: 02 00 (Pending)
    (II) PSB(0): SDVO: R: 02 00 (Pending)
    (II) PSB(0): SDVO: R: 02 00 (Pending)
    (II) PSB(0): SDVO: R: 02 00 (Pending)
    (II) PSB(0): SDVO: R: 02 00 (Pending)
    (II) PSB(0): SDVO: R: 02 00 (Success)
    (II) PSB(0): Debug: SDVO: W: 0B (i830_SDVO_CMD_GET_ATTACHED_DISPLAYS)
    (II) PSB(0): SDVO: R: 02 00 (Pending)
    (II) PSB(0): SDVO: R: 02 00 (Pending)
    (II) PSB(0): SDVO: R: 02 00 (Pending)
    (II) PSB(0): SDVO: R: 02 00 (Pending)
    (II) PSB(0): SDVO: R: 02 00 (Pending)
    (II) PSB(0): SDVO: R: 02 00 (Pending)
    (II) PSB(0): SDVO: R: 02 00 (Pending)
    (II) PSB(0): SDVO: R: 02 00 (Success)
    (II) PSB(0): Output RGB0-1 has no monitor section
    (II) PSB(0): Debug: SDVO: W: 05 02 00 (i830_SDVO_CMD_SET_ACTIVE_OUTPUTS)
    (II) PSB(0): SDVO: R: (Success)
    (II) PSB(0): Debug: SDVO: W: 10 00 (i830_SDVO_CMD_SET_TARGET_INPUT)
    (II) PSB(0): SDVO: R: (Success)
    (II) PSB(0): Debug: SDVO: W: 1D (i830_SDVO_CMD_GET_INPUT_PIXEL_CLOCK_RANGE)
    (II) PSB(0): SDVO: R: C4 09 74 40 (Success)
    (II) PSB(0): SDVO device VID/DID: 02:42.02, clock range 25.0MHz – 165.0MHz, input 1: Y, input 2: N, output 1: Y, output 2: N
    (II) Debug: i830_psbPtrAddToList
    (II) Debug: i830_psbOutputCompat
    (II) PSB(0): Debug: i830_psbOutputTypesToIndex
    (II) PSB(0): Debug: Output crtc mask is 0×00000002, compat mask is 0×00000001
    (II) PSB(0): Debug: i830_psbOutputTypesToIndex
    (II) PSB(0): Debug: Output crtc mask is 0×00000001, compat mask is 0×00000002
    (II) PSB(0): Debug: xxi830_psbInitCrtcs
    (II) PSB(0): Debug: xxi830_psbCrtcInit
    (II) PSB(0): Debug: xxi830_psbCrtcInit
    (II) Debug: i830_psbOutputEnableCrtcForAllScreens
    (II) Debug: Marking crtc 0 as available for all screens.
    (II) Debug: i830_psbOutputEnableCrtcForAllScreens
    (II) Debug: Marking crtc 1 as available for all screens.
    (II) PSB(0): Debug: psbDeviceFinishInit
    (II) Debug: Really running psbDeviceFinishInit
    (++) PSB(0): i830_psbSaveHWState
    (II) PSB(0): Debug: xxi830_psbOutputSave
    (II) PSB(0): Debug: psbLVDSSave
    (II) PSB(0): Debug: xxi830_sdvo_save
    (II) PSB(0): Debug: SDVO: W: 20 (i830_SDVO_CMD_GET_CLOCK_RATE_MULT)
    (II) PSB(0): SDVO: R: 08 (Success)
    (II) PSB(0): Current clock rate multiplier: 8
    (II) PSB(0): Debug: SDVO: W: 04 (i830_SDVO_CMD_GET_ACTIVE_OUTPUTS)
    (II) PSB(0): SDVO: R: 02 00 (Success)
    (II) PSB(0): Debug: –save_active_outputs is 2
    (II) PSB(0): Debug: SDVO: W: 10 00 (i830_SDVO_CMD_SET_TARGET_INPUT)
    (II) PSB(0): SDVO: R: (Success)
    (II) PSB(0): Debug: SDVO: W: 12 (i830_SDVO_CMD_GET_INPUT_TIMINGS_PART1)
    (II) PSB(0): SDVO: R: 10 0B D0 B4 20 90 31 10 (Success)
    (II) PSB(0): Debug: SDVO: W: 13 (i830_SDVO_CMD_GET_INPUT_TIMINGS_PART2)
    (II) PSB(0): SDVO: R: 2D 6C C2 00 1C 00 00 00 (Success)
    (II) PSB(0): Debug: SDVO: W: 11 02 00 (i830_SDVO_CMD_SET_TARGET_OUTPUT)
    (II) PSB(0): SDVO: R: (Success)
    (II) PSB(0): Debug: SDVO: W: 18 (i830_SDVO_CMD_GET_OUTPUT_TIMINGS_PART1)
    (II) PSB(0): SDVO: R: 10 0B D0 B4 20 90 31 10 (Success)
    (II) PSB(0): Debug: SDVO: W: 19 (i830_SDVO_CMD_GET_OUTPUT_TIMINGS_PART2)
    (II) PSB(0): SDVO: R: 2D 6C C2 00 1C 00 00 00 (Success)
    (II) PSB(0): Debug: SDVO: W: 06 03 00 00 00 (i830_SDVO_CMD_GET_IN_OUT_MAP)
    (II) PSB(0): SDVO: R: (Success)
    (II) PSB(0): Debug: xxi830_psbCrtcSave pipe 0.
    (II) PSB(0): Debug: xxi830_psbCrtcSave pipe 1.
    (==) PSB(0): Shadow framebuffer disabled
    (II) Loading sub module “exa”
    (II) LoadModule: “exa”
    (II) Loading /usr/lib/xorg/modules//libexa.so
    (II) Module exa: vendor=”X.Org Foundation”
    compiled for 1.6.1.901, module version = 2.5.0
    ABI class: X.Org Video Driver, version 5.0
    (==) PSB(0): Acceleration enabled
    (==) PSB(0): [EXA] Allocate 32768 kiB for EXA pixmap cache.
    (==) PSB(0): [EXA] Allocate 4 kiB for scratch memory.
    (II) Debug: i830_psbOutputAssignToScreen
    (II) PSB(0): Output “RGB0-1″ is assigned to this screen.
    (II) Debug: i830_psbOutputAssignToScreen
    (II) PSB(0): Output “LVDS0″ is assigned to this screen.
    (II) PSB(0): Searching for matching Poulsbo mode(s):
    (II) PSB(0): Debug: psbLVDSDetect 1
    (II) PSB(0): Debug: psbGetLidStatus lidState= 0
    (II) PSB(0): Debug: psbLVDSGetModes
    (II) PSB(0): EDID for output LVDS0
    (II) PSB(0): Debug: psbLVDSModeValid
    (II) PSB(0): Printing probed modes for output LVDS0
    (II) PSB(0): Modeline “1024×768″x60.0 65.00 1024 1048 1184 1344 768 771 777 806 (48.4 kHz)
    (II) PSB(0): Debug: xxi830_sdvo_detect 1
    (II) PSB(0): Debug: SDVO: W: 0E (i830_SDVO_CMD_GET_ACTIVE_HOT_PLUG)
    (II) PSB(0): SDVO: R: 00 00 (Not supported)
    (II) PSB(0): Debug: SDVO: W: 0D 01 00 (i830_SDVO_CMD_SET_ACTIVE_HOT_PLUG)
    (II) PSB(0): Debug: SDVO: W: 0E (i830_SDVO_CMD_GET_ACTIVE_HOT_PLUG)
    (II) PSB(0): Debug: xxi830_sdvo_dpms 0, active_outputs=2
    (II) PSB(0): Debug: SDVO: W: 03 (i830_SDVO_CMD_GET_TRAINED_INPUTS)
    (II) PSB(0): SDVO: R: 01 (Success)
    (II) PSB(0): Debug: SDVO: W: 05 02 00 (i830_SDVO_CMD_SET_ACTIVE_OUTPUTS)
    (II) PSB(0): SDVO: R: (Success)
    (II) PSB(0): Debug: SDVO: W: 02 (i830_SDVO_CMD_GET_DEVICE_CAPS)
    (II) PSB(0): SDVO: R: 02 42 02 01 01 3D 3E 00 (Success)
    (II) PSB(0): Debug: SDVO: W: 0B (i830_SDVO_CMD_GET_ATTACHED_DISPLAYS)
    (II) PSB(0): SDVO: R: 02 00 (Pending)
    (II) PSB(0): SDVO: R: 02 00 (Pending)
    (II) PSB(0): SDVO: R: 02 00 (Pending)
    (II) PSB(0): SDVO: R: 02 00 (Pending)
    (II) PSB(0): SDVO: R: 02 00 (Pending)
    (II) PSB(0): SDVO: R: 02 00 (Pending)
    (II) PSB(0): SDVO: R: 02 00 (Pending)
    (II) PSB(0): SDVO: R: 02 00 (Success)
    (II) PSB(0): Debug: SDVO: W: 07 02 00 00 00 (i830_SDVO_CMD_SET_IN_OUT_MAP)
    (II) PSB(0): SDVO: R: (Success)
    (II) PSB(0): Debug: get attached displays=0×2,0×0,connectedouputs=0×2
    (II) PSB(0): Debug: xxi830_sdvo_get_modes
    (II) PSB(0): Debug: SDVO_DEVICE_CRT || SDVO_DEVICE_TMDS
    (II) PSB(0): Debug: i830_psbDDCGetModes
    (II) PSB(0): I2C device “SDVOB DDC Bus:E-EDID segment register” registered at address 0×60.
    (II) PSB(0): I2C device “SDVOB DDC Bus:ddc2″ registered at address 0xA0.
    (II) PSB(0): Debug: SDVO: W: 7A 02 (i830_SDVO_CMD_SET_CONTROL_BUS_SWITCH)
    (II) PSB(0): Debug: SDVO: W: 7A 02 (i830_SDVO_CMD_SET_CONTROL_BUS_SWITCH)
    (II) PSB(0): EDID for output RGB0-1
    (II) PSB(0): Manufacturer: DEL Model: a00b Serial#: 808605011
    (II) PSB(0): Year: 2004 Week: 49
    (II) PSB(0): EDID Version: 1.3
    (II) PSB(0): Analog Display Input, Input Voltage Level: 0.700/0.700 V
    (II) PSB(0): Sync: Separate
    (II) PSB(0): Max Image Size [cm]: horiz.: 34 vert.: 27
    (II) PSB(0): Gamma: 2.20
    (II) PSB(0): DPMS capabilities: StandBy Suspend Off; RGB/Color Display
    (II) PSB(0): Default color space is primary color space
    (II) PSB(0): First detailed timing is preferred mode
    (II) PSB(0): redX: 0.640 redY: 0.340 greenX: 0.279 greenY: 0.619
    (II) PSB(0): blueX: 0.140 blueY: 0.069 whiteX: 0.310 whiteY: 0.330
    (II) PSB(0): Supported VESA Video Modes:
    (II) PSB(0): 720×400@70Hz
    (II) PSB(0): 640×480@60Hz
    (II) PSB(0): 640×480@75Hz
    (II) PSB(0): 800×600@60Hz
    (II) PSB(0): 800×600@75Hz
    (II) PSB(0): 1024×768@60Hz
    (II) PSB(0): 1024×768@75Hz
    (II) PSB(0): 1280×1024@75Hz
    (II) PSB(0): Manufacturer’s mask: 0
    (II) PSB(0): Supported Future Video Modes:
    (II) PSB(0): #0: hsize: 1152 vsize 864 refresh: 75 vid: 20337
    (II) PSB(0): #1: hsize: 1280 vsize 1024 refresh: 60 vid: 32897
    (II) PSB(0): Supported additional Video Mode:
    (II) PSB(0): clock: 108.0 MHz Image Size: 338 x 270 mm
    (II) PSB(0): h_active: 1280 h_sync: 1328 h_sync_end 1440 h_blank_end 1688 h_border: 0
    (II) PSB(0): v_active: 1024 v_sync: 1025 v_sync_end 1028 v_blanking: 1066 v_border: 0
    (II) PSB(0): Serial No: 641804C302US
    (II) PSB(0): Monitor name: DELL E173FP
    (II) PSB(0): Ranges: V min: 56 V max: 75 Hz, H min: 31 H max: 80 kHz, PixClock max 140 MHz
    (II) PSB(0): EDID (in hex):
    (II) PSB(0): 00ffffffffffff0010ac0ba053553230
    (II) PSB(0): 310e010368221b78eecaf6a357479e23
    (II) PSB(0): 114f54a54b00714f8180010101010101
    (II) PSB(0): 010101010101302a009851002a403070
    (II) PSB(0): 1300520e1100001e000000ff00363431
    (II) PSB(0): 3830344333303255530a000000fc0044
    (II) PSB(0): 454c4c204531373346500a20000000fd
    (II) PSB(0): 00384b1f500e000a20202020202000c1
    (II) PSB(0): EDID vendor “DEL”, prod id 40971
    (II) PSB(0): Debug: Try to get edid_mon
    (II) PSB(0): Debug: SDVO: W: 7A 02 (i830_SDVO_CMD_SET_CONTROL_BUS_SWITCH)
    (II) PSB(0): Debug: SDVO: W: 7A 02 (i830_SDVO_CMD_SET_CONTROL_BUS_SWITCH)
    (II) PSB(0): Debug: xxi830_sdvo_mode_valid
    (II) PSB(0): Debug: xxi830_sdvo_mode_valid
    (II) PSB(0): Debug: xxi830_sdvo_mode_valid
    (II) PSB(0): Debug: xxi830_sdvo_mode_valid
    (II) PSB(0): Debug: xxi830_sdvo_mode_valid
    (II) PSB(0): Debug: xxi830_sdvo_mode_valid
    (II) PSB(0): Debug: xxi830_sdvo_mode_valid
    (II) PSB(0): Debug: xxi830_sdvo_mode_valid
    (II) PSB(0): Debug: xxi830_sdvo_mode_valid
    (II) PSB(0): Debug: xxi830_sdvo_mode_valid
    (II) PSB(0): Debug: xxi830_sdvo_mode_valid
    (II) PSB(0): Printing probed modes for output RGB0-1
    (II) PSB(0): Modeline “1280×1024″x60.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz)
    (II) PSB(0): Modeline “1280×1024″x75.0 135.00 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync (80.0 kHz)
    (II) PSB(0): Modeline “1280×1024″x60.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz)
    (II) PSB(0): Modeline “1152×864″x75.0 108.00 1152 1216 1344 1600 864 865 868 900 +hsync +vsync (67.5 kHz)
    (II) PSB(0): Modeline “1024×768″x75.0 78.75 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.0 kHz)
    (II) PSB(0): Modeline “1024×768″x60.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz)
    (II) PSB(0): Modeline “800×600″x75.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz)
    (II) PSB(0): Modeline “800×600″x60.3 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz)
    (II) PSB(0): Modeline “640×480″x75.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz)
    (II) PSB(0): Modeline “640×480″x59.9 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz)
    (II) PSB(0): Modeline “720×400″x70.1 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz)
    (II) PSB(0): Output LVDS0 connected
    (II) PSB(0): Output RGB0-1 connected
    (II) PSB(0): Using exact sizes for initial modes
    (II) PSB(0): Output LVDS0 using initial mode 1024×768
    (II) PSB(0): Output RGB0-1 using initial mode 1024×768
    (II) Debug: i830_psbOutputDisableCrtcForOtherScreens
    (II) Debug: Grabbing crtc 0 for screen 0
    (II) Debug: i830_psbOutputDisableCrtcForOtherScreens
    (II) Debug: Grabbing crtc 1 for screen 0
    (==) PSB(0): Using gamma correction (1.0, 1.0, 1.0)
    (==) PSB(0): DPI set to (96, 96)
    (–) Depth 24 pixmap format is 32 bpp
    (II) do I need RAC? No, I don’t.
    (II) resource ranges after preInit:
    [0] -1 0 0xffffffff – 0xffffffff (0×1) MX[B]
    [1] -1 0 0×000f0000 – 0×000fffff (0×10000) MX[B]
    [2] -1 0 0×000c0000 – 0×000effff (0×30000) MX[B]
    [3] -1 0 0×00000000 – 0×0009ffff (0xa0000) MX[B]
    [4] 0 0 0×000a0000 – 0×000affff (0×10000) MS[B]
    [5] 0 0 0×000b0000 – 0×000b7fff (0×8000) MS[B]
    [6] 0 0 0×000b8000 – 0×000bffff (0×8000) MS[B]
    [7] -1 0 0×0000ffff – 0×0000ffff (0×1) IX[B]
    [8] -1 0 0×00000000 – 0×00000000 (0×1) IX[B]
    [9] 0 0 0×000003b0 – 0×000003bb (0xc) IS[B]
    [10] 0 0 0×000003c0 – 0×000003df (0×20) IS[B]
    (II) PSB(0): Debug: psbScreenInit
    (II) PSB(0): Debug: psbDRIScreenInit
    (II) PSB(0): Debug: SAREA size is 8192
    drmOpenDevice: node name is /dev/dri/card0
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: Open failed
    drmOpenDevice: node name is /dev/dri/card0
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: Open failed
    drmOpenByBusid: Searching for BusID PCI:0:2:0
    drmOpenDevice: node name is /dev/dri/card0
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: Open failed
    drmOpenByBusid: drmOpenMinor returns -19
    drmOpenDevice: node name is /dev/dri/card1
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: Open failed
    drmOpenByBusid: drmOpenMinor returns -19
    drmOpenDevice: node name is /dev/dri/card2
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: Open failed
    drmOpenByBusid: drmOpenMinor returns -19
    drmOpenDevice: node name is /dev/dri/card3
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: Open failed
    drmOpenByBusid: drmOpenMinor returns -19
    drmOpenDevice: node name is /dev/dri/card4
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: Open failed
    drmOpenByBusid: drmOpenMinor returns -19
    drmOpenDevice: node name is /dev/dri/card5
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: Open failed
    drmOpenByBusid: drmOpenMinor returns -19
    drmOpenDevice: node name is /dev/dri/card6
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: Open failed
    drmOpenByBusid: drmOpenMinor returns -19
    drmOpenDevice: node name is /dev/dri/card7
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: Open failed
    drmOpenByBusid: drmOpenMinor returns -19
    drmOpenDevice: node name is /dev/dri/card8
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: Open failed
    drmOpenByBusid: drmOpenMinor returns -19
    drmOpenDevice: node name is /dev/dri/card9
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: Open failed
    drmOpenByBusid: drmOpenMinor returns -19
    drmOpenDevice: node name is /dev/dri/card10
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: Open failed
    drmOpenByBusid: drmOpenMinor returns -19
    drmOpenDevice: node name is /dev/dri/card11
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: Open failed
    drmOpenByBusid: drmOpenMinor returns -19
    drmOpenDevice: node name is /dev/dri/card12
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: Open failed
    drmOpenByBusid: drmOpenMinor returns -19
    drmOpenDevice: node name is /dev/dri/card13
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: Open failed
    drmOpenByBusid: drmOpenMinor returns -19
    drmOpenDevice: node name is /dev/dri/card14
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: Open failed
    drmOpenByBusid: drmOpenMinor returns -19
    drmOpenDevice: node name is /dev/dri/card0
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: Open failed
    drmOpenDevice: node name is /dev/dri/card0
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: Open failed
    drmOpenDevice: node name is /dev/dri/card1
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: Open failed
    drmOpenDevice: node name is /dev/dri/card2
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: Open failed
    drmOpenDevice: node name is /dev/dri/card3
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: Open failed
    drmOpenDevice: node name is /dev/dri/card4
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: Open failed
    drmOpenDevice: node name is /dev/dri/card5
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: Open failed
    drmOpenDevice: node name is /dev/dri/card6
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: Open failed
    drmOpenDevice: node name is /dev/dri/card7
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: Open failed
    drmOpenDevice: node name is /dev/dri/card8
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: Open failed
    drmOpenDevice: node name is /dev/dri/card9
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: Open failed
    drmOpenDevice: node name is /dev/dri/card10
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: Open failed
    drmOpenDevice: node name is /dev/dri/card11
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: Open failed
    drmOpenDevice: node name is /dev/dri/card12
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: Open failed
    drmOpenDevice: node name is /dev/dri/card13
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: Open failed
    drmOpenDevice: node name is /dev/dri/card14
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: open result is -1, (No such device)
    drmOpenDevice: Open failed
    (EE) [drm] drmOpen failed.
    (EE) PSB(0): [dri] DRIScreenInit failed. Disabling DRI.
    (EE) [drm] Could not uninstall irq handler.
    (EE) PSB(0): This driver currently needs DRM to operate.

    Fatal server error:
    AddScreen/ScreenInit failed for driver 0

    Please consult the The X.Org Foundation support
    at http://wiki.x.org
    for help.
    Please also check the log file at “/var/log/Xorg.0.log” for additional information.

    By fabdim August 14th, 2009 at 12:39 am

  • dergachev: sounds like it, if you had the same problem with Ubuntu. I’ve only tried Compiz on GNOME, I don’t run KDE.

    By adamw August 14th, 2009 at 8:44 am

  • AdamW :

    First thank you so much for the rpm , they were invaluable to me. I was running Ubuntu, but prefer Fedora. I was trying to install the Intel GMA500 (Poulsbo) by importing the .deb via alien and that failed. So I was working on the source code and found this page as I was searching for answers to the error messages I was getting.

    The driver installed fine, but I suggest you add the fact that you need to enable the RPM Fusion repositories to your original post (prevents error messages).

    I had a lot of trouble with the driver , my system would lock up after 5-15 minutes and X was very slow.

    I found a fix, adding these options to /etc/X11/xorg.conf

    Under Section “Device” add

    Option "AccelMethod" "exa"
    Option "MigrationHeuristic" "greedy"
    Option "NoDDC"

    after adding those options everything is working.

    By bodhi.zazen August 14th, 2009 at 11:58 am

  • bodhi: yes, I should probably explain the RPM Fusion dep on the page, you’re right – I’ll try and get to that.

    Of your configuration, there’s no need to explicitly set the 2D acceleration to EXA, that’s what it selects automatically anyway (you can check this in /var/log/Xorg.0.log), and I don’t think NoDDC can be doing anything useful. So I suspect MigrationHeuristic is what’s helping you, and there are definitely others recommending that setting on the Ubuntu forums. I’ll have to try it here and see what happens. I don’t get regular hangs, but the system does seem to hang if I leave it closed but running for a long time, or during intensive operations.

    By adamw August 14th, 2009 at 12:06 pm

  • MigrationHeuristic certainly seems to improve performance – Firefox scrolling is noticeably smoother and Neverball runs a lot smoother too. Thanks for that tip.

    By adamw August 14th, 2009 at 12:23 pm

  • Adamw

    After finding this thread and adding MigrationHeuristic to /etc/X11/xorg.conf seems to have resolved my random display lock up. All seems to be running fine and the resolution quality is tons better.

    Ya’ll are great and keep up the great work.

    By JGendreau August 15th, 2009 at 7:15 am

  • um i think i i have it installed correctly is this how its supposed to look?

    Intel Corporation System Controller Hub (SCH Poulsbo) Graphics Controller (rev 07)

    By samusishere August 15th, 2009 at 1:18 pm

  • desktop effects are running but there not the best iss there eny way can improve performance??

    By samusishere August 15th, 2009 at 1:26 pm

  • by the way im useing kde version forgot to mention that

    By samusishere August 15th, 2009 at 1:32 pm

  • Hi can someone please tell me how I set up a /etc/X11/xorg.conf file or replace mine with Admas as I cannot see anything attached.
    Many thanks
    Garry

    By optimistique1 August 18th, 2009 at 8:48 am

  • optimistique1: that section of the post is actually a link to my xorg.conf, just click on it. It can be a bit hard to see links on this site, I set the link color to a rather dark purple. I should change it…

    By adamw August 18th, 2009 at 8:56 am

  • Thanks a lot for the great work Adam, I managed to install it pretty flawless. I just got a problem with mplayer-vaapi I do not understand. It just refuses to play big buck bunny with option “-vo vaapi”. Did anybody ever try to play this movie in 1080p h264 encoded? I just get the error message “Could nit find matching colorspace….”

    By tok August 19th, 2009 at 2:21 am

  • Hi Adam, I got the file so many thanks for that. All I need to know now is how to replace the original xorg.conf file. I have only used Ubuntu in the past and I remember that you had to run some sort of command to enable you to copy/change any system files.
    Many thanks again
    Garry

    By optimistique1 August 19th, 2009 at 5:59 am

  • tok: you need -va vaapi as well, not just -vo vaapi. So it should be mplayer-vaapi -vo vaapi -va vaapi big_bug_bunny.mkv (or whatever the file’s called). I haven’t tried that movie specifically, though. I tested on a couple of anime shows (Animal Yokocho and Dennou Coil, since you didn’t ask :>).

    By adamw August 19th, 2009 at 7:44 am

  • optimistique: type su, hit enter. it will ask for your root password. type it and hit enter (you won’t see it echo to screen, this is normal). the prompt should change from a $ to a # if you’re doing it right. now copy the file: cp /home/optimistique/Download/xorg.conf /etc/X11/xorg.conf (that’s just an example, obviously put the correct location of the file in as the second part of the command). tada, you’re done.

    By adamw August 19th, 2009 at 7:46 am

  • Cool thanks for that Adam, my main problem at the moment is trying to get Fedora 11 to boot on my Sony Vaio P. I have tried two discs both with F11 on and as soon as the automatic boot prompt finishes, I get a little white cursor flashing at the top eft of the screen and then CD stops spinning and nothing happens. I believe that you have the Sony Vaio P, how did you get it to boot on your system?

    By optimistique1 August 19th, 2009 at 9:03 am

  • By the way they are the Live CD’s, not sure if that makes any difference.

    By optimistique1 August 19th, 2009 at 9:12 am

  • optimistique1: I didn’t have to do anything special that I recall. I used a USB stick to install, not CDs, I don’t have a CD drive that can connect to the P.

    By adamw August 19th, 2009 at 9:56 am

  • Todays kernel update seems to have broken your xorg-x11-drv-psb (psb driver)

    :(

    By bodhi.zazen August 19th, 2009 at 11:10 pm

  • bodhi: shouldn’t have done. Make sure you got the matching kernel-devel in the update, and check if/why akmods failed.

    By adamw August 20th, 2009 at 7:06 am

  • OK, I got it. It just took a looooooong time for akmod to build the psb module.

    By bodhi.zazen August 20th, 2009 at 8:39 pm

  • right, yeah, surprisingly enough atom CPUs are not the speediest compilers in the world :)

    By adamw August 20th, 2009 at 11:27 pm

  • No, they are under powered, I agree with you there.

    BUT for the price, size, and intended use I am very happy with it.

    By bodhi.zazen August 21st, 2009 at 9:29 am

  • Adam, I’m looking for some help – I get a black screen after switching my x.org conf to use the psb driver and rebooting. I can still SSH into the system.

    By voltagex August 21st, 2009 at 5:12 pm

  • voltagex: then ssh in and take a look at /var/log/Xorg.0.log , look for errors (EE) and warnings (WW).

    By adamw August 21st, 2009 at 7:10 pm

  • is not working for me I get a back screen after restart. I did everything correctly I already installed fedora 11 at least 5 times today. I am tired is not working.

    By pafuin September 8th, 2009 at 3:10 pm

  • Hello Adam,
    I have been lurking this blog posting in attempts to install the psb driver for my Acer AO751.

    I have the driver downloaded however I have not been able to enable it. I copied your xorg.conf file to /etc/X11 and restarted and I still get the vesa driver. In fact the xorg.conf file was modified so that the ‘Driver “psb”‘ line now reads ‘Driver “vesa”.

    Any help would be greatly appreciated.

    Thanks alot,

    Graham

    By grahampa September 14th, 2009 at 10:23 am

  • graham: that suggests the kernel module didn’t build successfully (the psb service automatically switches back to vesa if it finds the psb kernel module isn’t present). That usually happens if you don’t have the right kernel -devel package for the running kernel installed. Make sure you have the right version of the kernel -devel package, and make sure it’s the right arch (probably i586, not i686 -PAE).

    By adamw September 14th, 2009 at 12:07 pm

  • That was it. It’s working rather well. Thanks again!
    Graham

    By grahampa September 14th, 2009 at 6:45 pm

  • Hi Adam,

    I recall I post a comment somewhere here last week but I could not find the post. My system is called “fit-PC2″ and it uses Intel US15W SCH chip with poulsbo vga chip on it. I’ve tried different kernel-built modules but always got the following warnings and errors during X startup:

    (WW) Falling back to old probe method for psb
    (WW) PSB: No matching Device section for instance (BusID PCI:0@0:0:0) found
    (WW) PSB: No matching Device section for instance (BusID PCI:0@0:28:0) found
    (WW) PSB: No matching Device section for instance (BusID PCI:0@0:28:1) found
    (WW) PSB: No matching Device section for instance (BusID PCI:0@0:31:0) found
    (II) Loading extension MIT-SCREEN-SAVER
    (EE) PSB(0): the stolenBase is:0×3f800000
    (EE) PSB(0): screnIndex is:0;fbPhys is:0×3f800000; fbsize is:0×007bf000
    (EE) PSB(0): Probe Address LVDSBLC_B Slave 0×58 failed.
    (EE) PSB(0): has_fbdev is true
    (EE) PSB(0): Probe Address LVDSBLC_B Slave 0×58 failed.
    (EE) PSB(0): Probe Address LVDSBLC_B Slave 0×58 failed.
    (EE) PSB(0): Probe Address LVDSBLC_B Slave 0×58 failed.
    (EE) PSB(0): Probe Address LVDSBLC_B Slave 0×58 failed.
    (EE) PSB(0): Probe Address LVDSBLC_B Slave 0×58 failed.
    Fatal server error:
    Couldn’t find PLL settings for mode!

    Fedora 11
    2.6.30.5-43.fc11.i586 #1 SMP Thu Aug 27 21:18:54 EDT 2009 i686 i686 i386 GNU/Linux

    # lsmod
    Module Size Used by
    vfat 8604 1
    fat 40664 1 vfat
    fuse 49412 2
    psb 133384 1
    drm 152316 1 psb
    i2c_algo_bit 4836 1 psb
    ipv6 235712 12
    dm_multipath 14040 0
    uinput 6676 0
    mmc_block 9424 2
    pcspkr 2168 0
    serio_raw 5088 0
    i2c_isch 6976 0
    sdhci_pci 6956 0
    sdhci 17392 1 sdhci_pci
    i2c_core 25024 4 psb,drm,i2c_algo_bit,i2c_isch
    mmc_core 48448 2 mmc_block,sdhci
    snd_hda_codec_realtek 193456 1
    snd_hda_intel 24164 2
    snd_hda_codec 59380 2 snd_hda_codec_realtek,snd_hda_intel
    snd_hwdep 6716 1 snd_hda_codec
    snd_pcm 62596 2 snd_hda_intel,snd_hda_codec
    r8169 28192 0
    snd_timer 17876 1 snd_pcm
    mii 4024 1 r8169
    snd 50336 10 snd_hda_codec_realtek,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_pcm,snd_timer
    soundcore 5476 1 snd
    snd_page_alloc 7712 2 snd_hda_intel,snd_pcm
    video 18732 0
    output 2476 1 video
    ata_generic 4288 0
    pata_acpi 3648 0
    pata_sch 3156 2

    Any help would be greatly appreciated.

    Teetee

    By teetee1 September 15th, 2009 at 12:32 am

  • I already replied to your comment. It’s at http://www.happyassassin.net/2009/08/28/poulsbo-update/#comments .

    By adamw September 15th, 2009 at 12:47 am

  • absolutely clean install on my acer 750 (11.6 inch), no hiccups, nothing.. but i did modify your xorg to add the ‘heuristic’ options suggested in the comments.. (attached my xorg below).

    as you suggested, also added rpm fusion repos (free and non-free were needed) and the kernel-devel.i586 package before doing anything else.. thanks. (this was done on a fresh fedora 11 install, which is not updated at all, except for the kernel which was upgraded from 2.6.29 to 2.6.30 before installation of psb.

    everything worked like clockwork and was almost disappointed that there was nothing to tinker on :-) great work adam and really appreciate this thanks a lot again, my comp works like a charm. it used to hang every ten minutes on windoze xp, the default OS.

    my xorg.conf

    Section “Device”
    Identifier “Videocard0″
    Driver “psb”
    Option “IgnoreACPI”
    Option “AccelMethod” “exa”
    Option “MigrationHeuristic” “greedy”
    Option “NoDDC”
    EndSection

    Section “Extensions”
    Option “Composite” “Enable”
    EndSection

    Section “Screen”
    Identifier “screen1″
    Device “Videocard0″
    DefaultColorDepth 24

    Subsection “Display”
    Depth 24
    Virtual 3280 1050
    EndSubsection

    Subsection “Display”
    Depth 16
    Virtual 3280 1050
    EndSubsection

    Subsection “Display”
    Depth 15
    Virtual 3280 1050
    EndSubsection

    Subsection “Display”
    Depth 8
    Virtual 3280 1050
    EndSubsection
    EndSection

    By sreejiraj September 15th, 2009 at 8:38 pm

  • also, to the noobs who are wondering how to put in place adam’s xorg.conf file

    do this:

    type ’su’ at command-line..
    enter your admin password
    then type ‘cp /complete/path/to/downloaded/adam’sxorgfile /etc/X11/xorg.conf’

    (cp is command for copy-paste, and usually the complete path to downloaded file looks like this ‘/home/userid/Documents/xorg-poulsbo’)

    By sreejiraj September 15th, 2009 at 8:42 pm

  • sreej: as I noted in the updated post, you actually don’t need to tweak xorg.conf at all with the updated versions of the packages. The driver is patched to do IgnoreACPI by default, and the psb service sets the MigrationHeuristic when it creates xorg.conf. You only need to touch xorg.conf if you need to set up the Virtual bits for using an external output, otherwise you don’t need to do anything to it at all.

    By adamw September 15th, 2009 at 9:24 pm

  • Adam,

    I’m starting to toy with porting your X-server stability improvements back to ubuntu. Is your work in public version control somewhere or should I be working from your published .srpms?

    Are all of the stability improvements localized to the kmod packages or should I be digging into other parts of your effort?

    Thanks so much!

    -Jesse

    By jesse September 23rd, 2009 at 5:07 pm

  • Work from the SRPMs for now. But there’s no special sauce – all I’ve done is enable certain tweaks that were discussed in the Ubuntu Forums thread in the package, so you don’t have to mess with configuration files yourself. All I’ve changed is two things:

    set Option “MigrationHeuristic” “greedy” in xorg.conf
    set Option “IgnoreACPI” “true” in xorg.conf (actually I just patched this in the driver, but it’s the same result, the patch is xorg-x11-drb-psb-0.31.0-ignoreacpi.patch)

    That’s all you actually need, the other options that were discussed in the thread are just noise.

    By adamw September 23rd, 2009 at 5:51 pm

  • Hi Adam, Nice work, sir! Any chance you could help me get your code running on my copy of RHEL 5.3?

    I’ve successfully followed the steps regarding EPEL, free RPM Fusion, and non-free PRM Fusion, but then:

    [root@aceratom ~]# rpm -Uvh http://adamwill.fedorapeople.org/poulsbo/i586/poulsbo-repository-release-11-1.noarch.rpm
    Retrieving http://adamwill.fedorapeople.org/poulsbo/i586/poulsbo-repository-release-11-1.noarch.rpm
    error: Failed dependencies:
    rpmlib(FileDigests) = 11 is needed by poulsbo-repository-release-11-1.noarch

    By kcshelby October 1st, 2009 at 7:15 am

  • Sorry, too verbose:

    # rpm -Uvh http:…
    error: Failed dependencies:
    rpmlib(FileDigests) = 11 is needed by poulsbo-repository-release-11-1.noarch

    By kcshelby October 1st, 2009 at 7:17 am

  • You could try rebuilding the .src.rpms, you’d probably need to do that to make it work.

    By adamw October 1st, 2009 at 8:19 am

  • I have the driver working on new install of fedora 11. I have a dell mini 10 with the upgraded display. The resolution says it is in the correct resolution ( 1366×768 ) but it is really in 1024 x 768. anything i can do to try to fix?

    By tcsnyder October 20th, 2009 at 9:33 am

  • can you post /var/log/Xorg.0.log and the output of ‘xrandr’ run at a console, somewhere like http://fpaste.org ? thanks.

    By adamw October 20th, 2009 at 9:48 am

  • here is my Xoorg .0.log http://fpaste.org/EtjL/
    and my output of xrandr
    Screen 0: minimum 320 x 200, current 1366 x 768, maximum 1366 x 1366
    LVDS0 connected 1366×768+0+0 (normal left inverted right x axis y axis) 224mm x 126mm
    1366×768 60.0*+
    SDVO-1 disconnected (normal left inverted right x axis y axis)
    You have mail in /var/spool/mail/root

    By tcsnyder October 20th, 2009 at 10:03 am

  • well gnome-ruler says i have my correct resolution. but my panels and window decoartions are very large. my panels wont let me shrink them, they are at 32 px, but they are really 64 px. i can look elsewhere because it is not a driver problem.
    Thanks for the help

    By tcsnyder October 20th, 2009 at 10:08 am

  • tcsnyder: yeah, it really looks like it’s at the correct resolution, the xrandr output and Xorg.0.log show that pretty clearly.

    I’m going to take a guess that the DPI setting has been auto-set very high. Try going to System / Preferences / Appearance / Fonts, click Details, change Resolution to 96 dots per inch. Does that change it?

    By adamw October 20th, 2009 at 10:11 am

  • your a life saver, worked like a charm

    By tcsnyder October 20th, 2009 at 10:46 am

  • no problem :)

    By adamw October 20th, 2009 at 11:02 am

  • A cry for help. The same problem as fabdim upper had:

    > [drm] Initialized drm 1.1.0 20060810
    > psb 0000:00:02.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
    > psb 0000:00:02.0: setting latency timer to 64
    > [drm] psb – 5.0.1.0046
    > [drm:psb_do_init] *ERROR* Debug is 0×00000000
    > psb 0000:00:02.0: firmware: requesting msvdx_fw.bin
    > [drm:psb_do_init] *ERROR* Gatt must be 256M aligned. This is a bug.
    > set the msvdx clock to 0 in the psb_msvdx_uninit
    > DRM: fill_in_dev failed
    > psb 0000:00:02.0: PCI INT A disabled
    > DRM: drm_get_dev failed.
    > psb: probe of 0000:00:02.0 failed with error -22

    so DRM is not able to init and X hereby unable to access /dev/dri/card[1-14]

    The device has:
    > 00:02.0 VGA compatible controller: Intel Corporation System Controller
    > Hub (SCH Poulsbo) Graphics Controller (rev 07) (prog-if 00 [VGA controller])

    What could be tuned? Or maybe the device features too old/too new/other way unusual HW…

    By vitb October 20th, 2009 at 3:17 pm

  • Hi,
    I have problems to install the poulsbo-driver from rpmfusion.
    I am using the PAE-Kernel from Fedora 11. On the active repository of rpmfusion is no akmod-psb or kmod-psb and after using of your link (yum –enablerepo=rpmfusion-nonfree-updates-testing install xorg-x11-drv-psb), I get a dependence error.

    Fehlende Abhängigkeit: kernel-uname-r = 2.6.30.9-90.fc11.i586 wird benötigt von Paket kmod-psb-2.6.30.9-90.fc11.i586-4.41.1-10.fc11.2.i586 (rpmfusion-nonfree-updates-testing)

    Is there no support for i686- and PAE-Kernel at the moment from rpmfusion?

    P.S.: Sorry for my bad english.

    Regards Thomas

    By Fanninger Thomas October 21st, 2009 at 12:10 pm

  • Oops – looks like I need to update the instructions. Try just ‘yum install xorg-x11-drv-psb’. Enabling the testing repository shouldn’t be needed any more. Looks like that’s giving you a build for a kernel that hasn’t gone out as an official update yet, which is why it won’t install.

    By adamw October 21st, 2009 at 12:22 pm

  • More info.
    upon load of
    psb.ko with debug=5 ignore_acpi=1 no_fb=1 xres=1024 yres=768,
    dmesg reports:

    > [drm] psb – 5.0.1.0046
    > [drm:psb_do_init] *ERROR* Debug is 0×00000005
    > [psb:0x01:psb_msvdx_init] MSVDX: psb_msvdx_init
    > [psb:0x01:psb_msvdx_init] Enabling clocks
    > [psb:0x01:psb_msvdx_init] MSVDX: Setting up RENDEC
    > [psb:0x01:psb_msvdx_init] MSVDX: RENDEC A: 10000000 RENDEC B: 10200000
    > [psb:0x01:psb_setup_fw] MSVDX: psb_setup_fw
    > [psb:0x01:psb_setup_fw] MSVDX: Detected Poulsbo D1 or later revision.
    > [psb:0x01:psb_setup_fw] MSVDX: RAM bank size = 4096 bytes
    > psb 0000:00:02.0: firmware: requesting msvdx_fw.bin
    > [psb:0x01:psb_setup_fw] MSVDX: Retrieved pointers for firmware
    > [psb:0x01:psb_setup_fw] MSVDX: text_size: 2841
    > [psb:0x01:psb_setup_fw] MSVDX: data_size: 1046
    > [psb:0x01:psb_setup_fw] MSVDX: data_location: 0×82882c80
    > [psb:0x01:psb_setup_fw] MSVDX: First 4 bytes of text: 0×9040c001
    > [psb:0x01:psb_setup_fw] MSVDX: First 4 bytes of data: 0×809058b0
    > [psb:0x01:psb_setup_fw] MSVDX: Uploading firmware
    > [psb:0x01:psb_upload_fw] MSVDX: Upload done
    > [psb:0x01:psb_upload_fw] MSVDX: Upload done
    > [psb:0x01:psb_setup_fw] MSVDX: MTX Initial indications OK
    > [psb:0x01:psb_setup_fw] MSVDX: MSVDX_COMMS_AREA_ADDR = 00002cc0
    > [psb:0x01:psb_setup_fw] MSVDX releasing firmware resouces….
    > [drm:psb_do_init] *ERROR* Gatt must be 256M aligned. This is a bug.
    > set the msvdx clock to 0 in the psb_msvdx_uninit
    > DRM: fill_in_dev failed
    > psb 0000:00:02.0: PCI INT A disabled
    > DRM: drm_get_dev failed.
    > psb: probe of 0000:00:02.0 failed with error -22

    So the same alignment error. Commenting out that check makes the X totally stuck. Any advice would be greatly appreciated.

    By vitb October 21st, 2009 at 12:34 pm

  • Hi,
    sorry Adam, but on RPM-Fusion (Base + Update) is no kmod-Package. so it is not possible to install the driver on a new Fedora 11 (NET-Install) installation.
    Regards Thomas

    By Fanninger Thomas October 22nd, 2009 at 6:40 am

  • thomas: damn. just use the rpmfusion -updates-testing repo, then, and install the needed kernel from fedora updates-testing:

    http://koji.fedoraproject.org/koji/buildinfo?buildID=137009

    I’ll poke rpmfusion list and see if they can straighten this out.

    By adamw October 22nd, 2009 at 8:59 am

  • I am awaiting my new Archos 9 PCtablet which has a GMA500 and of course I will try to get Linux running on it. Are there poulsbo drivers for F12 yet? Or should I try F11 first?

    By lintweaker October 23rd, 2009 at 3:20 am

  • go with F11, I don’t have F12 working yet.

    By adamw October 23rd, 2009 at 7:11 am

  • is there any way to control the backlight brightness?

    By tcsnyder October 26th, 2009 at 4:51 pm

  • tcsnyder: on my P it just works (the keyboard control keys do the job). I think it varies by hardware. IgnoreACPI may be stopping this working on some systems, but we can’t avoid that at present.

    By adamw October 26th, 2009 at 5:48 pm

  • Hi Adam,

    First of all, thanks for all your efforts here.

    I just installed F11 on a new Asus Eee PC 1101HA which has the GMA 500 chipset. Following your instructions, I installed xorg-x11-drv-psb from the Fusion repo. I haven’t changed xorg.conf.

    Unfortunately, the Eee freezes during the boot process, moments after the “Welcome to Fedora” “Starting UDEV…” lines. At the end of the xorg log there is an error message:

    Fatal server error:
    Caught signal 11. Server aborting

    The complete xorg log is here:
    http://pastebin.com/m25112782

    Any ideas what is going wrong here?

    By cbrace October 29th, 2009 at 2:37 am

  • well, that X log shows it loading the VESA driver, not psb. How did you get the log, exactly? What still works and what doesn’t?

    By adamw October 29th, 2009 at 7:24 am

  • Ahhh… did I paste the wrong log?

    After the bootup sequence froze, I rebooted with run level 1. When I got the root prompt, I copied the xorg log to my home directory.

    What works is booting with the kernel-2.6.29.4-167. During the bootup it complains that there is psb.ko, but otherwise X comes up fine, except that resolution is limited to 800×600 and obviously not accelerated.

    However, if I try to boot kernel kernel-2.6.30.9-90, for which the kmod appears to be present, the boot process freezes at the point I mention above.

    pm -qa | grep kmod
    kmod-psb-2.6.30.9-90.fc11.i586-4.41.1-10.fc11.2.i586
    kmod-psb-4.41.1-10.fc11.2.i586

    Let me know if you need any additional info.

    Thanks

    By cbrace October 29th, 2009 at 11:28 am

  • cbrace: ah, it’s failing before it ever hits X, so the X log is irrelevant (and is not _from_ the failed boot at all, it’s from the working boot with the old kernel when you were using vesa).

    Can you look at /var/log/messages and see if there are any useful messages from around the time you tried to boot 2.6.30.9-90 and it failed?

    By adamw October 29th, 2009 at 11:39 am

  • I have just realized that the Eee is not freezing during when booting the later kernel w/ the psb kmod; just that the screen goes blank.

    Just now I have rebooted it with the 2.6.30 kernel. To my surprise, I find I can ssh into it from my desktop box; all the services have come up. According to ps, gdm and X are running.

    There is nothing of interest in the system log. This time however I do have a relevant xorg log for you:
    http://pastebin.com/d5dd6e109

    As you can see in line 5, this time it is booting 2.6.30 (last time this line indicated 2.6.29… my bad)

    Any idea what is going on here?

    By cbrace October 29th, 2009 at 1:26 pm

  • # go with F11, I don’t have F12 working yet.
    # By adamw October 23rd, 2009 at 7:11 am
    OK, thanks. I just tried F12 beta (i686 live CD) and it would not go past starting udev anyway. The F11 live CD seems to be working fine. Although there is no touch screen or working mouse, but that’s another matter.

    By lintweaker October 31st, 2009 at 6:17 am

  • Just for the news. Mandrive 2010 RC2 has full support for the GMA500 from the start. It recognized and installed the driver on installation. Works with compiz like a charm

    By tcsnyder November 4th, 2009 at 2:29 pm

  • tcsnyder: indeed, I expected that, I’ve been collaborating with Olivier Blin (from Mandriva) on this stuff, he provided some of the patches we all use on psb. Great news that it all works in 2010 as expected, that’s awesome for MDV users :)

    By adamw November 4th, 2009 at 2:38 pm

  • I finally managed to get the PSB driver working on my Archos 9 tablet! Now it is running fine with a beautiful 1024×600 resolution :) Unfortunately the tablet itself is not really usable with Linux, both the mouse and touchscreen do not work…

    By lintweaker November 6th, 2009 at 3:22 am

  • tcsnyder: thanks for the tip. I downloaded the new Mandriva release and gave it a try. Alas same results; the screen just blanks out at a given moment in the boot process.

    Here is a guy who got Fedora 11 working with the pcb driver on the same model Eee PC I have:
    I wish I knew what he is doing differently.

    By cbrace November 7th, 2009 at 8:38 am

  • ahhh….. WordPress stripped the URL out. Trying again with tinyurl: http://tiny.cc/Q3xB3

    If that doesn’t work, it is a customer review of the Eee PC 1101HA at Amazon.com by a customer named Martin Stadtler.

    By cbrace November 7th, 2009 at 8:43 am

  • I have Acer AcpireOne 751 with GMA 500
    I install Fedora 12 beta on my netbook. (I try to install 11, but i can’t – setup fail)
    do with rpmfusion and poulsbo repository yum install xorg-x11-drv-psb

    Nov 07 23:35:57 Installed: kmodtool-1-18.fc11.noarch
    Nov 07 23:35:58 Installed: xpsb-glx-0.18-4.fc11.i686
    Nov 07 23:36:01 Installed: akmods-0.3.6-3.fc12.noarch
    Nov 07 23:36:01 Installed: psb-firmware-0.30-3.fc11.noarch
    Nov 07 23:36:09 Installed: xorg-x11-drv-psb-0.31.0-11.fc11.i586
    Nov 07 23:36:10 Installed: akmod-psb-4.41.1-8.fc11.i586

    When system boot with psb driver (kernel-2.6.31.5-117.fc12.i686) – error. It can’t find psb.ko file.
    see fail log:
    http://slil.ru/28174406

    Then i try to make patch:
    http://lists.rpmfusion.org/pipermail/rpmfusion-commits/2009-September/006495.html
    but when compile – next error:
    make[2]: *** Нет правила для сборки цели (no rule for compile target) `/usr/src/akmods/psb-kernel-source-4.41.1/i810_drv.o’, needed for `/usr/src/akmods/psb-kernel-source-4.41.1/drm-psb.o’.

    Where I can get i810_drv. sources to compile it? Or maybe exist already compiled psb.ko for kernel-2.6.31.5*

    By ty4a November 7th, 2009 at 1:36 pm

  • f12 is not yet supported, sorry. You need to use f11, or live with vesa.

    By adamw November 7th, 2009 at 3:34 pm

  • Poulsbo isn’t officially supported by Ubuntu 9.10, but someone has already fixed that:

    https://wiki.ubuntu.com/HardwareSupportComponentsVideoCardsPoulsbo

    I had no luck with this, but perhaps someone else will.

    By cbrace November 10th, 2009 at 12:34 am

  • Thank you for your Poulsbo driver for Fedora 11.
    Unfortunately my new Acer Aspire 751 will not reboot with the psb driver and I ask whether you could suggest a way forward.

    1 .. yum install xorg-x11-drv-psb completes perfectly
    2 .. manual edit of xorg.conf to line Driver “psb” is overwritten on reboot to Driver “vesa”
    3 .. use of your posted xorg.conf results in no driver loaded, ie terminal only
    4 .. deletion of xorg.conf results in a new autogenerated file with once again Driver “vesa”
    5 .. adding Option “IgnoreACPI” “yes” makes no difference

    I would be most grateful for your ideas

    By johnscott November 11th, 2009 at 10:27 pm

  • if the xorg.conf gets written with ‘vesa’ it means the kernel module for the psb driver is not available, Make sure you have the right kernel-devel package for your running kernel installed; see the note in the post about how sometimes yum seems to install the wrong one, and check it.

    By adamw November 11th, 2009 at 10:59 pm

  • Since my previous comment re Poulsbo driver Fedora 11 Acer Asire 751, I have stumbled upon the solution. Having installed kmodtool, akmods, psb-firmware, akmod-psb, a reboot installed the Driver “psb” perfectly.
    It has made an amazing improvement.
    Many thanks again.

    By johnscott November 11th, 2009 at 11:11 pm

  • I installed the psb driver in Fedora 11 on an Acer One (A0751h with 1366 x 768 display) without a hitch. It certainly improved the graphics performance and seemed to work well. However, my will power is weak and I have installed Fedora 12 (in part to to get the stated Atom performance improvements).

    But I don’t see a psb driver for Fedora 12 in the rpm fusion archive (I followed the instructions for enabling the archive). My guess is that you have not yet ported the psb/poulsbo/gma500 driver to F12, do you think you will?

    I suppose that if you end up building a specific kernel (one that does not support PAE) that you would build it with the Atom improvements (which would seem ideal).

    By edward.h.welbon November 22nd, 2009 at 10:37 am

  • By the way, I don’t want to come off as unappreciative of the not inconsiderable effort that you put into the port of the Poulsbo Video driver for F11. I am very glad that you did it. I only wish there was some way I could help.

    By edward.h.welbon November 22nd, 2009 at 7:27 pm

  • BTW, for Ubuntu 9.10 there is a simple tutorial over there: http://blog.ygraphix.net/2009/11/08/intel-gma500-poulsbo-on-kubuntu-9-10/

    it’s french but copiing the command line contents is enough to get trough, and it definately works!

    By pysco68 November 26th, 2009 at 10:07 pm

  • @edward i tried installing from the ‘fedora 12′ repo from adam’s site.. sadly, i didn’t make it to X on reboot :-( However, the install process didn’t report any errors, i think.. anyway, more waiting I guess.. currently on opensuse11.2 till then (the only distro, apart from mandriva, that has working poulsbo on its latest version?)

    By sreejiraj December 1st, 2009 at 6:31 am

  • Nah, Ubuntu does too. Actually, most distros will, Fedora 12 is one of very few where it _can’t_ work. The difference is simply X server version; F12 went to X server 1.7 while most releases this round stuck with 1.6. The problem is the psb driver does not work with server 1.7.

    By adamw December 1st, 2009 at 6:50 am

  • [...] people. Over the three days of the conference, I must have talked to at least 20 people about Poulsbo. It’s a very hot topic, and it’s only going to get hotter. The theme is still one of [...]

    By AdamW on Linux and more » Blog Archive » FUDCon Toronto 2009 wrap-up December 10th, 2009 at 12:25 am

  • for VLC player must go to tools–>preferences –>video in output chose X11 video output and play video

    By dglaros August 10th, 2010 at 2:23 pm

Leave a Reply