CLASSIFICATION: UNCLASSIFIED Utkarsh,
I am running ParaView 5.0.1 connecting to a remote ParaView 5.0.1 server built
with osmesa
And I have rebuild osmesa from both
Mesa 11.1.2 and Mesa 11.2.2 using
./configure \
--disable-xvmc \
--disable-glx \
--disable-dri \
--with-dri-drivers= \
--with-gallium-drivers=swrast \
--enable-texture-float \
--disable-egl \
--enable-shared \
--with-egl-platforms= \
--enable-gallium-osmesa \
--enable-gallium-llvm=yes \
--prefix=<install prefix>
And I have tried replacing the library
lib/paraview-5.0/libOSMesa.so.7
with both libOSMesa.so from 11.1.2 and 11.2.2
and they are both still giving the same error
paraview/VTK/Rendering/OpenGL2/vtkOpenGLRenderWindow.cxx line 587
vtkOSOpenGLRenderWindow GL Version 2.1 with the gpu_shader4 extension is not
supported by your graphics driver, but is required for the new OpenGL rendering
backend. Please update your OpenGL driver.
If you are using Mesa please make sure you have version 10.6.5 and make sure
your driver support OpenGL 3.2
Any suggestions?
Thanks,
Joe Hennessey
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Joseph G. Hennessey Ph.D., Lockheed Martin Army Research Lab DOD Supercomputing
Resource Center
120 Aberdeen Blvd.
Aberdeen Proving Ground, MD 21005
Voice: 410-278-3619
Fax: 410-278-8799
Email: [email protected]
-----Original Message-----
From: ParaView [mailto:[email protected]] On Behalf Of Angelini,
Richard C (Rick) CIV USARMY RDECOM ARL (US)
Sent: Thursday, June 02, 2016 1:45 PM
To: Utkarsh Ayachit <[email protected]>
Cc: ParaView <[email protected]>
Subject: Re: [Paraview] [Non-DoD Source] Re: 5.0.1/Exodus Reader
All active links contained in this email were disabled. Please verify the
identity of the sender, and confirm the authenticity of all links contained
within the message prior to copying and pasting the address to a Web browser.
----
Utkarsh - thanks - in the mean time, we're going to try to build Mesa 11.1 (?)
outside of ParaView and link it in and see how far we can get! 8-) But it
would certainly be cleaner to use the Superbuild when you get that updated with
the proper Mesa build!
-----Original Message-----
From: Utkarsh Ayachit [Caution-mailto:[email protected]]
Sent: Thursday, June 02, 2016 1:18 PM
To: Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US)
<[email protected]>
Cc: Chuck Atkins <[email protected]>; ParaView <[email protected]>
Subject: Re: [Paraview] [Non-DoD Source] Re: 5.0.1/Exodus Reader
Roger that. I will have updates for you early next week (plan to work on it as
soon as I am done with the task at hand).
On Thu, Jun 2, 2016 at 12:45 PM, Angelini, Richard C (Rick) CIV USARMY RDECOM
ARL (US) <[email protected]> wrote:
> Our *immediate* concern is OSMesa - but we'll probably eventually want to
> address Mesa w/X support .....
>
> -----Original Message-----
> From: Utkarsh Ayachit [Caution-mailto:[email protected]]
> Sent: Thursday, June 02, 2016 9:48 AM
> To: Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US)
> <[email protected]>
> Cc: Chuck Atkins <[email protected]>; ParaView
> <[email protected]>
> Subject: Re: [Paraview] [Non-DoD Source] Re: 5.0.1/Exodus Reader
>
> Ah okay. Give me a few days to sort it out. The end goal is indeed to have
> superbuild build the right versions of Mesa. Do you only care about OSMesa
> or also Mesa with X support?
>
> Utkarsh
>
>
>
>
> On Thu, Jun 2, 2016 at 8:48 AM, Angelini, Richard C (Rick) CIV USARMY RDECOM
> ARL (US) <[email protected]> wrote:
>> Our current issues seem to be related to our osmesa build for the HPC_side
>> servers. The Superbuild is building 7.11.2 - you are suggesting that
>> we need to *manually* build a different version of Mesa and somehow link
>> in that new version of Mesa in to the Superbuild? We rely exclusively
>> on the Superbuild for compiling ParaView across 20 different HPC
>> systems - so stepping outside of the super build paradigm isn’t necessarily
>> obvious
>> to me! 8-)
>>
>>
>>
>>
>>
>> ________________________________
>> Rick Angelini
>> USArmy Research Laboratory
>> CISD/HPC Architectures Team
>> Phone: 410-278-6266
>>
>>
>>
>>
>> -----Original Message-----
>> From: Utkarsh Ayachit <[email protected]>
>> Date: Thursday, June 2, 2016 at 8:37 AM
>> To: Rick Angelini <[email protected]>
>> Cc: Chuck Atkins <[email protected]>, ParaView
>> <[email protected]>
>> Subject: Re: [Paraview] [Non-DoD Source] Re: 5.0.1/Exodus Reader
>>
>> All active links contained in this email were disabled. Please
>> verify the identity of the sender, and confirm the authenticity of
>> all links contained within the message prior to copying and pasting
>> the address to a Web browser.
>>
>>
>>
>>
>> ----
>>
>>> So there is much more to be done than adding
>>> -DPARAVIEW_RENDERING_BACKEND:STRING=OpenGL2
>>> -DVTK_RENDERING_BACKEND:STRING="OpenGL2"
>>> to the cmake flags?
>>
>> As far as ParaView is concerned, no there's not much more to it.
>> However if your OpenGL implementation doesn't support OpenGL 3.2
>> (released in 2009), then alas there's more work to get ParaView
>> working which could include building a newer version of Mesa. Not
>> sure if you have seen this blog [1], but that talks about how I got
>> Mesa to build with appropriate OpenGL renderer enabled. Things have
>> gotten a little better since then and the Docker script encapsulates
>> that. The moral of the story is get latest Mesa version and build it
>> with LLVM/Gallum support.
>>
>> Utkarsh
>>
>> [1]
>> Caution-Caution-https://blog.kitware.com/messing-with-mesa-for-paravi
>> ew-5-0vt
>> k
>> -7-0/
>>
CLASSIFICATION: UNCLASSIFIED
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Search the list archives at: http://markmail.org/search/?q=ParaView Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview
