Indirect rendering problems with 260.12.06 and 285GTX

kbios · 10-26-10, 12:16 PM

I'm trying to run some GL apps through ssh (indirect rendering). The card is a 285GTX, drivers are 260.12.06. Glxgears and blender work, but others (bzflag and etracer, for example) crash with

Code:

X Error of failed request:  BadLength (poly request too large or internal Xlib length error)
  Major opcode of failed request:  136 (GLX)
  Minor opcode of failed request:  2 (X_GLXRenderLarge)
  Serial number of failed request:  14605
  Current serial number in output stream:  14648

as soon as they try to setup the 3d scene (menu works). Both server and client are running Kubuntu 10.10 amd64.
I'm attaching nvidia-bug-report.log.gz, glxinfo output and Xorg.log.
Thanks for any help

**AaronP** · 10-27-10, 12:56 PM

Your glxinfo.log file shows that you're using the Mesa version of libGL on the cilent side. Does the problem go away if you use the NVIDIA libGL instead? This is likely to be a bug in the Mesa indirect GLX protocol handling.

kbios · 10-27-10, 02:58 PM

Hi AaronP, thanks for your answer. I tried copying /usr/lib/nvidia-current/* to the server (application server, so the glx client), but this makes every gl program segfault. Maybe this is because the server has no nvidia video card or driver (actually, it is a virtual machine)? Is there another way of using nvidia's libgl? Thanks

**AaronP** · 10-27-10, 04:02 PM

You need to make sure you copy over the correct TLS library too, which usually lives in /usr/lib/tls, but given that your libGL was in the wrong place (/usr/lib/nvidia-current instead of the standard /usr/lib), you may find it somewhere else.

The NVIDIA client-side libraries should work for indirect GLX rendering even on systems without NVIDIA hardware.

kbios · 10-28-10, 09:17 AM

Thanks, that worked

The tls libs on my system are still in /usr/lib/nvidia-current, but in the initial copy I didn't include subdirectories and that messed up everything. Now it is working properly. Also a big thank you to the NVIDIA engineer who decided to implement (although unofficially) OpenGL 2 through GLX.

10-27-10, 12:56 PM	#2
AaronP NVIDIA Corporation Join Date: Mar 2005 Posts: 2,487	Re: Indirect rendering problems with 260.12.06 and 285GTX Your glxinfo.log file shows that you're using the Mesa version of libGL on the cilent side. Does the problem go away if you use the NVIDIA libGL instead? This is likely to be a bug in the Mesa indirect GLX protocol handling.

10-27-10, 02:58 PM	#3
kbios Registered User Join Date: Oct 2010 Posts: 3	Re: Indirect rendering problems with 260.12.06 and 285GTX Hi AaronP, thanks for your answer. I tried copying /usr/lib/nvidia-current/* to the server (application server, so the glx client), but this makes every gl program segfault. Maybe this is because the server has no nvidia video card or driver (actually, it is a virtual machine)? Is there another way of using nvidia's libgl? Thanks

10-27-10, 04:02 PM	#4
AaronP NVIDIA Corporation Join Date: Mar 2005 Posts: 2,487	Re: Indirect rendering problems with 260.12.06 and 285GTX You need to make sure you copy over the correct TLS library too, which usually lives in /usr/lib/tls, but given that your libGL was in the wrong place (/usr/lib/nvidia-current instead of the standard /usr/lib), you may find it somewhere else. The NVIDIA client-side libraries should work for indirect GLX rendering even on systems without NVIDIA hardware.

10-28-10, 09:17 AM	#5
kbios Registered User Join Date: Oct 2010 Posts: 3	[SOLVED] Indirect rendering problems with 260.12.06 and 285GTX Thanks, that worked The tls libs on my system are still in /usr/lib/nvidia-current, but in the initial copy I didn't include subdirectories and that messed up everything. Now it is working properly. Also a big thank you to the NVIDIA engineer who decided to implement (although unofficially) OpenGL 2 through GLX.