On 11-03-24 07:04 AM, Chen Bill wrote:
> I have a problem trying to run Animator4 with vglrun.
>
> It seems it doesn't work even I use vglrun.
>
> When I run "vglrun a4" it just like I use "a4".
>
>
> error messages:
> =================================================
> QGLContext::makeCurrent(): Cannot make invalid context current.
> QGLContext::makeCurrent(): Cannot make invalid context current.
> QGLContext::makeCurrent(): Cannot make invalid context current.
> QGLContext::makeCurrent(): Cannot make invalid context current.
> QGLContext::makeCurrent(): Cannot make invalid context current.
> QGLContext::makeCurrent(): Cannot make invalid context current.
> QGLContext::makeCurrent(): Cannot make invalid context current.
> QGLContext::makeCurrent(): Cannot make invalid context current.
> QGLContext::makeCurrent(): Cannot make invalid context current.
> QGLContext::makeCurrent(): Cannot make invalid context current.
> Xlib:  extension "GLX" missing on display ":1.0".
> Xlib:  extension "GLX" missing on display ":1.0".
>
> Goodbye from Animator4
> =================================================
>
> Any suggestions?

 From those messages it seems that a4 does some internal checks and 
doesn't like it when VGL redirects and/or modifies certain GLX state.

You can run with +tr (VGL_TRACE) option to see if you can find out what 
VGL was doing when a4 became unhappy.  To determine this the writes from 
a4 and VGL trace need to be in order, but depending on where a4 writes 
to (stdout/stderr) they may not be written that way.

In the past I've used a script like this to force the output to be 
interleaved:

------------------------
#!/bin/sh

# run inside `script` to force unbuffered writes so the log is 
interleaved between app and VGL lines

LD_LIBRARY_PATH=. \
VGL_LOG=/dev/stdout \
VGL_TRACE=1 \
LD_PRELOAD=librrfaker.so \
VGL_COMPRESS=proxy \
VGL_VERBOSE=1 \
script -c "./glxinfo32" /dev/null

-------------------------

You'll need to change:
  a) LD_LIBRARY_PATH to the path where you have librrfaker.so (32 or 
64-bit depending on a4)
  b) /dev/stdout potentially to /dev/stderr
  c) ./glxinfo32 to the path to a4

You don't need to use vglrun in this case.


-Nathan

------------------------------------------------------------------------------
Enable your software for Intel(R) Active Management Technology to meet the
growing manageability and security demands of your customers. Businesses
are taking advantage of Intel(R) vPro (TM) technology - will your software 
be a part of the solution? Download the Intel(R) Manageability Checker 
today! http://p.sf.net/sfu/intel-dev2devmar
_______________________________________________
VirtualGL-Users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/virtualgl-users

Reply via email to