« And now for something completely different…
The success of Ubuntu »

July 19th, 2010

Poulsbo (GMA 500) driver in RPM Fusion repository for Fedora 13

So, I finally did it – I’ve uploaded a mostly working driver for the Intel Poulsbo (GMA 500) graphics chipset to the RPM Fusion repository for Fedora 13. As of right now, it’s in non-free updates-testing; it’ll be moved to the main updates repo at some point. To install it, set up RPM Fusion repos according to the instructions, then run this command:

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

You may also want to do this (it’ll make it work even when a new kernel comes out and Fusion doesn’t yet have a kmod-psb package for it):

yum –enablerepo=rpmfusion-nonfree-updates-testing install akmod-psb

Then just reboot, and usually it should work. Remember, you can get an mplayer build with video playback acceleration support which will let you play HD videos smoothly from my video-experimental repo: details in this post.

If you have trouble, check what kernel -devel package(s) is/are installed. 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 it works, but 3D acceleration and VA-API support don’t seem to be working, check the permissions on /dev/dri/card0; they should be 666 (rw-rw-rw-). If not, add this section to /etc/X11/xorg.conf:

Section “DRI”
Mode 0666
EndSection

Here’s some system-specific tweaks:

If you want to have an external monitor side-by-side with the laptop display, you’ll want to add a Screen section to /etc/X11/xorg.conf that looks much like the one in this file. You need to combine the dimensions of the displays you’ll have connected appropriately. For instance, I have a 1600×768 panel in my laptop and the external monitor would be a 1680×1050 screen, which would be to the right of the laptop panel. So I add together the horizontal dimensions – 1600+1680 = 3280 – and use the tallest single vertical dimension – 1050 – and wind up with a size of 3280×1050. That’s what I put in the ‘Virtual’ lines in the Display section. If your laptop display was 1024×768 and your external monitor 1280×1024, you’d do 2304×1024, and so on. Then you can configure the displays with gnome-display-properties or krandrtray or xrandr once X starts up.

If you’re using a Sony Vaio P (first generation), you’ll want the kernel parameters ‘mem=1900MB nohz=off’ to make everything work smoothly (this is nothing to do with the Poulsbo chipset, just other quirks of the Vaio P; I’m not sure if they’re needed on the second-gen P).

In case you’re someone who reads my blog but uses another distro, the driver is still packaged in Mandriva and should work out-of-the-box on 2010 and 2010 Spring (you may need to install additional packages from non-free to get 3D and video playback acceleration support, I’m not entirely sure, and I’m not sure how well it works on 2010 Spring). Ubuntu users will want to see this Wiki page and the recent pages of this forum thread for instructions and info. I’m not sure about other distros – do feel free to add info in the comments.

Note that this is entirely something I do in my spare time, and is not an official Red Hat project of any kind. Nothing to do with it is in any way representative of, or endorsed or supported by, Red Hat or the Fedora project.

Edit: I totally forgot to include credits in this post, very rude of me! I’m sorry. Thanks go to Olivier Blin at Mandriva, who did a lot of the work of porting the driver to work with X server 1.7 and later, and to the Ubuntu poulsbo community who did some more work, particularly Yves de Muyter who solved some thorny issues with EXA support. I really just packaged up the stuff other people have made for Fedora. :)

Posted by adamw in Mandriva, Personal, Red Hat, Technical | 103 Comments »

103 Responses to “Poulsbo (GMA 500) driver in RPM Fusion repository for Fedora 13”

  • Awesome, I can finally upgrade my mini 10 to F13 safely :)

    By Cosmin Deaconu July 19th, 2010 at 5:08 pm

  • Sweet

    By Randy July 19th, 2010 at 8:11 pm

  • This driver is brilliant.
    I don’t know what is going on with your machine, but I’ve got both 3D and vaapi working here on my T91-MT — did literally NOTHING from a stock install of F13 except add in the fusion repo and install the drivers.

    By DH July 20th, 2010 at 6:11 am

  • Adam, you are awesome! Now i can use my Eee 1201HA without pain. You did a great job, thank you very much!

    Also thanks to Yves and all other guys which names i don’t know who worked on this driver, Xorg patches, whatever directly or indirectly.

    This news is amazing. Thank you again!

    By sindikat July 20th, 2010 at 6:57 am

  • well, uh, I hate you! =)

    damnit. Now I have to figure out why the hell it doesn’t work for me…

    By adamw July 20th, 2010 at 7:02 am

  • Just a wild guess, but since you had your initial problem with 3d/vaapi failing, have you tried wiping the machine and installing F13 fresh? You could just have something incorrect stuck in a strange place.

    By DH July 20th, 2010 at 7:17 am

  • yeah, that’s what I think, but I’ve been trying to avoid that, I hate reinstalling. I may have to, though.

    By adamw July 20th, 2010 at 7:27 am

  • What do you get when you “strace glxinfo”?

    By DH July 20th, 2010 at 8:04 am

  • dh: http://fpaste.org/xza9/

    By adamw July 20th, 2010 at 8:14 am

  • Ooh. I see permissions denied on /dev/dri stuff. That could explain it, I guess. I’ll try that 666 thing…

    By adamw July 20th, 2010 at 8:15 am

  • yep – it’s just the permissions. I wonder why they didn’t come up right for me, though? Oh well, now I know what it is at least! Yay.

    By adamw July 20th, 2010 at 8:18 am

  • Nice ;)

    By DH July 20th, 2010 at 8:31 am

  • dh: does compiz work for you? I get a missing GLX extension error, even with the 3D acceleration working…

    By adamw July 20th, 2010 at 8:44 am

  • Nope, and from what I understand about it, it simply can’t work without that extension, and that extension is obviously within the “blob” part of the psb driver, so our only option is to see if intel can pull their knife out of their back.

    Did older versions of compiz work on psb?

    By DH July 20th, 2010 at 9:04 am

  • it worked in F11, yeah. Maybe I can do a build of an older compiz or something.

    By adamw July 20th, 2010 at 9:36 am

  • Try this:
    LIBGL_ALWAYS_INDIRECT=true compiz –replace

    I would try myself, but mine is busy compiling a kernel — the touchscreen driver first appears in 2.6.34, and the psb module won’t build with 2.6.35.

    By DH July 20th, 2010 at 9:46 am

  • Also, I think that the compiz packages from F11 would probably work on F13 without rebuilding.

    By DH July 20th, 2010 at 9:47 am

  • According to this: http://forum.compiz.org/viewtopic.php?f=124&t=10402

    The 0.9 branch with the “copytex” plugin doesn’t use the TFP extension any more.

    By DH July 20th, 2010 at 10:01 am

  • Section “DRI”
    Mode 0666
    EndSection

    Think that would help with the dri permissions?

    By DH July 20th, 2010 at 10:16 am

  • Holy crap.

    http://www.happyassassin.net/2010/05/21/video-acceleration-and-poulsbo-news/#comment-1690

    And your response…..

    By DH July 20th, 2010 at 10:20 am

  • yeah, that’s what I just added. I never did get around to trying it at that time. It does the job. Doesn’t explain why I need it and you don’t, but oh well.

    By adamw July 20th, 2010 at 10:40 am

  • I’ll look at that compiz branch, thanks.

    By adamw July 20th, 2010 at 10:41 am

  • [...] cards (GeForce 8xxx and later) using the proprietary driver, Intel Poulsbo (GMA 500) adapters using my driver packages for Fedora 13, S3 Chrome 530 GT and S3 Chrome 540 GTX adapters using S3’s own driver, and Intel i965 and [...]

    By AdamW on Linux and more » Blog Archive » Mplayer (VA-API, VDPAU, ffmpeg-mt) experimental build repository for Fedora 11, Rawhide July 20th, 2010 at 12:44 pm

  • Thank you, Thank you, Thank you! To everyone who made this possible.

    By Woogie July 20th, 2010 at 5:43 pm

  • Thank you so much for this.

    By Cody Smith July 20th, 2010 at 8:32 pm

  • You think you could add this patch to the kmod source: https://patchwork.kernel.org/patch/90678/

    ??

    This makes it work with 2.6.34 which is the first version that comes with several multitouch drivers, including mosart, which is required for t91mt, and probably some other poulsbo devices.

    By DH July 21st, 2010 at 7:13 am

  • Just wanted to add my thanks to Adam and everyone else that helped put this driver together. I can finally use F13 on my Sony P without feeling like it’s 1990 :)

    At the moment, I’m just using gnome, has anyone successfully gotten compiz running?

    By abyss July 21st, 2010 at 8:46 am

  • compiz is known not to work due to a missing GL extension (GLX_EXT_TEXTURE_FROM_PIXMAP or something similar). dh mentioned that the 0.9 branch doesn’t use that extension any more, I’m currently building that branch to see if it’ll work…

    By adamw July 21st, 2010 at 9:10 am

  • Compiz will….. run…. if you don’t mind losing your window decorations. ;)

    Just launch compiz with “–indirect-rendering”.

    Its not fun though….

    By DH July 21st, 2010 at 9:15 am

  • um, if you’re running compiz manually, you have to run gtk-window-decorator manually too, don’t you?

    By adamw July 21st, 2010 at 3:35 pm

  • I built compiz 0.9.0 for kicks. You can run compiz –replace and it works. Then you can run gtk-window-decorator and watch X crash instantly. At least, that’s how it goes for me.

    Then I put compiz 0.8.6 back, and it behaves the same, with DH’s workaround. Run compiz –indirect-rendering –replace , and it works. Run gtk-window-decorator, and X instantly falls over.

    Can’t figure a way to trace it. The compiz .src.rpm is at http://www.happyassassin.net/extras/compiz-0.9.0-1.fc13.src.rpm if anyone’s interested.

    By adamw July 21st, 2010 at 3:42 pm

  • Yeah, I was seeing that too with the gtk-window-decorator. Also tried emerald — same thing.

    By DH July 22nd, 2010 at 4:30 am

  • gtk-window-decorator is reporting a fatal io error….
    the xorg backtrace is saying something about psb_drv.so/libexa.so…… exa? Wonder if its a bug in Yves’ exa mixed patch….? Perhaps reverting that patch would fix it….

    This is the backtrace I’m getting from X:
    http://pastebin.com/YPT3q8ci

    By DH July 22nd, 2010 at 4:49 am

  • Well scratch that idea… does the exact same thing with exa classic.

    By DH July 22nd, 2010 at 5:07 am

  • Oooooh sweetness….
    I’ve got the touchscreen driver working now with kernel 2.6.34 — slightly modified and custom built and with a custom xorg-x11-drv-evdev.

    If anybody’s got an ASUS T91-MT ( — note: not applicable to regular T91, just the “MT” ) interested in doing this, here’s how to do it:
    1) Grab a kernel SRPM 2.6.34 (one market with a CHECK) for F13 from koji: http://koji.fedoraproject.org/koji/packageinfo?packageID=8 — I used the 2.6.34.1-20

    ** important: **NOT** 2.6.35, unless you’re a half decent kernel hacker interested in patching up the psb kmod to be compatible.
    2) Install said kernel source.
    3) Apply the two changes to the kernel as suggested here: http://newyork.ubuntuforums.org/showpost.php?p=9447113&postcount=1
    ** don’t know why, but the T91MT touchscreen driver, though part of the kernel, is BLACKLISTED by default… not going to work like that DUH!
    4) Build and install kernel.
    5) Get source for the psb kmod from rpmfusion and apply this patch: https://patchwork.kernel.org/patch/90678/

    ** this patch makes the psb kmod compatible with 2.6.34

    6) build and install kmod/akmod.

    By DH July 22nd, 2010 at 5:59 am

  • Ok, got the touchscreen drivers working now… which is great.
    Looking currently at the infamous xrandr-makes-screen-black and only way out is to hold the power button until it dies. There is something about it doing that in the ubuntu forum, and there is apparently a fix for it, just having a bit of hard time figuring out what exactly it is…..

    By DH July 22nd, 2010 at 6:43 am

  • nm… found it here: http://code.google.com/p/gma500/issues/detail?id=23&can=1

    By DH July 22nd, 2010 at 6:45 am

  • Beautiful.
    This thing is now just about working exactly the way I always wanted it to work. Now I just need to wire in xrandr+pointer rotate to the rotate button and it’ll be all set.

    So… summary of the adventures — very applicable to anyone with a convertible psb tablet, especially a T91-MT….

    Two patches needed over Adam’s source…
    1) https://patchwork.kernel.org/patch/90678/
    * compatibility with kernel 2.6.34
    2) http://code.google.com/p/gma500/issues/detail?id=23&can=1
    * rotation

    Kernel SRPM 2.6.34 from koji, needs a couple of things that you can find here prior to build and install:
    http://newyork.ubuntuforums.org/showthread.php?t=1507489

    And then of course you’re going to need a couple of extras for running in tablet mode….
    1) gok (on-screen keyboard).
    2) simulated secondary click (find in mouse presses)… note that for the touchscreen, it does NOT work by just holding your finger on the screen, you need to tap-hold.

    By DH July 22nd, 2010 at 7:14 am

  • Doesn’t appear to be any event or key code generated by the rotate button, so just added a little button on the gnome-panel to run a rotate script.

    This is the script:

    #!/bin/bash
    ROTATION=`xrandr -q | grep “LVDS0″ | cut -d\ -f4`
    INPUT=`xinput –list | grep “Asus” | head -n1 | cut -d\= -f2 | cut -c1`

    case $ROTATION in
    left) xrandr –screen 0 -o normal
    xinput –set-int-prop $INPUT “Evdev Axes Swap” 8 0
    xinput –set-int-prop $INPUT “Evdev Axis Inversion” 8 0 0;;
    *) xrandr –screen 0 -o left
    xinput –set-int-prop $INPUT “Evdev Axes Swap” 8 1
    xinput –set-int-prop $INPUT “Evdev Axis Inversion” 8 1 0;;
    esac

    This gives two rotation modes: normal and left. If one wanted, they could do an upside-down or right, but I see no need for those modes.

    Also note: the synaptics touchpad doesn’t rotate with this, but if you’re in tablet mode (left), the synaptics pad is inaccessible anyway.

    Time to shut this thing down — going to image it tonight so that I have a good backup for when I surely mess it all up and want to go back.

    By DH July 22nd, 2010 at 8:40 am

  • Thanks Adam.

    Everything works fine on my Dell Mini 12 but video playback. I just got sound but no video image.

    Greets
    Marcus

    By Marcus July 22nd, 2010 at 10:27 am

  • marcus: try grabbing the mplayer from http://www.happyassassin.net/2009/09/03/mplayer-va-api-vdpau-ffmpeg-mt-experimental-build-repository-for-fedora-11-rawhide/ and using that. It should give you much better playback than xv anyway, it uses the GMA 500′s hardware acceleration. I can play 720p video smoothly and even some 1080p is just about OK. (Tip: you may want to adjust PulseAudio’s resampling settings in /etc/pulse/daemon.conf ; the Atom CPUs are so weak that they can actually get maxed out just resampling some audio using Pulse’s default method).

    By adamw July 22nd, 2010 at 11:00 am

  • nice, DH. I’ll try and push an updated build with those patches today or tomorrow.

    By adamw July 22nd, 2010 at 11:00 am

  • mplayer-accelerated works fine :)

    Greets
    Marcus

    By Marcus July 22nd, 2010 at 11:19 am

  • dh: I just pushed psb-kmod and xorg-x11-drv-psb builds with those patches included, should show up in Fusion in a couple of days.

    By adamw July 22nd, 2010 at 1:33 pm

  • my brain off or….
    i have follow install instruction for PSB driver but….yum dont see nothing.

    1) yum –enablerepo=rpmfusion-nonfree-updates-testing install xorg-x11-drv-psb ERROR

    2) yum -–enablerepo=rpmfusion-nonfree-updates-testing install xorg-x11-drv-psb NO PACKAGE – or similar …sorry for english

    By olmo July 24th, 2010 at 7:52 am

  • have installed this on a fresh fedora13 install on a dell mini10(1010). installed adobe flash into firefox. youtube videos play in the browser frame just fine but full screen goes all white (the browser comes back if I hit escape)

    I did the DRI mode thing in /etc/X11/xorg.conf (the permissions were wrong, but this didn’t change much).

    any other clues?

    By John Pierce July 24th, 2010 at 11:29 am

  • Yeah, don’t expect a bug-free experience…. particularly when dealing with flash.

    By DH July 26th, 2010 at 4:20 am

  • Hi guys, i have an Acer ao751h and tried to install the poulsbo driver but it did not work… I did the following:
    1- A fresh install of fedora 13;
    2- $ su -c ‘yum update’
    3- $ su -c ‘yum localinstall –nogpgcheck http://download1.rpmfusion.org/free/fedora/rpmfusion-free-release-stable.noarch.rpm http://download1.rpmfusion.org/nonfree/fedora/rpmfusion-nonfree-release-stable.noarch.rpm‘
    4- $ su -c ‘yum update’ (again)
    5- $ su -c ‘yum –enablerepo=rpmfusion-nonfree-updates-testing install xorg-x11-drv-psb’

    The problem is that the last command did nothing, i tried “yum search psb” and only found the gpsbabel.i686 package. First i thought that the rpmfusion was not installed but i searched for the realcrypt package (a non free package) and i found it.

    Did i missed something?

    Thanks in advance!

    *sorry for my “engrish”, i am not that good at it…

    By stm82s July 26th, 2010 at 5:16 pm

  • you may have got a bad mirror. You can try editing the /etc/yum.repos.d file for rpmfusion repos and changing from the mirror list URL to the direct link to the main server instead (you just uncomment one line and comment out another).

    By adamw July 26th, 2010 at 5:55 pm

  • Dear Adam,

    I have a sony vaio p “first Generation” and i would be geatful if you can write a detailed step by step on how to change the mem=1900 mb nohz etc. in fedora 13.

    I am a linux newbie and hence would really appreciate your help.

    many thanks for your great work…

    By Khalid July 27th, 2010 at 2:30 am

  • Typically, running a “yum clean all” will eradicate any kind of preference for a particular mirror that may be cached by yum. It’ll probably work the second time if you do that.

    By DH July 27th, 2010 at 4:39 am

  • Hi Adam et al.,

    Excellent work, thank you so much!

    A couple of comments:

    (1) I had to add the same kernel parameters to make it work on my VAIO X.

    (2) It looks like there is an inconsistency in Adam’s video-experimental repo configuration: when yum looks for dependencies for mplayer-accelerated, it wants an older version of libva which is not there. However, I install the current libva rpm by hand, “yum install mplayer-accelerated” works fine. I can now play videos with smplayer with mplayer-accelerated as the backend.

    However, there is still no video in skype. Any chance of having a fix or workaround for that?

    Thanks again!

    By Dennis July 27th, 2010 at 6:19 am

  • It kind of works here, but it’s far from being perfect. In particular, both Firefox and Thunderbird have major display troubles: the widgets are fine, but main document (web page, or email body) are either not always refreshed or not even displayed. Tried both with and without compositing and it’s the same. Anyone has an idea where it comes from?

    Otherwise, video doesn’t work via xv, and although (for the first time!) vaapi works, the subtitles in mplayer are garbled, so it prevents to watch foreign movies :-(

    I haven’t dared trying to plug in my external screen via HDMI yet, as it has always crashed with xserver 1.7. Anyone has good experience with HDMI external output?

    By Eric Piel July 27th, 2010 at 2:32 pm

  • Finally I dared plugging in my HDMI screen: it crashed instantaneously :-S

    By Eric Piel July 27th, 2010 at 2:44 pm

  • Hello Adam and DH, unfortunately it is stil not working.
    First i tried the “yum clean all” followed by “yum update” and “yum search psb” commands but nothing changed. Then i looked for the file /etc/yum.repos.d/rpmfusion-nonfree.repo . The original file was like this:
    [rpmfusion-nonfree]
    name=RPM Fusion for Fedora $releasever – Nonfree
    #baseurl=http://download1.rpmfusion.org/nonfree/fedora/releases/$releasever/Everything/$basearch/os/
    mirrorlist=http://mirrors.rpmfusion.org/mirrorlist?repo=nonfree-fedora-$releasever&arch=$basearch
    enabled=1
    metadata_expire=7d
    gpgcheck=1
    gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-rpmfusion-nonfree-fedora-$releasever-$basearch

    And after the modification:
    [rpmfusion-nonfree]
    name=RPM Fusion for Fedora $releasever – Nonfree
    baseurl=http://download1.rpmfusion.org/nonfree/fedora/releases/$releasever/Everything/$basearch/os/
    #mirrorlist=http://mirrors.rpmfusion.org/mirrorlist?repo=nonfree-fedora-$releasever&arch=$basearch
    enabled=1
    metadata_expire=7d
    gpgcheck=1
    gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-rpmfusion-nonfree-fedora-$releasever-$basearch

    I changed the # of the three “sections” (rpmfusion-nonfree, rpmfusion-nonfree-debuginfo and rpmfusion-nonfree-source) and after that another “yum update” and “yum search psb”.

    I also made a fresh install of fedora 13 on a virtual machine and had the same problem. Any ideas?

    Sorry for the long message…

    By stm82s July 27th, 2010 at 3:31 pm

  • eric: i don’t have any problem with FF (running 4.0 beta 1 from upstream), haven’t tried Thunderbird (I use Evo). Xv borkage is known, Yves is trying to fix that. I’ve reported the problem with softsubs and vaapi to Gwenole before, it seems to be psb-specific – I tested with NVIDIA via vdpau-video and it doesn’t have that problem…

    By adamw July 27th, 2010 at 9:10 pm

  • Oh! It works fine with the upstream version! So this means it’s probably due to a difference in the compilation between the mandriva package and the upstream package… Not sure where is the bug, but probably more in the xserver or psb driver than the graphic library :-S

    Ah, I’ve also noticed that launching the tracker search window, crashes the server (with a backtrace in libexa + the psb driver). Maybe upgrading to something newer than xserver 1.7 will help. Getting nostalgic of 1.6, where everything worked so fine !

    By Eric Piel July 27th, 2010 at 11:52 pm

  • @stm82s:
    Not “rpmfusion-nonfree”…. “rpmfusion-nonfree-updates-testing”.

    You need to run “yum –enablerepo=rpmfusion-nonfree-updates-testing install xorg-x11-drv-psb”

    And note: the long dash before the “enablerepo” is actually TWO dashes — this forum software likes to mess with the characters.

    *** You *MUST* be running FEDORA *13* 32BIT.

    By DH July 28th, 2010 at 4:52 am

  • Again , Can anyone who own a sony vaio P , write a step by step instructions on how to change the “1900 mb = nohz etc. ”

    I would be really greatful.

    thanks all..

    By Khalid July 28th, 2010 at 5:59 am

  • Doesn’t matter if one owns that particular model — same for any. You append the stuff to the end of your kernel arguments.

    And before you do, you might want to look at the line to add better first, adding what you’ve got listed there won’t work.

    By DH July 28th, 2010 at 6:52 am

  • khalid: go to a console, do:

    su
    (enter your password)
    gedit /boot/grub/menu.lst

    the file /boot/grub/menu.lst will open up in a gedit window. On every line that starts with the word ‘kernel’, add the parameters to the end: mem=1900MB nohz=off

    Save the file, quit gedit. You’re done.

    By adamw July 28th, 2010 at 8:10 am

  • Dear DH,
    Thanks for your reply. I am not experienced enough to get into the kernel parameters and edit that bit of information.

    hence, i would be thankful if someone can take me through it step by step.

    thanks

    By Khalid July 28th, 2010 at 8:11 am

  • Adam posted it right above you.

    Note that this is basic stuff…. and is your friend and would definitely yield you the answer…. i.e. a search for “modify kernel argument fedora” would have gotten you the answer in the first result. When you don’t know something, don’t be afraid to search for it.

    By DH July 28th, 2010 at 9:03 am

  • I guess that angle brackets are read as html tags and get removed.. presumably for security. “and is your friend” should have read “and {insert your favorite search engine here} is your friend”

    By DH July 28th, 2010 at 9:05 am

  • DH i changed the file rpmfusion-nonfree-updates-testing to the main server and it worked! Yum found the package but could not install because of the PAE kernel. Following the guide of this page i looked for a i586 kernel but could not find one. Then i installed the regular i686 kernel and still could not install because yum asked for the 2.6.33.6-147.2.4 kernel and i only found the 2.6.33.6-147 version (the regular one). I change all the rpm fusion files in the /etc/yum.repos.d/ folder to the main server and made them enabled and still did not find it. I just realized that i am out of luck…

    Thanks a lot for the help so far. If you think of anything please let me known.

    By stm82s July 28th, 2010 at 4:13 pm

  • If it helps, the yum message (it is partly in portuguese):
    Error: Package: kmod-psb-2.6.33.6-147.2.4.fc13.i686-4.41.1-12.fc13.1.i686 (rpmfusion-nonfree-updates-testing)
    Requires: kernel-uname-r = 2.6.33.6-147.2.4.fc13.i686
    Instalados: kernel-PAE-2.6.33.3-85.fc13.i686 (@anaconda-InstallationRepo-201005130056.i386)
    Instalados: kernel-PAE-2.6.33.6-147.fc13.i686 (@updates)
    Available: kernel-2.6.33.3-85.fc13.i686 (fedora)
    Available: kernel-2.6.33.6-147.fc13.i686 (updates)
    Available: kernel-PAEdebug-2.6.33.3-85.fc13.i686 (fedora)
    Available: kernel-PAEdebug-2.6.33.6-147.fc13.i686 (updates)
    Available: kernel-debug-2.6.33.3-85.fc13.i686 (fedora)
    Available: kernel-debug-2.6.33.6-147.fc13.i686 (updates)
    Você pode tentar usar o parâmetro –skip-broken para contornar o problema
    (You could try to use the parameter –skip-broken to circumvent the problem)
    You could try running: rpm -Va –nofiles –nodigest

    By stm82s July 28th, 2010 at 4:13 pm

  • Just to make clear, the yum message i got from the virtual machine, in my system the kernel-2.6.33.6-147.fc13.i686 is installed and started by default but the error is the same.

    By stm82s July 28th, 2010 at 4:19 pm

  • … yum update kernel.
    reboot on the new kernel (version 2.6.33.6-147)
    … yum install the xorg psb driver.

    There’s nothing magic about this. If it doesn’t work, then it is probably because you’ve been rewriting your repo files and broke them.

    By DH July 29th, 2010 at 5:03 am

  • dh I do not think I expressed myself correctly. The kernel that is installed is the 2.6.33.6-147 , but the xorg-x11-drv-psb requires the kernel 2.6.33.6-147.2.4 .
    Before I modify the files of the repositories I made a backup of them and even restoring them the same message appears:
    Requires: kernel-uname-r = 2.6.33.6-147.2.4.fc13.i686
    Installed: kernel-2.6.33.6-147.fc13.i686 (@ updates)

    I do not want to bother with many questions, I will wait until the launch of a new kernel version to try again.

    Anyway I am very grateful for your help and for all the work of Adam, i had already installed Fedora 11 with his drivers and everything work nicely.

    Thanks again for the help and sorry for anything.

    By stm82s July 29th, 2010 at 4:06 pm

  • stm: 147.2.4 is a very new kernel, which may not be in your Fedora repo yet. Since Fedora and Fusion are separate there are occasionally little inconsistencies like this for a day or two, usually they go away if you wait.

    By adamw July 29th, 2010 at 10:45 pm

  • @stm:
    Take a careful look at what is in rpmfusion repos….
    There are more than one version of the kmod. Including the NOT-.2.4 version. There is also an ****a****kmod which will build itself automatically for your kernel as long as you have the matching kernel-devel installed.

    By DH July 30th, 2010 at 4:26 am

  • dh: sure, but the package simply named ‘psb-kmod’ will at any time require one specific kmod-psb-blahblah package (that’s what it’s for, to make the actual kmod get updated automatically), and the driver depends on the psb-kmod package. So what he’s seeing makes sense.

    By adamw July 30th, 2010 at 7:25 am

  • I finally pushed the button and ditched F12 + custom psb builds for F13 + RpmFusion ones :)

    Yay, all looks good, bar one catch: Disabling ShadowFB to get Xv acceleration costs me hibernation (while STR looks to be unaffected):
    - Hibernating from within X will hang on resume, but system seems to be alive underneath.
    - Hibernating from text console will kill X on resume, but system will otherwise work ok.

    Enabling ShadowFB gives me back hibernation. As I use hibernation to keep my workplace alive far more frequently than watching videos, I guess I’ll keep it like this…

    Funny, it made no difference in glxgears (both ~90fps).

    Hardware: AO751h

    Thanks Yves, Adam and all involved!

    By koukou73gr August 2nd, 2010 at 8:31 am

  • @koukou: did you apply the dri mode in your xorg.conf? If not, then you may not have had 3D working to begin with. 90 FPS reeks of software rendering.

    By DH August 3rd, 2010 at 6:03 am

  • No and you’re probably right. I actually just noticed the update killed my xorg.conf where I had it specified before in F12.

    But as hibernation is the actual show stopper for me, I’ll probably just pass along :)

    By koukou73gr August 4th, 2010 at 2:13 am

  • Adam, you made my Nokia Booklet 3G useable now ;) Thank you a lot!

    However I’m having issues with suspend/hybernate and filed it in Bugzilla. Adam, can you take a look there, please? https://bugzilla.redhat.com/show_bug.cgi?id=621176

    Regards, m.

    By Myroslav Opyr August 4th, 2010 at 5:25 am

  • Myroslav: You aren’t going to get anywhere with bugzilla on this since you’re using a hacked up blob driver.

    By DH August 5th, 2010 at 6:50 am

  • Adaw and DH: Just to inform, now that the 2.6.33.6-147.2.4 kernel is available, i updated my fedora and completed the installation. Everything is working nicely now.

    Thanks again!

    dh: i searched and found the kmod version for the old kernel, but every time i tried to install it yum “forced” the installation of the newer kmod. I may be wrong on this, but i think the problems i had happened because i did the dvd installation, with the updated and testing repositories. Anyway it is working now.

    By stm82s August 8th, 2010 at 5:52 am

  • DH: I’ve booted in PAE kernel that boots vesa driver and my symptoms are the same. Should I regenerate crash logs and submit separate bug without PSB running?

    By Myroslav Opyr August 10th, 2010 at 7:43 am

  • Hello people!!!Tnx all for relapse and solution about GMA 500 driver i find this i thing is a problem

    Section “DRI”
    Mode 0666
    EndSection

    i changed to

    Section “DRI”
    Mode 0666
    EndSection

    and work FIND!!!!and i have enabled 3D!!!

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

  • my blog does weird things to quotation marks, as you can see :)

    By adamw August 10th, 2010 at 2:25 pm

  • Hi everybody.

    I have an odd hardware setup. I’m using a FitPC2. It doesn’t have a screen connected to LVDS, only to TDMS via a TDMS to DVI bridge.

    In the logs the driver finds a blank mode for LVDS and my DVI screen is found on TDMS.

    Log:
    Output LVDS0 using initial mode 0×0 +0+0
    Output TMDS-1 using initial mode 144×900 +0+0

    Then there is a error “Couldn’t find PLL settings for mode!”

    The LCD looks like it keeps changing frequency, it flashed every few seconds…

    How do I disable the LVDS port? :)

    By Errol August 11th, 2010 at 12:35 pm

  • Errol: a custom xorg.conf should do the trick. See http://wiki.debian.org/XStrikeForce/HowToRandR12 for the syntax, it has examples for disabling outputs.

    By adamw August 11th, 2010 at 1:11 pm

  • Thx a lot!! :)

    By taljurf August 21st, 2010 at 3:16 am

  • Hello!

    I have tried to install the driver on my Asus EEE PC 1005 HA.

    But it doesn’t works.

    xserver is not starting.

    The error is: Fatal Error

    By Kalle August 22nd, 2010 at 1:49 pm

  • Sorry,

    to fast pushed RETURN ;)

    The Error is:

    Fatal Error
    no screens found

    Can anybody help me please?

    By Kalle August 22nd, 2010 at 1:51 pm

  • Did anyone get Vaapi working on an external display? It only works for me if I use mirror mode. is there a xvattr -a XV_CRTC -v 1 for VAAPI?

    By D August 23rd, 2010 at 4:34 am

  • Glad to see so many people are getting this working. I just got an Archos 9 tablet with a GMA500 chipset, but I’ve had no luck getting the Poulsbo drivers working on Gentoo. I updated the ebuilds to use the newest SRPMS from RPM Fusion and apply all the patches. All of the packages compile fine against Kernel 2.6.34 and X.org 1.8.2 and 1.7.7, but no matter what I do, `startx` always results in a black screen and an unusable console terminal. I’ve tried toggling ShadowFB and a few other options in xorg.conf to no avail. Does anyone have any other suggestions?

    By AdmiralNemo August 27th, 2010 at 4:19 pm

  • Hello Adam, Linux Gurus

    Thank you for all help with poulsbo. All this intel mess is driving me crazy.

    I have an asus 1101ha, and still some trouble with F13 and new driver.

    I added xorg-x11-drv-psb and akmod-psb, then rebooted, but I feel nothing happened. screen is as slow as standard vesa driver can go.

    I checked with yum search psb, and seems like all files are installed

    what else can be done to check for correct installation? driver status?

    Regards,

    ac

    By acoto August 29th, 2010 at 4:04 pm

  • Dear Adam,

    I have installed F13 with psb driver on a Vaio P first gen. The driver worked but I got a weird situation. My kernel crashed and with ioremap problems.
    Then USB ports does not work.

    Any hints?

    Regards, Felix.

    By Felix Leung September 3rd, 2010 at 7:13 pm

  • felix: sorry, not sure what’s going on there. I have an identical setup – F13 on first-gen P. It’s normal to get a ‘kernel crash’ notification at every boot, it’s harmless, just ignore it. But I dunno what’s causing the non-working USB ports. Did you add the ‘nohz=off’ kernel parameter that I recommended for the P?

    By adamw September 4th, 2010 at 1:27 am

  • Hi,

    I have installed F13 on my eeepc 1101ha. I’m running on the kernel 2.6.33. I made an yum install akmod-psb.i686*
    and when i do a lsmod |grep nouveau or lsmod |grep psb, but nothing run.

    The pilote for my GMA500 doesn’t run.

    Someoen can help me?

    By Jodora September 5th, 2010 at 11:15 am

  • Dear Adam,
    Sorry for not replying earlier because I lived on the other side of the globe. Thanks for informing the harmless kernel notification. I shall work on the mysterious usb then.

    regards, Felix.

    By Felix Leung September 5th, 2010 at 5:32 pm

  • Dear Adam,
    Found out sth is wrong in dmesg.

    ehci_hcd: USB 2.0 ‘Enhanced’ Host Controller (EHCI) Driver
    ehci_hcd 0000:00:1d.7: enabling device (0000 -> 0002)
    ehci_hcd 0000:00:1d.7: PCI INT D -> GSI 20 (level, low) -> IRQ 20
    ehci_hcd 0000:00:1d.7: setting latency timer to 64
    ehci_hcd 0000:00:1d.7: EHCI Host Controller
    ehci_hcd 0000:00:1d.7: new USB bus registered, assigned bus number 1
    ehci_hcd 0000:00:1d.7: debug port 0
    ehci_hcd 0000:00:1d.7: cache line size of 64 is not supported
    ehci_hcd 0000:00:1d.7: irq 20, io mem 0x7f800000
    ehci_hcd 0000:00:1d.7: startup error -110
    ehci_hcd 0000:00:1d.7: USB bus 1 deregistered
    ehci_hcd 0000:00:1d.7: PCI INT D disabled
    ehci_hcd 0000:00:1d.7: init 0000:00:1d.7 fail, -110
    ehci_hcd: probe of 0000:00:1d.7 failed with error -110

    is there anyway to reload ehci ?

    regards, Felix

    By Felix Leung September 5th, 2010 at 6:16 pm

  • Dear Adam,
    Re-installed without updating fixed the problem.
    sth wrong with the new kernel.

    will refrain from updating kernel for the time being.

    regards, Felix

    By Felix Leung September 8th, 2010 at 7:49 pm

  • Thank Adam . It Worked Properly In My Acer Aspire AO751H “Fedora 13″ but with a bit changes in procedure :
    for who could not install this driver I Suggest try these steps and it may be work :
    First : I Get Configurations from http://www.rpmfusion.org/configuration using Terminal …
    Second : I Logged in as root in terminal by typing (su –login) and entering my administrative password …
    Third : I Typed this command in terminal (yum install xorg-x11-drv-psb) and it downloaded some files & installed them .
    forth : Reboot & Every thing was ok & Fedora runs with 1366*768 resolution … :-)
    Thanks to Every one Who Provided This Driver …

    By Amir Safarzadeh (From Iran) September 14th, 2010 at 6:28 am

  • Install worked quite well on my Acer Aspire AO0751H. Resolution and 2D acceleration are fine, no 3D though.

    Interestingly, video playback with xine or vlc does not work in the standard installation. But in firefox, ogg (big buck bunny) and flash (adobe flash 10.1) videos are working properly. If I set ShadowFB to “true” in xorg.conf, video playback with xine and vlc is working but it is quite slow. window rendering seems also to get slower compared to ShadowFB = false.

    does anyone have an idea, why video playback is working in ff, but not with xine or vlc (I also tested this with the mplayer-accel, which also did not work)?

    By Sebastian September 16th, 2010 at 2:30 pm

  • Because xv doesn’t work. x11 (unaccelerated playback) and libva accelerated playback do.

    By adamw September 16th, 2010 at 2:49 pm

  • I have the same problem as Felix with the USB devices on a Sony Vaio X13 on Arch Linux (based on the sources you provide)..

    Problem only exists with “newer” kernels.

    Any information I can provide you with to help debug this?

    By Jon Gjengset September 27th, 2010 at 10:18 pm

  • USB ports have nothing to do with the graphics driver, you should talk to the kernel team.

    By adamw September 27th, 2010 at 10:20 pm

  • Hi, I have just installed Fedora 13 in my FitPC2 and as soon as I install the modules and reboot, I cannot get X to start. By checking the logs on X, I found this:

    Fatal server error:
    Couldn’t find PLL settings for mode!

    If I start with initmode 3, I can see the modules correctly loaded, but when I start X, the monitor turns off.

    I have tried a myriad of xorg.conf options to no avail. Any suggestion?

    By hapm September 30th, 2010 at 8:32 am

  • Looks like you might want to try adding this line to xorg.conf :

    Option “NoPanel” “true”

    in the ‘Device’ section. That’s from http://fit-pc2.com/download/ubuntu/files/xorg.conf , which is part of this guide for the Fit 2. There’s a lot of other crap in that xorg.conf , but I think that’s the operative bit.

    By adamw September 30th, 2010 at 8:39 am

  • After another attempt, I got it working by using the “NoPanel” option.

    I now have a working system! Cheers and thanks for the guide!

    By hapm September 30th, 2010 at 9:05 am

Leave a Reply

Log in with Persona or OpenID to post a comment without reCAPTCHA.