<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic 2023.1.x Errata: OSPRay runtime resolution fixes on linux in Intel® Rendering Toolkit</title>
    <link>https://community.intel.com/t5/Intel-Rendering-Toolkit/2023-1-x-Errata-OSPRay-runtime-resolution-fixes-on-linux/m-p/1480280#M101</link>
    <description>&lt;P&gt;2023.1.x OSPRay troubleshoot and workarounds.&lt;/P&gt;
&lt;P&gt;See details below on each of these issues.&lt;/P&gt;
&lt;P&gt;1. libomp not found&lt;/P&gt;
&lt;P&gt;2. libospray undefined symbols&lt;/P&gt;
&lt;P&gt;3. libze_loader (level-zero) not found&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;Issue 1:&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;On 2023.1.x release of the RenderKit, when running an OSPRay based program, you may observe an error like:&lt;/P&gt;
&lt;PRE class="code-java"&gt;&lt;SPAN class="code-quote"&gt;'could not open module lib ospray_module_cpu: libomp.so: cannot open shared object file: No such file or directory'&lt;/SPAN&gt;&lt;/PRE&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Resolution:&lt;/P&gt;
&lt;P&gt;Please ensure that the OpenMP library, libomp.so, is visible for the dynamic loader. You may install this library via a package like &lt;STRONG&gt;libomp-dev&lt;/STRONG&gt;&amp;nbsp;and &lt;STRONG&gt;libomp5&lt;/STRONG&gt; on Ubuntu 22.04 OS, however, the installer places this runtime in non-default runtime library search paths. The fix is to add the path to your linker search path.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Fix Example on Ubuntu 22.04:&lt;/P&gt;
&lt;P&gt;From a fresh terminal shell, source the environment variables for the oneAPI developer tools.&lt;/P&gt;
&lt;PRE&gt;source /opt/intel/oneapi/setvars.sh&lt;/PRE&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;This populates the LD_LIBRARY_PATH environment variable. Add the path to your libomp.so to your LD_LIBRARY_PATH. Format:&lt;/P&gt;
&lt;PRE&gt;export LD_LIBRARY_PATH=/path/to/library:${LD_LIBRARY_PATH}&lt;/PRE&gt;
&lt;P&gt;Example:&lt;/P&gt;
&lt;PRE&gt;export LD_LIBRARY_PATH=&lt;STRONG&gt;/usr/lib/llvm-14/lib&lt;/STRONG&gt;:${LD_LIBRARY_PATH}&lt;/PRE&gt;
&lt;P&gt;Note: As an alternative, you may also consider system wide edits with ld.so. See the man page for ld.so and ldconfig for details.&lt;/P&gt;
&lt;P&gt;Rerun the program:&lt;/P&gt;
&lt;PRE&gt;/opt/intel/oneapi/ospray/latest/bin/ospTutorialCpp&lt;/PRE&gt;
&lt;P&gt;Tip... Find utils are helpful if you can not find the library:&lt;/P&gt;
&lt;PRE&gt;sudo updatedb&lt;BR /&gt;locate libomp.so&lt;/PRE&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;Issue 2&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;On 2023.1.x release of RenderKit, OSPRay programs may display one of these undefined symbol errors.&lt;/P&gt;
&lt;PRE&gt;libospray.so.2: undefined symbol: _intel_fast_memcpy&lt;BR /&gt;libospray.so.2: undefined symbol: _intel_fast_memset&lt;BR /&gt;libospray.so.2: undefined symbol: __intel_cpu_feature_indicator_x&lt;/PRE&gt;
&lt;P&gt;Resolution:&lt;/P&gt;
&lt;P&gt;Symbols for the above need to be made visible for affected programs. These symbols are in libirc.so provided as part of the Intel oneAPI DPC/C++ Compiler Runtime libraries. It is simplest to install them with the compiler in the oneAPI &lt;A href="https://www.intel.com/content/www/us/en/developer/tools/oneapi/base-toolkit-download.html" target="_self"&gt;BaseKit&lt;/A&gt;.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Workaround:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;A workaround for this error is to use the LD_PRELOAD facility for the undefined symbols... example:&lt;/P&gt;
&lt;PRE&gt;LD_PRELOAD=/opt/intel/oneapi/compiler/2023.1.0/linux/compiler/lib/intel64_lin/libirc.so /opt/intel/oneapi/ospray/latest/bin/ospBenchmark&lt;/PRE&gt;
&lt;P&gt;&amp;nbsp;Or example&amp;nbsp;&lt;/P&gt;
&lt;PRE&gt;LD_PRELOAD=/opt/intel/oneapi/compiler/2023.1.0/linux/compiler/lib/intel64_lin/libirc.so /opt/intel/oneapi/ospray/latest/bin/ospTutorialCpp&lt;/PRE&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;Issue 3:&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;On 2023.1.x release of Rendering Toolkit, OSPRay programs may show a missing dependency on libze_loader. Example:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;LI-CODE lang="markup"&gt;#ospray: INVALID device --&amp;gt; Load of ospray_module_cpu failed due to: 'could not open module lib ospray_module_cpu: libze_loader.so.1: cannot open shared object file: No such file or directory'&lt;/LI-CODE&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Resolution:&lt;/P&gt;
&lt;P&gt;Related dependencies are found from a shared library object found within the&amp;nbsp;&lt;STRONG&gt;level-zero&amp;nbsp;&lt;/STRONG&gt;and&amp;nbsp;&lt;STRONG&gt;level-zero-devel&amp;nbsp;&lt;/STRONG&gt;packages.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;These packages can be accessed in a manually or with a system package . Example for manual package install:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;1) Navigate to the level-zero releases &lt;A href="https://github.com/oneapi-src/level-zero/releases" target="_self"&gt;page&lt;/A&gt;.&lt;/P&gt;
&lt;P&gt;2) Download the level-zero and level-zero-devel .deb packages. Example:&lt;/P&gt;
&lt;PRE class="code-java"&gt;wget https:&lt;SPAN class="code-comment"&gt;//github.com/oneapi-src/level-zero/releases/download/v1.9.4/level-zero_1.9.4+u18.04_amd64.deb
&lt;/SPAN&gt;wget https:&lt;SPAN class="code-comment"&gt;//github.com/oneapi-src/level-zero/releases/download/v1.9.4/level-zero-devel_1.9.4+u18.04_amd64.deb&lt;/SPAN&gt;&lt;/PRE&gt;
&lt;P&gt;3) Install the packages. Example:&lt;/P&gt;
&lt;PRE class="code-java"&gt;dpkg -i level-zero*.deb&lt;/PRE&gt;
&lt;P&gt;Tip... if you have findutils, confirm the location of libze_loader.so.1 on disk:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;LI-CODE lang="markup"&gt;sudo updatedb
locate libze_loader.so.1&lt;/LI-CODE&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;4) Try running the program again.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;LI-CODE lang="markup"&gt;ospBenchmark&lt;/LI-CODE&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;These packages are hosted on Intel maintained repositories. Instructions on deploying this dependency are found within discrete GPU setup procedures.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;If you have an Intel graphics device on the system, review setup procedures for&amp;nbsp;&lt;STRONG&gt;&lt;A href="https://dgpu-docs.intel.com/driver/client/overview.html" target="_self"&gt;'arc'&lt;/A&gt;, &lt;A href="https://dgpu-docs.intel.com/driver/installation.html#installation-procedure" target="_self"&gt;'flex'&lt;/A&gt;, and &lt;A href="https://dgpu-docs.intel.com/driver/installation.html#installation-procedure" target="_self"&gt;'max'&lt;/A&gt;&lt;/STRONG&gt; package repositories.&lt;/P&gt;
&lt;P&gt;Note that discrete GPU targeting is not available in with this release of OSPRay.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;After configuring the repository as described for setup:&lt;/P&gt;
&lt;P&gt;SUSE OS&lt;/P&gt;
&lt;PRE&gt;sudo zypper install -y level-zero level-zero-devel&lt;/PRE&gt;
&lt;P&gt;Ubuntu OS&lt;/P&gt;
&lt;PRE&gt;sudo apt-get install -y level-zero level-zero-devel&lt;/PRE&gt;
&lt;P&gt;RH OS&lt;/P&gt;
&lt;PRE&gt;sudo dnf install -y level-zero level-zero-devel&lt;/PRE&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;-MichaelC&lt;/P&gt;</description>
    <pubDate>Fri, 09 Jun 2023 20:56:14 GMT</pubDate>
    <dc:creator>Michael_C_Intel1</dc:creator>
    <dc:date>2023-06-09T20:56:14Z</dc:date>
    <item>
      <title>2023.1.x Errata: OSPRay runtime resolution fixes on linux</title>
      <link>https://community.intel.com/t5/Intel-Rendering-Toolkit/2023-1-x-Errata-OSPRay-runtime-resolution-fixes-on-linux/m-p/1480280#M101</link>
      <description>&lt;P&gt;2023.1.x OSPRay troubleshoot and workarounds.&lt;/P&gt;
&lt;P&gt;See details below on each of these issues.&lt;/P&gt;
&lt;P&gt;1. libomp not found&lt;/P&gt;
&lt;P&gt;2. libospray undefined symbols&lt;/P&gt;
&lt;P&gt;3. libze_loader (level-zero) not found&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;Issue 1:&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;On 2023.1.x release of the RenderKit, when running an OSPRay based program, you may observe an error like:&lt;/P&gt;
&lt;PRE class="code-java"&gt;&lt;SPAN class="code-quote"&gt;'could not open module lib ospray_module_cpu: libomp.so: cannot open shared object file: No such file or directory'&lt;/SPAN&gt;&lt;/PRE&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Resolution:&lt;/P&gt;
&lt;P&gt;Please ensure that the OpenMP library, libomp.so, is visible for the dynamic loader. You may install this library via a package like &lt;STRONG&gt;libomp-dev&lt;/STRONG&gt;&amp;nbsp;and &lt;STRONG&gt;libomp5&lt;/STRONG&gt; on Ubuntu 22.04 OS, however, the installer places this runtime in non-default runtime library search paths. The fix is to add the path to your linker search path.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Fix Example on Ubuntu 22.04:&lt;/P&gt;
&lt;P&gt;From a fresh terminal shell, source the environment variables for the oneAPI developer tools.&lt;/P&gt;
&lt;PRE&gt;source /opt/intel/oneapi/setvars.sh&lt;/PRE&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;This populates the LD_LIBRARY_PATH environment variable. Add the path to your libomp.so to your LD_LIBRARY_PATH. Format:&lt;/P&gt;
&lt;PRE&gt;export LD_LIBRARY_PATH=/path/to/library:${LD_LIBRARY_PATH}&lt;/PRE&gt;
&lt;P&gt;Example:&lt;/P&gt;
&lt;PRE&gt;export LD_LIBRARY_PATH=&lt;STRONG&gt;/usr/lib/llvm-14/lib&lt;/STRONG&gt;:${LD_LIBRARY_PATH}&lt;/PRE&gt;
&lt;P&gt;Note: As an alternative, you may also consider system wide edits with ld.so. See the man page for ld.so and ldconfig for details.&lt;/P&gt;
&lt;P&gt;Rerun the program:&lt;/P&gt;
&lt;PRE&gt;/opt/intel/oneapi/ospray/latest/bin/ospTutorialCpp&lt;/PRE&gt;
&lt;P&gt;Tip... Find utils are helpful if you can not find the library:&lt;/P&gt;
&lt;PRE&gt;sudo updatedb&lt;BR /&gt;locate libomp.so&lt;/PRE&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;Issue 2&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;On 2023.1.x release of RenderKit, OSPRay programs may display one of these undefined symbol errors.&lt;/P&gt;
&lt;PRE&gt;libospray.so.2: undefined symbol: _intel_fast_memcpy&lt;BR /&gt;libospray.so.2: undefined symbol: _intel_fast_memset&lt;BR /&gt;libospray.so.2: undefined symbol: __intel_cpu_feature_indicator_x&lt;/PRE&gt;
&lt;P&gt;Resolution:&lt;/P&gt;
&lt;P&gt;Symbols for the above need to be made visible for affected programs. These symbols are in libirc.so provided as part of the Intel oneAPI DPC/C++ Compiler Runtime libraries. It is simplest to install them with the compiler in the oneAPI &lt;A href="https://www.intel.com/content/www/us/en/developer/tools/oneapi/base-toolkit-download.html" target="_self"&gt;BaseKit&lt;/A&gt;.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Workaround:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;A workaround for this error is to use the LD_PRELOAD facility for the undefined symbols... example:&lt;/P&gt;
&lt;PRE&gt;LD_PRELOAD=/opt/intel/oneapi/compiler/2023.1.0/linux/compiler/lib/intel64_lin/libirc.so /opt/intel/oneapi/ospray/latest/bin/ospBenchmark&lt;/PRE&gt;
&lt;P&gt;&amp;nbsp;Or example&amp;nbsp;&lt;/P&gt;
&lt;PRE&gt;LD_PRELOAD=/opt/intel/oneapi/compiler/2023.1.0/linux/compiler/lib/intel64_lin/libirc.so /opt/intel/oneapi/ospray/latest/bin/ospTutorialCpp&lt;/PRE&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;Issue 3:&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;On 2023.1.x release of Rendering Toolkit, OSPRay programs may show a missing dependency on libze_loader. Example:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;LI-CODE lang="markup"&gt;#ospray: INVALID device --&amp;gt; Load of ospray_module_cpu failed due to: 'could not open module lib ospray_module_cpu: libze_loader.so.1: cannot open shared object file: No such file or directory'&lt;/LI-CODE&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Resolution:&lt;/P&gt;
&lt;P&gt;Related dependencies are found from a shared library object found within the&amp;nbsp;&lt;STRONG&gt;level-zero&amp;nbsp;&lt;/STRONG&gt;and&amp;nbsp;&lt;STRONG&gt;level-zero-devel&amp;nbsp;&lt;/STRONG&gt;packages.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;These packages can be accessed in a manually or with a system package . Example for manual package install:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;1) Navigate to the level-zero releases &lt;A href="https://github.com/oneapi-src/level-zero/releases" target="_self"&gt;page&lt;/A&gt;.&lt;/P&gt;
&lt;P&gt;2) Download the level-zero and level-zero-devel .deb packages. Example:&lt;/P&gt;
&lt;PRE class="code-java"&gt;wget https:&lt;SPAN class="code-comment"&gt;//github.com/oneapi-src/level-zero/releases/download/v1.9.4/level-zero_1.9.4+u18.04_amd64.deb
&lt;/SPAN&gt;wget https:&lt;SPAN class="code-comment"&gt;//github.com/oneapi-src/level-zero/releases/download/v1.9.4/level-zero-devel_1.9.4+u18.04_amd64.deb&lt;/SPAN&gt;&lt;/PRE&gt;
&lt;P&gt;3) Install the packages. Example:&lt;/P&gt;
&lt;PRE class="code-java"&gt;dpkg -i level-zero*.deb&lt;/PRE&gt;
&lt;P&gt;Tip... if you have findutils, confirm the location of libze_loader.so.1 on disk:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;LI-CODE lang="markup"&gt;sudo updatedb
locate libze_loader.so.1&lt;/LI-CODE&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;4) Try running the program again.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;LI-CODE lang="markup"&gt;ospBenchmark&lt;/LI-CODE&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;These packages are hosted on Intel maintained repositories. Instructions on deploying this dependency are found within discrete GPU setup procedures.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;If you have an Intel graphics device on the system, review setup procedures for&amp;nbsp;&lt;STRONG&gt;&lt;A href="https://dgpu-docs.intel.com/driver/client/overview.html" target="_self"&gt;'arc'&lt;/A&gt;, &lt;A href="https://dgpu-docs.intel.com/driver/installation.html#installation-procedure" target="_self"&gt;'flex'&lt;/A&gt;, and &lt;A href="https://dgpu-docs.intel.com/driver/installation.html#installation-procedure" target="_self"&gt;'max'&lt;/A&gt;&lt;/STRONG&gt; package repositories.&lt;/P&gt;
&lt;P&gt;Note that discrete GPU targeting is not available in with this release of OSPRay.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;After configuring the repository as described for setup:&lt;/P&gt;
&lt;P&gt;SUSE OS&lt;/P&gt;
&lt;PRE&gt;sudo zypper install -y level-zero level-zero-devel&lt;/PRE&gt;
&lt;P&gt;Ubuntu OS&lt;/P&gt;
&lt;PRE&gt;sudo apt-get install -y level-zero level-zero-devel&lt;/PRE&gt;
&lt;P&gt;RH OS&lt;/P&gt;
&lt;PRE&gt;sudo dnf install -y level-zero level-zero-devel&lt;/PRE&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;-MichaelC&lt;/P&gt;</description>
      <pubDate>Fri, 09 Jun 2023 20:56:14 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Rendering-Toolkit/2023-1-x-Errata-OSPRay-runtime-resolution-fixes-on-linux/m-p/1480280#M101</guid>
      <dc:creator>Michael_C_Intel1</dc:creator>
      <dc:date>2023-06-09T20:56:14Z</dc:date>
    </item>
  </channel>
</rss>

