I have reached a point with this where it is impossible to go any
further without the app. The issue does not appear to be related to
Mono, as I am able to bring up the Tao OpenGL examples with no problem
using VirtualGL and TurboVNC. I have created a tracker item here:
https://sourceforge.net/t
Another user ran into this same issue and attempted all of my proposed
fixes below. None worked. At this point I'm stymied. I'm going to try
bringing up a simple C# OpenGL demo in mono, but if I can't get that to
fail in the same way, I don't know what else can be done without the app.
On 4/15
Hi,
Thanks for your help. I will try those solutions after vacations.
Kind regards
David
El 15/04/2011 12:17, DRC escribió:
> David,
>
> We seem to have stalled out on this, and there were a lot of rapid-fire
> e-mails exchanged between you and Nathan, in which multiple things were
> tried and mu
David,
We seem to have stalled out on this, and there were a lot of rapid-fire
e-mails exchanged between you and Nathan, in which multiple things were
tried and multiple interleaved results posted, so this e-mail is my
attempt to summarize what we know. I would encourage everyone involved
to atte
Hi,
I postponed this issue due to other tasks coming over.
Anyway I put here the procedure to reproduce the "extension GLX" issue.
I've tried using TurboVNC, X forwarding and cygwin-X.
1.- Launch "runwb2" with "vglrun".
2.- The workbench opens well. In the case of TurboVNC the color depth is
po
On 11-03-29 04:52 PM, DRC wrote:
> NOTE: that error can also be displayed when attempting to use VirtualGL
> with an executable that is setuid root, but I can't imagine that that
> would be the case with ANSYS. It could be, however, that one of the
> executables that the launcher130 script invoke
NOTE: that error can also be displayed when attempting to use VirtualGL
with an executable that is setuid root, but I can't imagine that that
would be the case with ANSYS. It could be, however, that one of the
executables that the launcher130 script invokes is setuid root.
I don't know if there'
On 11-03-23 09:48 AM, r...@englobe-tec.com wrote:
>
> When using launcher130 I get the following error, does it give any light
> on the issue?
>
> ERROR: ld.so: object 'librrfaker.so' from LD_PRELOAD cannot be
> preloaded: ignored.
It means the system couldn't find librrfaker.so or couldn't find a
When using launcher130 I get the following error, does it give any
light on the issue?
ERROR: ld.so: object 'librrfaker.so' from LD_PRELOAD cannot be
preloaded: ignored.
--
Enable your software for Intel(R) Active Mana
The exact output that I get when trying through ssh is:
$ /opt/VirtualGL/bin/vglrun runwb2
[VGL] NOTICE: Automatically setting VGL_CLIENT environment variable
to
[VGL]10.1.255.247, the IP address of your SSh client.
Xlib: extension "NV-GLX" missing on display "localhost:10.0".
Xlib: ext
BODY { font-family:Arial, Helvetica, sans-serif;font-size:12px;
}Hello!
I tried with the same result.
I've also tried accessing through ssh X forwarding, also with the
same result.
Thanks
David
On Mon 8:31 PM , "DRC" dcomman...@users.sourceforge.net sent:
Did you try renaming the version
Did you try renaming the version of libGL.so.1 that is installed by the
application?
On 3/21/11 11:45 AM, r...@englobe-tec.com wrote:
> I've tried this and there are new lines in the output.
>
> [VGL] WARNING: The OpenGL rendering context obtained on X display
> [VGL]:0.0 is indirect, which
I've added -d :1.0 to the vglrun in the script and the output changed
to:
[VGL] WARNING: The OpenGL rendering context obtained on X display
[VGL]:1.0 is indirect, which may cause performance to suffer.
[VGL]If :1.0 is a local X display, then the framebuffer device
[VGL]permissions
BODY { font-family:Arial, Helvetica, sans-serif;font-size:12px;
}I've tried this and there are new lines in the output.
[VGL] WARNING: The OpenGL rendering context obtained on X display
[VGL]:0.0 is indirect, which may cause performance to suffer.
[VGL]If :0.0 is a local X display, the
BTW, if you can't make sense from ld.log another simple way is to put
the vglrun command inside the runwb2 script (prefix the mono command).
That will narrow down if mono is unhappy or it is the script.
-Nathan
On 11-03-17 12:28 PM, r...@englobe-tec.com wrote:
> Hi Nathan,
> I wish a good heali
Yes, that is quite possible.
http://sourceforge.net/mailarchive/forum.php?thread_name=201009161641.14204.nate%40hpcintegrators.com&forum_name=virtualgl-users
and
http://sourceforge.net/tracker/?func=detail&aid=3005112&group_id=117509&atid=678327
may shed some insight. Some things to try (in th
Seems like my previous messages didn't reach the list (perhaps due
to the attachments) I reproduce here the last one. Regarding to
this... could be that the libGL.so.1 used by ANSYS (installed into
its directory) has a diferent version or is conflicting with the one
provided by the system?
**
Seems like my previous messages didn't reach the list (perhaps due
to the attachments) I reproduce here the last one. Regarding to
this... could be that the libGL.so.1 used by ANSYS (installed into its
directory) has a diferent version or is conflicting with the one
provided by the system?
BODY { font-family:Arial, Helvetica, sans-serif;font-size:12px;
}I've checked that vglgears runs well with vglrun through TurboVNC.
This confirms that the problem is reduced to the concrete application.
On Thu 4:50 PM , "Nathan Kidd" nathan...@spicycrypto.ca sent:
On 11-03-17 07:55 AM, wrote
body { font-family: Arial,Helvetica,sans-serif; font-size: 12px; }Hi
Nathan,
I wish a good healing for you. Thanks for your time and efforts.
I sent the log in another mail but it seems like it was blocked
somewhere
I'll go further with this since I really want to use my 3D
accelerator remote
On 11-03-17 07:55 AM, r...@englobe-tec.com wrote:
> "LD_PRELOAD=librrfaker.so ls" returned the usual ls output (no error
> messages there). So I atach ld.log files to this mail.
>
> Using LD_DEBUG_OUTPUT to something like ld.log kept returning that grep
> output in the console, even unsetting +tr o
BODY { font-family:Arial, Helvetica, sans-serif;font-size:12px; }Hi
Nathan,
"LD_PRELOAD=librrfaker.so ls" returned the usual ls output (no error
messages there). So I atach ld.log files to this mail.
Using LD_DEBUG_OUTPUT to something like ld.log kept returning that
grep output in the console,
On 37-01--10 02:59 PM, r...@englobe-tec.com wrote:
> I've tried the suggestions you gave:
>
> 1.- Adding -oglhw gave no apparent result
>
> 2.- Adding those 2 lines to the script added the following lines to the
> output:
>
> libdlfaker.so:librrfaker.so
> /ansys_inc/v130/Framework/bin/Linux64:/ansy
On 11-03-15 02:43 PM, DRC wrote:
> The root of the problem is that VirtualGL is not being engaged for some
> reason,
> With any application-specific issue like this, if I can't immediately
> discern what is happening by reading the trace output, the only other
> recourse is to get a copy of the ap
The root of the problem is that VirtualGL is not being engaged for some
reason, so the application is trying to send GLX commands directly to
TurboVNC (which fails, because TurboVNC doesn't have the GLX extension,
as you saw below when you tried to run glxinfo without vglrun.)
Adding +v +tr to the
You're missing vglrun. Please read the docs.
On 3/15/11 11:55 AM, r...@englobe-tec.com wrote:
> Hi all,
> I'm having problems to use VirtualGL in a server. I have a NVIDIA Quadro
> FX 4800. When running ANSYS 13.0 workbench from TurboVNC I get this
> message in the output:
>
> extension "GLX" m
For the record, these people seem to be doing fine with Intel cards
and VirtualGL:
http://trac.nchc.org.tw/grid/wiki/VirtualGL_UsageNote
2009/11/22 Jose Rodriguez :
> 2009/11/22 DRC :
>> OK, so perhaps I should have said it doesn't have "full 3D
>> acceleration", but the result is the same. Mo
2009/11/22 DRC :
> OK, so perhaps I should have said it doesn't have "full 3D
> acceleration", but the result is the same. Most built-in Linux drivers
> are "2.5D" accelerated at best.
>
> Let me put this another way-- the 3D driver must support Pbuffer-enabled
> FB configs in order to work in a V
OK, so perhaps I should have said it doesn't have "full 3D
acceleration", but the result is the same. Most built-in Linux drivers
are "2.5D" accelerated at best.
Let me put this another way-- the 3D driver must support Pbuffer-enabled
FB configs in order to work in a VirtualGL server. NVIDIA and
2009/11/21 DRC :
> This adapter is not using 3D acceleration. Note that the OpenGL
> renderer is Mesa. That's software OpenGL. You need
> hardware-accelerated OpenGL, which is only going to come from an NVidia
> or ATI adapter with the vendor's 3D drivers installed.
I have to disagree with you
This adapter is not using 3D acceleration. Note that the OpenGL
renderer is Mesa. That's software OpenGL. You need
hardware-accelerated OpenGL, which is only going to come from an NVidia
or ATI adapter with the vendor's 3D drivers installed.
Jose Rodriguez wrote:
> 2009/11/21 DRC :
>> What is t
2009/11/21 DRC :
> What is the output of /opt/VirtualGL/bin/glxinfo -c on display :0?
> Please post.
I wouldn't be surprised if the card wasn't up to the task. I found a
thread in a graphics forum where a developer mentions that "[he has]
an application that uses pbuffers and if the pbuffer
size i
What is the output of /opt/VirtualGL/bin/glxinfo -c on display :0?
Please post.
On Nov 21, 2009, at 4:38 AM, Jose Rodriguez
wrote:
> 2009/11/21 DRC :
>> Not having accelerated 3D drivers installed is the most obvious
>> cause of
>> that VirtualGL error message. Just because GLX exists doe
2009/11/21 DRC :
> Not having accelerated 3D drivers installed is the most obvious cause of
> that VirtualGL error message. Just because GLX exists doesn't mean that
> Pbuffers are available. In general, you have to install the vendor
> drivers for the 3D graphics card in order to get Pbuffers.
Not having accelerated 3D drivers installed is the most obvious cause of
that VirtualGL error message. Just because GLX exists doesn't mean that
Pbuffers are available. In general, you have to install the vendor
drivers for the 3D graphics card in order to get Pbuffers. The output
of '/opt/Virtu
If the 3D-enabled X server is not listening on display :0, then you need
to set the VGL_DISPLAY environment variable to whatever display it is
listening on, e.g.:
export VGL_DISPLAY=:1
Or you can simply pass this to vglrun, e.g.
vglrun -d :1 {your app}
Jose Rodriguez wrote:
> Hello.
>
> I
I'm trying to get this working but I don't see where the problem is. I
didn't have any *dm so I installed one to be sure that there is a
'real' X server running. Then I started vncserver from
/opt/TurboVNC/bin:
ps aux | grep X
root 2251 0.2 2.8 13012 7144 tty7 Ss+ 19:33 0:03
/usr/
37 matches
Mail list logo
