Re: [Dri-devel] Maya Testing on New Radeon Driver

SourceForge Headquarters 225 Broadway Suite 1600 San Diego, CA 92101 +1 (858) 454-5900

Ian Romanick wrote:
> 
> On Sat, Apr 06, 2002 at 09:42:36AM -0700, Brian Paul wrote:
> > Ian Romanick wrote:
> > >
> > > Also, I just noticed that when Maya starts up it logs the following message
> > > in its "script editor" windows.  It repeats four times.
> > >
> > > // Warning: Unable to get OpenGL visual with a depth buffer, trying without //
> > >
> > > What would be the easiest way for me to figure out exactly what type of
> > > visual it is trying to get?
> >
> > Modify glXChooseVisual() to print the attribute tokens/values as the list
> > is parsed.  It would be interesting to know what it's looking for.
> >
> >
> > >  This may not be important because it only
> > > happens when I run w/a 16-bpp display.
> 
> The issue is that Maya is requesting at least 23-bits of Z-buffer.  In
> 16-bit mode, we only have 16-bits of Z-buffer, so it can't find a visual.
> On the Radeon, is depth bpp == color bpp a hardware limitation or just the
> way the drivers were done?

Probably just the way it was done.  It would be fairly easy to allow an
XF86Config option for zbuffer depth, but quite a bit more work to support 16
and 32 bpp side-by-side.

> In other news, I tried (using CVS as of the morning of 4/9) running in
> 1152x864 and "maximizing" the Maya (so that it would fit) and running in
> Maya's expected 1280x1024.  In both cases, I hit the following assertion:
> 
> radeon_vtxfmt.c863: radeonFlushVertices: Assertion `vb.installed' failed.
> 
> #0  0x432b4a01 in __kill () from /lib/i686/libc.so.6
> #1  0x432b47da in raise (sig=6) at ../sysdeps/posix/raise.c:27
> #2  0x432b5f82 in abort () at ../sysdeps/generic/abort.c:88
> #3  0x432ae120 in __assert_fail () at assert.c:74
> #4  0x466c5a02 in radeonFlushVertices (ctx=0x89fb070, flags=2)
>     at radeon_vtxfmt.c:863
> #5  0x466c3a9e in VFMT_FALLBACK_OUTSIDE_BEGIN_END (
>     caller=0x466db7cb "radeonNewList") at radeon_vtxfmt.c:335
> #6  0x4658f227 in _mesa_NewList (list=514, mode=4864) at dlist.c:4765
> #7  0x430b94e9 in DRI_glXUseXFont (font=25167761, first=0, count=256,
>     listbase=513) at xfont.c:343
> 
> I can try to provide any other info that might be helpful.  Just let me know
> what is needed.

I committed a fix for a similar-sounding problem today - it would be
interesting to see if this has changed.

Keith