[SOLVED] OpenGL doesn't work on X-Win32 with SLES11

timvandijk039 · 07-06-2010, 08:15 AM

I didn't have any luck finding the solution for not getting opengl working on a SLES11 server with a remote X-Win32 client. As a reference I've used the tool "glxgears" for testing.

We have two servers. One (server A) with SLES10 and the other (server B) with SLES11. We use X-Win32 (ver. 9.x) as an X-server on a Microsoft Windows client machine. Both servers are connected to with ssh with X11 forwarding enabled (Xclock works fine on both).

Starting glxgears from server A works fine; Three nice gears are displayed. Doing exactly the same on server B however results in the following error:

Code:

glxgears: Error: couldn't get an RGB, Double-buffered visual.

When I run glxinfo the output is:

Code:

server-B:~ # glxinfo
name of display: localhost:13.0
Error: couldn't find RGB GLX visual

   visual  x  bf lv rg d st colorbuffer ax dp st accumbuffer  ms  cav
 id dep cl sp sz l  ci b ro  r  g  b  a bf th cl  r  g  b  a ns b eat
----------------------------------------------------------------------
0x23 16 tc  1  0  0 c  .  .  0  0  0  0  0  0  0  0  0  0  0  0 0 None
0x24 16 tc  1  0  0 c  .  .  0  0  0  0  0  0  0  0  0  0  0  0 0 None
0x25  8 pc  1  0  0 c  .  .  0  0  0  0  0  0  0  0  0  0  0  0 0 None
0x26  8 pc  1  0  0 c  .  .  0  0  0  0  0  0  0  0  0  0  0  0 0 None

There are no errors of warning messages in the X-server logs (X-Win32).

I'm stuck at the moment and in need of assistance.
Thanks in advance for any replies.

timvandijk039 · 09-23-2010, 07:44 AM

We finally figured out a solution for the problem above. For the benefit sharing knowledge with others I'll post some directions for those us who came across the same problems as we did.

The problem were the new OpenGL libraries used in SLES11.2. The XWin32 clients we used (version 8 and 9) couldn't handle the OpenGL requests from the SLES11.2 server. An upgrade to XWin32 version 2010 solved our problem.

Thanks to those people taking the time in reading my post and finding a solution!