X fails to load psb module on Lucid

EXA module has been updated (from EXA Classic to MIxed)
In your xorg.log i see also some old settings no more usefull.

Try to reinstall PSB drivers from scratch following updated instruction in the wiki.

Ok, I've done this (reinstalled the drivers), but still have the same error (though a diff on the logfiles shows that there are a few slight differences). Latest log attached.

Are there other config settings which I must set manually? My xorg.conf file is pretty basic (monitor, screen, dri, and device sections -- dri mode 0666, and device driver "psb").

ABI mismatch is strange, should not happen because drivers are compiled against latest xorg version.
i've attached the xorg.conf created automatically by poulsbo-config... it's really simple and *should* not need any other tweaks.

Could you try also the Lucid Livecd with gma500 support to see if this issue is present?
http://linuxtracker.org/index.php?page=torrent-details&id=f0b262a10d2a4401a4641cb01aef44c8fbccd051
I'd like to isolate your issue.

I tried the iso image, and it *does* work. I looked at the logfiles, and it appears that the only difference is that the exa module on my system is compiled for an older version of X. The question is where this module is coming from -- is it something leftover from a previous install, and if so, why isn't it replaced by one of the x or psb packages?

Looking in /usr/lib/xorg/modules/, it is clear that this is the problem, since the modification time of libexa.so is from 2010-04-29, and for libexa.so.xserver-xorg-video-psb it is recent.

Supposedly the xserver-xorg-core package provides the libexa.so library... I tried reinstalling xserver-xorg-core, but it doesn't change the modification time / size of libexa.so at all (size is 63268 bytes) -- however, in the package itself the mtime of libexa is 2010-07-21. So I guess that apt isn't overwriting/replacing libexa (permissions on libexa are normal, so that's not the problem). Hopefully that helps some in coming up with a solution. (of course I can just manually replace libexa and it should work, but it would be better to have a solution which works for users who may have also gotten their system into a similar state, and don't know what to do about it).