Poulsbo aka Intel GMA500 drivers PKGBUILD

mulenmar · 2010-04-19 05:17:12

Okay, I've got good news and bad news.

The good news is, I was digging through my archives and found a few old Xserver 1.6 PKGBUILDS I had squirrelled away -- and two of them are the FBDEV driver that isn't in the Kdemod repo! (Cue the Hallelujah Chorus) I've always gotten much better performance with it than with the VESA driver.

The only bad news is I've been awake for ~30 hours and was getting ready to call it a night when I stumbled across the packages, so I'm trying not to fall asleep typing this as-is and can't test which one is the right one, or whether BOTH work with Xserver 1.6.

Since I can't just attach the files here, I put them on drop.io:

http://drop.io/hh6gtvv

and tomorrow will also store them privately on my blog, just to be safe.

I'll try to figure out which file is the right package tomorrow. Hopefully if anyone is wrestling with the PSB or IEGD driver and gives up will now at least have a faster alternative than VESA to fall back on now. If someone could put the package in a proper repository, to ensure they don't get pulled for excessive traffic, that would be perfect. (I know nothing about how to create such things, and have no idea what drop.io's limit is.)

Last edited by mulenmar (2010-04-19 05:19:05)

ypnos · 2010-04-19 07:44:36

pie86: thx! perhaps they only updated the xorg files then? I will check that..

mulenmar · 2010-04-20 10:04:17

Apparently it was the older of the two packages that works with xorg-server 1.6. I've removed the other package from the drop.io account.

Also, I'm pleased to report that once the Xserver 1.6 packages from the Kdemod repo,, the FBDEV package I located, and the openssl-compatibility package from the AUR were all installed, everything works as it should. Not a big surprise at this point, since it hasn't been long since Xserver 1.6 was the standard for Arch, but I imagine that in other distros more effort would've been needed.

I'd like some input before I update the wiki about this, if anyone has a moment. Should I just add the process to the Acer Aspire One wiki page, or do you think a entire new page, with a link to it at the appropriate part of the Acer Aspire One article, would be more appropriate? As the process of installing an older Xserver may be helpful to people with other hardware, even if not for using the Poulsbo hardware, I'm leaning more towards the separate page solution. Problem is, my wiki skills are nowhere near up to the task yet.

The fastest solution to that problem would be for me to write a blog post about the process, and then link to it in the Acer Aspire One article until I can practice enough to put together a decent wiki page -- or until someone else does the job and lets me know.

ypnos · 2010-04-20 10:07:43

Actually I wonder if a special page about "Poulsbo" wouldn't be a good idea, given all the other knowledge (about PSB, IEGD..) buried in this thread.

I don't know any other use case for xserver 1.6 right now, but perhaps if there will be other hardware where it is needed, the wiki page for that can just reference the accoriding chapter on poulsbo wiki page? I think there is not soooo much to tell about installing Xserver 1.6 alone anyway.

mulenmar · 2010-04-20 10:39:13

ypnos wrote:

Actually I wonder if a special page about "Poulsbo" wouldn't be a good idea, given all the other knowledge (about PSB, IEGD..) buried in this thread.

Thanks, that's what I was thinking. I wouldn't be able to do a section on IEGD, as I haven't gotten that working (except for once, and with massive instability, on Fedora 10.) but I'll try to practice my wiki skills an create a page later on. I'd also be quite happy to contribute if soneone else created the page. I can edit, I just can't create structuring yet, need to study that.

yqnos wrote:

I don't know any other use case for xserver 1.6 right now, but perhaps if there will be other hardware where it is needed, the wiki page for that can just reference the accoriding chapter on poulsbo wiki page? I think there is not soooo much to tell about installing Xserver 1.6 alone anyway.

Although I'm still not entirely convinced that it's an Xserver 1.7 issue and not just a misconfiguration in my xorg.conf, I can't safely use mplayer -vo xv on my old laptop's ATI Rage Mobility M3 -- the Xserver becomes virtually unresponsive and the video jitters. (I might post a thread about it later if I can't figure it out myself, I won't further clutter the thread with details. )So, there *may* be at least one other need for Xserver 1.6. But you're right, a reference in each article to a Poulsbo article, "Installing Xserver 1.6" section that needs it should be quite sufficient.

ypnos · 2010-04-20 11:15:36

I created a page, everybody feel free to fill with contents:
http://wiki.archlinux.org/index.php/Poulsbo

mulenmar · 2010-04-20 13:41:13

ypnos wrote:

I created a page, everybody feel free to fill with contents:
http://wiki.archlinux.org/index.php/Poulsbo

Ooh, shiny. I'll go get some caffeine and get to work right away. Thanks, ypnos!

pie86 · 2010-04-20 14:57:55

ypnos wrote:

I created a page, everybody feel free to fill with contents:
http://wiki.archlinux.org/index.php/Poulsbo

Great! I'd like to help out but my English is terrible!!...according to me is better if I overhaul my work and post something complete (perhaps with the help of chris who is working on something similar (I think)).

mulenmar · 2010-04-20 15:57:59

I've put in the directions for installing Xorg 1.6 and the FBDEV driver, and slightly clarified the PSB vs IEGD section, but having the PSB and IEGD work together in this thread makes precisely referencing info for each more work. I've also marked the article as a stub and slapped myself upside the head for assuming that Wiki editing is difficult.

Still working, I'll be working on the section for the old Ultra Mobile Group's PSB driver next, and then the Uvesafb method.

pie86 wrote:

I'd like to help out but my English is terrible!!...according to me

If you'd like, you could email me what you'd like added to the article and I'll proofread it for you, I'm a native Americanized-English speaker.

Last edited by mulenmar (2010-04-20 15:58:23)

mulenmar · 2010-04-20 22:02:17

woah wrote:

Since its initial announcement, has anyone heard any additional information regarding that GMA500 driver based on Gallium3D?

For the record, BOTH the older PSB driver from the Ultra Mobile Group and the IEGD driver are Gallium3d implementations. http://community.edc.intel.com/t5/Softw … /2355#M253

woah · 2010-04-21 16:40:49

mulenmar wrote:

woah wrote:
Since its initial announcement, has anyone heard any additional information regarding that GMA500 driver based on Gallium3D?
For the record, BOTH the older PSB driver from the Ultra Mobile Group and the IEGD driver are Gallium3d implementations. http://community.edc.intel.com/t5/Softw … /2355#M253

So does this mean the drivers we've got now are pretty much our best bet (for the forseeable fufure, anyway)?

And thank you so much for creating/editing that wiki page.

mulenmar · 2010-04-21 18:26:58

woah wrote:

mulenmar wrote:
woah wrote:
Since its initial announcement, has anyone heard any additional information regarding that GMA500 driver based on Gallium3D?
For the record, BOTH the older PSB driver from the Ultra Mobile Group and the IEGD driver are Gallium3d implementations. http://community.edc.intel.com/t5/Softw … /2355#M253
So does this mean the drivers we've got now are pretty much our best bet (for the forseeable fufure, anyway)?
And thank you so much for creating/editing that wiki page.

ypnos created it, I just contributed stuff I've basically written before in a slightly different way. Thanks, though.

Alright, I'm working the process for installling the old PSB driver. Here are the steps I had to do, can anyone suggest easier methods?

Get kernel ready
* Downgrade kernel to 2.6.31.5
* Downgrade/install kernel firmware to 2.6.31 <-- Not sure if was necessary
* Forcibly remove linux-api-headers via

sudo pacman -Rd linux-api-headers

* Install kernel-headers-2.6.31.5

Create and install psb module
* Build chris.griffith's psb-firmware from AUR and install
* Build chris.griffith's psb-kmod from AUR and install
* Build chris.griffith's libdrm-poulsbo from AUR and install

Create and install the PSB driver for Xorg
* Instal xf86dgaproto
* Build chris.griffith's xpsb-glx from AUR and install
* Add ixar's repository (first post in thread)
* Install ixar's xorg-x11-drv-psb (couldn't get chris.griffith's to build)

I'm going to wipe out all of the Xorg and Poulsbo stuff I've installed and do it again a couple times, to make sure I listed everything and figure out exactly which of ixar's and with of chris.griffith's packages do and don't work.

Expect an update and "bug reports" within 24 hours.

EDIT: Not done testing, but it appears that with the kernel and headers mentioned above, the only one of chris.griffith's packages that is needed is psb-kmod. Everything else can be used straight from ixar's repo. Still have to follow the order, though.

Last edited by mulenmar (2010-04-22 08:31:21)

Jonhoo · 2010-04-26 22:13:57

Poulsbo drivers for Xserver 1.7?
http://www.happyassassin.net/2010/04/26 … -incoming/

descendent87 · 2010-05-05 23:07:51

Yes mandriva have managed to get psb driver working with Xserver 1.7, fedora drivers are coming soon and people are trying to build them for ubuntu. See here for details & patches

treba · 2010-05-18 14:42:52

hey mulenmar,
big thanks for this little tutorial, i was finally able to switch from jolicloud to arch.

even if i had to change the order a little bit (for example i had to install libdrm in order to install libgl, first), overall it worked. i will post my solution, too, when i have time to make a clean install again.

i was really embrassed when i found out that this driver even supports kms or at least changes the resolution at startup. adding "psb" to modules in /etc/mkinitcpio.conf like in the wiki entry for intel even enables it directly at the start of the bootprocess.
see http://wiki.archlinux.org/index.php/Int … Setting.29 for it.

i will add it to the wiki page soon.

greetings,
treba

redox · 2010-05-21 12:19:44

Ok, I got the IEGD 10.3 driver working on my Acer 751h full resolution (1366x768).

I followed mostly the nanoANT guide http://www.nanoant.com/linux/compiling- … stribution

Steps:

1. Get IEGD package from Intel
2. Downgrade X as informed in Arch wiki
3. Downgrade kernel to 2.6.31-ARCH <-- IEGD tests did not work in current kernel, did not test X
4. Follow the nanoANT guide, but after copying IKM/val/agp/agpm0vmob2/interface_abs.h you must edit it to include following line:

#define phys_to_gart(x) (x)

, then it should compile.

5. Copy the files from IEGD package to proper places. These files are located in IEGD_10_3_Linux/driver/Xorg-xserver-1.6.4.901/ This is what i copied after examining install scripts :

cp iegd_drv.so /usr/lib/xorg/modules/drivers/
cp libXiegd_escape.so.2.0.0 /usr/lib/
cp hdmi.so lvds.so analog.so sdvo.so softpd.so tv.so /usr/lib/xorg/modules/
cp iegd_dri.so /usr/lib/dri/
cp iegd_drv_video.so /usr/lib/xorg/modules/drivers/
cp libva.so.0.29.0 /usr/lib/

6. modprobe the module and create default xorg.conf, then edit it to contain Driver "iegd"

I haven't yet tested video, and some of the files in driver folder are still a mystery. I'll edit the wiki if this solution is stable enough.

Updates:

1. Flash works

Last edited by redox (2010-05-21 12:32:12)

ypnos · 2010-05-21 12:21:46

Great! Please don't forget to edit wiki. I will try it then on my fit pc.

btw. did you test va-api?

ighea · 2010-05-21 12:22:20

The IEGD driver "works" on 2.6.33 and propably on 2.6.34 too, but at least with .33 it is very unstable and may hard lock the system randomly.

imraro · 2010-06-15 17:05:35

Any news?

Last edited by imraro (2010-06-15 17:06:45)

CPUnltd · 2010-06-16 07:32:04

haven't heard anything new in ages... my fitpc2 now runs XP so that it can keep my magicjack functional (till the Linux client comes out in the year 20never) and I'm running an Acer Revo in place of the fitpc2 with MUCH better results (since it uses the Nvidia ION GPU I get some real performance out of it.

pie86 · 2010-06-16 10:12:50

I'm still using my 2.6.31 patched kernel and outdated Xorg. Unfortunately couldn't work on the PKGBUILD anymore becouse exams are stealing my spare time!:(

Anyway...80h of movies played without any problem! ...I can say I'm satisfied for the moment.

smartboyathome · 2010-06-16 13:42:19

I have a GMA500 in my HP Mini 210-1010NR, and using a stock Xorg from testing I get native resolution and 2D rendering just fine. I don't even want to bother with 3D since that would be too much hassle for too little gain at this point.

Jonhoo · 2010-06-21 01:54:23

Hmm.. I still don't get proper 2D performance using the new Xorg 1.8 from extra on my Sony Vaio X13 w/GMA500..
Still just uses the framebuffer driver and thus redraws the whole screen whenever something changes..

mulenmar · 2010-07-11 18:10:21

Acer Aspire One 751h, Linux 2.6.34-ARCH, Xserver 1.8

With this latest kernel, there are several address space collisions which prevent using the uvesafb+915resolution-static solution to get the native 1366x768 resolution.

pci_root PNP0A08:00: address space collision: host bridge window [mem 0x000c0000-0x000dffff] conflicts with reserved [mem 0x000d00000-0x000ffff]

Appending "pci=nocrs", without the quotation marks, solves the issue. I have no idea why or what it means, but it was suggested in dmesg.log, so I tried it and it works.

I'll add it to the Wiki shortly, after I look up what this option means.

EDIT: Thank you Linux documentation people! From kernel-parameters.txt:

nocrs                      [X86] Ignore PCI host bridge windows from ACPI. If you need to use this, please report a bug.

EDIT 2: Poulsbo entry updated to actually describe and link the the "generic framebuffer option" the intro mentioned, Uvesafb entry updated with Troubleshooting section, including the "pci=nocrs".

Funny -- a few minutes after I originally posted this, it was the first Google result for "pci=nocrs uvesafb"

EDIT #3: Apparently, the address space collision is a known bug -- #FS19645

Last edited by mulenmar (2010-07-11 22:20:49)

imraro · 2010-07-16 15:13:52

Not good news ((

Arch Linux

#226 2010-04-19 05:17:12

Re: Poulsbo aka Intel GMA500 drivers PKGBUILD

#227 2010-04-19 07:44:36

Re: Poulsbo aka Intel GMA500 drivers PKGBUILD

#228 2010-04-20 10:04:17

Re: Poulsbo aka Intel GMA500 drivers PKGBUILD

#229 2010-04-20 10:07:43

Re: Poulsbo aka Intel GMA500 drivers PKGBUILD

#230 2010-04-20 10:39:13

Re: Poulsbo aka Intel GMA500 drivers PKGBUILD

#231 2010-04-20 11:15:36

Re: Poulsbo aka Intel GMA500 drivers PKGBUILD

#232 2010-04-20 13:41:13

Re: Poulsbo aka Intel GMA500 drivers PKGBUILD

#233 2010-04-20 14:57:55

Re: Poulsbo aka Intel GMA500 drivers PKGBUILD

#234 2010-04-20 15:57:59

Re: Poulsbo aka Intel GMA500 drivers PKGBUILD

#235 2010-04-20 22:02:17

Re: Poulsbo aka Intel GMA500 drivers PKGBUILD

#236 2010-04-21 16:40:49

Re: Poulsbo aka Intel GMA500 drivers PKGBUILD

#237 2010-04-21 18:26:58

Re: Poulsbo aka Intel GMA500 drivers PKGBUILD

#238 2010-04-26 22:13:57

Re: Poulsbo aka Intel GMA500 drivers PKGBUILD

#239 2010-05-05 23:07:51

Re: Poulsbo aka Intel GMA500 drivers PKGBUILD

#240 2010-05-18 14:42:52

Re: Poulsbo aka Intel GMA500 drivers PKGBUILD

#241 2010-05-21 12:19:44

Re: Poulsbo aka Intel GMA500 drivers PKGBUILD

#242 2010-05-21 12:21:46

Re: Poulsbo aka Intel GMA500 drivers PKGBUILD

#243 2010-05-21 12:22:20

Re: Poulsbo aka Intel GMA500 drivers PKGBUILD

#244 2010-06-15 17:05:35

Re: Poulsbo aka Intel GMA500 drivers PKGBUILD

#245 2010-06-16 07:32:04

Re: Poulsbo aka Intel GMA500 drivers PKGBUILD

#246 2010-06-16 10:12:50

Re: Poulsbo aka Intel GMA500 drivers PKGBUILD

#247 2010-06-16 13:42:19

Re: Poulsbo aka Intel GMA500 drivers PKGBUILD

#248 2010-06-21 01:54:23

Re: Poulsbo aka Intel GMA500 drivers PKGBUILD

#249 2010-07-11 18:10:21

Re: Poulsbo aka Intel GMA500 drivers PKGBUILD

#250 2010-07-16 15:13:52

Re: Poulsbo aka Intel GMA500 drivers PKGBUILD

Board footer