On 04/07/2012 01:12 AM, Devin Bougie wrote:
> Hi, All.  We're seeing a problem running opengl on a remote SL6
> system when the local system uses the proprietary nvidia drivers.  > This does not seem to be a problem with remote SL5 systems.
>
> The problem seems to only be when sitting at a local system with
> the nvidia drivers (tested with local SL5, SL6, and OS X) and
> running opengl on a remote SL6 system that doesn't have the nvidia
> drivers.
>
> I think the example below probably demonstrates this better than my
> description.  Any suggestions would be greatly appreciated, and please
> let me know if there is any more information we can provide.

Unfortunately I don't have any magical answer for you, but I can confirm 
that I can't reproduce this between Radeon HD 6310s and 4250s.

I do have a suspicion about what might be wrong, though...

Does the nVidia driver setup create an /etc/X11/xorg.conf during a 
post-install step? I SL6 doesn't have one by default but SL5 did. If 
something about the chipset or other detail of the X11 setup you've got 
is not detected correctly by default (as in, not detected correctly 
during the boot-time auto Xorg config step) then you might get problems. 
If the proprietary driver installation includes an xorg.conf creation 
step, however, this may be fixing the problem on the system with that 
driver installed, and thus produce this disparity.

I imagine that some chipsets will have this problem and some won't 
(regardless of maker), depending on how well the open source driver 
supports the specific chipset you've got.

I'm unclear on exactly how this impacts X11 forwarding, but this is an 
issue we danced around a bit on multi-head systems until we got our 
driver support sorted out (and subsequently we've stuck with the same 
few chip families from one maker now to narrow down our issues and 
knowledge requirement -- because no-3D is a show-stopper for us).