If the same 3D X server works with FastX and not with TigerVNC, then the problem is not with the 3D X server. That means that anything related to xorg.conf and the Xorg modules is probably a red herring. I would focus on the environment and the dynamic linker. Compare the output of ‘env’ in a FastX vs a TigerVNC session. Compare ‘vglrun ldd /opt/VirtualGL/bin/glxsheres’ in both sessions. Try explicitly setting VGL_GLLIB=/usr/lib/libGL.so.1 in the environment.
> On Aug 29, 2020, at 11:50 PM, Jake Carroll <[email protected]> wrote: > > Hi. > > Thanks for getting back to me. So - for clarity - the TigerVNC host/daemon > actually does run on the same nodes - but it is only TigerVNC that seems to > have the problem. FastX (whatever it does/however it works!) does not seem to > have the issue and it happily accelerates OpenGL out of the box just fine. > > You mentioned the LD_LIBRARY_PATH before and possibly that Tiger is > referencing the wrong libs. I found this floating around... > > From here and a few other places: > > https://gist.github.com/shehzan10/8d36c908af216573a1f0 > > They recommend the following: > > sudo mv /usr/lib/xorg/modules/extensions/libglx.so > /usr/lib/xorg/modules/extensions/libglx.so.orig > sudo ln -s /usr/lib/xorg/modules/extensions/libglx.so.XXX.YY > /usr/lib/xorg/modules/extensions/libglx.so > > Have you ever seen anything like this before? I have not tried it as yet. > > Thanks again. > >> On Sunday, August 30, 2020 at 1:41:13 PM UTC+10 DRC wrote: >> xorg.conf only affects the 3D X server. It isn’t clear from your message >> whether TigerVNC is running on the same machines as FastX. If it is not, >> then a bad xorg.conf could be the problem on the TigerVNC machines. The >> first thing I would try is accessing the GPU through the 3D X server on >> those machines without using VGL (see the “Sanity Check” section in the >> User’s Guide.) If you meant that TigerVNC is running on the same machines as >> FastX, then perhaps, for some reason, the TigerVNC customizations set >> LD_LIBRARY_PATH to point to a Mesa implementation of libGL rather than the >> GPU-accelerated version. Also double check that the StrudelWeb environment >> isn’t doing something stupid like setting VGL_DISPLAY to the 2D X server >> rather than the 3D X server. >> >>>> On Aug 29, 2020, at 9:56 PM, Jake Carroll <[email protected]> wrote: >>>> >>> Hi. >> >>> >>> I think I need a little bit of VirtualGL help. >>> >>> We've got an installation of FastX running on our SLURM controlled AMD Rome >>> nodes. The systems have 4 * nVidia T4 GPU's contained within. >>> >>> Using FastX + VirtualGL sessions works perfectly with MATE. So well, that >>> users often say how happy they are with it. >>> >>> However - we also run a custom TigerVNC based platform too, called >>> StrudelWeb. This was a local development. The problem we've got is that, >>> despite the same xorg.conf and everything else we can think of - the >>> TigerVNC sessions launched via Strudel do not seem to be able to use >>> anything but the llvmpipe MESA path. We can run some environmental >>> variables within such that VGL_LOGO=1 or similar exports absolutely pop up >>> the "VGL" logo in our X display windows over our Strudel Tiger VNC sessions >>> (glxspheres shows the VGL logo etc) but it is absolutely using the software >>> renderer. What we can't figure out is why VirtualGL + Tiger VNC won't pick >>> up the nvidia hardware or xorg config, but using FastX with an identical >>> xorg.conf seems to work perfectly. >>> >>> I'd post my xorg.conf but I don't want to fill this post with mess until >>> someone advice where I should start/what to look for first. >>> >>> So far I've tried a few things, including this in the xorg.conf: >>> >>> Option "UseDisplayDevice" "none" >>> >>> Which seems to have broken everything entirely (the nVidia T4 is a headless >>> GPU). >>> >>> I also looked at this: >>> >>> https://gist.github.com/shehzan10/8d36c908af216573a1f0 >>> >>> And thought it might help - but it assumes no implementation of something >>> like VirtualGL, so I wondered how relevant it was. >>> >>> So - I'm trying to work out what might be wrong with my remote launched >>> remote TigerVNC session via Strudel. >>> >>> For reference on what Strudel actually "is"... >>> >>> https://trac.version.fz-juelich.de/vis/wiki/vnc3d/strudel >>> >>> Thank you for your time. >>> >>> Regards, >>> >>> -jc >> >>> -- >>> You received this message because you are subscribed to the Google Groups >>> "VirtualGL User Discussion/Support" group. >>> To unsubscribe from this group and stop receiving emails from it, send an >>> email to [email protected]. >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/virtualgl-users/d84f788d-3566-4e6f-8dc5-9a31be944d19n%40googlegroups.com. > > -- > You received this message because you are subscribed to the Google Groups > "VirtualGL User Discussion/Support" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/virtualgl-users/44cd3102-0c60-4265-9f2b-223e43096a41n%40googlegroups.com. -- You received this message because you are subscribed to the Google Groups "VirtualGL User Discussion/Support" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/virtualgl-users/A57B5E3C-803C-408A-BD6F-054B4BB986B0%40virtualgl.org.
