DRI issues

[Bob Raymond]

dep wrote:
> begin  Bob Raymond's  quote:
> 
> | No response from him, but the status of this has changed a bit now.
> | I've got the appropriate driver, etc. (a cvsup'ing did the trick),
> | DRI loads, but I get segfaulting when I try anything GLX. Running
> | xpdyinfo gives me "XFree86-DRI" so I assume I'm OK there.  I
> | shudder to think what will happen when a screensaver loads.
> 
> what does it say when you do glxinfo? we're looking for something like 
> this up top:
> 
> name of display: :0.0
> display: :0  screen: 0
> direct rendering: Yes
> server glx vendor string: SGI
> server glx version string: 1.2

I get:

rraymond at EPoX rraymond $ glxinfo
name of display: :0.0
r200CreateScreen
Segmentation fault

> there has also been a *big* issue that i think is attributable to some 
> gl implementations. for instance, some what appear to be utter locks 
> of suse 8.1; in my experimentation here, though, it is utter locks 
> brought on by xscreensavers and some vid cards and the current xfree 
> shipped by suse. otoh, on my matrox g-400 with recent cvs xfree, 
> there has been no such problem.

I don't get locks, the screensaver (in my case, "Pipes - another," just 
doesn't come up (blank screen).


				Bob Raymond