I've included the output from glxinfo in the attached file.
The machines are using version 2.3.3. I will upgrade them both to 2.4 beta
and see if that helps.
I'll reread the background document and see if it sinks in better this
time.
$ /opt/VirtualGL/bin/glreadtest
GLreadtest v2.3.3 (Build
Several things clicked in my head whenever I saw the output from
GLXinfo. Your 3D X server is on display :20, which tells me that it's
probably not the root X server (sorry if I missed that before.) If
there are multiple 3D X servers running on the machine, then you have to
either:
-- make
I am running TurboVNC and VirtualGL (v2.3.3) on two linux machines running
Ubuntu 10.4. I start up a TurboVNC server on the remote machine. I
connect to that server with a TurboVNC viewer. When I run 'vglrun
glxgears' i get:
x$ vglrun glxgears
Running synchronized to the vertical refresh.
Hi Nathan,
Thanks for getting back to me. I don't believe I'm using a binary driver,
the NVIDIA X server settings say Driver version 331.49. I also don't
believe I'm switching virtual consoles. When I login remotely, the system
acts as though there aren't any XServer functions connected to it.
I agree the 3D X server is always running. That was why I was supprised
that remotely logging in I don't get the 3D X server functionality. I only
used the -d option to hijack the 3D X server functionality from another
display. What I can't figure out is why the 3D X server runs when you log
in
Your question doesn't make sense, which means that either you aren't
choosing your words correctly or you still don't understand how the
system is supposed to work. What do you mean by running? The 3D X
server is completely independent of TurboVNC. They are different X
servers. VirtualGL
Thanks, I appreciate you putting up with me.
I agree, my wording is very inaccurate. In general, I program applications
on top of systems, but I've been tasked to set up TurboVNC/virtualgl so
here goes. Please forgive me for using incorrect terms, I'll try my best.
Machine 1 has TurboVNC and
