On Fre, 2002-09-06 at 02:10, Jos� Fonseca wrote: 
> 
> I'm not a Radeon developer but I'll gonna try to help you regarding DRI.

I missed this one somehow...


> On Tue, Sep 03, 2002 at 11:00:08AM +0200, Didier Moens wrote:
> [...]
> > 
> > / Using stock RHL 7.3 XFree86 4.2.0 :
> > 
> > * with DRI enabled (from stock DRI up to the latest CVS), there is are
> > severe screen artefacts when running VMware (http://www.vmware.com) in
> > full screen mode ; VMware's technical support people (of whom I have no
> > reason to believe they are technically impaired, rather to the contrary)
> > say they adhere to (DGA2 ?) standards.
> > This screen corruption is mitigated by moving the mouse pointer or
> > scrolling windows contents ; with DRI disabled, no corruption occurs.
> > On request, I can supply a screenshot illustrating this behaviour.
> 
> I'm not sure what's the DGA support status of the existing DRI drivers.
> Please check if there is a way to disable DGA support on VMWARE
> and try it to see if that problem is really DGA related. If not on
> VMWARE, it's possible to turn off DGA extension support on XF86Config-4 
> (I don't know it by heart by I can find that out for you).

Maybe DGA isn't broken but 2D acceleration with DRI enabled.

One way to work around the problem would be to run two servers, one with DRI
enabled and another one without for VMware.


> > * glxgears performance is limited to approx. 500 fps ; this seems rather
> > below par to me, wrt. to benchmarks of equivalent Radeon desktop models
> > (700-1000 fps).

glxgears isn't really a meaningful benchmark, 4.2.0 was slower than the current
DRI drivers, and Mobility chips are slower than desktop chips.


> > / Using Xree86 20020829 :
> > 
> > * same screen corruption as with stock XFree 4.2 ;

Can you try again with a 20020906 or later snapshot? I've cleaned up 2D
acceleration with DRI enabled and fixed some bugs.


> > * with the DRI nightly binary driver packages, when running glxinfo,
> > glxgears, ... I get a message about TCL being disabled, after which a
> > segmentation fault occurs. All pointers to libGL.so seem correct ;

Where did that libGL.so come from?

> > * with a freshly compiled DRI CVS20020830, I can run glxinfo (please
> > find it below, LIBGL_DEBUG=verbose), but glxgears opens a window with
> > some (perhaps not so) random garbage, and locks the computer hard (no
> > Alt-SysRq).

That was a known problem with chips without a TCL unit. It's been fixed
for VEs at least, we're still looking for feedback with an M6. Again,
please try a current DRI snapshot and post your experience to the
dri-devel list.


-- 
Earthling Michel D�nzer (MrCooper)/ Debian GNU/Linux (powerpc) developer
XFree86 and DRI project member   /  CS student, Free Software enthusiast

_______________________________________________
Xpert mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xpert

Reply via email to