On Sat, 2010-03-06 at 14:10 +0200, Maxim Levitsky wrote:
> On Sat, 2010-03-06 at 11:18 +0100, Florian Mickler wrote:
> > On Fri, 05 Mar 2010 23:48:48 +0200
> > Maxim Levitsky <maximlevit...@gmail.com> wrote:
> >
> > > On Fri, 2010-03-05 at 13:36 -0800, Jesse Barnes wrote:
> > > > On Fri, 05 Mar 2010 23:18:07 +0200
> > > > Maxim Levitsky <maximlevit...@gmail.com> wrote:
> > > >
> > > > > On Fri, 2010-03-05 at 12:55 -0800, Jesse Barnes wrote:
> > > > > > On Fri, 05 Mar 2010 22:42:21 +0200
> > > > > > Maxim Levitsky <maximlevit...@gmail.com> wrote:
> > > > > >
> > > > > > > After quite long period of inactivity, I updated graphical stack
> > > > > > > on my
> > > > > > > desktop/server.
> > > > > > >
> > > > > > > To say the truth, I did such update about month ago, but found
> > > > > > > out that
> > > > > > > X refuses flatly to use DRI modules. I assumed that it was my
> > > > > > > mistake in
> > > > > > > compilation process (although it is automated).
> > > > > >
> > > > > > That generally indicates a build or config problem of some kind.
> > > > > > Did
> > > > > > you ever narrow it down?
> > > > > Because the same compile process works now, I suspect that wasn't
> > > > > build
> > > > > failure.
> > > >
> > > > Well something weird is going on; maybe you didn't build X after Mesa
> > > > or with the right Mesa includes?
> > > I am very sure that this issue isn't relevant now.
> > >
> > > I do compile (libdrm, mesa, xserver, xf86-intel, and evdev driver in
> > > that order, compiling everything from scratch (doing git clean -dfx in
> > > all directories)
> >
> > if you just want a working setup, perhaps you should try using
> > something that got (probably) tested by at least some people:
> > http://intellinuxgraphics.org/2009Q4.html
> > cheers,
> > Flo
>
> Well, I now have a working setup with mesa
> ebbc73d1aed283c9bc4aa2b37bed4374bbaec5b5
>
> The problem is that I hoped that once all heavy work in regard to KMS
> was done, there will be no serious regressions in 3D stack, but only bug
> fixes, because it is very hard to track and fix bugs there.
>
> However, once again 3D stack is in bad shape, and this is not good.
More testing shows the following behaviour:
Full screen mode is completely busted. As soon as any 3D application
switches to full screen mode, even without changing the resolution, it
hangs (note that I didn't see GPU hangs due to that)
Compiz is broken (its also a full screen app...). As soon as it starts,
it draws few windows, and then stalls.
In window mode all applications do work.
Now I guess this is worth a bugzilla entry.
(If this isn't there yet...)
Best regards,
Maxim Levitsky
------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Mesa3d-dev mailing list
Mesa3d-dev@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mesa3d-dev
