Using Mesa from git commit d2f19a554a9089fddb5e978e3a732bbf71d77f93 X.Org 7.3 from openSUSE BuildService, drm from git commit 79744d730c90019edd367eee4a8ec1fa22d53402 and kernel 2.6.23.1 (with or without drm modules from git) AIGLX cannot start and gives the following error message: (EE) AIGLX error: dlsym for __driCreateNewScreen_20050727 failed (/usr/lib/dri/i915_dri.so: undefined symbol: __driCreateNewScreen_20050727) (EE) AIGLX: reverting to software rendering In the MESA GIT tree I found that the links in src/mesa/drivers/dri/i9{1,6}5/server/ are not correct (one level missing). This concerns intel_dri.c, and three other files in the 965 directory. But changing these links did not change anything.
It's not loading because the module versions are incompatible. You need to build X from git master to use Mesa from git master.
(In reply to comment #1) > It's not loading because the module versions are incompatible. You need to > build X from git master to use Mesa from git master. > Hi one question is not the opposite ? You need to build Mesa from git master to build X from git master. I don't had time to test it, but with xorg-server 1.4 I will try use mega git master , like , we do normally , DRI development normally is based on a X server stable . the opposite is not true (I think)
(In reply to comment #2) > (In reply to comment #1) > > It's not loading because the module versions are incompatible. You need to > > build X from git master to use Mesa from git master. > > Hi one question is not the opposite ? > You need to build Mesa from git master to build X from git master. This is true. And, to use AIGLX, your X server and Mesa versions must match. > I don't had time to test it, but with xorg-server 1.4 I will try use mega git > master , like , we do normally , DRI development normally is based on a X > server stable . > the opposite is not true (I think) You can't. The DRI interface changed massively.
Mass version move, cvs -> git
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.