Re: [Chromium-users] Chromium GLX problem at the slavenode: problem still there after fixing GLX

[Sean A. <ah...@or...>]

Okay, quick question.  Can you run (and see) glxgears on every display
involved?  I get the feeling that you don't have a complete setup on
your cluster.

If the GLX extension is missing on any of your displays, you will have
trouble doing any OpenGL, let alone Chromium.

Being root won't matter one way or the other.

-Sean

__
Sean Ahern
Oak Ridge National Laboratory
865-241-3748

Michelle Chu wrote:
> Hello, there,
> First of all, I would like to thank Dale and Sean for your suggestions. I
> downloaded MegaLib and installed it at my slave node. Now, I can run glxinfo
> succesfully, glxgears command  generates a openGL window with spinning
> gears. Command xdpyinfo | grep -i glx` gives NV-GLX
> 
> 
> However, when i tried to run the demo atlantis at the slave node by typing:
> python crdemo.conf atlantis &
> it runs ok,
> then i typed: crserver &
> still shows: CR warning: oscarnode7: Render SPU: Display :0.0 doesn't
> support GLX
> CR warning: Render SPU: couldn't get a visual, renderspu_SystemInitVisual
> failed
> CR warning: Render SPU: couldn't create a window, renderspu_FindVisual
> return NULL
> CR error: Render SPU: Couldn't get a double-buffered RGB visual with Z!
> 
> 
> I noticed that on one of my  chromium working slave node, xdpyinfo |grep -i
> glx gives GLX, and NV-GLX.  Could the missing GLX cause the problem in the
> above case?
> 
> BTW, i am using root account when typing these above commands.
> 
> Michelle