Re: [Paraview] gpu_shader4 extension is not supported

2017-07-05 Thread Patrick Begou
I'm starting again this thread as I still have a problem with mesa (and so all mesa advices will be in the same discussion). Now it is on a server with an AMD Firepro GPU. The Centos6.9 mesa version is too old (mesa-libGL-10.4.3-1.el6.x86_64). Installing a new el6 mesa rpm

Re: [Paraview] gpu_shader4 extension is not supported

2017-05-23 Thread Burlen Loring
Sweet! On 05/23/2017 12:51 AM, Patrick Begou wrote: Thanks a lot Burlen, all is running fine now with this setup for mesa on the front-end. With Paraview, I had to add some parameters for ffmpeg-3.3 libraries that were not automaticaly loaded and set LD_LIBRARY_PATH to load llvm is a separate

Re: [Paraview] gpu_shader4 extension is not supported

2017-05-23 Thread Patrick Begou
Thanks a lot Burlen, all is running fine now with this setup for mesa on the front-end. With Paraview, I had to add some parameters for ffmpeg-3.3 libraries that were not automaticaly loaded and set LD_LIBRARY_PATH to load llvm is a separate directory from mesa but all runs fine now: export

Re: [Paraview] gpu_shader4 extension is not supported

2017-05-17 Thread Burlen Loring
- one build for the front end with GUI: it has no GPU but a windowing system (this is the blocking point at this time) OK. to accomplish this, first do a Mesa build configured as follows(glx+software rendering) ../mesa-17.0.6/configure --enable-texture-float --enable-glx --disable-dri

Re: [Paraview] gpu_shader4 extension is not supported

2017-05-17 Thread Patrick Begou
Yes Burlen, this is exactly what I try to do: - one build for the nodes whitout GUI as they have no windowing system nor GPU (I build this using the wiki documentation) - one build for the front end with GUI: it has no GPU but a windowing system (this is the blocking point at this time) - one

Re: [Paraview] gpu_shader4 extension is not supported

2017-05-16 Thread Burlen Loring
that's the point. this allows you to run without the windowing system or GPU on the cluster. Most cluster have neither. If you wanted to provide the GUI then I would suggest you have two installs of both ParaView and Mesa. One based on OSMesa, the other based on some X11 enabled OpenGL.

Re: [Paraview] gpu_shader4 extension is not supported

2017-05-16 Thread Patrick Begou
Burlen Loring wrote: ../mesa-17.0.2/configure --enable-texture-float --disable-glx --disable-dri --disable-egl --disable-gles1 --disable-gles2 --disable-gbm --disable-driglx-direct --disable-xvmc --enable-gallium-osmesa --with-gallium-drivers=swrast,swr

Re: [Paraview] gpu_shader4 extension is not supported

2017-05-16 Thread Patrick Begou
Hi Burlen, I think there is a main concept that I do not understand in building Paraview and Mesa as I have also all the wiki pages printed in front of me since the begining. It is how to build paraview on a server without GPU _but_ with Paraview GUI enabled. With the Wiki I was able to build

Re: [Paraview] gpu_shader4 extension is not supported

2017-05-15 Thread Burlen Loring
Hi Patrick, Your output shows you enabled some gpu specific drivers, and GLX. I think that is going to screw things up for you. Best to disable all of them but the ones you specifically need and to explicitly disable glx. Here is how I configured OSMesa for a Cray

Re: [Paraview] gpu_shader4 extension is not supported

2017-05-15 Thread Patrick Begou
Hi Chuck, Hi Burlen Thanks for your reply. I've attached the setup of my mesa installation. I have more options enabled in my config than in yours. May be too much as this frontend has no GPU available. I'll try a setup with -DVTK_USE_X=OFF as Burlen suggest, but is it possible to build

Re: [Paraview] gpu_shader4 extension is not supported

2017-05-12 Thread Burlen Loring
Hi Patrick, OSMesa (and friends such as OpenSWR) do not need to make use of GLX. In fact I think it should be disabled completely for that case in both Mesa and ParaView builds. For eg, when you configure ParaView you'd specify -DVTK_USE_X=OFF. At least this is how it was in the past. I