Mar 20, 2019 The list of drivers including its major properties and below tables with a features matrix: Great responsiveness for the specs, but youtube sucks on html5. Intel GMA Driver Optimized for MS Windows: Linux on GMA. Partners Support Community Ubuntu. Sudo add-apt-repository ppa:gma500/ppa sudo apt-get update. Technical details.
Pmarques2014-05-11 21:44:58 UTCI have a embedded PC system here that has an Atom Z510. The system includes a GMA500 graphics chip.The display is connected through the LVDS port and has a resolution of 1024x768.The system works ok in Windows and painfully slowly in Linux with the vesa driver, but without any flicker.Using the gma500 driver, the pixel clock seems to be half of what it should be (measured with an oscilloscope).
When the image is good the pixel clock is around 65MHz. When the gma500 driver sets the resolution the pixel clock goes to around 32MHz. This gives a frame rate of around 30Hz which explains the horrible screen flicker. The performance is quite good, though.I tried running xrandr to create new modes, but the pixel clock is always wrong, no matter what I tried.The kernel version is 3.12.1. I looked at the git repository log to see if anything changed in the meanwhile that could affect this, but nothing popped up.Can you give me some pointers to what I should try next? Some obscure kernel parameter?
Do you need more information?The linux graphics system changed a bit over the last few years (KMS, etc.) and I missed some of the changes, so please bare with me if I ask silly questions.Thanks in advance for any help. Linuxuser-05-18 18:23:18 UTCI have the same issue on an ASUS Eee PC 1101HA running Ubuntu 14.04 LTS.The screen starts to flicker around 30 seconds after the gma500gfx.ko kernel module is loaded.This happens both on the console (no X started) and then X started.The flicker is changing.
When it starts it hits the screen like a storm. Then it 'stabilizes' at a lower flicker rate.Graphics performance is good with the gma500gfx.ko accelerator, but I found no way to get rid of the flickering.When vesafb is used, no flickering occurs. But vesafb is tied to the VESA modes listed in the BIOS, and sadly 1366x768 is missing, so instead 1024x768 is used which results in a wrong aspect ratio. It's also very slow.I don't know what Ubuntu 12.04.4 does differently, but with the previous LTS version of Ubuntu this flickering does not occur.Hopefully this will be fixed soon. Pmarques2014-05-20 23:23:09 UTCI can try to bisect (although it will be slightly painful), but unlike linuxuser330250 I didn't find a kernel version that actually works with this machine.I always tried to install complete distributions to avoid kernel/Mesa/whatever version incompatibilities, but all the distros I tried either worked with VESA (too old) or had the flicker issue (more recent).
IIRC some had the gma500 driver with flicker and poor video playback performance, but the most recent ones only seem to have the flicker issue.linuxuser330250, can you point me to the version of Ubuntu that worked for you so that I can try it too? At least if that works I'll have a starting point for bisecting.Thanks in advance,Paulo Marques. Linuxuser-05-22 20:13:33 UTCThere are some interesting pages about the Poulsbo IGP:Seems that 12.04 also uses the gma500gfx.ko. My time is limited right now, but I will report back in a few weeks, as I plan to downgrade from Ubuntu 14.04 to 12.04 and I will check 1) kernel version and 2) gma500 driver on 12.04.I did run 12.04 on this netbook before I upgraded to 14.04, and there was definitely no flicker.pmarques, please report if you have luck with 12.04.4.Patrik Jakobsson, thanks for working on it (soon). Why was stoked cancelled. Linuxuser-06-03 21:52:23 UTCI've installed 12.04.4 again on my system and the flicker is NOT there.
It was there with 14.04. (I can run the 14.04 installer again to see it flicker.)On 14.04 however the flicker starts after about 15 to 25 seconds, so it is not there right from the start.Logically, there definitely happend something between those versions. I have to get the logs and post them, please stand by for this.Question: HOW should I find out, what is wrong, or rather: different with 14.04 compared to 12.04.4? Linuxuser-06-04 18:39:52 UTCStatus?My ASUS EeePC 1101HA has an Intel Atom Z520 processor @1.33GHz and a US15W Ultra Mobile chipset. This very chipset includes an IGP called Intel GMA500 or Poulsbo, which really is a PowerVR SGX 535 embedded graphics core.Links that might be of interest:QUESTIONS:1) Why does it flicker at all?2) Why does it flicker in at least one case (linuxuser) on 14.04 but not on 12.04.4 of Ubuntu?3) Why does it flicker on every Linux in another case (pmarques)?4) What can we do about it and how to proceed?Notably there are various bug reports of users with the Poulsbo chipset graphics having similar problems. Patrik Jakobsson2014-06-04 21:25:24 UTCHi, thanks for all the infoIt seems there are two different issues.
One regression and one that probably is as old as the driver itself.I have an ASUS1201HA that I can test with to see if I suffer from the same problem. In that case I can bisect it.
If not I have written a regdumper that I'll post somewhere (if I can find it) that can give us a clue about what is wrong.With that said, I have no idea when I'll have time to look at this. Hopefully soon but my backlog just keeps growing at the moment. If you're in a hurry, the only advise I can give you is to dig into the code yourself.ThanksPatrik. Pmarques2014-06-04 23:21:23 UTCOne thing I noticed on the Xorg.log I posted is that at some point it has this. 25.686 (II) modesetting(0): Modeline '1024x768'x30.1 1048 1184 1344 768 771 777 806 (24.2 kHz P).So, it seems that the system knows it is working at 30.1 Hz (instead of 60Hz), but all my attempts to use xrandr to convince the display to go to 60Hz didn't work. I don't rule out that I might have been doing something wrong, though.I can try to look at the code, but all the code under 'drivers/gpu/drm/gma500' is around 30k lines.
Intel Gma 500 Driver Download
Can you at least give me some pointers at which files I should look at first? Are they even in this directory?