RE: GLX problem from SGI to Linux

New Message Reply Date view Thread view Subject view Author view

From: Brian Corrie (brian.corrie++at++newmic.com)
Date: 01/09/2002 09:03:54

All,

Although I am not an expert, I "think" I at least marginally know what is
going on here... I am sure someone at SGI could clarify more precisely.

It is my understanding that Performer (and many OpenGL apps that run on
SGIs) use SGI specific OpenGL extensions. In particular, DGL or distributed
GL (???), is an X protocol extension that SGI uses to perform some rendering
capabilities on the remote X server. In particular, I seem to remember
running an app on an Octane at one point and displaying it on an Onyx (why
one might do this is another story 8-) and getting the anti-aliasing quality
of the Onyx even though the app was running on the Octane. This implies that
the app was using the SGI Onyx hardware to perform the rendering... It may
have been my imagination, but that seems to have been the case.

Thus when you display an app that uses these DGL (and other SGI specific)
extensions on a machine with an X server that does not support DGL you get a
VendorPrivate X extension error.

That is my take on it... I would love to hear the real story from someone a
bit more knowledgable 8-)

        Brian

> Hello,
>
> When you 'setenv DISPLAY' some SGI applications want a 4DWM window
> manager running
> on the target machine. I think Performer is such an application.
>
> Mario
>
> Robert Nitti wrote:
> >
> > Hi,
> >
> > When I try to run an OpenGL app from an SGI to a Linux box
> (via "setenv
> > DISPLAY mylinuxmachine:0"), i get the following error
> below. I did an
> > "xhost +" on the Linux side to accept the X commands. Can
> anyone tell me
> > why this is?
> >
> >
> > X Error of failed request: GLXUnsupportedPrivateRequest
> > Major opcode of failed request: 142 (GLX)
> > Minor opcode of failed request: 17 (X_GLXVendorPrivateWithReply)
> > Serial number of failed request: 824
> > Current serial number in output stream: 824
> >
> >
> >
> > When I do a "setenv DISPLAY mylinuxmachine:0" and type
> "glxinfo" i also get
> > the following:
> >
> > display: mylinuxmachine:0
> > X Error of failed request: GLXUnsupportedPrivateRequest
> > Major opcode of failed request: 142 (GLX)
> > Minor opcode of failed request: 17 (X_GLXVendorPrivateWithReply)
> > Serial number of failed request: 16
> > Current serial number in output stream: 16
> >
> >
> > My SGI is running 6.5.14f. My Linux box is running RH 7.0
> with Mesa 3.4-13
> > with an Nvidia card (the Mesa GL libs [libGL, libGLcore]
> were replaced by
> > the Nvidia ones).
> >
> > Thanx
> > Robert
> >
> >
> >
> --------------------------------------------------------------
> ---------
> > List Archives, Info, FAQ: http://www.sgi.com/software/performer/
> > Open Development Project: http://oss.sgi.com/projects/performer/
> > Submissions: info-performer++at++sgi.com
> > Admin. requests: info-performer-request++at++sgi.com
> >
> --------------------------------------------------------------
> ---------
> --------------------------------------------------------------
> ---------
> List Archives, Info, FAQ: http://www.sgi.com/software/performer/
> Open Development Project: http://oss.sgi.com/projects/performer/
> Submissions: info-performer++at++sgi.com
> Admin. requests: info-performer-request++at++sgi.com
> --------------------------------------------------------------
> ---------

New Message Reply Date view Thread view Subject view Author view

This archive was generated by hypermail 2b29 : Wed Jan 09 2002 - 09:02:16 PST

This message has been cleansed for anti-spam protection. Replace '++at++' in any mail addresses with the '@' symbol.