DaVinci Resolve Studio 15 Beta doesn't run on Linux

A place for feedback and discussion on DaVinci Resolve 15
  • Author
  • Message
Offline

Orlando Esponda

  • Posts: 21
  • Joined: Mon Aug 21, 2017 7:49 pm
  • Location: Mexico City

DaVinci Resolve Studio 15 Beta doesn't run on Linux

PostTue Apr 10, 2018 6:10 pm

Hello,

I've been using Resolve Studio 14.2 without issues under Fedora 27. Today I wanted to give it a try to the latest beta (I must say I'm very excited about the fusion integration, being a Fusion user since v2.5 ;) ). Unfortunately it doesn't run on my system and I'm not sure why. I know the recommended OS is Centos not Fedora, but as I mentioned before, I haven't had any trouble using either Resolve or Fusion on Fedora 25-27.

When I try to run it from terminal I get this:

Code: Select all
[oesponda@brain bin]$ ./resolve
./resolve: /opt/resolve/bin/../libs/libCg.so: no version information available (required by ./resolve)
./resolve: /opt/resolve/bin/../libs/libCgGL.so: no version information available (required by ./resolve)
ActCCMessage Already in Table: Code= 2282, Mode=  0, Level=  0, CmdKey= 8, Option= 0
ActCCMessage Already in Table: Code= c005, Mode= 13, Level=  1, CmdKey= -1, Option= 0
ActCCMessage Already in Table: Code= c006, Mode= 13, Level=  1, CmdKey= -1, Option= 0
ActCCMessage Already in Table: Code= c007, Mode= 13, Level=  1, CmdKey= -1, Option= 0
15.0b (#030) Linux/Clang
Main thread starts: 209A00C0
[0x7f02209a00c0] | Undefined            | INFO  | 2018-04-10 12:42:10,783 | --------------------------------------------------------------------------------
[0x7f02209a00c0] | Undefined            | INFO  | 2018-04-10 12:42:10,783 | Loaded log config from /opt/resolve/configs/log-conf.xml
[0x7f02209a00c0] | Undefined            | INFO  | 2018-04-10 12:42:10,783 | --------------------------------------------------------------------------------


I tried creating symlinks to the system libraries (libCg.so and libCg.so) but unfortunately the result is the same.

Here's the output of the ldd command:

Code: Select all
[oesponda@brain bin]$ ldd ./resolve
./resolve: /opt/resolve/bin/./../libs/libCg.so: no version information available (required by ./resolve)
./resolve: /opt/resolve/bin/./../libs/libCgGL.so: no version information available (required by ./resolve)
        linux-vdso.so.1 (0x00007fff09f93000)
        libc++.so.1 => /opt/resolve/bin/./../libs/libc++.so.1 (0x00007f16bc36f000)
        libc++abi.so.1 => /opt/resolve/bin/./../libs/libc++abi.so.1 (0x00007f16bc140000)
        libcudart.so.9.1 => /opt/resolve/bin/./../libs/libcudart.so.9.1 (0x00007f16bbed2000)
        libnvrtc.so.9.1 => /opt/resolve/bin/./../libs/libnvrtc.so.9.1 (0x00007f16ba7a6000)
        libQt5Core.so.5 => /opt/resolve/bin/./../libs/libQt5Core.so.5 (0x00007f16ba1c6000)
        libQt5Gui.so.5 => /opt/resolve/bin/./../libs/libQt5Gui.so.5 (0x00007f16b9c5c000)
        libQt5Multimedia.so.5 => /opt/resolve/bin/./../libs/libQt5Multimedia.so.5 (0x00007f16bc78d000)
        libQt5Network.so.5 => /opt/resolve/bin/./../libs/libQt5Network.so.5 (0x00007f16bc688000)
        libQt5OpenGL.so.5 => /opt/resolve/bin/./../libs/libQt5OpenGL.so.5 (0x00007f16b9bfa000)
        libQt5Sql.so.5 => /opt/resolve/bin/./../libs/libQt5Sql.so.5 (0x00007f16b9ab3000)
        libQt5Widgets.so.5 => /opt/resolve/bin/./../libs/libQt5Widgets.so.5 (0x00007f16b943a000)
        libQt5Xml.so.5 => /opt/resolve/bin/./../libs/libQt5Xml.so.5 (0x00007f16b93f1000)
        libGLU.so.1 => /lib64/libGLU.so.1 (0x00007f16b9146000)
        libGL.so.1 => /lib64/libGL.so.1 (0x00007f16b8eba000)
        fusionscript.so => /opt/resolve/bin/./../libs/Fusion/fusionscript.so (0x00007f16b8899000)
        libluajit-5.1.so.2 => /opt/resolve/bin/./../libs/libluajit-5.1.so.2 (0x00007f16b861a000)
        libtbbmalloc.so.2 => /opt/resolve/bin/./../libs/libtbbmalloc.so.2 (0x00007f16b83db000)
        libtbbmalloc_proxy.so.2 => /opt/resolve/bin/./../libs/libtbbmalloc_proxy.so.2 (0x00007f16b81d6000)
        libXxf86vm.so.1 => /lib64/libXxf86vm.so.1 (0x00007f16b7fd0000)
        libfreetype.so.6 => /lib64/libfreetype.so.6 (0x00007f16b7d1b000)
        libXext.so.6 => /lib64/libXext.so.6 (0x00007f16b7b09000)
        libSM.so.6 => /lib64/libSM.so.6 (0x00007f16b7901000)
        libICE.so.6 => /lib64/libICE.so.6 (0x00007f16b76e5000)
        libX11.so.6 => /lib64/libX11.so.6 (0x00007f16b73a7000)
        libbz2.so.1 => /lib64/libbz2.so.1 (0x00007f16b7196000)
        libxml2.so.2 => /lib64/libxml2.so.2 (0x00007f16b6e30000)
        libm.so.6 => /lib64/libm.so.6 (0x00007f16b6ae5000)
        libdl.so.2 => /lib64/libdl.so.2 (0x00007f16b68e1000)
        librt.so.1 => /lib64/librt.so.1 (0x00007f16b66d9000)
        libavformat.so.57 => /opt/resolve/bin/./../libs/libavformat.so.57 (0x00007f16b62df000)
        libavcodec.so.57 => /opt/resolve/bin/./../libs/libavcodec.so.57 (0x00007f16b4d77000)
        libavutil.so.55 => /opt/resolve/bin/./../libs/libavutil.so.55 (0x00007f16b4b04000)
        libMXF.so => /opt/resolve/bin/./../libs/libMXF.so (0x00007f16b47f6000)
        libSMDK-Linux-x64.so.4.7 => /opt/resolve/bin/./../libs/libSMDK-Linux-x64.so.4.7 (0x00007f16b434c000)
        libmp4decMT.so => /opt/resolve/bin/./../libs/libmp4decMT.so (0x00007f16b401c000)
        libmp4encMT.so => /opt/resolve/bin/./../libs/libmp4encMT.so (0x00007f16b3ab0000)
        libsonyxavcenc.so => /opt/resolve/bin/./../libs/libsonyxavcenc.so (0x00007f16b3824000)
        liblog4cxx.so.10 => /opt/resolve/bin/./../libs/liblog4cxx.so.10 (0x00007f16b330d000)
        libapr-1.so.0 => /opt/resolve/bin/./../libs/libapr-1.so.0 (0x00007f16b30d1000)
        libaprutil-1.so.0 => /opt/resolve/bin/./../libs/libaprutil-1.so.0 (0x00007f16b2ea4000)
        libopencv_calib3d.so.3.3 => /opt/resolve/bin/./../libs/libopencv_calib3d.so.3.3 (0x00007f16b2ae4000)
        libopencv_core.so.3.3 => /opt/resolve/bin/./../libs/libopencv_core.so.3.3 (0x00007f16b25e0000)
        libopencv_features2d.so.3.3 => /opt/resolve/bin/./../libs/libopencv_features2d.so.3.3 (0x00007f16b2331000)
        libopencv_flann.so.3.3 => /opt/resolve/bin/./../libs/libopencv_flann.so.3.3 (0x00007f16b20c5000)
        libopencv_highgui.so.3.3 => /opt/resolve/bin/./../libs/libopencv_highgui.so.3.3 (0x00007f16b1ebc000)
        libopencv_imgcodecs.so.3.3 => /opt/resolve/bin/./../libs/libopencv_imgcodecs.so.3.3 (0x00007f16b1c93000)
        libopencv_imgproc.so.3.3 => /opt/resolve/bin/./../libs/libopencv_imgproc.so.3.3 (0x00007f16b150a000)
        libopencv_ml.so.3.3 => /opt/resolve/bin/./../libs/libopencv_ml.so.3.3 (0x00007f16b1256000)
        libopencv_objdetect.so.3.3 => /opt/resolve/bin/./../libs/libopencv_objdetect.so.3.3 (0x00007f16b1009000)
        libopencv_video.so.3.3 => /opt/resolve/bin/./../libs/libopencv_video.so.3.3 (0x00007f16b0dbd000)
        libopencv_videoio.so.3.3 => /opt/resolve/bin/./../libs/libopencv_videoio.so.3.3 (0x00007f16b0ba6000)
        libopencv_dnn.so.3.3 => /opt/resolve/bin/./../libs/libopencv_dnn.so.3.3 (0x00007f16b069d000)
        libcudnn.so.5 => /opt/resolve/bin/./../libs/libcudnn.so.5 (0x00007f16ab42e000)
        libSonyRawDev.so.3 => /opt/resolve/bin/./../libs/libSonyRawDev.so.3 (0x00007f16ab025000)
        libGLEW.so.1.9 => /opt/resolve/bin/./../libs/libGLEW.so.1.9 (0x00007f16aadb3000)
        libOpenCL.so.1 => /lib64/libOpenCL.so.1 (0x00007f16aabad000)
        libgvc.so.6 => /opt/resolve/bin/./../libs/libgvc.so.6 (0x00007f16aa90c000)
        libcgraph.so.6 => /opt/resolve/bin/./../libs/libcgraph.so.6 (0x00007f16aa6f6000)
        libcdt.so.5 => /opt/resolve/bin/./../libs/libcdt.so.5 (0x00007f16aa4f1000)
        libxdot.so.4 => /opt/resolve/bin/./../libs/libxdot.so.4 (0x00007f16aa2ec000)
        libpathplan.so.4 => /opt/resolve/bin/./../libs/libpathplan.so.4 (0x00007f16aa0e4000)
        libDNxHR.so => /opt/resolve/bin/./../libs/libDNxHR.so (0x00007f16a994a000)
        libimf.so => /opt/resolve/bin/./../libs/libimf.so (0x00007f16a9487000)
        libirc.so => /opt/resolve/bin/./../libs/libirc.so (0x00007f16a922f000)
        libsvml.so => /opt/resolve/bin/./../libs/libsvml.so (0x00007f16a8634000)
        libintlc.so.5 => /opt/resolve/bin/./../libs/libintlc.so.5 (0x00007f16a83de000)
        libArriRawSDK.so.5 => /opt/resolve/bin/./../libs/libArriRawSDK.so.5 (0x00007f16a63df000)
        libgvcodec.so => /opt/resolve/bin/./../libs/libgvcodec.so (0x00007f16a61b8000)
        libcurl.so.4 => /lib64/libcurl.so.4 (0x00007f16a5f38000)
        libid3-3.8.so.3 => /opt/resolve/bin/./../libs/libid3-3.8.so.3 (0x00007f16a5cfb000)
        libuuid.so.1 => /lib64/libuuid.so.1 (0x00007f16a5af6000)
        libssl.so.10 => /lib64/libssl.so.10 (0x00007f16a5889000)
        libcrypto.so.10 => /lib64/libcrypto.so.10 (0x00007f16a5429000)
        libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f16a520b000)
        librsvg-2.so.2 => /lib64/librsvg-2.so.2 (0x00007f16a4fd3000)
        libCg.so => /opt/resolve/bin/./../libs/libCg.so (0x00007f16a3afa000)
        libCgGL.so => /opt/resolve/bin/./../libs/libCgGL.so (0x00007f16a3976000)
        libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x00007f16a375f000)
        libc.so.6 => /lib64/libc.so.6 (0x00007f16a33a7000)
        /lib64/ld-linux-x86-64.so.2 (0x00007f16bc651000)
        libstdc++.so.6 => /lib64/libstdc++.so.6 (0x00007f16a3020000)
        libGLX.so.0 => /lib64/libGLX.so.0 (0x00007f16a2dee000)
        libGLdispatch.so.0 => /lib64/libGLdispatch.so.0 (0x00007f16a2b38000)
        libpng16.so.16 => /lib64/libpng16.so.16 (0x00007f16a2903000)
        libz.so.1 => /lib64/libz.so.1 (0x00007f16a26ec000)
        libxcb.so.1 => /lib64/libxcb.so.1 (0x00007f16a24c4000)
        liblzma.so.5 => /lib64/liblzma.so.5 (0x00007f16a229e000)
        libexpat.so.1 => /lib64/libexpat.so.1 (0x00007f16a206a000)
        libcrypt.so.1 => /lib64/libcrypt.so.1 (0x00007f16a1e34000)
        libXmu.so.6 => /lib64/libXmu.so.6 (0x00007f16a1c1a000)
        libXi.so.6 => /lib64/libXi.so.6 (0x00007f16a1a09000)
        libnghttp2.so.14 => /lib64/libnghttp2.so.14 (0x00007f16a17e2000)
        libidn2.so.0 => /lib64/libidn2.so.0 (0x00007f16a15c5000)
        libssh2.so.1 => /lib64/libssh2.so.1 (0x00007f16a1398000)
        libpsl.so.5 => /lib64/libpsl.so.5 (0x00007f16a118a000)
        libssl.so.1.1 => /lib64/libssl.so.1.1 (0x00007f16a0f1e000)
        libcrypto.so.1.1 => /lib64/libcrypto.so.1.1 (0x00007f16a0a94000)
        libgssapi_krb5.so.2 => /lib64/libgssapi_krb5.so.2 (0x00007f16a0847000)
        libkrb5.so.3 => /lib64/libkrb5.so.3 (0x00007f16a0560000)
        libk5crypto.so.3 => /lib64/libk5crypto.so.3 (0x00007f16a032d000)
        libcom_err.so.2 => /lib64/libcom_err.so.2 (0x00007f16a0129000)
        libldap-2.4.so.2 => /lib64/libldap-2.4.so.2 (0x00007f169fed6000)
        liblber-2.4.so.2 => /lib64/liblber-2.4.so.2 (0x00007f169fcc5000)
        libgdk_pixbuf-2.0.so.0 => /lib64/libgdk_pixbuf-2.0.so.0 (0x00007f169fa9d000)
        libgio-2.0.so.0 => /lib64/libgio-2.0.so.0 (0x00007f169f703000)
        libpangocairo-1.0.so.0 => /lib64/libpangocairo-1.0.so.0 (0x00007f169f4f5000)
        libpangoft2-1.0.so.0 => /lib64/libpangoft2-1.0.so.0 (0x00007f169f2de000)
        libpango-1.0.so.0 => /lib64/libpango-1.0.so.0 (0x00007f169f090000)
        libgobject-2.0.so.0 => /lib64/libgobject-2.0.so.0 (0x00007f169ee3b000)
        libfontconfig.so.1 => /lib64/libfontconfig.so.1 (0x00007f169ebf6000)
        libcairo.so.2 => /lib64/libcairo.so.2 (0x00007f169e8d9000)
        libcroco-0.6.so.3 => /lib64/libcroco-0.6.so.3 (0x00007f169e69e000)
        libglib-2.0.so.0 => /lib64/libglib-2.0.so.0 (0x00007f169e38a000)
        libXau.so.6 => /lib64/libXau.so.6 (0x00007f169e184000)
        libfreebl3.so => /lib64/libfreebl3.so (0x00007f169df81000)
        libXt.so.6 => /lib64/libXt.so.6 (0x00007f169dd19000)
        libunistring.so.2 => /lib64/libunistring.so.2 (0x00007f169d999000)
        libkrb5support.so.0 => /lib64/libkrb5support.so.0 (0x00007f169d78a000)
        libkeyutils.so.1 => /lib64/libkeyutils.so.1 (0x00007f169d584000)
        libresolv.so.2 => /lib64/libresolv.so.2 (0x00007f169d36d000)
        libsasl2.so.3 => /lib64/libsasl2.so.3 (0x00007f169d150000)
        libssl3.so => /lib64/libssl3.so (0x00007f169cefe000)
        libsmime3.so => /lib64/libsmime3.so (0x00007f169ccd7000)
        libnss3.so => /lib64/libnss3.so (0x00007f169c9af000)
        libnssutil3.so => /lib64/libnssutil3.so (0x00007f169c77d000)
        libplds4.so => /lib64/libplds4.so (0x00007f169c579000)
        libplc4.so => /lib64/libplc4.so (0x00007f169c374000)
        libnspr4.so => /lib64/libnspr4.so (0x00007f169c136000)
        libgmodule-2.0.so.0 => /lib64/libgmodule-2.0.so.0 (0x00007f169bf32000)
        libffi.so.6 => /lib64/libffi.so.6 (0x00007f169bd2a000)
        libpcre.so.1 => /lib64/libpcre.so.1 (0x00007f169bab6000)
        libselinux.so.1 => /lib64/libselinux.so.1 (0x00007f169b88d000)
        libmount.so.1 => /lib64/libmount.so.1 (0x00007f169b639000)
        libharfbuzz.so.0 => /lib64/libharfbuzz.so.0 (0x00007f169b3a1000)
        libthai.so.0 => /lib64/libthai.so.0 (0x00007f169b197000)
        libpixman-1.so.0 => /lib64/libpixman-1.so.0 (0x00007f169aef0000)
        libxcb-shm.so.0 => /lib64/libxcb-shm.so.0 (0x00007f169acec000)
        libxcb-render.so.0 => /lib64/libxcb-render.so.0 (0x00007f169aade000)
        libXrender.so.1 => /lib64/libXrender.so.1 (0x00007f169a8d4000)
        libpcre2-8.so.0 => /lib64/libpcre2-8.so.0 (0x00007f169a650000)
        libblkid.so.1 => /lib64/libblkid.so.1 (0x00007f169a405000)
        libgraphite2.so.3 => /lib64/libgraphite2.so.3 (0x00007f169a1d9000)
        libdatrie.so.1 => /lib64/libdatrie.so.1 (0x00007f1699fd2000)



Does anyone have an idea on what could be going on here? I know there's still on beta, and I just simply reinstalled Resolve 14 for now. I also have my dongle for Fusion Studio but really wanted to try the new approach of having them both in the same place.

DaVinci Resolve Studio 15.0b1 Linux
Fedora 27 (up to date)
Nvidia GTX1070
Nvidia Driver v390.48



Thanks in advance for any help,
Orlando.
Offline

Abdelrahman Magdy

  • Posts: 226
  • Joined: Fri Jan 23, 2015 10:08 pm

Re: DaVinci Resolve Studio 15 Beta doesn't run on Linux

PostTue Apr 10, 2018 6:24 pm

My advice would be to try running it on a CentOS machine if you have one available. See if it does the same thing. I am recommending this, because it will be your only way to getting official support from Blackmagic. After all, community support can only get you to a certain point when you are dealing with a proprietary program, as no one (except Blackmagic in this case) is able to actually examine what is happening in the background.

So, at least for the beta versions of DR15, try them on CentOS.
System specs:
Resolve version: 15.0.0B.065
Fusion version: 9.0.2
OS: CentOS 7
CPU: Intel i7-4790k 4GHz Quad-Core
RAM: 32GB
GPU: NVIDIA GeForce 1080 Ti 11GB
Offline

Orlando Esponda

  • Posts: 21
  • Joined: Mon Aug 21, 2017 7:49 pm
  • Location: Mexico City

Re: DaVinci Resolve Studio 15 Beta doesn't run on Linux

PostTue Apr 10, 2018 6:33 pm

Thanks Abdelrahman Magdy,

And yes, I know what you mean. Unfortunately I don't have a CentOS machine. I tried CentOS before Fedora and strangely enough I had troubles with some programs and hardware... go figure. Fedora has been solid so far with all my apps and hardware.

Anyway, I guess I will need to wait to the final release to see if it works or not under Fedora.
Offline
User avatar

MikeRochefort

  • Posts: 61
  • Joined: Thu Feb 12, 2015 2:48 am
  • Location: New England

Re: DaVinci Resolve Studio 15 Beta doesn't run on Linux

PostTue Apr 10, 2018 7:25 pm

Just curious, what did you symlink and where did you symlink it to?

Cheers,
Mike
https://michaelrochefort.com/
3D Lookdev, Compositing, and Sysadmin
Fusion Studio 9.0.2
DaVinci Resolve Studio 15b3
CentOS 7.5.1804 | Intel i7-6850K | 32GB memory | 3x GTX 1070
Offline

Arthur Sergin

  • Posts: 14
  • Joined: Wed Oct 11, 2017 7:37 am

Re: DaVinci Resolve Studio 15 Beta doesn't run on Linux

PostTue Apr 10, 2018 7:42 pm

Orlando Esponda wrote:Hello,

I've been using Resolve Studio 14.2 without issues under Fedora 27. Today I wanted to give it a try to the latest beta (I must say I'm very excited about the fusion integration, being a Fusion user since v2.5 ;) ). Unfortunately it doesn't run on my system and I'm not sure why. I know the recommended OS is Centos not Fedora, but as I mentioned before, I haven't had any trouble using either Resolve or Fusion on Fedora 25-27.

When I try to run it from terminal I get this:.........


I would start with
Code: Select all
$ ldd /opt/resolve/bin/resolve
in order to see any problem binaries involved. You should install them or symlink to proper binary if ldd report any "not found" status.
Hardware: Ryzen 7 1700, PRIME X370-PRO, 16Gb DDR4, GeForce GTX 1070, NVMe 960 EVO 250GB, WD 7200rpm 1Tb
OS: Ubuntu Linux 16.04x
Nvidia Driver: v396.26
Cuda: 9.2.88
Offline

Abdelrahman Magdy

  • Posts: 226
  • Joined: Fri Jan 23, 2015 10:08 pm

Re: DaVinci Resolve Studio 15 Beta doesn't run on Linux

PostTue Apr 10, 2018 10:11 pm

Orlando Esponda wrote:Thanks Abdelrahman Magdy,

And yes, I know what you mean. Unfortunately I don't have a CentOS machine. I tried CentOS before Fedora and strangely enough I had troubles with some programs and hardware... go figure. Fedora has been solid so far with all my apps and hardware.

Anyway, I guess I will need to wait to the final release to see if it works or not under Fedora.

That is really strange. I, myself, am a fan of Debian-based distros, but I had to switch to CentOS for Resolve and Fusion. I have never experienced any problems with any of my software or hardware.

Hopefully, it will work for you. Maybe even in one of the new beta releases.
System specs:
Resolve version: 15.0.0B.065
Fusion version: 9.0.2
OS: CentOS 7
CPU: Intel i7-4790k 4GHz Quad-Core
RAM: 32GB
GPU: NVIDIA GeForce 1080 Ti 11GB
Offline

Orlando Esponda

  • Posts: 21
  • Joined: Mon Aug 21, 2017 7:49 pm
  • Location: Mexico City

Re: DaVinci Resolve Studio 15 Beta doesn't run on Linux

PostTue Apr 10, 2018 10:14 pm

MikeRochefort wrote:Just curious, what did you symlink and where did you symlink it to?

Cheers,
Mike


Hey Mike, nice to see you here as well,

I created these simlinks:
Code: Select all
[root@brain usr]# ln -s /usr/lib64/libCgGL.so /opt/resolve/libs/libCgGL.so
[root@brain usr]# ln -s /usr/lib64/libCg.so /opt/resolve/libs/libCg.so

But the result was the message when trying to run from terminal:
Code: Select all
./resolve: /opt/resolve/bin/../libs/libCg.so: no version information available (required by ./resolve)
./resolve: /opt/resolve/bin/../libs/libCgGL.so: no version information available (required by ./resolve)


Arthur Sergin wrote:I would start with
Code: Select all
$ ldd /opt/resolve/bin/resolve
in order to see any problem binaries involved. You should install them or symlink to proper binary if ldd report any "not found" status.

Thanks Arthur, but if take a closer look at my original post, the second part is exactly that. I tried to symlink the two libraries having troubles, but the output of ldd afterwards was exactly the same.

Orlando.
Offline

Kjella

  • Posts: 2
  • Joined: Sat Mar 03, 2018 2:18 pm
  • Real Name: Kjell Rune Skaaraas

Re: DaVinci Resolve Studio 15 Beta doesn't run on Linux

PostTue Apr 10, 2018 10:51 pm

I would guess it's expecting a symlink to libCg.so.[version] or libCg.so.[version].[subversion]
Offline

Orlando Esponda

  • Posts: 21
  • Joined: Mon Aug 21, 2017 7:49 pm
  • Location: Mexico City

Re: DaVinci Resolve Studio 15 Beta doesn't run on Linux

PostWed Apr 11, 2018 12:48 am

Kjella wrote:I would guess it's expecting a symlink to libCg.so.[version] or libCg.so.[version].[subversion]


Thanks Kjella,

I didn't think about it but it makes sense (looking at the ldd message). The original libraries that come with the installation don't specify any version/subversion (they are called just like that: libCg.so and libCgGL.so). And then I checked the ones installed with Resolve 14 and it's the same, no version/subversion.

The output of ldd on Resolve 14's libraries is:
Code: Select all
[root@brain usr]# ldd -v /opt/resolve/libs/libCg.so
        statically linked
[root@brain usr]# ldd -v /opt/resolve/libs/libCgGL.so 
/opt/resolve/libs/libCgGL.so: /lib64/libCg.so: no version information available (required by /opt/resolve/libs/libCgGL.so)
        linux-vdso.so.1 (0x00007ffd59bbd000)
        libCg.so => /lib64/libCg.so (0x00007f098ada2000)
        libm.so.6 => /lib64/libm.so.6 (0x00007f098aa57000)
        libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f098a839000)
        libc.so.6 => /lib64/libc.so.6 (0x00007f098a483000)
        /lib64/ld-linux-x86-64.so.2 (0x00007f098c27b000)

        Version information:
        /opt/resolve/libs/libCgGL.so:
                libCg.so (VERSION) => not found
        /lib64/libCg.so:
                libm.so.6 (GLIBC_2.2.5) => /lib64/libm.so.6
                libpthread.so.0 (GLIBC_2.2.5) => /lib64/libpthread.so.0
                libc.so.6 (GLIBC_2.2.5) => /lib64/libc.so.6
        /lib64/libm.so.6:
                ld-linux-x86-64.so.2 (GLIBC_PRIVATE) => /lib64/ld-linux-x86-64.so.2
                libc.so.6 (GLIBC_2.4) => /lib64/libc.so.6
                libc.so.6 (GLIBC_2.2.5) => /lib64/libc.so.6
                libc.so.6 (GLIBC_PRIVATE) => /lib64/libc.so.6
        /lib64/libpthread.so.0:
                ld-linux-x86-64.so.2 (GLIBC_2.2.5) => /lib64/ld-linux-x86-64.so.2
                ld-linux-x86-64.so.2 (GLIBC_PRIVATE) => /lib64/ld-linux-x86-64.so.2
                libc.so.6 (GLIBC_2.14) => /lib64/libc.so.6
                libc.so.6 (GLIBC_2.3.2) => /lib64/libc.so.6
                libc.so.6 (GLIBC_2.4) => /lib64/libc.so.6
                libc.so.6 (GLIBC_2.2.5) => /lib64/libc.so.6
                libc.so.6 (GLIBC_PRIVATE) => /lib64/libc.so.6
        /lib64/libc.so.6:
                ld-linux-x86-64.so.2 (GLIBC_2.3) => /lib64/ld-linux-x86-64.so.2
                ld-linux-x86-64.so.2 (GLIBC_PRIVATE) => /lib64/ld-linux-x86-64.so.2

So it seems like Resolve 14's libraries don't have any version/subversion either, but the program opens and doesn't complain at all. So I'm not sure the version is actually needed.

Probably is just a compilation incompatibility, but who knows...
Offline
User avatar

dilnix

  • Posts: 2
  • Joined: Thu Apr 12, 2018 9:02 am
  • Location: Kyiv
  • Real Name: Dimka Filippov

Re: DaVinci Resolve Studio 15 Beta doesn't run on Linux

PostThu Apr 12, 2018 9:13 am

Hello,

I'm having the same problem. Resolve 15b1 don't start in my Fedora.
As I know CentOS is very similar to Fedora. So I hope that developers of Resolve could get attention on this thread and fix this issue.
Offline

Abdelrahman Magdy

  • Posts: 226
  • Joined: Fri Jan 23, 2015 10:08 pm

Re: DaVinci Resolve Studio 15 Beta doesn't run on Linux

PostThu Apr 12, 2018 4:30 pm

dilnix wrote:Hello,

I'm having the same problem. Resolve 15b1 don't start in my Fedora.
As I know CentOS is very similar to Fedora. So I hope that developers of Resolve could get attention on this thread and fix this issue.

Don't expect any help from the developers when it comes to Fedora. Fedora is, of course, similar to CentOS, as they both originate from the same source (i.e. RHEL).

However, the major difference between CentOS/RHEL and Fedora is that the latter is sort of the playground for testing new features that might later be added to RHEL. In Fedora, AFAIK, you will get the most recent and cutting edge updates, thus resulting in a system that is, at least theoretically, less stable compared to RHEL and CentOS.

Since stability is a major concern for production environments, this is why Blackmagic, and other software companies, only support stable OS.

Again, as I said earlier, when Resolve 15 gets to the final release, it might magically start working again under Fedora. But if you want any sort of help from the developers, you will have to rely on CentOS. Anything else, and your only source of help will be the community, as it is really difficult for any company to support all the Linux distros out there.
System specs:
Resolve version: 15.0.0B.065
Fusion version: 9.0.2
OS: CentOS 7
CPU: Intel i7-4790k 4GHz Quad-Core
RAM: 32GB
GPU: NVIDIA GeForce 1080 Ti 11GB
Offline

prysme

  • Posts: 3
  • Joined: Fri Apr 13, 2018 7:40 am
  • Real Name: Emmanuel Duss

Re: DaVinci Resolve Studio 15 Beta doesn't run on Linux

PostFri Apr 13, 2018 7:57 am

Hello All,

I am getting the same issue on the latest Fedora, former Resolver 14 was working fine, but 15 is not starting at all.

I know that only CENTOS is supported, but I hope that Blackmagic have also plan to support other well know distributions.

After searching, testing and waiting for a Video Editing application on Linux, Resolve is really a killer app even as a proprietary software, for 300$ I would seriously consider to buy it because it worst the money. I know a bunch of people that run Linux that could be also interested of buying the software, but none of them are using CENTOS.

Anyway I'm pretty sure that Resolve 15 final will work on Fedora, and I hope that BlackMagic is going to consider other linux distributions, the application is targeting pro/semi-pro consumers, but the product is also affordable to regular end-users.

So thanks for making this application working on linux, and keep going to support at least debian based distribution and Fedora or at least consider to provide statically link binaries to enlarge the support at no cost.

Once again thank you for this product and to make it affordable for non professional.

e.
Offline

Simas Gineika

  • Posts: 23
  • Joined: Sat Nov 25, 2017 6:33 pm

Re: DaVinci Resolve Studio 15 Beta doesn't run on Linux

PostFri Apr 13, 2018 6:57 pm

I have same issue. Sadly CentOS doesn't work properly with my hardware, doesn't boot at all to be precise. Hopefully new updates will be released soon to fix this issue.

————————UPDATE———————
today installed Centos on my pc, and sadly there is no officiall kernel update yet.
Although have updated but ran into issues with Nvidia drivers, and system failed after running into boot/crash loop. Anyway running Fedora 27 have no such problems as it is updated frequently. Maybe to frequently but at least it supports hardware. Please Blackmagic, fix upcoming version to run on Fedora distro. Can’t wait to try new Resolve!!
Offline
User avatar

jesuslovesyou101

  • Posts: 3
  • Joined: Fri Apr 13, 2018 10:47 pm
  • Location: Indiana, USA
  • Real Name: Daniel Clem

Re: DaVinci Resolve Studio 15 Beta doesn't run on Linux

PostFri Apr 13, 2018 11:38 pm

I am having the exact same issue on Linux mint. At first it wouldn't do anything. but searching another forum popped a result from another thread that said to installed a couple packages that were missing, can't remember. And that got me to this point.

I have found the files in question in the resolve folder (libCg.so and libCgGL.so) and indead no version number while other files do have version numbers on the end of the file names. Maybe its a silly idea, but why can't we either peak inside, or get official feed back from the devs for what the versions are and just rename the files to match how the others include the versions?

I'm not a Linux power user. I'm just a common guy who learned some thing after getting fed up with Windows many years ago and switched to Ubuntu (and other deb based distros) and never looked back. So don't know how to do sys links.

Honestly I only recently found out DaVinci runs on linux, and to top that there was a free version. So wanting to learn editing and grading I snatched it up. I wouldn't mind rolling back to the last stable version that didn't have any issues. What is the best way (if this version information issue can't be "Resolved" ) to uninstalled 15 beta in order to install the previous version so not to cause a conflict?

Thank you for any assistance and feedback.
"If I had 6 hours to cut down a tree. I would spend the first 4 sharpening the axe."
~ Abraham Lincoln
Offline

HealthWyzeMedia

  • Posts: 1
  • Joined: Sat Apr 14, 2018 3:14 am
  • Real Name: Sarah Corriher

Re: DaVinci Resolve Studio 15 Beta doesn't run on Linux

PostSat Apr 14, 2018 3:28 am

I am running Ubuntu 16.04, and I ran into the same problem. I fixed it and was able to run Davinci 15 by installing nvidia-modprobe (apt-get install nvidia-modprobe). I also previously ran these commands to fix other errors:

Code: Select all
apt-get install libssl-dev
ln -s /usr/lib /usr/lib64
ln -s /usr/lib/x86_64-linux-gnu/libgstreamer-1.0.so.0 /usr/lib/libgstreamer-0.10.so.0
ln -s /usr/lib/x86_64-linux-gnu/libgstbase-1.0.so.0 /usr/lib/libgstbase-0.10.so.0
ln -s /lib/x86_64-linux-gnu/libssl.so.1.0.0 /usr/lib/libssl.so.10
ln -s /lib/x86_64-linux-gnu/libcrypto.so.1.0.0 /usr/lib/libcrypto.so.10


Despite these issues, sound finally works on Linux! I also want to say that it's insane that BlackMagic is basing their Linux version on CentOS, when only a tiny portion of people use it. Why wouldn't you code for the distribution that most people are using? In the very least, these changes could be automatic. The Ubuntu distribution owns the lion's share of the market, yet it seems to be the toughest distro to get Davinci to work on. CentOS is just used primarily for Internet servers, not workstations. It's like trying to win an election by only campaigning to people in the Green party. Sure, you have every right to do it, but does it make any sense?
Specifications

  • 16GB RAM
  • GeForce GTX 660
Offline

Simas Gineika

  • Posts: 23
  • Joined: Sat Nov 25, 2017 6:33 pm

Re: DaVinci Resolve Studio 15 Beta doesn't run on Linux

PostMon Apr 16, 2018 9:15 pm

Small update again, on Fedora 27, I was able to run Resolve 15 by adding nvidia-drm.modeset=1 parameter to grub and updated Nvida drivers to the latest (390.48) It kinda works, I'm able to add videos to timeline, and edit, but as soon as I try to switch to fusion it crashes.

FusionScript Server [10652] Started
Host 'Fusion' [10413] Added
Host 'Fusion' Killed
FusionScript Server [10652] Terminated
Segmentation fault (core dumped)
Offline

Martin Schitter

  • Posts: 734
  • Joined: Tue Apr 28, 2015 10:41 pm

Re: DaVinci Resolve Studio 15 Beta doesn't run on Linux

PostMon Apr 16, 2018 10:18 pm

one very important and hard to catch detail should bee seen in the fact, that resolve on linux will stop very early in the startup process, if it doesn't find a working OpenCL installation. on many distributions the nvidia-drivers are split in a lot of parts, and many user do not care much about OpenCL, because CUDA usually works much better on this kind of hardware. but in the case of resolve, it will not even search for CUDA, but immediately stop, if OpenCL isn't present.

therefore: just do a quick check by `clinfo`, if resolve doesn't start.
Offline
User avatar

MikeRochefort

  • Posts: 61
  • Joined: Thu Feb 12, 2015 2:48 am
  • Location: New England

Re: DaVinci Resolve Studio 15 Beta doesn't run on Linux

PostTue Apr 17, 2018 12:36 am

HealthWyzeMedia wrote:
Despite these issues, sound finally works on Linux! I also want to say that it's insane that BlackMagic is basing their Linux version on CentOS, when only a tiny portion of people use it. Why wouldn't you code for the distribution that most people are using?


Pretty much all post production houses around the globe (at least in VFX) that operate in a Linux environment utilize RHEL or CentOS. To others, not catering to that market over the home or indie user would be insane. Not to mention pretty much every other professional tool that supports Linux is built on and supports those two distros (they are nearly bit-for-bit identical), and the VFX Platform is(based on package version) built around it. Why break a standard when it exists? I'm not discounting other distros, and frankly I'm surprised Fedora is having the issues it is.

Cheers,
Mike
https://michaelrochefort.com/
3D Lookdev, Compositing, and Sysadmin
Fusion Studio 9.0.2
DaVinci Resolve Studio 15b3
CentOS 7.5.1804 | Intel i7-6850K | 32GB memory | 3x GTX 1070
Offline

Abdelrahman Magdy

  • Posts: 226
  • Joined: Fri Jan 23, 2015 10:08 pm

Re: DaVinci Resolve Studio 15 Beta doesn't run on Linux

PostTue Apr 17, 2018 12:51 am

MikeRochefort wrote:
HealthWyzeMedia wrote:
Despite these issues, sound finally works on Linux! I also want to say that it's insane that BlackMagic is basing their Linux version on CentOS, when only a tiny portion of people use it. Why wouldn't you code for the distribution that most people are using?


Pretty much all post production houses around the globe (at least in VFX) that operate in a Linux environment utilize RHEL or CentOS. To others, not catering to that market over the home or indie user would be insane.

Cheers,
Mike

I agree with Mike. Ubuntu (and other Debian-based distros) might be dominant when it comes to Linux distros on most home users' computers. But, AFAIK (and I don't have official numbers here) RHEL/CentOS has always been the dominant when it comes to professional production environments. It might have something to do with the fact that Red Hat has always been providing professional support for their OS, or something else might be the reason here.

Considering that Resolve on Linux has been only available, until very recently, with the Resolve Advanced Panel, Blackmagic's largest panel, it is easy to see why they have went with RHEL/CentOS as their main supported OS.

Now, could that change in the future? Maybe, who knows? Initially, when Blackmagic released Resolve on Linux, it seemed that they would never consider supporting Linux's system audio. However, they decided to do exactly that in Resolve 15. So, later, they might think of supporting at least one of the Debian-based distros. For now, though, you can still get it to run on Ubuntu or Linux Mint, but you will have to rely on the community to figure out solutions for whatever issues you might encounter. I was running Resolve on Linux Mint, but every time I had a problem and called the tech support, they would say that they will look into it, but the solution would be something that works on RHEL/CentOS, and that there is no guarantee that it will work on Mint. This is why I decided to switch to CentOS, and, to be honest, I actually like it. Aside from a couple of things here and there that I think were better supported on Mint, my experience with CentOS has been pretty good.
System specs:
Resolve version: 15.0.0B.065
Fusion version: 9.0.2
OS: CentOS 7
CPU: Intel i7-4790k 4GHz Quad-Core
RAM: 32GB
GPU: NVIDIA GeForce 1080 Ti 11GB
Offline

Martin Schitter

  • Posts: 734
  • Joined: Tue Apr 28, 2015 10:41 pm

Re: DaVinci Resolve Studio 15 Beta doesn't run on Linux

PostTue Apr 17, 2018 3:36 am

Abdelrahman Magdy wrote:I agree with Mike. Ubuntu (and other Debian-based distros) might be dominant when it comes to Linux distros on most home users' computers. But, AFAIK (and I don't have official numbers here) RHEL/CentOS has always been the dominant when it comes to professional production environments. It might have something to do with the fact that Red Hat has always been providing professional support for their OS, or something else might be the reason here.


i really can't stand this stupid chatter and all the glorification of a few well known brands amongst the linux distributions. sure -- we all know similar from mac-vs-windows fights. but do we really want to share their culture? isn't linux and this kind of 'freedom' proclaimed by the GNU manifest different even in this regard?

i would neither agree on the actual importance or dominance of the mentioned very commercial oriented distributions, nor do i see any significant technical benefits or advance inextricably linked to them. the vital user community of debian, arch etc. and the vast amount of helpful documentation originated by them, is IMHO much more valuable in practice, than just utilizing the most prestigious brand of linux derivative...

but back to the main thread...

15b1 works really well on linux!

this is why i spend some time recently, to experiment with more user friendly and distribution agnostic alternatives to its present deployment. for this purpose i used nvidia-docker to prepare ready-prepared images of a clean CentOS runtime environment resp. resolve setup, which can be transferred and executed on nearly any kind of linux just the same. it's still in a very early stage of development, but you can already take a look at: https://gitlab.com/mash-graz/resolve to get a rough idea about this uncommon approach and all its pro and cons.
Offline

Abdelrahman Magdy

  • Posts: 226
  • Joined: Fri Jan 23, 2015 10:08 pm

Re: DaVinci Resolve Studio 15 Beta doesn't run on Linux

PostTue Apr 17, 2018 8:19 am

Martin Schitter wrote:
Abdelrahman Magdy wrote:I agree with Mike. Ubuntu (and other Debian-based distros) might be dominant when it comes to Linux distros on most home users' computers. But, AFAIK (and I don't have official numbers here) RHEL/CentOS has always been the dominant when it comes to professional production environments. It might have something to do with the fact that Red Hat has always been providing professional support for their OS, or something else might be the reason here.


i really can't stand this stupid chatter and all the glorification of a few well known brands amongst the linux distributions. sure -- we all know similar from mac-vs-windows fights. but do we really want to share their culture? isn't linux and this kind of 'freedom' proclaimed by the GNU manifest different even in this regard?

i would neither agree on the actual importance or dominance of the mentioned very commercial oriented distributions, nor do i see any significant technical benefits or advance inextricably linked to them. the vital user community of debian, arch etc. and the vast amount of helpful documentation originated by them, is IMHO much more valuable in practice, than just utilizing the most prestigious brand of linux derivative...

but back to the main thread...

15b1 works really well on linux!

this is why i spend some time recently, to experiment with more user friendly and distribution agnostic alternatives to its present deployment. for this purpose i used nvidia-docker to prepare ready-prepared images of a clean CentOS runtime environment resp. resolve setup, which can be transferred and executed on nearly any kind of linux just the same. it's still in a very early stage of development, but you can already take a look at: https://gitlab.com/mash-graz/resolve to get a rough idea about this uncommon approach and all its pro and cons.
I am not saying one is more important than the other, and I personally believe that users should be free to choose ehatever distro they would like to run.

Believe me, if I had to choose, I probably won't be running CentOS for my main desktop, but I need to run because I need Blackmagic's support when I get a problem. I am trying to build my workflow around Resolve for the time being, as it is the only NLE on Linux that I actually liked.

I know how important the user community is, as I myself relied on it hundreds of times since I started using Linux. It is just that, with a proprietary program like Resolve, the community won't be able to help with every single problem, as some of them would be related to the actual code of Resolve that they don't have access to.

When it comes ti the whole 'dominance' part, maybe this isn't the best word to describe the situation. Let's use 'popular' instead.

Am I trying to say that this popularity should matter and that users should stick to popular distros? No. Does it matter to Blackmagic? Of course. Keep in mind, they are not an open source company by the way, so they won't care that much about the values of open source.

I personally wish that they would find a way to release Resolve in an *.appimagen so it runs across all distros, but until that happens, I was just stating the fact that, due to the popularity of RHEL/CentOS within the big VFX and animation studios, this is why Blackmagic chose to only support Resolve on this distro.

Sent from my SM-G920F using Tapatalk
System specs:
Resolve version: 15.0.0B.065
Fusion version: 9.0.2
OS: CentOS 7
CPU: Intel i7-4790k 4GHz Quad-Core
RAM: 32GB
GPU: NVIDIA GeForce 1080 Ti 11GB
Offline

Sulo Kokki

  • Posts: 113
  • Joined: Thu Sep 28, 2017 11:39 pm

Re: DaVinci Resolve Studio 15 Beta doesn't run on Linux

PostTue Apr 17, 2018 9:58 am

HealthWyzeMedia wrote:I also want to say that it's insane that BlackMagic is basing their Linux version on CentOS, when only a tiny portion of people use it. Why wouldn't you code for the distribution that most people are using?
Because when BMD bought out the assets for Resolve (and other DavSys products) at the turn of the decade, it was running on an RHEL turnkey system. BMD took the route of least hassle and switched Red Hat to CentOS. This was/is the Advanced Panel setup; the stand-alone version has only been around for a year or so.

MikeRochefort wrote:Pretty much all post production houses around the globe (at least in VFX) that operate in a Linux environment utilize RHEL or CentOS. To others, not catering to that market over the home or indie user would be insane.
Those big post houses are likely to use the Advanced Panel turnkey system, anyway. To utilize CentOS in that sort of config is acceptable - but to shove that platform to stand-alone users is a horse of different color. Flatpak would serve the stand-alone users better than having to hack it out of CentOS.

Martin Schitter wrote:i really can't stand this stupid chatter and all the glorification of a few well known brands amongst the linux distributions.
But Martin, CentOS is such a pro distro compared to the likes of Debian/Arch :-D (Jokes aside, it's sad that particularly Arch and/or AMD GPU users are getting the short end of the stick, coupled with arguments that CentOS, by some mysterious attributes, defaults as a better Resolve platform than the rest of the Linux distros.)

Abdelrahman Magdy wrote:Believe me, if I had to choose, I probably won't be running CentOS for my main desktop, but I need to run because I need Blackmagic's support when I get a problem.
I've found that I'm better off using Linux Mint for exactly the same reason. It runs just fine with an Nvidia GPU. Getting the baseline setup right was tricky, for sure, because the software came in with inherent bugs that BMD was apparently oblivious to. Yes, this stuff occurred on CentOS too - support said they can replicate the issues, but were unaware of when they'd be fixed. So I thought, they can keep their supported config for all I care.

Martin Schitter wrote:15b1 works really well on linux!
Early days, but I'm siding with you on that. :)
Linux Mint 18.3 | DaVinci Resolve 15.0b6 | Desktop Video 10.9.3 | OSX 10.11.6
Offline

Abdelrahman Magdy

  • Posts: 226
  • Joined: Fri Jan 23, 2015 10:08 pm

Re: DaVinci Resolve Studio 15 Beta doesn't run on Linux

PostTue Apr 17, 2018 10:20 am

Sulo Kokki wrote:But Martin, CentOS is such a pro distro compared to the likes of Debian/Arch

By the way, as far as I can see from the posts here, no one said that CentOS is a better distro for pros compared to Debian/Arch. What was said is that RHEL/CentOS seems to be used more in the pro circles, especially when it comes to VFX and animation studios. How did that happen? I haven't done any research to find the answer for that question. Does that mean that CentOS is a better distro? Not at all.

I can't speak about Arch, as I haven't tried it or any distros based on it, but I have been using Debain based distros since 2012, and I personally prefer them. The fact that their user community is bigger, which means it is easier to find support, is on its own a good reason for me to like them.

Also, the amount of packages available on these distros is amazing when compared to CentOS. There are some programs that I have struggled to run on CentOS, which used to run very easily on Linux Mint.

Sulo Kokki wrote:I've found that I'm better off using Linux Mint for exactly the same reason. It runs just fine with an Nvidia GPU. Getting the baseline setup right was tricky, for sure, because the software came in with inherent bugs that BMD was apparently oblivious to. Yes, this stuff occurred on CentOS too - support said they can replicate the issues, but were unaware of when they'd be fixed. So I thought, they can keep their supported config for all I care.

In this case, you are right. CentOS doesn't guarantee that any bugs you find in the software will be fixed. However, there seems to be few things, which I couldn't get to work on Linux Mint, that worked out of the box on CentOS. Tbh, they were specific to Fusion not Resolve. On Linux Mint, Fusion's Render Manager only worked for me if I ran Fusion with 'sudo'. There might have been something that I could have configured to get it to work, but I couldn't find it at that time. The other thing was Python. For some reason, I couldn't get Fusion to recognise Python on Linux Mint at all. These two things, for instance, worked out of the box.
System specs:
Resolve version: 15.0.0B.065
Fusion version: 9.0.2
OS: CentOS 7
CPU: Intel i7-4790k 4GHz Quad-Core
RAM: 32GB
GPU: NVIDIA GeForce 1080 Ti 11GB
Offline

Abdelrahman Magdy

  • Posts: 226
  • Joined: Fri Jan 23, 2015 10:08 pm

Re: DaVinci Resolve Studio 15 Beta doesn't run on Linux

PostTue Apr 17, 2018 10:32 am

Martin Schitter wrote:this is why i spend some time recently, to experiment with more user friendly and distribution agnostic alternatives to its present deployment. for this purpose i used nvidia-docker to prepare ready-prepared images of a clean CentOS runtime environment resp. resolve setup, which can be transferred and executed on nearly any kind of linux just the same. it's still in a very early stage of development, but you can already take a look at: https://gitlab.com/mash-graz/resolve to get a rough idea about this uncommon approach and all its pro and cons.

This looks like an interesting solution, Martin. I will have to try it sometime.
System specs:
Resolve version: 15.0.0B.065
Fusion version: 9.0.2
OS: CentOS 7
CPU: Intel i7-4790k 4GHz Quad-Core
RAM: 32GB
GPU: NVIDIA GeForce 1080 Ti 11GB
Offline

Martin Schitter

  • Posts: 734
  • Joined: Tue Apr 28, 2015 10:41 pm

Re: DaVinci Resolve Studio 15 Beta doesn't run on Linux

PostTue Apr 17, 2018 7:38 pm

Abdelrahman Magdy wrote:I personally wish that they would find a way to release Resolve in an *.appimagen so it runs across all distros, ...


yes -- i can understand this desire, but after experimenting with many different approaches, i finally have to say, that AppImage isn't able to isolate those complexity, which should be seen as as the source of most actual incompatibilities in case of resolve. AppImage is a really simple and very limited form of packaging, which is much weaker than snappy and flatpack, docker/LXC containerization, light wight clear/kata vm containers, and full blown virtual machines. this ordered sequence of well know alternatives also reflects their actual isolation capabilities resp. ability to reproduce a given runtime environment in a foreign ambient. in case of resolve the latter becomes really important, because the real troubles are usually not related to simple library dependencies or the feature set of a particular linux kernel, but in most cases affected by graphic card related issues and differences between driver releases.

the really strange and somehow paradox side of BMDs decision, to choose CentOS as the only officially supported platform, should be simply seen in the obvious fact, that this particular linux distribution doesn't come with support for the required proprietary nvidia graphics card drivers out of the box. in contrast to most other distributions, where users can install all the necessary drives with a simple package management command, which guaranties similar and reproducible conditions on any machine, you will will always find all sorts of different on an partially incompatible nvidia drivers on CentOS setups. this should be really seen as one of the most obvious reasons, why it simple doesn't make sense, to concentrate on on this particular distribution or insist on it's 'popularity' in the professional wold, because of this undeniable obvious shortcomings concerning unified GPU driver support.

when i have chosen nvidia-docker and a unmodified CentOS runtime environment within the containers this time, this was mainly motivated by the fact, that i simply can not stand this really stupid attitude of some BMD representatives and DR fanboys anymore, which always blame the users and their inadequate setups for anything, which doesn't work as expected. but in this model, you simply can not argue in this manner. it represents in fact a much more clean and unmodified CentOS environment, as you'll ever will find it anywhere on a real world studio workstation. but even in this case you still have to fight unavoidable varieties caused by different graphic hardware and driver differences on the host side, although the nvidia developers did a really great job to workaround most of this issues by providing nvidia-docker especially for this purpose and publishing a set of ready prepared official docker base images.

although it's a little bit laborious to setup nvidia-docker for the first time, it will make updates and various other user cases much more comfortable. that's why it's also very common solution to deploy complex setups in the machine learning nowadays, where you need similar access to GPU hardware.

it's also very interesting, that you can not only switch between different versions of the application very easily by this approach, it also helps to expose some strange behavior of resolve in slightly different runtime enviroments.

just to give you an example:

when i yesterday was in hurry, to push some changes to the repository and the CI system, which automatically rebuilds the images, i did miss a little detail. on a test run on my private machine at home, it did show some crashes (immediately going down, whenever i opened the color tab), which i've never seen all the days before. i couldn't fix it quickly and went to bed a little bit frustrated. but when i got up, after the second cup of coffee, i somehow noticed, that i did utilize a slightly less restrictive setup in my earlier tests. so i added a simple '--privileged' option into the startup scrip, and the issues disappeared. that's a very interesting observation, because you should expect the same behavior, if you try to run resolve on any more secure linux distributions too.

finally i have to say, that i still see this docker related experiments just as a last resort to work around all those limitations of the actual installer in an acceptable consequent way, but i wouldn't suggest it as a real alternative to more advanced native packaging. it's already quite questionable, that many closed source applications come with huge sets of accompanying dynamic libraries, which somehow nearly duplicate a whole linux setup. that's IMHO a quite regrettable development. it's not only making installer packages unnecessary bloated, but it also inherits a lot of bugs within all those libraries, which are often already fixed in the same libraries on the system. this makes it very hard to trace and fix bugs in a more reliable manner. using the system libraries and adequate package dependencies looks much more satisfying in this respect. software development should always be seen as kind of teamwork, where everybody has to concentrate on just his specific task, without hindering other players on the field by claiming the whole playground for oneself.
Last edited by Martin Schitter on Tue Apr 17, 2018 8:20 pm, edited 5 times in total.
Offline

Simas Gineika

  • Posts: 23
  • Joined: Sat Nov 25, 2017 6:33 pm

Re: DaVinci Resolve Studio 15 Beta doesn't run on Linux

PostTue Apr 17, 2018 7:55 pm

okay, I get the output like this after clinfo:

Code: Select all
X server found. dri2 connection failed!
DRM_IOCTL_I915_GEM_APERTURE failed: Invalid argument
Assuming 131072kB available aperture size.
May lead to reduced performance or incorrect rendering.
get chip id failed: -1 [22]
param: 4, val: 0
DRM_IOCTL_I915_GEM_APERTURE failed: Invalid argument
Assuming 131072kB available aperture size.
May lead to reduced performance or incorrect rendering.
get chip id failed: -1 [22]
param: 4, val: 0
DRM_IOCTL_I915_GEM_APERTURE failed: Invalid argument
Assuming 131072kB available aperture size.
May lead to reduced performance or incorrect rendering.
get chip id failed: -1 [22]
param: 4, val: 0
X server found. dri2 connection failed!
DRM_IOCTL_I915_GEM_APERTURE failed: Invalid argument
Assuming 131072kB available aperture size.
May lead to reduced performance or incorrect rendering.
get chip id failed: -1 [22]
param: 4, val: 0
DRM_IOCTL_I915_GEM_APERTURE failed: Invalid argument
Assuming 131072kB available aperture size.
May lead to reduced performance or incorrect rendering.
get chip id failed: -1 [22]
param: 4, val: 0
DRM_IOCTL_I915_GEM_APERTURE failed: Invalid argument
Assuming 131072kB available aperture size.
May lead to reduced performance or incorrect rendering.
get chip id failed: -1 [22]
param: 4, val: 0
cl_get_gt_device(): error, unknown device: 0
X server found. dri2 connection failed!
DRM_IOCTL_I915_GEM_APERTURE failed: Invalid argument
Assuming 131072kB available aperture size.
May lead to reduced performance or incorrect rendering.
get chip id failed: -1 [22]
param: 4, val: 0
DRM_IOCTL_I915_GEM_APERTURE failed: Invalid argument
Assuming 131072kB available aperture size.
May lead to reduced performance or incorrect rendering.
get chip id failed: -1 [22]
param: 4, val: 0
DRM_IOCTL_I915_GEM_APERTURE failed: Invalid argument
Assuming 131072kB available aperture size.
May lead to reduced performance or incorrect rendering.
get chip id failed: -1 [22]
param: 4, val: 0
X server found. dri2 connection failed!
DRM_IOCTL_I915_GEM_APERTURE failed: Invalid argument
Assuming 131072kB available aperture size.
May lead to reduced performance or incorrect rendering.
get chip id failed: -1 [22]
param: 4, val: 0
DRM_IOCTL_I915_GEM_APERTURE failed: Invalid argument
Assuming 131072kB available aperture size.
May lead to reduced performance or incorrect rendering.
get chip id failed: -1 [22]
param: 4, val: 0
DRM_IOCTL_I915_GEM_APERTURE failed: Invalid argument
Assuming 131072kB available aperture size.
May lead to reduced performance or incorrect rendering.
get chip id failed: -1 [22]
param: 4, val: 0
cl_get_gt_device(): error, unknown device: 0
Number of platforms                               3
  Platform Name                                   NVIDIA CUDA
  Platform Vendor                                 NVIDIA Corporation
  Platform Version                                OpenCL 1.2 CUDA 9.1.84
  Platform Profile                                FULL_PROFILE
  Platform Extensions                             cl_khr_global_int32_base_atomics cl_khr_global_int32_extended_atomics cl_khr_local_int32_base_atomics cl_khr_local_int32_extended_atomics cl_khr_fp64 cl_khr_byte_addressable_store cl_khr_icd cl_khr_gl_sharing cl_nv_compiler_options cl_nv_device_attribute_query cl_nv_pragma_unroll cl_nv_copy_opts cl_nv_create_buffer
  Platform Extensions function suffix             NV

  Platform Name                                   Portable Computing Language
  Platform Vendor                                 The pocl project
  Platform Version                                OpenCL 1.2 pocl 0.15-pre, LLVM 5.0.0
  Platform Profile                                FULL_PROFILE
  Platform Extensions                             cl_khr_icd
  Platform Extensions function suffix             POCL

  Platform Name                                   Intel Gen OCL Driver
  Platform Vendor                                 Intel
  Platform Version                                OpenCL 2.0 beignet 1.3
  Platform Profile                                FULL_PROFILE
  Platform Extensions                             cl_khr_global_int32_base_atomics cl_khr_global_int32_extended_atomics cl_khr_local_int32_base_atomics cl_khr_local_int32_extended_atomics cl_khr_byte_addressable_store cl_khr_3d_image_writes cl_khr_image2d_from_buffer cl_khr_depth_images cl_khr_spir cl_khr_icd cl_intel_accelerator cl_intel_subgroups cl_intel_subgroups_short cl_khr_gl_sharing
  Platform Extensions function suffix             Intel
X server found. dri2 connection failed!
DRM_IOCTL_I915_GEM_APERTURE failed: Invalid argument
Assuming 131072kB available aperture size.
May lead to reduced performance or incorrect rendering.
get chip id failed: -1 [22]
param: 4, val: 0
DRM_IOCTL_I915_GEM_APERTURE failed: Invalid argument
Assuming 131072kB available aperture size.
May lead to reduced performance or incorrect rendering.
get chip id failed: -1 [22]
param: 4, val: 0
DRM_IOCTL_I915_GEM_APERTURE failed: Invalid argument
Assuming 131072kB available aperture size.
May lead to reduced performance or incorrect rendering.
get chip id failed: -1 [22]
param: 4, val: 0
cl_get_gt_device(): error, unknown device: 0

  Platform Name                                   NVIDIA CUDA
Number of devices                                 3
  Device Name                                     GeForce GTX 1080 Ti
  Device Vendor                                   NVIDIA Corporation
  Device Vendor ID                                0x10de
  Device Version                                  OpenCL 1.2 CUDA
  Driver Version                                  390.48
  Device OpenCL C Version                         OpenCL C 1.2
  Device Type                                     GPU
  Device Available                                Yes
  Device Profile                                  FULL_PROFILE
  Device Topology (NV)                            PCI-E, 65:00.0
  Max compute units                               28
  Max clock frequency                             1582MHz
  Compute Capability (NV)                         6.1
  Device Partition                                (core)
    Max number of sub-devices                     1
    Supported partition types                     None
  Max work item dimensions                        3
  Max work item sizes                             1024x1024x64
  Max work group size                             1024
  Compiler Available                              Yes
  Linker Available                                Yes
  Preferred work group size multiple              32
  Warp size (NV)                                  32
  Preferred / native vector sizes                 
    char                                                 1 / 1       
    short                                                1 / 1       
    int                                                  1 / 1       
    long                                                 1 / 1       
    half                                                 0 / 0        (n/a)
    float                                                1 / 1       
    double                                               1 / 1        (cl_khr_fp64)
  Half-precision Floating-point support           (n/a)
  Single-precision Floating-point support         (core)
    Denormals                                     Yes
    Infinity and NANs                             Yes
    Round to nearest                              Yes
    Round to zero                                 Yes
    Round to infinity                             Yes
    IEEE754-2008 fused multiply-add               Yes
    Support is emulated in software               No
    Correctly-rounded divide and sqrt operations  Yes
  Double-precision Floating-point support         (cl_khr_fp64)
    Denormals                                     Yes
    Infinity and NANs                             Yes
    Round to nearest                              Yes
    Round to zero                                 Yes
    Round to infinity                             Yes
    IEEE754-2008 fused multiply-add               Yes
    Support is emulated in software               No
  Address bits                                    64, Little-Endian
  Global memory size                              11718230016 (10.91GiB)
  Error Correction support                        No
  Max memory allocation                           2929557504 (2.728GiB)
  Unified memory for Host and Device              No
  Integrated memory (NV)                          No
  Minimum alignment for any data type             128 bytes
  Alignment of base address                       4096 bits (512 bytes)
  Global Memory cache type                        Read/Write
  Global Memory cache size                        458752 (448KiB)
  Global Memory cache line size                   128 bytes
  Image support                                   Yes
    Max number of samplers per kernel             32
    Max size for 1D images from buffer            134217728 pixels
    Max 1D or 2D image array size                 2048 images
    Max 2D image size                             16384x32768 pixels
    Max 3D image size                             16384x16384x16384 pixels
    Max number of read image args                 256
    Max number of write image args                16
  Local memory type                               Local
  Local memory size                               49152 (48KiB)
  Registers per block (NV)                        65536
  Max constant buffer size                        65536 (64KiB)
  Max number of constant args                     9
  Max size of kernel argument                     4352 (4.25KiB)
  Queue properties                               
    Out-of-order execution                        Yes
    Profiling                                     Yes
  Prefer user sync for interop                    No
  Profiling timer resolution                      1000ns
  Execution capabilities                         
    Run OpenCL kernels                            Yes
    Run native kernels                            No
    Kernel execution timeout (NV)                 Yes
  Concurrent copy and kernel execution (NV)       Yes
    Number of async copy engines                  2
  printf() buffer size                            1048576 (1024KiB)
  Built-in kernels                               
  Device Extensions                               cl_khr_global_int32_base_atomics cl_khr_global_int32_extended_atomics cl_khr_local_int32_base_atomics cl_khr_local_int32_extended_atomics cl_khr_fp64 cl_khr_byte_addressable_store cl_khr_icd cl_khr_gl_sharing cl_nv_compiler_options cl_nv_device_attribute_query cl_nv_pragma_unroll cl_nv_copy_opts cl_nv_create_buffer

  Device Name                                     GeForce GTX 1080
  Device Vendor                                   NVIDIA Corporation
  Device Vendor ID                                0x10de
  Device Version                                  OpenCL 1.2 CUDA
  Driver Version                                  390.48
  Device OpenCL C Version                         OpenCL C 1.2
  Device Type                                     GPU
  Device Available                                Yes
  Device Profile                                  FULL_PROFILE
  Device Topology (NV)                            PCI-E, 17:00.0
  Max compute units                               20
  Max clock frequency                             1733MHz
  Compute Capability (NV)                         6.1
  Device Partition                                (core)
    Max number of sub-devices                     1
    Supported partition types                     None
  Max work item dimensions                        3
  Max work item sizes                             1024x1024x64
  Max work group size                             1024
  Compiler Available                              Yes
  Linker Available                                Yes
  Preferred work group size multiple              32
  Warp size (NV)                                  32
  Preferred / native vector sizes                 
    char                                                 1 / 1       
    short                                                1 / 1       
    int                                                  1 / 1       
    long                                                 1 / 1       
    half                                                 0 / 0        (n/a)
    float                                                1 / 1       
    double                                               1 / 1        (cl_khr_fp64)
  Half-precision Floating-point support           (n/a)
  Single-precision Floating-point support         (core)
    Denormals                                     Yes
    Infinity and NANs                             Yes
    Round to nearest                              Yes
    Round to zero                                 Yes
    Round to infinity                             Yes
    IEEE754-2008 fused multiply-add               Yes
    Support is emulated in software               No
    Correctly-rounded divide and sqrt operations  Yes
  Double-precision Floating-point support         (cl_khr_fp64)
    Denormals                                     Yes
    Infinity and NANs                             Yes
    Round to nearest                              Yes
    Round to zero                                 Yes
    Round to infinity                             Yes
    IEEE754-2008 fused multiply-add               Yes
    Support is emulated in software               No
  Address bits                                    64, Little-Endian
  Global memory size                              8513978368 (7.929GiB)
  Error Correction support                        No
  Max memory allocation                           2128494592 (1.982GiB)
  Unified memory for Host and Device              No
  Integrated memory (NV)                          No
  Minimum alignment for any data type             128 bytes
  Alignment of base address                       4096 bits (512 bytes)
  Global Memory cache type                        Read/Write
  Global Memory cache size                        327680 (320KiB)
  Global Memory cache line size                   128 bytes
  Image support                                   Yes
    Max number of samplers per kernel             32
    Max size for 1D images from buffer            134217728 pixels
    Max 1D or 2D image array size                 2048 images
    Max 2D image size                             16384x32768 pixels
    Max 3D image size                             16384x16384x16384 pixels
    Max number of read image args                 256
    Max number of write image args                16
  Local memory type                               Local
  Local memory size                               49152 (48KiB)
  Registers per block (NV)                        65536
  Max constant buffer size                        65536 (64KiB)
  Max number of constant args                     9
  Max size of kernel argument                     4352 (4.25KiB)
  Queue properties                               
    Out-of-order execution                        Yes
    Profiling                                     Yes
  Prefer user sync for interop                    No
  Profiling timer resolution                      1000ns
  Execution capabilities                         
    Run OpenCL kernels                            Yes
    Run native kernels                            No
    Kernel execution timeout (NV)                 No
  Concurrent copy and kernel execution (NV)       Yes
    Number of async copy engines                  2
  printf() buffer size                            1048576 (1024KiB)
  Built-in kernels                               
  Device Extensions                               cl_khr_global_int32_base_atomics cl_khr_global_int32_extended_atomics cl_khr_local_int32_base_atomics cl_khr_local_int32_extended_atomics cl_khr_fp64 cl_khr_byte_addressable_store cl_khr_icd cl_khr_gl_sharing cl_nv_compiler_options cl_nv_device_attribute_query cl_nv_pragma_unroll cl_nv_copy_opts cl_nv_create_buffer

  Device Name                                     GeForce GTX 1080
  Device Vendor                                   NVIDIA Corporation
  Device Vendor ID                                0x10de
  Device Version                                  OpenCL 1.2 CUDA
  Driver Version                                  390.48
  Device OpenCL C Version                         OpenCL C 1.2
  Device Type                                     GPU
  Device Available                                Yes
  Device Profile                                  FULL_PROFILE
  Device Topology (NV)                            PCI-E, b3:00.0
  Max compute units                               20
  Max clock frequency                             1733MHz
  Compute Capability (NV)                         6.1
  Device Partition                                (core)
    Max number of sub-devices                     1
    Supported partition types                     None
  Max work item dimensions                        3
  Max work item sizes                             1024x1024x64
  Max work group size                             1024
  Compiler Available                              Yes
  Linker Available                                Yes
  Preferred work group size multiple              32
  Warp size (NV)                                  32
  Preferred / native vector sizes                 
    char                                                 1 / 1       
    short                                                1 / 1       
    int                                                  1 / 1       
    long                                                 1 / 1       
    half                                                 0 / 0        (n/a)
    float                                                1 / 1       
    double                                               1 / 1        (cl_khr_fp64)
  Half-precision Floating-point support           (n/a)
  Single-precision Floating-point support         (core)
    Denormals                                     Yes
    Infinity and NANs                             Yes
    Round to nearest                              Yes
    Round to zero                                 Yes
    Round to infinity                             Yes
    IEEE754-2008 fused multiply-add               Yes
    Support is emulated in software               No
    Correctly-rounded divide and sqrt operations  Yes
  Double-precision Floating-point support         (cl_khr_fp64)
    Denormals                                     Yes
    Infinity and NANs                             Yes
    Round to nearest                              Yes
    Round to zero                                 Yes
    Round to infinity                             Yes
    IEEE754-2008 fused multiply-add               Yes
    Support is emulated in software               No
  Address bits                                    64, Little-Endian
  Global memory size                              8513978368 (7.929GiB)
  Error Correction support                        No
  Max memory allocation                           2128494592 (1.982GiB)
  Unified memory for Host and Device              No
  Integrated memory (NV)                          No
  Minimum alignment for any data type             128 bytes
  Alignment of base address                       4096 bits (512 bytes)
  Global Memory cache type                        Read/Write
  Global Memory cache size                        327680 (320KiB)
  Global Memory cache line size                   128 bytes
  Image support                                   Yes
    Max number of samplers per kernel             32
    Max size for 1D images from buffer            134217728 pixels
    Max 1D or 2D image array size                 2048 images
    Max 2D image size                             16384x32768 pixels
    Max 3D image size                             16384x16384x16384 pixels
    Max number of read image args                 256
    Max number of write image args                16
  Local memory type                               Local
  Local memory size                               49152 (48KiB)
  Registers per block (NV)                        65536
  Max constant buffer size                        65536 (64KiB)
  Max number of constant args                     9
  Max size of kernel argument                     4352 (4.25KiB)
  Queue properties                               
    Out-of-order execution                        Yes
    Profiling                                     Yes
  Prefer user sync for interop                    No
  Profiling timer resolution                      1000ns
  Execution capabilities                         
    Run OpenCL kernels                            Yes
    Run native kernels                            No
    Kernel execution timeout (NV)                 No
  Concurrent copy and kernel execution (NV)       Yes
    Number of async copy engines                  2
  printf() buffer size                            1048576 (1024KiB)
  Built-in kernels                               
  Device Extensions                               cl_khr_global_int32_base_atomics cl_khr_global_int32_extended_atomics cl_khr_local_int32_base_atomics cl_khr_local_int32_extended_atomics cl_khr_fp64 cl_khr_byte_addressable_store cl_khr_icd cl_khr_gl_sharing cl_nv_compiler_options cl_nv_device_attribute_query cl_nv_pragma_unroll cl_nv_copy_opts cl_nv_create_buffer

  Platform Name                                   Portable Computing Language
Number of devices                                 1
  Device Name                                     pthread-Intel(R) Core(TM) i9-7920X CPU @ 2.90GHz
  Device Vendor                                   GenuineIntel
  Device Vendor ID                                0x8086
  Device Version                                  OpenCL 1.2 pocl HSTR: pthread-x86_64-unknown-linux-gnu-haswell
  Driver Version                                  0.15-pre
  Device OpenCL C Version                         OpenCL C 1.2 pocl
  Device Type                                     CPU
  Device Available                                Yes
  Device Profile                                  FULL_PROFILE
  Max compute units                               24
  Max clock frequency                             4300MHz
  Device Partition                                (core)
    Max number of sub-devices                     24
    Supported partition types                     equally, by counts
  Max work item dimensions                        3
  Max work item sizes                             4096x4096x4096
  Max work group size                             4096
  Compiler Available                              Yes
  Linker Available                                Yes
1 error generated.
=== CL_PROGRAM_BUILD_LOG ===
error: <built-in>:2:10: '/usr/lib64/clang/5.0.0/include/opencl-c.h' file not found
error: <built-in>:2:10: '/usr/lib64/clang/5.0.0/include/opencl-c.h' file not found
error: <built-in>:2:10: '/usr/lib64/clang/5.0.0/include/opencl-c.h' file not found
  Preferred work group size multiple              <getWGsizes:523: build program : error -11>
  Preferred / native vector sizes                 
    char                                                16 / 16     
    short                                                8 / 8       
    int                                                  4 / 4       
    long                                                 2 / 2       
    half                                                 8 / 8        (n/a)
    float                                                4 / 4       
    double                                               2 / 2        (cl_khr_fp64)
  Half-precision Floating-point support           (n/a)
  Single-precision Floating-point support         (core)
    Denormals                                     Yes
    Infinity and NANs                             Yes
    Round to nearest                              Yes
    Round to zero                                 Yes
    Round to infinity                             Yes
    IEEE754-2008 fused multiply-add               Yes
    Support is emulated in software               No
    Correctly-rounded divide and sqrt operations  No
  Double-precision Floating-point support         (cl_khr_fp64)
    Denormals                                     Yes
    Infinity and NANs                             Yes
    Round to nearest                              Yes
    Round to zero                                 Yes
    Round to infinity                             Yes
    IEEE754-2008 fused multiply-add               Yes
    Support is emulated in software               No
  Address bits                                    64, Little-Endian
  Global memory size                              65058062336 (60.59GiB)
  Error Correction support                        No
  Max memory allocation                           17179869184 (16GiB)
  Unified memory for Host and Device              Yes
  Minimum alignment for any data type             128 bytes
  Alignment of base address                       1024 bits (128 bytes)
  Global Memory cache type                        Read/Write
  Global Memory cache size                        32768 (32KiB)
  Global Memory cache line size                   64 bytes
  Image support                                   Yes
    Max number of samplers per kernel             16
    Max size for 1D images from buffer            1073741824 pixels
    Max 1D or 2D image array size                 2048 images
    Max 2D image size                             32768x32768 pixels
    Max 3D image size                             2048x2048x2048 pixels
    Max number of read image args                 128
    Max number of write image args                128
  Local memory type                               Global
  Local memory size                               268435456 (256MiB)
  Max constant buffer size                        268435456 (256MiB)
  Max number of constant args                     8
  Max size of kernel argument                     1024
  Queue properties                               
    Out-of-order execution                        No
    Profiling                                     Yes
  Prefer user sync for interop                    Yes
  Profiling timer resolution                      1ns
  Execution capabilities                         
    Run OpenCL kernels                            Yes
    Run native kernels                            Yes
  printf() buffer size                            1048576 (1024KiB)
  Built-in kernels                               
  Device Extensions                               cl_khr_byte_addressable_store cl_khr_global_int32_base_atomics cl_khr_global_int32_extended_atomics cl_khr_local_int32_base_atomics cl_khr_local_int32_extended_atomics cl_khr_3d_image_writes cl_khr_fp64 cl_khr_int64_base_atomics cl_khr_int64_extended_atomics

  Platform Name                                   Intel Gen OCL Driver
Number of devices                                 0

NULL platform behavior
  clGetPlatformInfo(NULL, CL_PLATFORM_NAME, ...)  NVIDIA CUDA
  clGetDeviceIDs(NULL, CL_DEVICE_TYPE_ALL, ...)   Success [NV]
  clCreateContext(NULL, ...) [default]            Success [NV]
  clCreateContext(NULL, ...) [other]              Success [POCL]
  clCreateContextFromType(NULL, CL_DEVICE_TYPE_DEFAULT)  No platform
  clCreateContextFromType(NULL, CL_DEVICE_TYPE_CPU)  No devices found in platform
  clCreateContextFromType(NULL, CL_DEVICE_TYPE_GPU)  No platform
  clCreateContextFromType(NULL, CL_DEVICE_TYPE_ACCELERATOR)  No devices found in platform
  clCreateContextFromType(NULL, CL_DEVICE_TYPE_CUSTOM)  No devices found in platform
  clCreateContextFromType(NULL, CL_DEVICE_TYPE_ALL)  No platform

ICD loader properties
  ICD loader Name                                 OpenCL ICD Loader
  ICD loader Vendor                               OCL Icd free software
  ICD loader Version                              2.2.12
  ICD loader Profile                              OpenCL 2.2



Can someone help me to solve Fusion problem? I'm not quite experienced in Linux systems yet.
Offline

Martin Schitter

  • Posts: 734
  • Joined: Tue Apr 28, 2015 10:41 pm

Re: DaVinci Resolve Studio 15 Beta doesn't run on Linux

PostTue Apr 17, 2018 8:11 pm

Simas Gineika wrote:okay, I get the output like this after clinfo


the occurrences of i915 dri entries in this output let me guess, that you are using a mixed setup of intelI iGPU and nvidia cards. this wouldn't work on CentOS, because it doesn't support GLVND, but on fedora it's o.k. this output looks good. OpenCL is available.

but the crash, when you switch to the fusion tab, could be perhaps have the same reasons as mentioned in my last post -- but that's just a very vague guess, because there are so much other possibilities thinkable as well.

studding the cryptic output in the /opt/resolve/logs folder is often the most useful advice.
Offline

Abdelrahman Magdy

  • Posts: 226
  • Joined: Fri Jan 23, 2015 10:08 pm

Re: DaVinci Resolve Studio 15 Beta doesn't run on Linux

PostTue Apr 17, 2018 8:30 pm

Martin Schitter wrote:yes -- i can understand this desire, but after experimenting with many different approaches, i finally have to say, that AppImage isn't able to isolate those complexity, which should be seen as as the source of most actual incompatibilities in case of resolve. AppImage is a really simple and very limited form of packaging, which is much weaker than snappy and flatpack, docker/LXC containerization, light wight clear/kata vm containers, and full blown virtual machines.

Can't argue on this one as I haven't delved that deeply into different approaches to packaging.

Martin Schitter wrote:the really strange and somehow paradox side of BMDs decision, to choose CentOS as the only officially supported platform, should be simply seen in the obvious fact, that this particular linux distribution doesn't come with support for the required proprietary nvidia graphics card drivers out of the box. in contrast to most other distributions, where users can install all the necessary drives with a simple package management command, which guaranties similar and reproducible conditions on any machine, you will will always find all sorts of different on an partially incompatible nvidia drivers on CentOS setups. this should be really seen as one of the most obvious reasons, why it simple doesn't make sense, to concentrate on on this particular distribution or insist on it's 'popularity' in the professional wold, because of this undeniable obvious shortcomings concerning unified GPU driver support.

I have personally had no issues so far with Nvidia drivers on CentOS. All I do is add the 'elrepo' repository, and install the kmod-nvidia packages using 'yum'. It only needs a couple of command lines, works out of the box (at least for me), and updates regularly.

However, I might have the answer to why Blackmagic are not concerned about the fact that users cannot easily install Nvidia drivers on CentOS using package managers. The thing is, Blackmagic wants the users to download the drivers directly from Nvidia's website and install them. Anything else, and their support would repeat the same message "We don't support this config. You should install the official proprietary drivers". They have told me that before when I contacted them about an issue I had.

After checking with one of the CentOS forum admins, he confirmed that the kmod-nvidia are the official drivers, only packaged to make them easier to maintain and update, I chose to ignore Blackmagic's warning on this one, and have been using them with no issues at all since then.

Martin Schitter wrote:when i have chosen nvidia-docker and a unmodified CentOS runtime environment within the containers this time, this was mainly motivated by the fact, that i simply can not stand this really stupid attitude of some BMD representatives and DR fanboys anymore, which always blame the users and their inadequate setups for anything, which doesn't work as expected.

This is the same reason why I had to switch to CentOS. I got tired from getting the same response, and since, as I said, I don't have enough experience with things like containers, the only way for me to eliminate that OS variable from the equation was to switch to CentOS.

Martin Schitter wrote:finally i have to say, that i still see this docker related experiments just as a last resort to work around all those limitations of the actual installer in an acceptable consequent way, but i don't see it as a real alternative to more advanced native packaging.

Can't disagree with you on this one. I think with programs like Resolve, where not all users are expected to have enough technical knowledge to fiddle with the system, these programs should be made into easy-to-install native packages. Hope Blackmagic would consider doing that soon, although I have a feeling they won't.
System specs:
Resolve version: 15.0.0B.065
Fusion version: 9.0.2
OS: CentOS 7
CPU: Intel i7-4790k 4GHz Quad-Core
RAM: 32GB
GPU: NVIDIA GeForce 1080 Ti 11GB
Offline

Simas Gineika

  • Posts: 23
  • Joined: Sat Nov 25, 2017 6:33 pm

Re: DaVinci Resolve Studio 15 Beta doesn't run on Linux

PostTue Apr 17, 2018 9:07 pm

This is the same reason why I had to switch to CentOS. I got tired from getting the same response, and since, as I said, I don't have enough experience with things like containers, the only way for me to eliminate that OS variable from the equation was to switch to CentOS.

I think with programs like Resolve, where not all users are expected to have enough technical knowledge to fiddle with the system, these programs should be made into easy-to-install native packages. Hope Blackmagic would consider doing that soon, although I have a feeling they won't.


I feel you. for me, I was trying to setup CentOS on my hardware, and was a mess. Simple things as wacom tablet doesn't work until you update kernel. spent few hours on that.. After kernel update had issues with installing nvidia official drivers and after that was unable to boot and system halted. Well at least from this post I know that there was kmod-nvidia. But that small thing, can't spend days on installing and reinstalling system :) I believe new 7.5 release will be really good, but updates on that is so slow, and lot's of hardware are left unsupported even one year old. Really would be nice to have smooth installation, as mentioned before, not all users have experience. Although sometimes even step-by-step guides is even hard to find. And for now, looks like OpenCL works, and check logs in resolve folder, well, I checked, but have no idea what the output means. So will stick with fusion 9.0.2 for now until b2 will be released
Offline

Abdelrahman Magdy

  • Posts: 226
  • Joined: Fri Jan 23, 2015 10:08 pm

Re: DaVinci Resolve Studio 15 Beta doesn't run on Linux

PostWed Apr 18, 2018 9:32 am

Simas Gineika wrote:I feel you. for me, I was trying to setup CentOS on my hardware, and was a mess. Simple things as wacom tablet doesn't work until you update kernel. spent few hours on that.. After kernel update had issues with installing nvidia official drivers and after that was unable to boot and system halted. Well at least from this post I know that there was kmod-nvidia. But that small thing, can't spend days on installing and reinstalling system :)

It seems I am the only one not having major issues with CentOS :D. I have two Wacom tablets and they both work fine on it. The only two issues I had with it is the fact that the customization on CentOS is a bit limited, and that I couldn't get the GUI calibration to work. Both issues were fixed using xsetwacom. Not the most ideal situation of course, but it works fine. In fact, one of my tablets doesn't work properly on Windows, but works perfectly on CentOS.

Regarding the official Nvidia drivers, I agree they are a huge headache. I have tried multiple times to install the ones available on Nvidia's website to make sure that I am using everything recommended by Blackmagic, but every time I did that, CentOS would fail to boot. This is why I basically gave up on it, and just used the kmod-nvidia packages, and they work really well.

Simas Gineika wrote:Although sometimes even step-by-step guides is even hard to find.

This is my main gripe with CentOS. Because the user-base outside the enterprise world seems to be small compared to distros like Ubuntu and Linux Mint, there are less resources for users on how to fix issues. Sometimes, I would find solutions that would work on Ubuntu, but they won't work for me because of the differences between the two distros. This makes using CentOS a bit difficult. After all, the time I have to learn the ins and outs of an OS like CentOS is limited to the times when I am not focusing on my main career, so sometimes I will need some easy and quick help.

My main hope now is that Blackmagic would consider releasing native packages, maybe for Resolve 16, as I am sure they will be busy trying to get Resolve 15 to a usable stable release.
System specs:
Resolve version: 15.0.0B.065
Fusion version: 9.0.2
OS: CentOS 7
CPU: Intel i7-4790k 4GHz Quad-Core
RAM: 32GB
GPU: NVIDIA GeForce 1080 Ti 11GB
Offline

Simas Gineika

  • Posts: 23
  • Joined: Sat Nov 25, 2017 6:33 pm

Re: DaVinci Resolve Studio 15 Beta doesn't run on Linux

PostWed Apr 18, 2018 9:43 am

May I ask what wacom tablet you have? As i use PTH-660 (intuos pro paper) version and it was not recognised until i updated kernel to 4.15
Offline

Abdelrahman Magdy

  • Posts: 226
  • Joined: Fri Jan 23, 2015 10:08 pm

Re: DaVinci Resolve Studio 15 Beta doesn't run on Linux

PostWed Apr 18, 2018 1:47 pm

Simas Gineika wrote:May I ask what wacom tablet you have? As i use PTH-660 (intuos pro paper) version and it was not recognised until i updated kernel to 4.15

I have an old Bamboo Pen & Touch (CTH-460) and a Cintiq 13 HD. As far as I remember, I don't think I needed the update for them to work. I updated the kernel anyway to get the latest security features, but, at least, I am 80% sure the Bamboo worked out of the box. For the Cintiq, I would have gone through the update anyway, as I usually update the kernel before installing the Nvidia drivers that are needed to be able to use multiple monitors.
System specs:
Resolve version: 15.0.0B.065
Fusion version: 9.0.2
OS: CentOS 7
CPU: Intel i7-4790k 4GHz Quad-Core
RAM: 32GB
GPU: NVIDIA GeForce 1080 Ti 11GB
Offline
User avatar

jesuslovesyou101

  • Posts: 3
  • Joined: Fri Apr 13, 2018 10:47 pm
  • Location: Indiana, USA
  • Real Name: Daniel Clem

Re: DaVinci Resolve Studio 15 Beta doesn't run on Linux

PostWed Apr 18, 2018 5:51 pm

Ok to those who have gotten version 15 running, specifically any Ubuntu / Mint users, what did you do? and if I need to update in order to better fix the issues, do I manually delete the installed files, and if so are there any others besides " /opt/resolve/bin/resolve " that the desktop shortcut links to?
"If I had 6 hours to cut down a tree. I would spend the first 4 sharpening the axe."
~ Abraham Lincoln
Offline

Lars Goldschlager

  • Posts: 1
  • Joined: Wed Apr 18, 2018 5:50 pm
  • Real Name: Lars Goldschlager

Re: DaVinci Resolve Studio 15 Beta doesn't run on Linux

PostWed Apr 18, 2018 6:23 pm

As the IT half of a digital lab, on the topic of the discussion about distros to choose for default, I must say, I can perfectly well understand why RHEL and subsequently CentOS (as a, no money upfront alternative) were chosen. In "those days" and mainly still, Red Hat was the only company offering enterprise grade support and contracts for users, which would've been a plus both for Davinci Systems during development and their clients during maintenance/use.

Yet, I think those ages have changed, and I also feel strongly that touting CentOS as a "professional" distro for the use of BM for Resolve is as correct as trying to use a Cat shovel for running the Indy 500 since it's a professional vehicle.

I do not think it'd be sane for BM to chase a moving target, I feel if they do decide to give a nod to indie users by supporting some form of portability (static builds, flatpak, appimage, other containers, this is a discussion that can rage for months and to which I can bring no intelligent discourse) by spending man hours to develop such a version it's a boon to us, but I also feel CentOS might not be the best choice for the professional and oficial support.

Yes, CentOS can do everything any other distro does, whatever the original intent, if tweaked enough, but that doesn't make the process easy or necessarily stable (beyond known controlled environments like the Advanced Panel). I believe the right distro to achieve this would be Ubuntu.

First, the existence of subdistros like Ubuntu Studio and Debian Studio tells us there's already work being done towards a goal common to what we're trying to achieve with Resolve. That's effort that helps both the developer and the user.

Second, Canonical already has experience working with companies, like Steam, to help deliver a product/environment, and even when at not the same corporative level as Red Hat, I feel they're one of the strongest corporate players in Linux currently. Only their targets do not always align with what we could consider corporate.

And then here's an important inflection point... production and post production must work, yes, we can't make clients wait while we fix systems and try to make them work endlessly, but yet I feel it's wrong to apply the enterprise mentality to this media since we NEED to be more agile than other types of work. Workflows standards and technologies change in this media with blazing speed compared to what it would for a bank or a google server farm, we're already submerged in a quiet but lively fight for a dominant HDR standard, we've burned through generations of SDI and several network distribution protocols are taking hold, we are watching the birth of IMF and the maturity of Aces and a back and forth between the installed base of H264 vs the capabilities of H265 for online end user distribution, etc etc etc.

In short, I feel we need the "best of both worlds", working machines that get security patches for a decent amount of time while we can set up fresh new rapid cycle distros and libraries for tests and upgrades to new requirements.

We need the availability of support for the developers and large corporate deployments plus a non hostile community support for the end user (as someone in IT, in mostly not the best working conditions through most of my career I've dealt with all sorts of community support for all kind of OS including two flavors of BSD, two flavors of unix and five distros of Linux, and only programmers will understand this but dealing with the CentOS community vs the Ubuntu and Debian communities is like dealing with lisp programmers compared to python programmers, they're extremely knowledgeable and willing to help, but at the same time headstrong and not necessarily friendly to an end user, not that I believe they HAVE to be).

I feel, right now, the only environment that provides all this is Ubuntu and Canonical. I'm not saying it's the best, there are many reasons to choose other distros and their communities, but I feel it's the only currently logical fit.

Not that BM has any incentive to expend the large amount of money this change would cost to implement for no benefit other than making a system that already works for their large customers friendlier to their indie and free users.

Now if they'd reach the conclusion that they can maintain CentOS on the Advanced Panel which would make install on existing CentOS machines hassle free, and get enough revenue from Studio to feed the maintenance of using Ubuntu as an "alternative" official distro, then as a Debian user I'd be wonderfully glad, I'm sure I can make it work as I did with Steam at home ;) .

Now back at trying to have 15b1 recognize my existing working cuda 8.0 and OpenCL setups on Stretch to avoid having to stop jobs to dual boot into CentOS. Be well all.
Offline

Simas Gineika

  • Posts: 23
  • Joined: Sat Nov 25, 2017 6:33 pm

Re: DaVinci Resolve Studio 15 Beta doesn't run on Linux

PostWed Apr 18, 2018 6:58 pm

Abdelrahman Magdy wrote:
Simas Gineika wrote:May I ask what wacom tablet you have? As i use PTH-660 (intuos pro paper) version and it was not recognised until i updated kernel to 4.15

I have an old Bamboo Pen & Touch (CTH-460) and a Cintiq 13 HD. As far as I remember, I don't think I needed the update for them to work. I updated the kernel anyway to get the latest security features, but, at least, I am 80% sure the Bamboo worked out of the box. For the Cintiq, I would have gone through the update anyway, as I usually update the kernel before installing the Nvidia drivers that are needed to be able to use multiple monitors.


thats what I’m saying, new hardware is not supported on CentOS and to make everything work again for noob like me is bit of a pain. With fedora 27 had just install nvidia drivers and all good to go.

anyone who managed to run Resolve on other distro than CentOS give me a shout too! Need help!
Offline

Martin Schitter

  • Posts: 734
  • Joined: Tue Apr 28, 2015 10:41 pm

Re: DaVinci Resolve Studio 15 Beta doesn't run on Linux

PostWed Apr 18, 2018 6:59 pm

jesuslovesyou101 wrote:Ok to those who have gotten version 15 running, specifically any Ubuntu / Mint users, what did you do? and if I need to update in order to better fix the issues, do I manually delete the installed files, and if so are there any others besides " /opt/resolve/bin/resolve " that the desktop shortcut links to?


yes -- that's indeed one of the most important questions!

hacks, which do not respect the main principles, how a debian/mint/ubuntu system should be maintained, are therefore a really questionable help. proper uninstall capabilities and the awareness about all existing files in main system directories by the package management system are simply indispensable requirements on this kind of distributions.

and -- yes -- unfortunately the resolve installer (especially the panel driver module) will try to touch some files in the /usr hierarchy and [try to] install udev-rules and libraries at places, where they shouldn't be placed on this kind of distribution.

it's quite easy reproducible resp. analyzable if you run the installer within a container and use 'docker diff' to see, which files get actually changed. this was the mechanism, i used in earlier attempts, to generate .deb packages of resolve for myself.
Offline

Simas Gineika

  • Posts: 23
  • Joined: Sat Nov 25, 2017 6:33 pm

Re: DaVinci Resolve Studio 15 Beta doesn't run on Linux

PostThu Apr 19, 2018 9:14 pm

Code: Select all
./resolve: /opt/resolve/bin/../libs/libCg.so: no version information available (required by ./resolve)
./resolve: /opt/resolve/bin/../libs/libCgGL.so: no version information available (required by ./resolve)


This is terminal output. I already have libCg-3.1.0013-7 installed, also there are these libCg.so and libCgGL.so files in '/opt/resolve/libs' already, so I'm not sure what problem is. Anyone had same issues? Please let me know if there is workaround on that one
Offline

Martin Schitter

  • Posts: 734
  • Joined: Tue Apr 28, 2015 10:41 pm

Re: DaVinci Resolve Studio 15 Beta doesn't run on Linux

PostThu Apr 19, 2018 9:59 pm

Simas Gineika wrote:
Code: Select all
./resolve: /opt/resolve/bin/../libs/libCg.so: no version information available (required by ./resolve)
./resolve: /opt/resolve/bin/../libs/libCgGL.so: no version information available (required by ./resolve)


This is terminal output. I already have libCg-3.1.0013-7 installed, also there are these libCg.so and libCgGL.so files in '/opt/resolve/libs' already, so I'm not sure what problem is. Anyone had same issues? Please let me know if there is workaround on that one


this warning doesn't have to be senn as an indicator for a serious issue. it could be caused by the relocation of files, which perhaps doesn't satisfy other nvidia libraries expectations.

if you want to test, if the system wide Cg support works, use: 'cginfo'

this also prints a path, where this libraries should be expected usually.
Offline
User avatar

jesuslovesyou101

  • Posts: 3
  • Joined: Fri Apr 13, 2018 10:47 pm
  • Location: Indiana, USA
  • Real Name: Daniel Clem

Re: DaVinci Resolve Studio 15 Beta doesn't run on Linux

PostFri Apr 20, 2018 1:56 pm

As a side note, I do not currently use any dedicated graphics units, only Intel Integrated HD. With Lightworks this was perfectly sufficient for the 720p the free version is limited to. And supposedly DaVinci is even more efficient than Lightworks so I suspect for my limited uses integrated graphics will still be fine for what limited things I do (When it finally does work! )
"If I had 6 hours to cut down a tree. I would spend the first 4 sharpening the axe."
~ Abraham Lincoln
Offline

Martin Schitter

  • Posts: 734
  • Joined: Tue Apr 28, 2015 10:41 pm

Re: DaVinci Resolve Studio 15 Beta doesn't run on Linux

PostFri Apr 20, 2018 4:43 pm

jesuslovesyou101 wrote:As a side note, I do not currently use any dedicated graphics units, only Intel Integrated HD. With Lightworks this was perfectly sufficient for the 720p the free version is limited to. And supposedly DaVinci is even more efficient than Lightworks so I suspect for my limited uses integrated graphics will still be fine for what limited things I do (When it finally does work! )


i think, for resolve it's really useful and actually even necessary on the linux platform until now, to have an additional nvidia GPU and CUDA computing capabilities available. if you do not need for very demanding jobs, it can be a really affordable one -- like the 1050ti 4GB VRAM cards -- which will provide all the necessary compatibility to more expensive nvidia products, just slower, but not unusable for acceptable satisfying practical work.

resolves free version is much less restrictive in its feature set and supported project size and output formats than lightworks, but it's indeed more demanding in it's hardware requirements too.

in general i really understand your point of view and always try to keep the necessary investments and hardware dependencies as small as possible. it simple doesn't make much sense for less profit oriented work, do act like those others, which work on company property or earn so much money by their work, that everything looks quite different from their point of view. but for the majority of real world users, it's much more useful to find the right size resp. reasonable compromises, than just the ultimate high end solution.

nevertheless i also see the advantage, that applications may gain, if they do not try to support the least common denominator, but set a minimal entry thresholds, to process everything beyond this barrier much more efficient. i therefore have learned to live with this requirement of CUDA capable computing devices in the field of video processing and machine learning, because it really makes sense in practice to concentrate most development efforts on this particular solution to handle tasks in the most efficient and nowadays common manner.

sure -- compatibility to other GPU vendors solutions or pure CPU processing is a nice supplement, but it's often not the optimal choice, if thereby the possibilities of the whole system will be limited to a significant degree. this kind of leveling on the smallest measure usually isn't very satisfying to anyone.

this shouldn't be misunderstood as an excuse for applications, which tend to utilize all available computing resources in a really wasteful manner. but the exemplary ones usually work quite well on moderate hardware as well, because they simply have to scale very well to solve much more demanding tasks an significant more expensive hardware.
Offline

xpavement

  • Posts: 1
  • Joined: Fri Apr 20, 2018 6:26 pm
  • Real Name: Randall Lingenfelter

Re: DaVinci Resolve Studio 15 Beta doesn't run on Linux

PostFri Apr 20, 2018 6:45 pm

I was also getting the same message as the OP on an Ubunutu 17.10 install. I am running on an Nvidia GeForce GTX 960 card with an Intel Core i5 6600. At some point in the past I had installed some drivers for the on chip Intel video from here, trying to get quicksync to work along with nvenc:

https://01.org/linuxgraphics/

These don't look to be supported anymore, but I had a directory called /opt/intel which had a copy of libOpenCL.so.1 in it. I renamed the directory to intelx and then tried to run resolve 15 and it finally came up!

I also had some error messages about cuda, so I also had to upgrade my drivers to 390.48 and also upgraded my cuda toolkit install to 9.1.

When I run resolve at the command line now, I still get the error messages about libCg.so and libCgGL.so having no version info, so it didn't seem to be the actual cause of my issue. I ran the strace command and dug through the output to find a mention of libOpenCL.so.1 in it.

Code: Select all
cd /opt/resolve/bin
strace ./resolve
Offline

Sulo Kokki

  • Posts: 113
  • Joined: Thu Sep 28, 2017 11:39 pm

Re: DaVinci Resolve Studio 15 Beta doesn't run on Linux

PostFri Apr 20, 2018 11:42 pm

jesuslovesyou101 wrote:Ok to those who have gotten version 15 running, specifically any Ubuntu / Mint users, what did you do?
Well, we updated the Nvidia drivers to 390.30, removed Resolve 14.3 via Synaptic pkg manager, and installed the 15.0b1.deb.

For a first time Mint install, please review the v14 Mint install guide.

Note: v14 had a region bug, which in 15b1 is fixed. Mandatory English (US) session is gone (thanks, BMD :-D).

Lars Goldschlager wrote:I do not think it'd be sane for BM to chase a moving target, I feel if they do decide to give a nod to indie users by supporting some form of portability (static builds, flatpak, appimage, other containers, this is a discussion that can rage for months and to which I can bring no intelligent discourse) by spending man hours to develop such a version it's a boon to us, but I also feel CentOS might not be the best choice for the professional and oficial support.
+1 on both.

Resolve in a Flatpak would be great, but also, CentOS is what it is. Even the official ISO needs refurbishing.

Lars Goldschlager wrote:CentOS ... doesn't make the process easy or necessarily stable (beyond known controlled environments like the Advanced Panel). I believe the right distro to achieve this would be Ubuntu.
I agree that the Ubuntu family would be a good choice for a stable and accessible platform.

We'll see if things change by the RC. At least the system audio issue has finally been muted (thanks again, BMD).
Linux Mint 18.3 | DaVinci Resolve 15.0b6 | Desktop Video 10.9.3 | OSX 10.11.6
Offline

prysme

  • Posts: 3
  • Joined: Fri Apr 13, 2018 7:40 am
  • Real Name: Emmanuel Duss

Re: DaVinci Resolve Studio 15 Beta doesn't run on Linux

PostWed Apr 25, 2018 5:10 pm

For those who still have issue to launch resolve on Linux, I've finally success to run it on fedora 27

My issue, resolve was stuck when started, no splash screen, no issue on log.
I am running a NVIDIA card with no IGP with the latest nvidia proprietary driver.

I remove mesa-libOpenCL, then resolve splash screen was appearing, but still resolve shutdown down after the splash screen with still no issue on log.

I've finally discover this directory /etc/OpenCL/vendors with nvidia.icd and another pocl.icd
I remove the pocl.icd and now resolve is starting fine.

So it solve my case and I hope it could also help some of you.
Cheers;
e
Offline

Martin Schitter

  • Posts: 734
  • Joined: Tue Apr 28, 2015 10:41 pm

Re: DaVinci Resolve Studio 15 Beta doesn't run on Linux

PostThu Apr 26, 2018 12:07 pm

Sulo Kokki wrote:
Lars Goldschlager wrote:CentOS ... doesn't make the process easy or necessarily stable (beyond known controlled environments like the Advanced Panel). I believe the right distro to achieve this would be Ubuntu.


I agree that the Ubuntu family would be a good choice for a stable and accessible platform.


todays official release of ubuntu 18.04 LTS (Bionic Beaver), which brought some very important changes to make ubuntu more standard compliant and stable (e.g. returning to the more common X11 default graphic server and gnome desktop environment), this looks indeed as the most reasonable choose to maximize real wold demands. it's not only by far the most frequently used distribution today, but it's also a quite promising base to make software more compatible with most other modern linux distributions resp. realistic testing and fixing all those minor bugs concerning the rather small differences between various distributions. although i personally prefer to work on a slightly different setup (debian testing + cinnamon desktop), i really think, this new ubuntu LTS release should be seen as the most satisfying compromise and general orientation in nowadays linux software development and all its compatibility requirements.
Offline

Sulo Kokki

  • Posts: 113
  • Joined: Thu Sep 28, 2017 11:39 pm

Re: DaVinci Resolve Studio 15 Beta doesn't run on Linux

PostThu Apr 26, 2018 12:18 pm

The 18.04 LTS is due to make a strong foundation to the upcoming Mint 19 ;)
Linux Mint 18.3 | DaVinci Resolve 15.0b6 | Desktop Video 10.9.3 | OSX 10.11.6
Offline
User avatar

dilnix

  • Posts: 2
  • Joined: Thu Apr 12, 2018 9:02 am
  • Location: Kyiv
  • Real Name: Dimka Filippov

Re: DaVinci Resolve Studio 15 Beta doesn't run on Linux

PostThu Apr 26, 2018 3:31 pm

prysme wrote:For those who still have issue to launch resolve on Linux, I've finally success to run it on fedora 27

My issue, resolve was stuck when started, no splash screen, no issue on log.
I am running a NVIDIA card with no IGP with the latest nvidia proprietary driver.

I remove mesa-libOpenCL, then resolve splash screen was appearing, but still resolve shutdown down after the splash screen with still no issue on log.

I've finally discover this directory /etc/OpenCL/vendors with nvidia.icd and another pocl.icd
I remove the pocl.icd and now resolve is starting fine.

So it solve my case and I hope it could also help some of you.
Cheers;
e


Nice case.

But in my situation, after removing of mesa-libOpenCL and /etc/OpenCL/vendors/pocl.icd I have resolve still not starting... In my system there are 2 GPUs - Intel & NVIDIA and I'm using bumblebee to switch them, so in my case I need to run not simply Resolve executable... but with prefix of "optirun" to get it work with NVIDIA driver.
Resolve 14 was good to start with prefix and work with NVIDIA driver. Resolve 15 still just silently do nothing.
Offline
User avatar

MikeRochefort

  • Posts: 61
  • Joined: Thu Feb 12, 2015 2:48 am
  • Location: New England

Re: DaVinci Resolve Studio 15 Beta doesn't run on Linux

PostThu Apr 26, 2018 4:55 pm

Which driver version are you using? I couldn’t get Resolve 15 to work on my CentOS box until I removed the self-installed Intel OpenCL driver, removed ocl-icd, and reinstalled my NVIDIA driver. I recommend using 390.42 or above as that is the driver a suggested in the install PDF. I and a few others are running 390.48 totally fine.

Cheers,
Mike
https://michaelrochefort.com/
3D Lookdev, Compositing, and Sysadmin
Fusion Studio 9.0.2
DaVinci Resolve Studio 15b3
CentOS 7.5.1804 | Intel i7-6850K | 32GB memory | 3x GTX 1070
Offline

aidanryan

  • Posts: 5
  • Joined: Sun May 20, 2018 1:57 am
  • Real Name: Aidan Ryan

Re: DaVinci Resolve Studio 15 Beta doesn't run on Linux

PostSun May 20, 2018 2:03 am

For anybody running Fedora 27, I had a previous install of CUDA 9.1 and Nvidia drivers on my system. Following prysme's post:

For those who still have issue to launch resolve on Linux, I've finally success to run it on fedora 27

My issue, resolve was stuck when started, no splash screen, no issue on log.
I am running a NVIDIA card with no IGP with the latest nvidia proprietary driver.

I remove mesa-libOpenCL, then resolve splash screen was appearing, but still resolve shutdown down after the splash screen with still no issue on log.

I've finally discover this directory /etc/OpenCL/vendors with nvidia.icd and another pocl.icd
I remove the pocl.icd and now resolve is starting fine.

So it solve my case and I hope it could also help some of you.
Cheers;
e


I removed pocl.icd from /etc/OpenCL/vendors which had no effect. I also tried to remove mesa-libOpenCL, which was not installed. I then installed mesa-libOpenCL and removed all .icd files from /etc/OpenCL except nvidia.icd. This proved to be what allowed Resolve 15b3 to run on my particular Fedora 27 installation. It seems that OpenCL must be present on the machine, even if you intend to run Resolve using CUDA. Next step is testing fusion and making sure that basic functionality works. I assume the issue is not actually having libOpenCL installed, as prysme was only able to get it to work once removing libOpenCL, so it must be some nvidia-related link left over from libOpenCL's install and an issue with the .icd files.
Last edited by aidanryan on Tue Jun 19, 2018 1:20 pm, edited 1 time in total.
Offline

willmtemple

  • Posts: 1
  • Joined: Thu Jun 07, 2018 3:57 am
  • Real Name: Will Temple

Re: DaVinci Resolve Studio 15 Beta doesn't run on Linux

PostThu Jun 07, 2018 3:58 am

I am on Fedora 28 and found that removing `mesa-libopencl` was required for me to run resolve, though it's worth noting that I also have `beignet` installed.
Offline

Jeff Smart

  • Posts: 10
  • Joined: Wed Dec 06, 2017 4:12 am

Re: DaVinci Resolve Studio 15 Beta doesn't run on Linux

PostSat Jun 30, 2018 5:48 am

GREAT NEWS - I'd like to confirm "DaVinci Resolve Studio 15b5" will run on the "just released - 29Jun2018" Linux Mint 19 "Tara" Cinnamon (atleast for my system/config). Tested today 30June2018. Apparently Linux Mint 19 core is similar enough to Ubuntu 18.x except no/or little data collection :)

SYSTEM:
10 yr old P5 Asus MB, 4 core i5, 6GB RAM (yeap - not great), AMD RX550 4GB GPU card running AMD-GPU-PRO-18.20 Radeon Software for Linux, BMD PCIe Intensity Pro (HDMI to playback monitor with audio c/ HDMI). BMD DR dongle.

OPERATION:
DaVinci starts up nicely, shows 1xGPU as AMD RX550. I can edit UHD, grade, playback..shows Fusion tab but didn't want to push it too much with insufficient memory.

ISSUES:
* playback audio sometimes dropping out over Intensity HDMI audio output.
* h.265 source footage quit slow to playback compared with h.265 (probably since H.265 decode is not GPU accelerated compared to my iMac where the i7/MacOS now does super fast hardware h.265 decode/encode.
* DaVinci crashed with a log about Fusion server disconnected when I set a non-typical or >SD Playback resolution and frame rate for Intensity. I did install the v10.11 DEB package latest BMD Desktop Video suite. I'm guessing system/GPU memory shortage to do so much ? I had to remove the Intensity card, restart Resolve and reduce & save the playback resolution playback setting to NTSC, than re-installl the Intensity card and we seemed good.

INSTALLATION:
Install was quite straight forward, need the libssl dependancy & sym linking, note: target dir: is /usr/lib on Linux Mint. Also installed the xserver-xorg-hwe as discussed in many places. Months ago I did try to install DaVinci Resolve on Linux Mint 18 and gave up - too many OS/GPU bits not working, even the RX550 was a mess, and finally no Open CL. Besides even working, I expect DR on Linux and a modern supped up system would really rock for little $. Great job BMD team !

Hope this helps and makes someone's day a bit brighter :)
Jeff
Next

Return to DaVinci Resolve 15 Beta

Who is online

Users browsing this forum: Miltos Pilalitos, Oyvind Stiauren and 6 guests