OTOY Forums

Hi,

We just bought Octane and Modo plugin for our Linux workstation and we are eager to get started testing it our properly!

Standalone version installed and works without problems. GPU is recognised etc.

Installed the Modo 901 plugin (v2.25)
These are the issues:

1)
On Modo launch it throws an error saying Unknown command "octane.command init".

2)
When trying to license it, it misses the "Authorise" button.

3)
Opening Octane Render setup it only has 2 icons/buttons on the top - "GPU" and "images".

4
The "Octane render viewport" under the Octane menu is missing.

I tried with the latest v3 beta as well - same issues.
Initially we tried it with the DEMO version - same issues.


Workstation specs:

HP Z800 2x2,66 Hexacore Xeon
48 GB RAM
CentOS 6.7
Nvidia driver version 352.79

We look forward to get this up and running, so any help is very welcome!

Best Regards,
Henrik Mark

Hi Henrick

All these issues are effectively the same problem - the /usr/share/Luxology/Content/Kits/OctaneRenderForModo901/extra/701/64/OctaneRender for Modo.lx file did not load. In general, this occurs when the Nvidia/cuda dependencies can not be loaded.

However, first make sure Modo is setup to load from that location by gong into Modo and System->Open Content Folder. It should open a folder where the Kit folder contains the OctaneRenderForModo901 folder (and associated files).

Can you also pls post the result of "ldd /usr/share/Luxology/Content/Kits/OctaneRenderForModo901/extra/701/64/OctaneRender for Modo.lx" - so I can check it is loading the correct versions of the dependencies.

Did you install the Nvidia drivers from the Nvidia site installer? If so, I couldn't see any reference to version 352.79 there. I am actually running 346.22.

Finally, does Octane Standalone run for you on that Centos box?

Thanks

Paul

Hi Paul,

Thank you for your reply.

- Octane Standalone runs fine on this CentOS box.

- Plugin is installed in the correct folder and it opens from inside Modo as it should.

- I downloaded the Nvidia driver from their website, installed from command line as needed. Check attached png for Nvidia website driver overview.,

- Output from the command you asked me to run shows a missing OctaneRender folder or file inside ./extra/701/64/ The output is:

[root@cgi01 darren]# ldd /usr/share/Luxology/Content/Kits/OctaneRenderForModo901/extra/701/64/OctaneRender for Modo.lx
/usr/share/Luxology/Content/Kits/OctaneRenderForModo901/extra/701/64/OctaneRender:
ldd: /usr/share/Luxology/Content/Kits/OctaneRenderForModo901/extra/701/64/OctaneRender: No such file or directory
for:
ldd: ./for: No such file or directory
Modo.lx:
ldd: ./Modo.lx: No such file or directory
[root@cgi01 darren]#

Let me know what else to do to assist on this!

Cheers,
Henrik

If Octane Standalone runs and renders, then the Nvidia driver should be fine.

ldd /usr/share/Luxology/Content/Kits/OctaneRenderForModo901/extra/701/64/OctaneRender for Modo.lx

My apologies - you will need to esc the spaces - so the correct command is:
Paul

EDIT:
It seems that for CentOS 6.x the available lib version is GLIBC_2.12


[root@cgi01 darren]# ldd /usr/share/Luxology/Content/Kits/OctaneRenderForModo901/extra/701/64/OctaneRenderForModo.lx
/usr/share/Luxology/Content/Kits/OctaneRenderForModo901/extra/701/64/OctaneRenderForModo.lx: /lib64/libc.so.6: version `GLIBC_2.14' not found (required by /usr/share/Luxology/Content/Kits/OctaneRenderForModo901/extra/701/64/OctaneRenderForModo.lx)
linux-vdso.so.1 => (0x00007ffd8f4fe000)
liboctane.so => /usr/share/Luxology/Content/Kits/OctaneRenderForModo901/extra/701/64/liboctane.so (0x00007f1c54650000)
libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f1c54418000)
libQtCore.so.4 => /usr/lib64/libQtCore.so.4 (0x00007f1c53fb4000)
libQtGui.so.4 => /usr/lib64/libQtGui.so.4 (0x00007f1c5338c000)
libstdc++.so.6 => /usr/lib64/libstdc++.so.6 (0x00007f1c53085000)
libm.so.6 => /lib64/libm.so.6 (0x00007f1c52e01000)
libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x00007f1c52beb000)
libc.so.6 => /lib64/libc.so.6 (0x00007f1c52856000)
libgomp.so.1 => /usr/lib64/libgomp.so.1 (0x00007f1c52641000)
libX11.so.6 => /usr/lib64/libX11.so.6 (0x00007f1c52304000)
libXext.so.6 => /usr/lib64/libXext.so.6 (0x00007f1c520f1000)
libfreetype.so.6 => /usr/lib64/libfreetype.so.6 (0x00007f1c51e54000)
libGL.so.1 => /usr/lib64/libGL.so.1 (0x00007f1c51b24000)
libGLU.so.1 => /usr/lib64/libGLU.so.1 (0x00007f1c518a3000)
libcuda.so.1 => /usr/lib64/libcuda.so.1 (0x00007f1c508ee000)
libdl.so.2 => /lib64/libdl.so.2 (0x00007f1c506ea000)
librt.so.1 => /lib64/librt.so.1 (0x00007f1c504e1000)
/lib64/ld-linux-x86-64.so.2 (0x0000003357a00000)
libz.so.1 => /lib64/libz.so.1 (0x00007f1c502cb000)
libgthread-2.0.so.0 => /lib64/libgthread-2.0.so.0 (0x00007f1c500c7000)
libglib-2.0.so.0 => /lib64/libglib-2.0.so.0 (0x00007f1c4fdaf000)
libpng12.so.0 => /usr/lib64/libpng12.so.0 (0x00007f1c4fb89000)
libgobject-2.0.so.0 => /lib64/libgobject-2.0.so.0 (0x00007f1c4f93d000)
libSM.so.6 => /usr/lib64/libSM.so.6 (0x00007f1c4f734000)
libICE.so.6 => /usr/lib64/libICE.so.6 (0x00007f1c4f518000)
libXi.so.6 => /usr/lib64/libXi.so.6 (0x00007f1c4f309000)
libXrender.so.1 => /usr/lib64/libXrender.so.1 (0x00007f1c4f0ff000)
libXrandr.so.2 => /usr/lib64/libXrandr.so.2 (0x00007f1c4eef6000)
libXfixes.so.3 => /usr/lib64/libXfixes.so.3 (0x00007f1c4ecf1000)
libXcursor.so.1 => /usr/lib64/libXcursor.so.1 (0x00007f1c4eae6000)
libXinerama.so.1 => /usr/lib64/libXinerama.so.1 (0x00007f1c4e8e4000)
libfontconfig.so.1 => /usr/lib64/libfontconfig.so.1 (0x00007f1c4e6ae000)
libxcb.so.1 => /usr/lib64/libxcb.so.1 (0x00007f1c4e48f000)
libnvidia-tls.so.352.79 => /usr/lib64/tls/libnvidia-tls.so.352.79 (0x00007f1c4e28c000)
libnvidia-glcore.so.352.79 => /usr/lib64/libnvidia-glcore.so.352.79 (0x00007f1c4b7f7000)
libuuid.so.1 => /lib64/libuuid.so.1 (0x00007f1c4b5f3000)
libexpat.so.1 => /lib64/libexpat.so.1 (0x00007f1c4b3ca000)
libXau.so.6 => /usr/lib64/libXau.so.6 (0x00007f1c4b1c7000)

Thanks. Options are you can update to the latest Centos, you can update your glibc (generally seems to be not recommended), or I can attempt to compile the plugin to use the GLIBC_2.12 (unsure if this is possible or not - but I will investigate later today).

Paul

Hi Paul,

Thanks for all your efforts.
We are genuinely thankful that you make this great piece of software available on Linux. The only viable solution for those wanting raw power

However i think moving straight into CentOS 7 is a bit of a rush for a lot of people. I guess 90% of users are still in the more stable version 6. If possible i would prefer your last suggestion, making it a bit more backward compatible. We will happily be you "test-mice" on the path getting there!

Let me know what i can do to help out on the way.

Many thanks.

Cheers,
Henrik Mark

However i think moving straight into CentOS 7 is a bit of a rush for a lot of people. I guess 90% of users are still in the more stable version 6. If possible i would prefer your last suggestion, making it a bit more backward compatible. We will happily be you "test-mice" on the path getting there!

I agree Henrik. I will investigate how to compile with GLIBC_2.12 - I just need to make sure I don't break the plugin for other Linux users. I will get back to you shortly...

Paul