MASTER: GMA-500 lacks driver for 8.10 and 9.10 (poulsbo works only on 8.04 and 9.04)

[Trevor]

-psb does not work on Intrepid (8.10) because it was developed only for working against Hardy 8.04(LTS).

For Intrepid, upstream would need to update it to work with the newer xserver/mesa/libdrm/kernel included in that release. For example, it would need to use the new memory manager in libdrm and the new libpciaccess, among other things.

For Jaunty, this work is under review. There might be additional porting tasks, so the amount of work to get -psb updated may be increasing.

[Original Report]
I install the Ubuntu 8.10 and reboot computer , it in direct enters the text mode .
I press CTRL+ALT+F7 >>>the screen is blank.
My platform is intel Atom and display is LVDS panel.
The Xorg.0.log have the some errors.
MY xorg.conf as below .
Section "Device"
 Identifier "Configured Video Device"
EndSection

Section "Monitor"
 Identifier "Configured Monitor"
EndSection

Section "Screen"
 Identifier "Default Screen"
 Monitor "Configured Monitor"
 Device "Configured Video Device"
EndSection

[Trevor (trevor-hsu)]

I tried the Ubuntu 8.04 it work fine,but 8.10 can not work.

[Alan Jenkins (aj504)]

I would guess you have one of the intel graphics which do not have specific driver support. I'm thinking of the GMA-500. To confirm this, you should try to find exactly what your graphics are. Try running "lspci".

You may find it is simply not possible to use linux with this hardware combination. (Until intel get the driver situation sorted). Sorry.

---

The logs show X is using the VESA driver, a generic driver which is used as a fallback. This can often work. But it doesn't necessarily support the full hardware capabilities.

In this case, X _seems_ to be saying that there are only a few valid VESA modes, with resolutions on 800x600 and 640x480. And your monitor doesn't support the timings for these modes, being a recent/fussy/less usual 1024x600 LCD.

[Trevor (trevor-hsu)]

Yes .
My graphic is intel GMA-500 and I known Intel do not have specific driver support for Ubuntu Desktop version.
But I want to know why 8.04 can work and 8.10 can not work.

[Trevor (trevor-hsu)]

My monitor have 1024x600 LCD,But I install the XP and Ubuntu 8.04 they default resolution are 800x600.
So I think my LCD may suppot this timing.
I guess the drive and Xorg of 8.10 can not support it .
Could I shall Xorg of 8.10 change to Xorg of 8.04?

[Alan Jenkins (aj504)]

Sorry, I missed where you said 8.04 works. Yes, there must be some problem in the Xorg or the Vesa driver for 8.10.

I'm afraid this is beyond my experience. You will have to wait for someone else for any real help. Ubuntu 8.04 is "LTS", it will apparently be supported for three years. Maybe you will decide to stick with 8.04 for a while instead :-).

I would not recommend trying to install the Xorg from 8.04. I guess it might work - but you will be fighting the package management system.

If you have time, you may be able to find out a little more for yourself. But it's a dark area. I make no guarantees, and I probably can't give you any more help.

1) Look at the differences between Xorg.log in 8.04 and 8.10. See if 8.04 does anything different in /etc/X11/xorg.conf. (If you do, please attach a copy of both files from 8.04).

2) Find out exactly what timings 8.04 uses. Run "xvidtune" from a terminal, and look at the output from clicking the "Show" button. The line of numbers is in the same format as the "ModeLine" directive as used in xorg.conf. (See "man xorg.conf" for details). Try entering this modeline into xorg.conf on Ubuntu 8.10. I'm *not* saying this will work, it just might make it clearer what the problem is.

[Bryce Harrington (bryce)]

-poulsbo is incompatible with 8.10. It has its own libdrm dependency which differs from the stock version in 8.10, as well as having certain kernel/mesa dependencies which I think are not satisfied with 8.10.

As well, it is still uncertain whether it will be supportable in jaunty, due to the dependency differences. For now you'll need to stick to 8.04 if you want to use -psb on this hardware. -vesa is another option which should work, just not as natively.

Marking as wishlist against -psb. I don't know if it's likely this will get fixed for intrepid, but I'll open a task against it as well just in case.

[Loïc Minier (lool)]

Could you please attach the output of "sudo lspci -vvnn >lspci-vvnn.txt" to this bug report?

[Trevor (trevor-hsu)]

To compare the xorg.0.log of8.04 and xorg.0.log8.10.
I found something：
8.04
(WW) VESA(0): Unable to estimate virtual size
(II) VESA(0): Not using built-in mode "640x480" (hsync out of range)
(--) VESA(0): Virtual size is 800x600 (pitch 800)
(**) VESA(0): *Built-in mode "800x600"

8.10
(WW) VESA(0): Unable to estimate virtual size
(II) VESA(0): Not using built-in mode "800x600" (hsync out of range)
(II) VESA(0): Not using built-in mode "640x480" (hsync out of range)
(EE) VESA(0): No valid modes
I think this is the major error.
Why 8.04 can got "(--) VESA(0): Virtual size is 800x600 (pitch 800)"?

[Alan Jenkins (aj504)]

Trevor's Xorg.0.log for 8.04 shows that it is not using psb_drv. It makes no mention of the psb-specific module included in xserver-xorg-video-psb. Rather, on both 8.04 and 8.10 he was using the *non*-native VESA driver.

The problem is that in 8.10, the VESA driver can no longer find any valid mode for his monitor. In 8.04, it was able to successfully drive it at 800x600.

I've reassigned the bug accordingly. I don't have authority to change the Importance myself. Someone with authority should change the Importance - I don't think this is a wishlist.

[Alan Jenkins (aj504)]

Trevor: I can see an interesting difference here:

8.04:
VESA(0): Configured Monitor: Using hsync range of 31.50-36.48 kHz
VESA(0): Configured Monitor: Using vrefresh range of 50.00-60.00 Hz
...
(II) VESA(0): Attempting to use 56Hz refresh for mode "800x600" (114)

8.10:
VESA(0): <default monitor>: Using hsync value of 36.48 kHz
VESA(0): <default monitor>: Using vrefresh value of 60.00 Hz

8.10 seems to be insisting on a *single* vrefresh value of 60 Hz. I don't understand why it would do that. I've always seen the values for monitors expressed as a *range* of valid values.

8.04 uses a refresh rate of 56Hz, which is within it's range of 50-60. Perhaps 8.10 can't use the same timing because it will only accept modes of exactly 60 Hz.

I expect you *can* work around this problem, if you don't mind editting xorg.conf manually. You can specify the vrefresh and hsync ranges of your monitor manually, using the values from 8.04. I.e.

Section "Monitor"
 Identifier "Configured Monitor"
        HorizSync 31.50-36.48
        VertRefresh 50.00-60.00
EndSection

If you can, try to look up the values for your monitor. They should be on the back of the monitor, or in a manual. Or you may be able to find the figures online. V-refresh should have "Hz" on the end, H-sync should have "kHz".

My suspicion is that your monitor EDID (automatic configuration) doesn't provide these values directly. So X probably has to guess, or use some defaults - and this has changed between versions. Ironically, I would suspect the defaults were changed to increase compatibility with timing-fussy LCDs when using the Vesa driver :-D.

[Trevor (trevor-hsu)]

The bug is to solve, I add the
"HorizSync 31.50-36.48 and VertRefresh 50.00-60.00"
into my xorg.conf .
After reboot , the sysytem enter to the GDM.
Thanks

[Alan Jenkins (aj504)]

You're most welcome. I'm glad I was able to help. I hope you find your upgraded Ubuntu worth the effort :-).

[Bryce Harrington (bryce)]

This bug report should focus on the original issue that -psb is not available for Intrepid.

Regarding the -vesa issue, file a separate bug report if you'd like that investigated as well. Probably it is an xorg-server or kernel problem. -vesa is pretty generic so the bug is unlikely to live in it.

[Stefano Pedretti (stefano-pedretti)]

https://blueprints.edge.launchpad.net/ubuntu-mobile/+spec/poulsbo-packaging

[Kyle Cronan (kyle-pbx)]

Here is a workaround:

http://ubuntuforums.org/showthread.php?p=7091572

[Rotbart van Dainig (rotbart-van-dainig)]

Am Freitag, den 17.04.2009, 23:27 +0000 schrieb Kyle Cronan:
> Here is a workaround:

Just not for Jaunty.

[Stefano Pedretti (stefano-pedretti)]

One step closer:

http://www.phoronix.com/scan.php?page=news_item&px=NzE1Mw

[Rotbart van Dainig (rotbart-van-dainig)]

Am Donnerstag, den 23.04.2009, 07:19 +0000 schrieb Stefano Pedretti:
> One step closer:

Actually, one step closer to closing this bug is this:

https://launchpad.net/~ubuntu-mobile/+archive/ppa?field.series_filter=intrepid

[Morten Kjeldgaard (mok0)]

I have this issue on a Dell Mini 10. It uses the Poulsbo chipset and the GMA500 graphics chip.

Currently, the display runs at 800x576, but the nominal resolution is 1024x576, so everything looks "Squished". The X-driver currently in use is vesa, but the trick of manually setting the modeline in xorg.conf doesn't work, because the vesa driver refuses to run in the (rather odd) native resolution.

I am running jaunty, lpia arch. Everything works great on the Dell mini 10, with exception of the screen resolution.

I hope to see a proper X-driver soon, but just having the vesa driver work at 1024x576 would be a big improvement.

[Chris McCormick (chris-mccormick)]

I have the same issue on a Dell Mini 12, Jaunty lpia architecture. The native resolution is 1200x800 but it was defaulting to 1024x768 which stretches and blurs the graphics horribly.

I got a non-squished resolution by downloading a dpkg of 815resolution from an old i386 version of Ubuntu, but the frame rate is extremely slow, almost to the point of non-useability, and 3d is not working at all.

It would be great to see some proper work put in by the Ubuntu team in packaging the Poulsbo drivers for Jaunty. Hopefully pressure can be put upstream on Intel to release the drivers and firmware licensed under a proper FOSS license. I find it incredible that there is this big hole in what is a swiftly emerging Linux market: netbooks across the entire high end Dell Mini range.

[Chris McCormick (chris-mccormick)]

Wow, reading back on this and seeing that psb-kernel-source has been uploaded to https://launchpad.net/~ubuntu-mobile/+archive/ppa?field.series_filter=jaunty makes me realise how ungrateful this bug report sounds. Would like to register my appreciation of the hard work being put in by the Ubuntu team and understanding that the psb driver is a complex situation.

[Rotbart van Dainig (rotbart-van-dainig)]

Thanks to Steve, Intrepid already runs at native resolution on the Kontron KTUS15 here - Video seems ok, too.

[Brian Teague (bteague)]

I'll second Chris McCormick's comments - this seems as good a forum as any to thank the Ubuntu Mobile developers for working with Intel to develop working drivers for Poulsbo. The Intrepid packages work great - I'm looking forward to a Jaunty solution.

[Daniel Letzeisen (dtl131)]

The Ubuntu Mobile team has packaged it for Jaunty now: http://ppa.launchpad.net/ubuntu-mobile/ubuntu/pool/main/x/xserver-xorg-video-psb/

[Markus Heberling (markus-tisoft)]

I have tried the driver from ppa on a fresh jaunty install on a FIT-PC2.

X fails to start. I have attached the xorg log.

[Timon_and_Pumba (timonterbraak)]

I have a Fit-PC2 using this chip: http://fit-pc2.com/wiki/index.php?title=Main_Page

[Markus Heberling (markus-tisoft)]

I got it working by adding HorizSync and VertRefresh in the "Monitor" section in my xorg.conf.

You can get the correct values by running "sudo ddcprobe" after installing the xresprobe package. Look for monitorrange in the output.

Seems like the driver is unable to detect that itself and then fails badly...

[metalfan (julius-junghans)]

fit-pc2 on 8.10, 2.6.27-11

[Markus Heberling (markus-tisoft)]

@metalfan

Use the ddcprobe workaround I descibed above. That sould fix this error.

I have the following i my xorg.conf and it works fine:

Section "Monitor"
 Identifier "Configured Monitor"
 HorizSync 30-81
 VertRefresh 56-85
EndSection

[metalfan (julius-junghans)]

I just tested that workaround on a fresh 9.04 installation, no luck.

ive installed poulsbo-driver-2d and 3d.

[breezeight (nicolabrisotto)]

Hi!
Here I've just posted what works for me on ubuntu 8.10:

http://bris8.wordpress.com/2009/06/30/ubuntu-on-acer-ao751h/

I hope it's useful, let me know!

Nicola

[Stefano Pedretti (stefano-pedretti)]

I heard about no support in 9.04 for Poulsbo GMA 500 video section.

Can someone give me more?

[metalfan (julius-junghans)]

Solution for fit-pc2:

To get it running you can install ubuntu 8.04 and follow these steps: http://www.fit-pc2.com/forum/viewtopic.php?f=9&t=655

[Nicolas DERIVE (kalon33)]

Are there some news about poulsbo support under upcoming Karmic ?

[Loïc Minier (lool)]

We wont get a karmic version

[Fabs (fabriciosn)]

I am experiencing the same problem on Karmic, with an eeepc 1101ha. I am also experiencing a very slow video performance. It was unusable around 15 august, but then an update made it a little bit more usable, but i can't for example render a video properly.

I read the entire discussion about resolution, but I think the performance is related to that also, am I wrong? What I get from this is that if Intel does not release the drivers in a proper way, we won't have any better support for this graphics card?

[Mark Edgington (edgimar)]

See https://wiki.ubuntu.com/HardwareSupportComponentsVideoCardsPoulsbo for info on using the driver with Karmic.

[Christian Stöveken (excogitation)]

For 9.10 there's a way to make it work here:
http://ubuntuforums.org/showthread.php?t=1253406

[Jose Bernardo (bernardo-bandos)]

Christian, the wiki has been edited/added with the info gathered by the participants in that thread, so it is up to date. It would be nice if it at least it was added to the release notes.

[Jim Popovitch (jimpop)]

For Karmic (9.10) here is what I had to do (from http://mail.ale.org/pipermail/ale/2009-October/113618.html)

The solution is to manually d/l and install this package:

http://ppa.launchpad.net/ubuntu-mobile/ppa/ubuntu/pool/main/x/xserver-xorg-video-psb/xserver-xorg-video-psb_0.31.0-0ubuntu1~904um1_i386.deb

then add this software source:

    deb http://ppa.launchpad.net/lucazade/gma500/ubuntu karmic main

and then add Lucazade's key:

    apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 6699F3D9

then

    apt-get update
    apt-get install psb-firmware psb-kernel-headers psb-kernel-source
xpsb-glx libdrm-poulsbo1 poulsbo-config

and then set your xorg.conf to this:

-------------------------------------------------------
Section "Device"
        Identifier "Configured Video Device"
        Option "IgnoreACPI"
        Option "AccelMethod" "exa"
        Option "MigrationHeuristic" "greedy"
        Option "NoDDC"
        Driver "psb"
EndSection

Section "DRI"
    Mode 0666
EndSection

Section "Monitor"
        Identifier "Configured Monitor"
EndSection

Section "Screen"
        Identifier "Default Screen"
        Monitor "Configured Monitor"
        Device "Configured Video Device"
EndSection

#Added for mouse pad
Section "InputDevice"
        Identifier "Mouse0"
        Driver "synaptics"
        Option "Protocol" "auto"
        Option "Device" "/dev/input/mouse0"
        Option "ZAxisMapping" "4 5 6 7"
        Option "CorePointer"
        Option "HorizEdgeScroll" "1"
EndSection
-------------------------------------------------------

Now if you look at the launchpad page for the software source
(https://launchpad.net/~lucazade/+archive/gma500) you will see that
the required xserver-xorg-video-psb package failed to build 3 weeks
ago. Dig around a bit and you will see that the build error is a
very minor "unable to rm -f a *directory*" which is why the needed
package isn't in the gma550 PPA. <sigh>

-Jim P.

[Fabián Rodríguez (magicfab)]

From https://lists.ubuntu.com/archives/ubuntu-devel/2009-August/028670.html:
"I'm quite sorry to say that the Poulsbo drivers will not be in Karmic
Koala. The Poulsbo chipset has a proprietary section to the driver and
Intel has said they are not supporting Karmic Koala, so its out of my hands."

I have also tried this guide mentioned above, however, and it (partially) works:
https://wiki.ubuntu.com/HardwareSupportComponentsVideoCardsPoulsbo

By "partially" I mean I got the right resolution and 3d effects but video was a bit laggy.

[Jim Popovitch (jimpop)]

I have zero lags. The psb driver (sans the packaging/distribution mess) works perfectly. I don't see any need for Intel to formally support the psb driver on Karmic as long as they just support the driver in general. Did Atheros support the Hardy wireless driver of years past? This whole psb mess has given me a bad feeling about Ubuntu. Again, the driver works, it's the packaging/distribution/politics that suck. Shame on Ubuntu if they don't support this in Karmic as the Poulsbo chipset is probably the most important thing for Ubuntu to pay attention to. There are now hundreds of thousands of inexpensive (cheaper than an iPhone!) netbooks hitting the market with the Poulsbo chipset. Most of those are going to go to college, and other, students who will be eager to try *any* Linux distro on them. If it works on Gentoo, then they will stick with Gentoo. <- Marc S, Pete G, you reading this?

[Loïc Minier (lool)]

@jimpop, this is not a place to vent your frustration. Would we have received a suitable driver for the current kernels, we'd have uploaded it in the ~ubuntu-mobile PPA or even to Ubuntu as we did for the previous versions.

Intel has top quality drivers for its other chipsets, but not for Poulsbo due to a complex IP issues. This is not in our control to fix for them, and we don't have the resources to reverse engineer or forward port the existing kernel bits (these were even rejected from staging in the upstream linux kernel).

If you're aware of a forward ported or reverse engineered driver which we could include, then this is the right place to mention it. I think it's too late for the 9.10 release, but it could be prepared in a PPA or considered for 10.04.

(Note that the recipes in this bug only apply to the xorg video driver but don't cover the kernel counterparts which are needed for psb-drm and hence 2D and 3D acceleration.)

[Loïc Minier (lool)]

Also note that support for Poulsbo is expected to work with Ubuntu 8.10 and 9.04 after installing the packages from the ~ubuntu-mobile PPA.

[Jim Popovitch (jimpop)]

How much more 2d or 3d accelleration do I need beyond what the present psb (that is incorrectly packaged and distributed) gives:

~$ glxgears
1256 frames in 5.0 seconds
1425 frames in 5.0 seconds
1499 frames in 5.0 seconds
1459 frames in 5.0 seconds

The trick to Poulsbo is to have all chipset components (audio, video, etc) configured and working properly. A poorly configured hda-intel module can have adverse affects on the video perfomance, etc.

Can you now fix the packaging so that the driver can be distributed easily so that the Acer AO751h can work out of the box with Karmic.

Thanks,

-Jim P.

[Jim Popovitch (jimpop)]

BTW Loïc, @boredandblogging and @linuxcrypt (who together with me started #atllinuxfest) both witnessed the existing psb driver working on my AO751h yesterday.

[Loïc Minier (lool)]

@jimpop: on which release are you seeing which package work perfectly?

(BTW glxgears isn't a benchmark: it just flips between images back and forth)

[Jim Popovitch (jimpop)]

On Thu, Oct 8, 2009 at 13:36, Loïc Minier <email address hidden> wrote:
> @jimpop: on which release are you seeing which package work perfectly?

linux-image-2.6.31-12-generic
psb-kernel-source-4.41.6-0ubuntu1~910
xserver-xorg-video-0.31.0-0ubuntu1~904

Yes, I know those are 2D packages... but they produce stunningly
clear, and vibrant, HD quality for non DRM vids. I wish I had an HD
camera to shoot the quality that those drivers produce on the AO751h.

-Jim P.

[Jim Popovitch (jimpop)]

Wow, apparently no one can say it better than this guy:

http://www.happyassassin.net/2009/01/30/intel-gma-500-poulsbo-graphics-on-linux-a-precise-and-comprehensive-summary-as-to-why-youre-screwed/

[Jim Popovitch (jimpop)]

Video improvement for full screen HD video, set "DefaultDepth 16" in your xorg.conf

[amichair (amichai2)]

@jimpop: how would one go about installing these great drivers on a fresh Karmic release? btw maybe u should contact the author of that blog (from almost a year ago) with your discoveries, see if u can make sense of it together and maybe push this forward?

[Jim Popovitch (jimpop)]

@amichair: see port #44 in this thread for the installation steps. The author of that blog post is spot-on. I did a deep-dive of the source and it is a mess, mostly due to it's age. Linux DRM (Direct Rendering Manager) has changed a lot since the psb code was written... and at this point it's going to take a re-write to get it up to par. As i understand it, there is an effort underway to do just that.

[amichair (amichai2)]

thanx, that last paragraph about errors got me thinking that's not the final solution. So the current solution works perfectly, but has horrible code? if it works, isn't that enough to include it in the standard repos?

I'm glad to hear at least there's an effort on the way to rewrite... from the post and this thread it sounded like no one wants to touch it.

[Jim Popovitch (jimpop)]

I honestly don't know why Ubuntu MOTU wouldn't include something, from a previous release, that works in the current release. I often suspected politics as a LOT of the formal Ubuntu replies/comments are rather questionable (i.e. "Intel won't support the psb on Karmic", as if Intel would support a driver in any specific Linux distro.)

[ridgerunner7 (ridgerunner7)]

sounds like help is on the way

http://www.phoronix.com/scan.php?page=news_item&px=NzY2Mg

[TomaszChmielewski (mangoo-wpkg)]

Will poulsbo / gma500 be supported in Ubuntu 10.04 / Lucid?

[mtv (mtv)]

I checked the Ubuntu 10.04 / Lucid alpha-3 / on an AspireOne 751h (11.6 ").
Intel gma500 not supported. 1366x768 Resolution not work.

[Timo Aaltonen (tjaalton)]

the right thing to do here is to close the bug, -psb is not coming back in the foreseeable future.

[Jmadero (jmadero)]

This is crazy....netbooks are the fastest growing computer type and it's just going to be ignored by the Ubuntu developers? Seems like a poor decision

[Loïc Minier (lool)]

This is not getting ignored; we're waiting for an opensource driver or some public up-to-date proprietary bits. Please only comment here if you have some technical comments on the bug.

[pst007x (turone)]

This is a nightmare, however I searched and got 2d working ok, 3d appears to be installed but does not operate or allow any desktop visual effects.

ACER ASPIRE ONE ZA3
I am running Linux kernel version 2.6.31-19
Ubuntu 9.10 Karmic

Ubuntu is awesome, could be the best OS out there, but it is the little things like this that devalues all the hard work the Ubuntu team and community.

Apple and Microsoft dominate the PC market, if Ubuntu got their act together they would not stand a chance!

I used the following sequence:

Ubuntu 9.10 and Netbook MSI Wind: Graphic not working
Hey ubuntu users, i found the solution for the problem on http://inpec-web.de/index.php/2010/0...e-1/#comment-6

Heres the englisch Version of what I did for Ubuntu Karmic Koala Desktop Edition 2.6.31-19-generic #56-Ubuntu (might also work with NBR :

First do an Ubuntu Update, then type to terminal

gksu gedit /etc/apt/sources.list.d/mobile.list

and add the following sources

deb http://ppa.launchpad.net/ubuntu-mobile/ppa/ubuntu karmic main

deb-src http://ppa.launchpad.net/ubuntu-mobile/ppa/ubuntu karmic main

deb http://ppa.launchpad.net/ubuntu-mobile/ppa/ubuntu jaunty main

deb-src http://ppa.launchpad.net/ubuntu-mobile/ppa/ubuntu jaunty main

deb http://ppa.launchpad.net/lucazade/gma500/ubuntu/ karmic main

deb-src http://ppa.launchpad.net/lucazade/gma500/ubuntu/ karmic main

deb http://ppa.launchpad.net/lucazade/gma500/ubuntu karmic main
deb-src http://ppa.launchpad.net/lucazade/gma500/ubuntu karmic main

then do ‘apt-get update’
then
sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 99D6B21CC6598A30
sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys F5F2A6FE6699F3D9

then install the driver with

sudo apt-get install psb-kernel-source psb-firmware poulsbo-driver-3d poulsbo-driver-2d

Then enter sudo gedit /etc/modprobe.d/blacklist.conf
and just add the line“blacklist i915″

Now you have to edit the
gksu gedit /etc/X11/xorg.conf (might be empty)

XORG.CONF

Section "Device"
        Identifier "GMA500"
        Driver "psb"
        Option "DownScale" "false"
        Option "ExaNoComposite" "false"
        #Option "ExaMem" "131072"
 #Option "ExaScratch" "4"
 #Option "ExaCached" "false"
        Option "IgnoreACPI" "true"
        Option "LidTimer" "false"
        Option "NoAccel" "false"
        Option "NoFitting" "false"
        Option "NoPanel" "false"
        Option "MigrationHeuristic" "greedy"
        Option "ShadowFB" "false"
        Option "SWcursor" "false"
        Option "Vsync" "false"
EndSection

Section "DRI"
 Mode 0666
EndSection

Section "Extensions"
 Option "Composite" "Enable"
 Option "RENDER" "Enable"
EndSection

The next step is

sudo gedit /usr/srv/psb-kernel-source4.41.*/intel_lvds.c
in my case the star is 6.

Now search with CTRL & F “static int intel_lvds_get_modes(struct drm_output *output)” and comment

if (edid)
drm_add_edid_modes(output, edid);
these lines out so it looks like this:
/* if (edid) */
/* drm_add_edid_modes(output, edid); */
Now do
sudo dpkg-reconfigure psb-kernel-source

and reboot.

The last step:

sudo gedit /usr/bin/compiz

search for

WHITELIST="nvi...

[Richard Ulrich (richi-paraeasy)]

Using the script from :
https://wiki.ubuntu.com/HardwareSupportComponentsVideoCardsPoulsbo/
with Karmic I get:
- Correct Resolution
- Compiz Working
- GoogleEarth speed acceptable
- Video Playback acceptable (could be better)
- Builtin Audio is broken, Bluetooth or USB audio works, where the quality is good over bluetooth, but bad with two USB soundcards tested.

Really looking forward to a good driver.

[m0dcm (dave-maydew)]

You'll be lucky, it doesn't look like Canonical are going to support the GMA500 in future releases of Ubuntu! It's quite upsetting as there are Netbook users like us that want to use Ubuntu, especially the latest version upon release, and we can't! What I'd like to know is how Jolicloud have managed to do it, and with full video accelleration, and Canonical can't.

Please Canonical get a GMA500 driver working in 10.04, we want to stick with Ubuntu as it's the Operating System of choice, and Intel Embedded Devices are not going away!!!

[Jeremy Bícha (jbicha)]

m0dcm, you act as though this is Canonical's problem but it isn't. It takes a lot of luck, time, and work to reverse engineer drivers when you don't have any cooperation from the ones that built the hardware. The ones who built the hardware haven't bothered to release newer drivers that work on the video stack used in Lucid. Maybe they will in a few months as the Linux kernel 2.6.32 happens to be an important release. My advice is to reinstall Karmic as many have had luck with getting the drivers working there, or if you like Jolicloud, you can use that (Jolicloud is built on Karmic any way; that's why it works, it's not Canonical being lazy or incompetent or malicious).

[rth. (rth.)]

Let us collect money to pay the developers!

Is there an organisation which takes care of the users needs? Which collects money to forward them to the developers, so that they can work for us, the users?

[m0dcm (dave-maydew)]

Canonical should be looking out for their Users! and the Linux Foundation should too!!!!!
I did read something that "In November 2009, the Linux Foundation released the details of a new, rewritten Linux driver that would support this chipset and Intel's other upcoming chipsets. The Direct Rendering Manager and X.org parts would be free software, but the 3D component (using Gallium3D) will still be proprietary." and more news from Phoronix about this from November 2009 can be found here, http://www.phoronix.com/scan.php?page=news_item&px=NzY2Mg
But as you know, there's NOTHING that's been done.

I know I had a very ignorant reply back from Intel about the GMA500 driver, saying that it's down to the Distrobution to fix the problem. Maybe we (all GMA500 users) should all send a message to Intel to get them to do something.....

[resplin (resplin)]

Instructions for getting a Dell Mini 10 working with both Karmic and Lucid are in my blog:

http://richard.esplins.org/siwi/2010/01/16/kubuntu-karmic-dell-mini-10/

The Karmic instructions are distilled from comments on this bug report.

The Lucid instructions come from the script discussed at this page:

http://code.google.com/p/gma500/wiki/InstallScript

Thank you to those who made it possible to get this working!

[D (dj-lp)]

Here's how you even get hardware video decoding acceleration: http://linux-tipps.blogspot.com/2010/06/setting-up-vaapi-hardware-accelerated.html.