Re: XQuartz 2.5.0_rc2
Re: XQuartz 2.5.0_rc2
- Subject: Re: XQuartz 2.5.0_rc2
- From: Jeremy Huddleston <email@hidden>
- Date: Wed, 07 Apr 2010 22:49:37 -0700
There is a bug in your remote mesa.
See https://bugs.freedesktop.org/show_bug.cgi?id=24226
You should be able to do it via:
LIBGL_ALWAYS_INDIRECT=1 glxgears
That works for me.
On Apr 7, 2010, at 19:17, James Gunning wrote:
> Dear Jeremy,
> thanks for all your great work on Xquartz. I'm running the latest 2.5.0.
> I wonder if you can send to the list some clarification (or a URL) about remote openGL.
>
> I find at present I can't get a glxgears from a remote linux box to work
> with any combination of
> LIBGL_ALWAYS_SOFTWARE
> LIBGL_ALWAYS_INDIRECT
> LIBGL_ALWAYS_HARDWARE
>
> at present.
>
> With LIBGL_ALWAYS_INDIRECT unset
> glxinfo gives me
> name of display: localhost:10.0
> Error: couldn't find RGB GLX visual or fbconfig
>
> with LIBGL_ALWAYS_INDIRECT set, glxinfo seems OK:
> ...
> name of display: localhost:10.0
> display: localhost:10 screen: 0
> direct rendering: No (LIBGL_ALWAYS_INDIRECT set)
> server glx vendor string: SGI...
> ....
>
>
> But glxgears yields
> X Error of failed request: BadAlloc (insufficient resources for operation)
> Major opcode of failed request: 147 (GLX)
> Minor opcode of failed request: 3 (X_GLXCreateContext)
> Serial number of failed request: 20
> Current serial number in output stream: 22
>
> In previous versions, I got remote openGL to work OK via LIBGL_ALWAYS_INDIRECT.
> I'm doubtless confused. Any clarifications welcome.
>
> Very best wishes,
> James.
>
> <James_Gunning.vcf> _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> X11-users mailing list (email@hidden)
>
> This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
X11-users mailing list (email@hidden)
This email sent to email@hidden