DaVinci Resolve on Linux - Install issues

Get answers to your questions about color grading, editing and finishing with DaVinci Resolve.
  • Author
  • Message
Offline
User avatar

vitaminx

  • Posts: 11
  • Joined: Thu Jun 06, 2019 12:59 pm
  • Real Name: Roman Schmidt

Re: DaVinci Resolve on Linux - Install issues

PostFri Nov 27, 2020 3:13 am

Heep042 wrote:I got Resolve to launch using Mesa OpenGL, and just the amdocl64 part from AMDGPU-PRO. Color grading seems to work, transitions work (including fusion ones). The issue was one OpenCL extension misbehaving (particularly, clGetGLContextInfoKHR), so I blacklisted it using LD_PRELOAD trick, and all the code for it can be found on my GitHub repo (h33p/resolve-amdocl-fix).

Alternatively, try this GDB script:
Code: Select all
set breakpoint pending on
b clGetGLContextInfoKHR
run
p $device_ptr = (unsigned long*)$rcx
finish
p *$device_ptr = 0
p $rax = -30
c


Wow, you're a master! That actually works for me (I mean the h33p/resolve-amdocl-fix part, I didn't try gdb) :)
I'm on Debian + Radeon Vega64 + Resolve 16 + amdgpu-pro OpenCL drivers

Thank you so much :)
Offline

Jeeggs

  • Posts: 3
  • Joined: Fri Nov 27, 2020 12:27 am
  • Real Name: Ric Lim

Re: DaVinci Resolve on Linux - Install issues

PostSat Nov 28, 2020 7:50 pm

Davinci Resolve 16 load with error dialog box: "DaVinci Resolve could not find any OpenCl capable GPUs. Would you like to review and update your DaVinci Resolve Hardware Configuration?" Quit or Update Configuration button.

I've clicked on Update Configuration button and on Media Storage System tab I can choose on drop down under GPU processing mode (of M emory and GPU) the OpenCL option. But when I try to save it tells me to add at least one media storage volume. and it just terminate. Before I could go in to Media Storage to add a folder but it also terminates after.

My config.dat file is below and shows Site.1.FS.1.Root = /Videos. Before just says HOMEDIR or something. That root Video folder have create and delete access for root. Tried running DaVinci as root but same issue.

I've added amdgpu-pro opencl only with:
Code: Select all
./amdgpu-pro-install -y --opencl=pal,legacy –headless –no-dkms


and use Heep042 fix from his github. so I run my make file that I named resolvemake
Code: Select all
make -f resolvemake


which created the amdocl_fix.so file
This is all in the path ~/Documents/DaVinci_Resolve_Fix

So for the run_resolve.sh file I've pointed LD_PRELOAD to the path

Code: Select all
LD_PRELOAD=.~/Documents/DaVinci_Resolve_Fix/amdocl_fix.so /opt/resolve/bin/resolve


My system:
Ryzen 5 3600x 16GB with RX 580 8GB
Linux Mint 20

When I first installed and run DaVinci Resolve 17 beta directly I got similar error but don't have the option to choose GPU mode. Now I can choose opencl but still terminates and media storage have nothing in it. But even with config.dat pointing to /Videos it is still blank and still prompt me to add and then terminates.

Here is part of the content of the log file.
Code: Select all
[0x7f993d348640] | Main                 | INFO  | 2020-11-28 12:17:41,630 | Running DaVinci Resolve v16.2.7.010 (Linux/Clang)
[0x7f993d348640] | Main                 | INFO  | 2020-11-28 12:17:41,631 | Updating display GPU information...
Ignoring OpenCL error -1001: 'Unspecified Error', GPUPropertiesUtilUnix.cpp:339.
[0x7f993d348640] | Main                 | INFO  | 2020-11-28 12:17:41,631 | There is no OpenCL platform
[0x7f993d348640] | Main                 | INFO  | 2020-11-28 12:17:41,631 | 0 GPUs (excluding display GPU) found. Using OpenCL for processing.
[0x7f993d348640] | Main                 | INFO  | 2020-11-28 12:17:41,631 | Not GLmap capable. GPUs: 0 discrete, 0 integrated, 0 external. Auto mapping, OpenCL processing, main display not on external GPU.
[0x7f993d348640] | Main                 | INFO  | 2020-11-28 12:17:41,631 | Setting LsManager.3.NumGPUs = 1
[0x7f993d348640] | IO                   | INFO  | 2020-11-28 12:17:41,631 | RED InitializeSdk with library path at /opt/resolve/libs
[0x7f993d348640] | IO                   | INFO  | 2020-11-28 12:17:41,676 | R3DAPI 7.3.4-47A00 (20200818 L64S) R3DSDK 7.3.4-47A00 (20200818 L64D C3B1) RED OPENCL 7.3.4-49818 (20200819) [/opt/resolve/libs/] init is successful
[0x7f993d348640] | Main                 | INFO  | 2020-11-28 12:17:41,676 | 0 RED rocket cards available
There are 1 GPUs in the system.
libDeckLinkAPI.so: cannot open shared object file: No such file or directory
[0x7f993d348640] | Main                 | INFO  | 2020-11-28 12:17:41,676 | Decklink model name: '', version: ''
[0x7f993d348640] | DVIP                 | INFO  | 2020-11-28 12:17:41,676 | DVIP Version : 16.2.7, Revision r006780-946c5d99, Branch release/16.2.7 (Release)
[0x7f993d348640] | Main                 | INFO  | 2020-11-28 12:17:41,700 | Installed custom font: Open Sans
[0x7f993d348640] | Main                 | INFO  | 2020-11-28 12:17:41,700 | Installed custom font: Open Sans
[0x7f993d348640] | Main                 | INFO  | 2020-11-28 12:17:41,700 | Installed custom font: Open Sans
[0x7f993d348640] | Main                 | INFO  | 2020-11-28 12:17:41,704 | Finished loading Application style sheet
Local.Speed.Debug switched OFF - ''
[0x7f991c67e700] | LeManager            | INFO  | 2020-11-28 12:17:41,795 | 521, 38
[0x7f993d348640] | BtCommon             | INFO  | 2020-11-28 12:17:42,313 | Memory config: reserved=6000M pinned=4000M log=0
[0x7f993d348640] | BtCommon             | INFO  | 2020-11-28 12:17:42,313 | Using default pooled memory manager
[0x7f991be7d700] | BtCommon             | INFO  | 2020-11-28 12:17:42,313 | BtResourceManager Process Thread Started
[0x7f993d348640] | BtCommon             | INFO  | 2020-11-28 12:17:42,313 | Daemon DPDecoder is started 8750
[0x7f993d348640] | BtCommon             | INFO  | 2020-11-28 12:17:42,313 | Daemon DPDecoder is started 8751
[0x7f993d348640] | BtCommon             | INFO  | 2020-11-28 12:17:42,314 | Daemon DPDecoder is started 8752
[0x7f993d348640] | BtCommon             | INFO  | 2020-11-28 12:17:42,314 | Daemon DPDecoder is started 8753
[0x7f993d348640] | BtCommon             | INFO  | 2020-11-28 12:17:42,314 | Daemon DPDecoder is started 8754
[0x7f993d348640] | BtCommon             | INFO  | 2020-11-28 12:17:42,314 | Daemon DPDecoder is started 8755
[0x7f993d348640] | BtCommon             | INFO  | 2020-11-28 12:17:42,314 | Daemon DPDecoder is started 8756
[0x7f993d348640] | BtCommon             | INFO  | 2020-11-28 12:17:42,314 | Daemon DPDecoder is started 8757
[0x7f993d348640] | SyManager            | INFO  | 2020-11-28 12:17:42,318 | Total: 20, NumDtThreads: 8, NumComms: 0, NumSites: 1

[0x7f993d348640] | SyManager            | INFO  | 2020-11-28 12:17:42,318 | Lookaheads -> playback = 20, record = 20, stop = 2

Sy High Command Handler Thread ----- (140295541331712)
SY high priority cmd handler thread starts: 19E79700
Sy Data Handler Thread ----- (140295524546304)
SY data handler thread starts: 18E77700
Sy Low Command Handler Thread ----- (140295532939008)
SY low priority cmd handler thread starts: 19678700
Gs High Command Handler Thread ----- (140295499368192)
GS high priority cmd handler thread starts: 17674700
Gs Low Command Handler Thread ----- (140295490975488)
GS low priority cmd handler thread starts: 16E73700
Dp High Command Handler Thread ----- (140295474190080)
DP high priority cmd handler thread starts: 15E71700
Dt High Command Handler Thread ----- (140295457404672)
DT high priority cmd handler thhread starts: 14E6F700
[0x7f9916672700] | GsManager            | INFO  | 2020-11-28 12:17:42,319 | Gs Processor Thread ----- (140295482582784)

Dt Low Command Handler Thread ----- (140295449011968)
Dp Low Command Handler Thread ----- (140295465797376)
DT low priority cmd handler thread starts: 1466E700
DP low priority cmd handler thread starts: 15670700
GS processor thread starts: 16672700
[0x7f993d348640] | DtManager            | INFO  | 2020-11-28 12:17:42,319 | Using 8 generic IO threads
Local.Speed.Verbose switched OFF - ''
[0x7f993d348640] | DtManager            | INFO  | 2020-11-28 12:17:42,319 | Total of 16 IO threads (including 8 generic and 8 Red decode threads)
[0x7f9913e6d700] | DtManager            | INFO  | 2020-11-28 12:17:42,319 | Dt Data Handler Thread Started
DT data handler thread starts: 13E6D700
[0x7f991366c700] | DtManager            | INFO  | 2020-11-28 12:17:42,319 | Dt Worker Thread Started
[0x7f9917e75700] | SyManager            | ERROR | 2020-11-28 12:17:42,319 | Failed to connect to panel socket
[0x7f9910666700] | DtManager            | INFO  | 2020-11-28 12:17:42,319 | Dt Worker Thread Started
[0x7f9911e69700] | DtManager            | INFO  | 2020-11-28 12:17:42,319 | Dt Worker Thread Started
[0x7f991266a700] | DtManager            | INFO  | 2020-11-28 12:17:42,319 | Dt Worker Thread Started
[0x7f990ce5f700] | DtManager            | INFO  | 2020-11-28 12:17:42,319 | Dt Worker Thread Started
[0x7f9917e75700] | SyManager            | ERROR | 2020-11-28 12:17:42,319 | DRIVER: open /var/tmp/davinci_socket failed
[0x7f990fe65700] | DtManager            | INFO  | 2020-11-28 12:17:42,319 | Dt Worker Thread Started
Ls High Command Handler Thread ----- (140295281157888)
Ls Low Command Handler Thread ----- (140295272765184)
LS low priority cmd handler thread starts: 09E59700
[0x7f990e662700] | DtManager            | INFO  | 2020-11-28 12:17:42,319 | Dt Worker Thread Started
Ls Data Handler Thread ----- (140295264372480)
Ls High Command Handler Thread ----- (140295255979776)
Ls Low Command Handler Thread ----- (140295247587072)
Ls Data Handler Thread ----- (140295239194368)
LS low priority cmd handler thread starts: 08656700
LS data handler thread starts: 09658700
[0x7f990f664700] | DtManager            | INFO  | 2020-11-28 12:17:42,319 | Dt Worker Thread Started
LS data handler thread starts: 07E55700
Ls High Command Handler Thread ----- (140295230801664)
Ls Data Handler Thread ----- (140295214016256)
Ls Low Command Handler Thread ----- (140295222408960)
Mem Data Transmitter Thread ----- (140295205623552)
[0x7f9912e6b700] | DtManager            | INFO  | 2020-11-28 12:17:42,319 | Dt Worker Thread Started
LS low priority cmd handler thread starts: 06E53700
Mem data transmitter thread starts: 05E51700
[0x7f9906652700] | GPUManager           | INFO  | 2020-11-28 12:17:42,319 | Let There Be OpenCL Light!
[0x7f9910e67700] | DtManager            | INFO  | 2020-11-28 12:17:42,319 | Dt Worker Thread Started
[0x7f990d660700] | DtManager            | INFO  | 2020-11-28 12:17:42,319 | Dt Worker Thread Started
[0x7f9911668700] | DtManager            | INFO  | 2020-11-28 12:17:42,319 | Dt Worker Thread Started
[0x7f990c65e700] | DtManager            | INFO  | 2020-11-28 12:17:42,319 | Dt Worker Thread Started
[0x7f990be5d700] | DtManager            | INFO  | 2020-11-28 12:17:42,319 | Dt Worker Thread Started
[0x7f990b65c700] | DtManager            | INFO  | 2020-11-28 12:17:42,319 | Dt Worker Thread Started
[0x7f990ee63700] | DtManager            | INFO  | 2020-11-28 12:17:42,319 | Dt Worker Thread Started
[0x7f990ae5b700] | DtManager            | INFO  | 2020-11-28 12:17:42,319 | Dt Worker Thread Started
[0x7f993d348640] | DbCommon2            | INFO  | 2020-11-28 12:17:42,319 | Loading dblist file: /root/.local/share/DaVinciResolve/configs/.dblist
[0x7f990de61700] | DtManager            | INFO  | 2020-11-28 12:17:42,319 | Dt Worker Thread Started
[0x7f9906652700] | GPUManager           | INFO  | 2020-11-28 12:17:42,324 | Start detecting OpenCL boards
Ignoring OpenCL error -1001: 'Unspecified Error', OpenCLBoardManager.cpp:232.
[0x7f9906652700] | GPUManager           | WARN  | 2020-11-28 12:17:42,324 | There is no OpenCL platform
[0x7f9906652700] | GPUManager           | INFO  | 2020-11-28 12:17:42,324 | 0 OpenCL boards detected
Urgent message: CRITICAL_PREF: DaVinci Resolve could not find any OpenCL capable GPUs. Would you like to review and update your DaVinci Resolve Hardware Configuration? ||Please ensure that appropriate GPU drivers are installed and your DaVinci Resolve hardware is configured appropriately.
[0x7f9906652700] | GPUManager           | ERROR | 2020-11-28 12:17:42,324 | CRITICAL_PREF: DaVinci Resolve could not find any OpenCL capable GPUs. Would you like to review and update your DaVinci Resolve Hardware Configuration? ||Please ensure that appropriate GPU drivers are installed and your DaVinci Resolve hardware is configured appropriately.
[0x7f9906652700] | IP                   | ERROR | 2020-11-28 12:17:42,324 | Failed to initialize OpenCL boards
LS data handler thread starts: 06652700
/opt/resolve/bin/BlackmagicRawAPI/libBlackmagicRawAPI.so: cannot open shared object file: No such file or directory
/opt/resolve/bin/libBlackmagicRawAPI.so: cannot open shared object file: No such file or directory
[0x7f993d348640] | IO                   | INFO  | 2020-11-28 12:17:42,328 | Using DNxHR library v2.5.2.68r
[0x7f993d348640] | IO                   | INFO  | 2020-11-28 12:17:42,331 | Kdu ctx(0), bundle(0), thds(2)
[0x7f993d348640] | IO                   | INFO  | 2020-11-28 12:17:42,331 | Kdu ctx(2), bundle(0), thds(2)
[0x7f993d348640] | IO                   | INFO  | 2020-11-28 12:17:42,331 | Kdu ctx(4), bundle(0), thds(2)
[0x7f993d348640] | IO                   | INFO  | 2020-11-28 12:17:42,331 | Kdu ctx(6), bundle(0), thds(2)
[0x7f993d348640] | IO                   | INFO  | 2020-11-28 12:17:42,331 | Kdu ctx(8), bundle(0), thds(1)
[0x7f993d348640] | IO                   | INFO  | 2020-11-28 12:17:42,331 | Kdu ctx(9), bundle(0), thds(1)
[0x7f993d348640] | IO                   | INFO  | 2020-11-28 12:17:42,331 | Kdu ctx(10), bundle(0), thds(1)
[0x7f993d348640] | IO                   | INFO  | 2020-11-28 12:17:42,331 | Kdu ctx(11), bundle(0), thds(1)
ALSA lib pcm_dmix.c:1089:(snd_pcm_dmix_open) unable to open slave

MidiInDummy: This class provides no functionality.


MidiOutDummy: This class provides no functionality.

ALSA lib pcm_dmix.c:1089:(snd_pcm_dmix_open) unable to open slave

about 48 lines of the ALSA error.

Continuation of the log file:
Code: Select all
[0x7f993d348640] | Fairlight            | INFO  | 2020-11-28 12:17:43,529 | 00.00.00.872(000): Running Fairlight (r001014-43fe498b)
[0x7f993d348640] | UI.GLContext         | INFO  | 2020-11-28 12:17:43,537 | Creating shared OpenGL context for this thread (2 total).
[0x7f993d348640] | UI.GLContext         | INFO  | 2020-11-28 12:17:43,538 | Initialized OpenGL 4.6 (requested 2.0) on device 'X.Org Radeon RX 580 Series (POLARIS10, DRM 3.35.0, 5.4.0-26-generic, LLVM 10.0.0)'
ALSA lib pcm_dmix.c:1089:(snd_pcm_dmix_open) unable to open slave
ALSA lib pcm_dmix.c:1089:(snd_pcm_dmix_open) unable to open slave
ALSA lib pcm_dmix.c:1089:(snd_pcm_dmix_open) unable to open slave
ALSA lib pcm_dmix.c:1089:(snd_pcm_dmix_open) unable to open slave
ALSA lib pcm_dmix.c:1089:(snd_pcm_dmix_open) unable to open slave
ALSA lib pcm_dmix.c:1089:(snd_pcm_dmix_open) unable to open slave
All textures are loaded : 1.
[0x7f993d348640] | Fusion               | INFO  | 2020-11-28 12:17:43,688 | Fusion Build: r067722-ef6f045d_004 (Sep 15 2020 11:32:26)
[0x7f993d348640] | Fusion               | INFO  | 2020-11-28 12:17:43,688 | fusionsystem: = "/opt/resolve/libs/Fusion/libfusionsystem.so"
[0x7f993d348640] | Fusion               | INFO  | 2020-11-28 12:17:43,692 | FusionLibs: = "/opt/resolve/libs/Fusion/"
[0x7f993d348640] | Fusion               | INFO  | 2020-11-28 12:17:43,692 | UserData:   = "/root/.local/share/DaVinciResolve/Fusion"
[0x7f993d348640] | Fusion               | INFO  | 2020-11-28 12:17:43,692 | Profiles:   = "UserData:Profiles/"
ERROR: ld.so: object '.~/Documents/DaVinci_Resolve_Fix/amdocl_fix.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.

That ERROR ld.so repeated about seven more times followed by the ALSA error again for several more times.
then:
Code: Select all
[0x7f9860a10700] | UI.GLContext         | INFO  | 2020-11-28 12:17:43,766 | Creating shared OpenGL context for this thread (3 total).
[0x7f9860a10700] | DVIP                 | ERROR | 2020-11-28 12:17:43,769 | DeviceContextInterface.cpp:40: DVIP Exception: OpenCL error
 - API: OpenCL
 - API Error Code: Unknown CL error. (-1001)
 - Call stack:
     /opt/resolve/bin/resolve() [0x604f8f4]
     /opt/resolve/bin/resolve() [0x602bdcd]
     /opt/resolve/bin/resolve() [0x6044f84]
     /opt/resolve/bin/resolve() [0x60d2687]
     /opt/resolve/bin/resolve() [0x60d24b0]
     /opt/resolve/bin/resolve() [0x6036143]
     /opt/resolve/bin/resolve() [0x6036207]
     /opt/resolve/bin/resolve() [0x21f902d]
     /opt/resolve/bin/resolve() [0x21fd56d]
     /lib/x86_64-linux-gnu/libpthread.so.0(+0x9609) [0x7f994deb2609]

[0x7f9860a10700] | UI.GLIO              | ERROR | 2020-11-28 12:17:43,769 | Failed to create DVIP context.
[0x7f993d348640] | UI.GLIO              | ERROR | 2020-11-28 12:17:43,769 | Failed to initialize worker thread.
[0x7f993d348640] | Undefined            | ERROR | 2020-11-28 12:17:43,769 | Failed to initialize GPU Scopes, OpenGL Interop or GLIO is required.
ALSA lib pcm_dmix.c:1089:(snd_pcm_dmix_open) unable to open slave
ALSA lib pcm_dmix.c:1089:(snd_pcm_dmix_open) unable to open slave
[0x7f993d348640] | UI                   | ERROR | 2020-11-28 12:17:43,799 | Failed to find text 'Apple ProRes' in combo-box
[0x7f993d348640] | UI                   | WARN  | 2020-11-28 12:17:43,799 | Failed to find value '0' in combo-box
ALSA lib pcm_dmix.c:1089:(snd_pcm_dmix_open) unable to open slave
ALSA lib pcm_dmix.c:1089:(snd_pcm_dmix_open) unable to open slave
ALSA lib pcm_dmix.c:1089:(snd_pcm_dmix_open) unable to open slave
ALSA lib pcm_dmix.c:1089:(snd_pcm_dmix_open) unable to open slave
ALSA lib pcm_dmix.c:1089:(snd_pcm_dmix_open) unable to open slave
ALSA lib pcm_dmix.c:1089:(snd_pcm_dmix_open) unable to open slave
libScannerAPI.so: cannot open shared object file: No such file or directory
ALSA lib pcm_dmix.c:1089:(snd_pcm_dmix_open) unable to open slave
[0x7f993d348640] | DbCommon2            | INFO  | 2020-11-28 12:17:43,898 | Sm2SysIdEntry is not supported in disk database (xml) mode
ALSA lib pcm_dmix.c:1089:(snd_pcm_dmix_open) unable to open slave
ALSA lib pcm_dmix.c:1089:(snd_pcm_dmix_open) unable to open slave
SY panel handler thread starts: 17E75700
[0x7f9917e75700] | SyManager            | ERROR | 2020-11-28 12:17:43,921 | Failed to connect to panel socket
ALSA lib pcm_dmix.c:1089:(snd_pcm_dmix_open) unable to open slave
ALSA lib pcm_dmix.c:1089:(snd_pcm_dmix_open) unable to open slave
ALSA lib pcm_dmix.c:1089:(snd_pcm_dmix_open) unable to open slave
ALSA lib pcm_dmix.c:1089:(snd_pcm_dmix_open) unable to open slave
ALSA lib pcm_dmix.c:1089:(snd_pcm_dmix_open) unable to open slave
ALSA lib pcm_dmix.c:1089:(snd_pcm_dmix_open) unable to open slave
ALSA lib pcm_dmix.c:1089:(snd_pcm_dmix_open) unable to open slave
ALSA lib pcm_dmix.c:1089:(snd_pcm_dmix_open) unable to open slave
ALSA lib pcm_dmix.c:1089:(snd_pcm_dmix_open) unable to open slave
ALSA lib pcm_dmix.c:1089:(snd_pcm_dmix_open) unable to open slave
ALSA lib pcm_dmix.c:1089:(snd_pcm_dmix_open) unable to open slave
ALSA lib pcm_dmix.c:1089:(snd_pcm_dmix_open) unable to open slave
ALSA lib pcm_dmix.c:1089:(snd_pcm_dmix_open) unable to open slave
ALSA lib pcm_dmix.c:1089:(snd_pcm_dmix_open) unable to open slave
ALSA lib pcm_dmix.c:1089:(snd_pcm_dmix_open) unable to open slave
ALSA lib pcm_dmix.c:1089:(snd_pcm_dmix_open) unable to open slave
ALSA lib pcm_dmix.c:1089:(snd_pcm_dmix_open) unable to open slave
[0x7f993d348640] | UI                   | WARN  | 2020-11-28 12:17:44,169 | Failed to load media metadata preset list or the list is empty.
[0x7f993d348640] | UI                   | WARN  | 2020-11-28 12:17:44,174 | Failed to load media metadata preset list or the list is empty.
ALSA lib pcm_dmix.c:1089:(snd_pcm_dmix_open) unable to open slave
ALSA lib pcm_dmix.c:1089:(snd_pcm_dmix_open) unable to open slave
ALSA lib pcm_dmix.c:1089:(snd_pcm_dmix_open) unable to open slave
ALSA lib pcm_dmix.c:1089:(snd_pcm_dmix_open) unable to open slave
ALSA lib pcm_dmix.c:1089:(snd_pcm_dmix_open) unable to open slave


Same error repeating over and over and other than the ALSA lines repeated other lines includes the following (i've condensed and removed the long lines of repetitive ALSA error):
Code: Select all
[0x7f993d348640] | UI                   | INFO  | 2020-11-28 12:17:45,460 | Not creating special GL widget for screen 0
ALSA lib pcm_dmix.c:1089:(snd_pcm_dmix_open) unable to open slave
ALSA lib pcm_dmix.c:1089:(snd_pcm_dmix_open) unable to open slave
[0x7f993d348640] | UI.ActionManager     | WARN  | 2020-11-28 12:17:45,685 | Action [sessionDolbyVisionAnalyzeAllShots] is not a valid global action
[0x7f993d348640] | UI.ActionManager     | WARN  | 2020-11-28 12:17:45,685 | Action [sessionDolbyVisionAnalyzeSelectedShots] is not a valid global action
[0x7f993d348640] | UI.ActionManager     | WARN  | 2020-11-28 12:17:45,685 | Action [sessionDolbyVisionAnalyzeSelectedAndGroup] is not a valid global action
[0x7f993d348640] | UI.ActionManager     | WARN  | 2020-11-28 12:17:45,685 | Action [sessionDolbyVisionAnalyzeCurrentFrame] is not a valid global action
[0x7f993d348640] | UI.ActionManager     | WARN  | 2020-11-28 12:17:45,685 | Action [sessionHDR10PlusAnalyzeAllShots] is not a valid global action
[0x7f993d348640] | UI.ActionManager     | WARN  | 2020-11-28 12:17:45,685 | Action [sessionHDR10PlusAnalyzeSelectedShots] is not a valid global action
[0x7f993d348640] | UI.ActionManager     | WARN  | 2020-11-28 12:17:45,685 | Action [sessionHDR10PlusAnalyzeSelectedAndGroup] is not a valid global action
[0x7f993d348640] | UI.ActionManager     | WARN  | 2020-11-28 12:17:45,685 | Action [sessionHDR10PlusAnalyzeCurrentFrame] is not a valid global action
ALSA lib pcm_dmix.c:1089:(snd_pcm_dmix_open) unable to open slave
[0x7f993d348640] | UI                   | WARN  | 2020-11-28 12:17:45,767 | Failed to find value '8192' in combo-box
ALSA lib pcm_dmix.c:1089:(snd_pcm_dmix_open) unable to open slave
[0x7f993d348640] | UI                   | WARN  | 2020-11-28 12:17:45,821 | Failed to find value '100' in combo-box
ALSA lib pcm_dmix.c:1089:(snd_pcm_dmix_open) unable to open slave
ALSA lib pcm_dmix.c:1089:(snd_pcm_dmix_open) unable to open slave
[0x7f993d348640] | UI.MenuBar           | WARN  | 2020-11-28 12:17:46,053 | Plugged In Action [fusion_menu1_triggered(bool)] is owned by [0x7f9856523bb0]
[0x7f993d348640] | UI.MenuBar           | WARN  | 2020-11-28 12:17:46,053 | Plugged In Action [fusion_menu2_triggered()] is owned by [0x7f9856523bb0]
[0x7f993d348640] | UI.MenuBar           | WARN  | 2020-11-28 12:17:46,053 | Plugged In Action [fusion_menu3_triggered()] is owned by [0x7f9856523bb0]
[0x7f993d348640] | UI.MenuBar           | WARN  | 2020-11-28 12:17:46,053 | Plugged In Action [fusion_menu5_triggered()] is owned by [0x7f9856523bb0]
[0x7f993d348640] | UI.MenuBar           | WARN  | 2020-11-28 12:17:46,053 | Plugged In Action [fusion_menu8_triggered()] is owned by [0x7f9856523bb0]
[0x7f993d348640] | UI.MenuBar           | WARN  | 2020-11-28 12:17:46,053 | Plugged In Action [workspace_sub1_menu1_triggered()] is owned by [0x7f9856523bb0]
ALSA lib pcm_dmix.c:1089:(snd_pcm_dmix_open) unable to open slave
ALSA lib pcm_dmix.c:1089:(snd_pcm_dmix_open) unable to open slave
****************** Flushing GPU Buffers
ALSA lib pcm_dmix.c:1089:(snd_pcm_dmix_open) unable to open slave
ALSA lib pcm_dmix.c:1089:(snd_pcm_dmix_open) unable to open slave
[0x7f993d348640] | IO                   | INFO  | 2020-11-28 12:17:46,122 | RED rocket decode has been disabled in the config file
ALSA lib pcm_dmix.c:1089:(snd_pcm_dmix_open) unable to open slave
[0x7f993d348640] | UI                   | WARN  | 2020-11-28 12:17:46,185 | Failed to find value '0' in combo-box
[0x7f993d348640] | UI                   | WARN  | 2020-11-28 12:17:46,185 | Failed to find value '0' in combo-box
[0x7f993d348640] | UI                   | WARN  | 2020-11-28 12:17:46,185 | Failed to find value '0' in combo-box
[0x7f993d348640] | UI                   | WARN  | 2020-11-28 12:17:46,185 | Failed to find value '0' in combo-box
[0x7f993d348640] | UI                   | WARN  | 2020-11-28 12:17:46,185 | Failed to find value '0' in combo-box
[0x7f993d348640] | UI                   | WARN  | 2020-11-28 12:17:46,185 | Failed to find value '0' in combo-box
ALSA lib pcm_dmix.c:1089:(snd_pcm_dmix_open) unable to open slave
ALSA lib pcmERROR: ld.so: object '.~/Documents/DaVinci_Resolve_Fix/amdocl_fix.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
_dmix.c:1089:(snd_pcm_dmix_open) unable to open slave
ALSA lib pcm_dmix.c:1089:(snd_pcm_dmix_open) unable to open slave
[0x7f9830976700] | UI                   | ERROR | 2020-11-28 12:17:49,280 | UiAutoUpdateController: Failed to get response from server (responseCode:2) (httpStatus:-1) (response:)
ALSA lib pcm_dmix.c:1089:(snd_pcm_dmix_open) unable to open slave
[0x7f993d348640] | UI                   | WARN  | 2020-11-28 12:17:51,967 | Failed to find value '0' in combo-box
[0x7f993d348640] | UI                   | WARN  | 2020-11-28 12:17:51,967 | Failed to find value '0' in combo-box
[0x7f993d348640] | UI                   | WARN  | 2020-11-28 12:17:51,967 | Failed to find value '0' in combo-box
[0x7f993d348640] | UI                   | WARN  | 2020-11-28 12:17:51,967 | Failed to find value '0' in combo-box
[0x7f993d348640] | UI                   | WARN  | 2020-11-28 12:17:51,968 | Failed to find value '-1' in combo-box
ALSA lib pcm_dmix.c:1089:(snd_pcm_dmix_open) unable to open slave
[0x7f993d348640] | DbCommon2            | INFO  | 2020-11-28 12:18:00,403 | Sm2SysIdEntry is not supported in disk database (xml) mode
ALSA lib pcm_dmix.c:1089:(snd_pcm_dmix_open) unable to open slave
[0x7f991c67e700] | LeManager            | INFO  | 2020-11-28 12:18:00,812 | 522, 101
[0x7f993d348640] | Main                 | INFO  | 2020-11-28 12:18:00,950 | Starting terminate sequence by calling g_MainTerm

[0x7f993d348640] | Main                 | INFO  | 2020-11-28 12:18:00,950 | Closing components
[0x7f993d348640] | UI                   | INFO  | 2020-11-28 12:18:00,950 | Audio thread terminated.
[0x7f993d348640] | Main                 | INFO  | 2020-11-28 12:18:00,950 | g_MainTerm: BtStartupShutdownControl.Shutdown() - begin
Exit SY panel handler
[0x7f9919678700] | SyManager            | INFO  | 2020-11-28 12:18:01,005 | Exit SY low priority cmd handler
[0x7f9919e79700] | SyManager            | INFO  | 2020-11-28 12:18:01,005 | Exit SY high priority cmd handler
Exit SY data handler
[0x7f993d348640] | Main                 | INFO  | 2020-11-28 12:18:01,029 | SvcManager: SyManager.StopThreads() - end
[0x7f9916672700] | GsManager            | INFO  | 2020-11-28 12:18:01,029 | Exit GS process handler
[0x7f993d348640] | Main                 | INFO  | 2020-11-28 12:18:01,030 | SvcManager: GsManager.StopThreads() - end
[0x7f993d348640] | Main                 | INFO  | 2020-11-28 12:18:01,030 | SvcManager: DpManager.StopThreads() - end
[0x7f9913e6d700] | DtManager            | INFO  | 2020-11-28 12:18:01,040 | Exit DT data handler thread
Exit GS low priority cmd handler
Exit GS high priority cmd handler
[0x7f991466e700] | DtManager            | INFO  | 2020-11-28 12:18:01,045 | Exit DT low priority cmd handler
[0x7f9914e6f700] | DtManager            | INFO  | 2020-11-28 12:18:01,045 | Exit DT high priority cmd handler
[0x7f9915670700] | DpManager            | INFO  | 2020-11-28 12:18:01,045 | Exit DP low priority cmd handler
[0x7f9915e71700] | DpManager            | INFO  | 2020-11-28 12:18:01,045 | Exit DP high priority cmd handler
[0x7f990f664700] | DtManager            | INFO  | 2020-11-28 12:18:01,056 | Exit DT worker thread
[0x7f990ee63700] | DtManager            | INFO  | 2020-11-28 12:18:01,056 | Exit DT worker thread
[0x7f990ae5b700] | DtManager            | INFO  | 2020-11-28 12:18:01,056 | Exit DT worker thread
[0x7f9911e69700] | DtManager            | INFO  | 2020-11-28 12:18:01,056 | Exit DT worker thread
[0x7f9912e6b700] | DtManager            | INFO  | 2020-11-28 12:18:01,056 | Exit DT worker thread
[0x7f990e662700] | DtManager            | INFO  | 2020-11-28 12:18:01,056 | Exit DT worker thread
[0x7f9910666700] | DtManager            | INFO  | 2020-11-28 12:18:01,056 | Exit DT worker thread
[0x7f990be5d700] | DtManager            | INFO  | 2020-11-28 12:18:01,056 | Exit DT worker thread
[0x7f9910e67700] | DtManager            | INFO  | 2020-11-28 12:18:01,056 | Exit DT worker thread
[0x7f990de61700] | DtManager            | INFO  | 2020-11-28 12:18:01,056 | Exit DT worker thread
[0x7f990fe65700] | DtManager            | INFO  | 2020-11-28 12:18:01,056 | Exit DT worker thread
[0x7f990c65e700] | DtManager            | INFO  | 2020-11-28 12:18:01,056 | Exit DT worker thread
[0x7f991366c700] | DtManager            | INFO  | 2020-11-28 12:18:01,056 | Exit DT worker thread
[0x7f990d660700] | DtManager            | INFO  | 2020-11-28 12:18:01,056 | Exit DT worker thread
[0x7f9911668700] | DtManager            | INFO  | 2020-11-28 12:18:01,056 | Exit DT worker thread
[0x7f990b65c700] | DtManager            | INFO  | 2020-11-28 12:18:01,056 | Exit DT worker thread
[0x7f991266a700] | DtManager            | INFO  | 2020-11-28 12:18:01,056 | Exit DT worker thread
[0x7f990ce5f700] | DtManager            | INFO  | 2020-11-28 12:18:01,056 | Exit DT worker thread
[0x7f993d348640] | Main                 | INFO  | 2020-11-28 12:18:01,076 | SvcManager: DtManager.StopThreads() - end
[0x7f9909658700] | LsManager            | INFO  | 2020-11-28 12:18:01,081 | Exit LS data handler
[0x7f990a65a700] | LsManager            | INFO  | 2020-11-28 12:18:01,085 | Exit LS high priority cmd handler
[0x7f9909e59700] | LsManager            | INFO  | 2020-11-28 12:18:01,085 | Exit LS low priority cmd handler
[0x7f993d348640] | Main                 | INFO  | 2020-11-28 12:18:01,102 | SvcManager: LsManager.StopThreads() - end
[0x7f9908656700] | LsManager            | INFO  | 2020-11-28 12:18:01,105 | Exit LS low priority cmd handler
[0x7f9908e57700] | LsManager            | INFO  | 2020-11-28 12:18:01,105 | Exit LS high priority cmd handler
[0x7f9907e55700] | LsManager            | INFO  | 2020-11-28 12:18:01,121 | Exit LS data handler
[0x7f993d348640] | Main                 | INFO  | 2020-11-28 12:18:01,129 | SvcManager: LsManager.StopThreads() - end
[0x7f9906652700] | LsManager            | INFO  | 2020-11-28 12:18:01,141 | Exit LS data handler
[0x7f9907654700] | LsManager            | INFO  | 2020-11-28 12:18:01,145 | Exit LS high priority cmd handler
[0x7f9906e53700] | LsManager            | INFO  | 2020-11-28 12:18:01,145 | Exit LS low priority cmd handler
[0x7f993d348640] | Main                 | INFO  | 2020-11-28 12:18:01,155 | SvcManager: LsManager.StopThreads() - end
Exit memory data transmitter
[0x7f993d348640] | DpManager            | INFO  | 2020-11-28 12:18:01,156 | Stopping DpWfmWorker threads -- start
[0x7f985b88a700] | DpManager            | INFO  | 2020-11-28 12:18:01,156 | DpWfmWorker thread exit
[0x7f985a888700] | DpManager            | INFO  | 2020-11-28 12:18:01,156 | DpWfmWorker thread exit
[0x7f985b089700] | DpManager            | INFO  | 2020-11-28 12:18:01,156 | DpWfmWorker thread exit
[0x7f985c08b700] | DpManager            | INFO  | 2020-11-28 12:18:01,156 | DpWfmWorker thread exit
[0x7f993d348640] | DpManager            | INFO  | 2020-11-28 12:18:01,160 | Stopping DpWfmWorker threads -- done
Delete service manager
Delete cmd transmitter/receiver
Delete data transmitter/receiver
Delete remote cmd receiver
Delete remote data receiver
Exit SiteManager
[0x7f993d348640] | IO                   | INFO  | 2020-11-28 12:18:01,164 | RED FinalizeSdk
[0x7f993d348640] | SyManager.Project    | INFO  | 2020-11-28 12:18:01,180 | Unlock project Untitled Project
[0x7f991be7d700] | BtCommon             | INFO  | 2020-11-28 12:18:01,183 | Exit BtResourceManager Process Thread
Offline

Walter Sonius

  • Posts: 103
  • Joined: Wed May 03, 2017 9:53 am

Re: DaVinci Resolve on Linux - Install issues

PostSun Nov 29, 2020 11:52 pm

Heep042 wrote:I got Resolve to launch using Mesa OpenGL, and just the amdocl64 part from AMDGPU-PRO. Color grading seems to work, transitions work (including fusion ones). The issue was one OpenCL extension misbehaving (particularly, clGetGLContextInfoKHR), so I blacklisted it using LD_PRELOAD trick, and all the code for it can be found on my GitHub repo (h33p/resolve-amdocl-fix).

Alternatively, try this GDB script:
Code: Select all
set breakpoint pending on
b clGetGLContextInfoKHR
run
p $device_ptr = (unsigned long*)$rcx
finish
p *$device_ptr = 0
p $rax = -30
c


Thanks h33p, Davinci Resolve 16.2.7 does finally work again (16.1 or higher required amdgpu Pro OpenGL) on AMD Radeon R9 390x 8GB on Ubuntu-mate 20.04.1 with default xorg & mesa and only opencl=legacy component from "amdgpu Pro 20.30-1109583".

The latest DR 17.0b2 still crashes when playing/editing any video with or without your blacklist trick on mesa, however this is also confirmed in didier.villevalois his post while his use indicates Pro OpenGL.

One strange thing is that the brawspeedtest does not show "opencl" anymore only "cpu" but it may have been the windows version which worked in the past... The independent Braw player did work fine btw in all versions.
Offline

didier.villevalois

  • Posts: 31
  • Joined: Fri Nov 13, 2020 12:54 pm
  • Real Name: Didier Villevalois

Re: DaVinci Resolve on Linux - Install issues

PostMon Nov 30, 2020 10:29 am

Heep042 wrote:I got Resolve to launch using Mesa OpenGL, and just the amdocl64 part from AMDGPU-PRO. Color grading seems to work, transitions work (including fusion ones). The issue was one OpenCL extension misbehaving (particularly, clGetGLContextInfoKHR), so I blacklisted it using LD_PRELOAD trick, and all the code for it can be found on my GitHub repo (h33p/resolve-amdocl-fix).

@h33p, thanks your fix rocks!

So I was able to able a fully functional DR 16.2.7 under Fedora 33 (even the black hole in the Fairlight page is gone !).

Following in the footsteps of Arch people (thanks a lot to the incredible maintainers of the opencl-amd AUR package!), I wrapped the OpenCL part of the debian packages of AMDGPU-PRO 20.45 for Ubuntu 20.04.1 in an RPM for Fedora 33. The rational here is that Ubuntu 20.04.1 has more recent kernels than CentOS 8. You can find the whole shenanigan here:
https://github.com/ptitjes/opencl-amd.

Used in addition with https://github.com/h33p/resolve-amdocl-fix, I now have a fully functional DaVinci Resolve 16.2.7:
  • gone is the problem with some sub-menus not being displayed correctly (problem b. with AMDGPU-PRO 20.45 under Ubuntu 20.04.1, described in viewtopic.php?f=21&t=127060)
  • gone is the black hole in the Fairlight page (problem c. with AMDGPU-PRO 20.45 under Ubuntu 20.04.1, described in viewtopic.php?f=21&t=127060)

Overall, this means that the OpenGL part of the in-kernel amdgpu drivers is far more stable than the legacy (as coined by themselves in the help of `amdgpu-pro-install`) "Pro" OpenGL provided in AMDGPU-PRO drivers.

For the record, my kernel version is `5.9.10-200.fc33.x86_64` and I'm running Wayland.

I will soon publish a new "Painless DR 16.2.7 install on Fedora 33" topic after some more testing.
Resolve 16.2.7 – Fedora 33 – Wayland – Kernel 5.10.22-200.fc33 – opencl-amd-20.45.1188099-3.fc33
AMD Ryzen Threadripper 3960X – AMD Radeon RX 5700 – 64GB DDR4 3200 – Samsung 980 Pro 1TB
Offline

lost_soul

  • Posts: 143
  • Joined: Fri May 31, 2019 12:30 am
  • Location: Vancouver
  • Real Name: Shawn Metheny

Re: DaVinci Resolve on Linux - Install issues

PostThu Dec 24, 2020 10:57 pm

If any one cares there are now rocm-runtime 3.9 and related packages available in Fedora 34. ROCm 3.7 was supposed to bring image support but rocm-runtime 3.9 doesn't.
Centos 8
RX 580
AMDGPU-pro
Studio 17.1
Offline

didier.villevalois

  • Posts: 31
  • Joined: Fri Nov 13, 2020 12:54 pm
  • Real Name: Didier Villevalois

Re: DaVinci Resolve on Linux - Install issues

PostSat Dec 26, 2020 12:56 pm

lost_soul wrote:If any one cares there are now rocm-runtime 3.9 and related packages available in Fedora 34. ROCm 3.7 was supposed to bring image support but rocm-runtime 3.9 doesn't.


If you read the fedora package release notes, they say that the rocm-device-libraries is needed for image support. Also some other package for opencl are required. Tom Stellar did package those foundation libraries but he has not yet packaged some other core components of ROCm necessary for OpenCL support : device-librariers, comgr, and rocr-open-runtime... I had the idea to try to create the spec files but I believe it is too much of an endeavor for me.
Resolve 16.2.7 – Fedora 33 – Wayland – Kernel 5.10.22-200.fc33 – opencl-amd-20.45.1188099-3.fc33
AMD Ryzen Threadripper 3960X – AMD Radeon RX 5700 – 64GB DDR4 3200 – Samsung 980 Pro 1TB
Offline

lost_soul

  • Posts: 143
  • Joined: Fri May 31, 2019 12:30 am
  • Location: Vancouver
  • Real Name: Shawn Metheny

Re: DaVinci Resolve on Linux - Install issues

PostFri Jan 01, 2021 11:04 pm

didier.villevalois wrote:
lost_soul wrote:If any one cares there are now rocm-runtime 3.9 and related packages available in Fedora 34. ROCm 3.7 was supposed to bring image support but rocm-runtime 3.9 doesn't.


If you read the fedora package release notes, they say that the rocm-device-libraries is needed for image support. Also some other package for opencl are required. Tom Stellar did package those foundation libraries but he has not yet packaged some other core components of ROCm necessary for OpenCL support : device-librariers, comgr, and rocr-open-runtime... I had the idea to try to create the spec files but I believe it is too much of an endeavor for me.


That was some rally great info. Thanks for sharing. I will keep an eye on Koji for it. As for building a spec file if it includes code from AMD then you will definitely want to pass. My understanding is that the AMD repo does not align well with the way any of the Linux distros lay out their files so a LOT of transmorgafying needs to be done to get it to work for each distro.
Centos 8
RX 580
AMDGPU-pro
Studio 17.1
Offline

didier.villevalois

  • Posts: 31
  • Joined: Fri Nov 13, 2020 12:54 pm
  • Real Name: Didier Villevalois

Re: DaVinci Resolve on Linux - Install issues

PostSat Jan 02, 2021 9:28 pm

lost_soul wrote:My understanding is that the AMD repo does not align well with the way any of the Linux distros lay out their files so a LOT of transmorgafying needs to be done to get it to work for each distro.


Well that is not really a problem, package spec files (and the other packaging format for that matter) are made to make that easy, as a lot of projects organize the built artefacts differently. The problem is more of the building part of ROCm. They use CMake but with some custom plugins and I don't know CMake enough.
Resolve 16.2.7 – Fedora 33 – Wayland – Kernel 5.10.22-200.fc33 – opencl-amd-20.45.1188099-3.fc33
AMD Ryzen Threadripper 3960X – AMD Radeon RX 5700 – 64GB DDR4 3200 – Samsung 980 Pro 1TB
Offline

Haevel

  • Posts: 1
  • Joined: Thu Jan 21, 2021 3:22 pm
  • Real Name: Abel AFENDULIS

Re: DaVinci Resolve on Linux - Install issues

PostThu Jan 21, 2021 3:35 pm

Hello, I have big troubles with DaVinci Resolve. I am running Linux Manjaro 20. 2.1 based on Arch Linux on a HP14dk notebook - Athlon 300U - Radeon Vega Mobile Gfx
I installed DaVinci Resolve from AUR. When I try to launch it crashes. I heard it's complicate with AMD GPU but may be you have a suggestion to solve this problem.

Many thanks !
Offline

franc01s

  • Posts: 19
  • Joined: Wed Nov 28, 2018 6:00 pm
  • Location: Montréal
  • Real Name: Francois Breton

Re: DaVinci Resolve on Linux - Install issues

PostSat Jan 23, 2021 5:36 pm

tthoms wrote:No splash screen at all

Just in case someone else runs into that issue : you can quit or kill the splash (It's actually a tour) and Resolve will continue to load.
Resolve 16.1.2 Linux | CentOS 8.1905
CPU: Intel Core i9-9900K 3.6 GHz 8-Core
Motherboard: Gigabyte Z390 AORUS PRO ATX LGA1151
Video Card: Sapphire Radeon RX 580 8 GB PULSE
Memory: G.Skill Ripjaws V Series 64 GB (4 x 16 GB) DDR4-3200
Offline

Sulo Kokki

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

Re: DaVinci Resolve on Linux - Install issues

PostFri Feb 05, 2021 9:27 pm

didier.villevalois wrote:I wrapped the OpenCL part of the debian packages of AMDGPU-PRO 20.45 for Ubuntu 20.04.1 in an RPM for Fedora 33. The rational here is that Ubuntu 20.04.1 has more recent kernels than CentOS 8.

Good one. With AMDGPU-PRO 20.40, the --no-dkms option works on a traditional install with the pal opencl backend (for Vega & Navi). With 20.45, the backend is rocr (used in amd hpc ecosystem). rocr dismissed the --no-dkms option and goes out of tree with the kernel module.

From your other post:
didier.villevalois wrote:The recently released AMDGPU-PRO 20.45 drivers strangely do not activate OpenCL for my card. Looking into it a little bit, it seems that AMD replaced the OpenCL components to use the new ROCm framework. It seems that it does not see the RX 5700.

Navi & rocr fail to provide an OpenCL device for Resolve? That's worrisome. It means the 20.45 driver is useless for Resolve, while 20.40 uses a deprecated backend.

lost_soul wrote:ROCm 3.7 was supposed to bring image support but rocm-runtime 3.9 doesn't.

Won't come fast enough. The proprietary driver is a mess.
Linux Mint 19.3 | DaVinci Resolve Studio 16.2.7 | 2700x 32gb Vega 56 | macOS Mojave
Offline

smunaut

  • Posts: 258
  • Joined: Sat Jan 30, 2021 6:15 pm
  • Real Name: Sylvain Munaut

Re: DaVinci Resolve on Linux - Install issues

PostSat Feb 06, 2021 9:11 am

Note that for DVR17, using just the OpenCL part of the driver doesn't work anymore (at least in the current beta). That yields a non-working CL/GL interop which DVR16 had a fallback for and was able to operate without it, but DVR17 doesn't. So you need the whole closed source (CL + GL + kernel part)
Ryzen 3700X - AMD R570X / NVidia RTX2700Super (switching between the 2) - Linux
Offline

Kris Limbach

  • Posts: 46
  • Joined: Sun Mar 05, 2017 9:07 am

Re: DaVinci Resolve on Linux - Install issues

PostSat Feb 06, 2021 9:21 am

this is just half of an install issue, but still: I cannot activate the studio version anymore, i get the "please contact blackmagic.." notice and they say "..you are using a non supported distro.." so I get all that.. the thing is: everything else is working fine. when i run davincri resolve it all works out of the box, if i try to install the studio version i get the message. before it also worked well, but i unfortunately have bm asked to reset my licenses :( so no idea what to do ...are there any tipps for activation besides using a tethered phone for internet connection? i tried all kinds of connections and dont think that is the problem, but that something has changed on the server side that prevents the activation... ? This is on ubuntu and linux mint 20.1 (two different installs, same problem)
Offline
User avatar

Dwaine Maggart

Blackmagic Design

  • Posts: 7820
  • Joined: Wed Aug 22, 2012 2:53 pm

Re: DaVinci Resolve on Linux - Install issues

PostWed Feb 17, 2021 5:44 am

I'll post my frustration with AMD GPU's under Linux, as I've wasted another day trying to make this work. And add that this is why we don't support AMD GPUs in Linux.

I have an HP z420 with a Xeon E5-2650 0 (Not a v2 or v4. Intel does not even want to admit to this CPU on their site. This is a Sandy Bridge CPU, not an Ivy Bridge, the importance of which I'll get to in a bit). And I'm testing with an AMD RX580.

I've tried both CentOS 7.9 and 8.3. I've tried the current AMD Linux driver for an RX580 from the AMD Driver Download area, for each of these OS's.

The AMD driver does not work at all. OK, so everyone says the ROCm driver is the thing to use. Installed ROCm 4. ./rocminfo shows all the CPU details, but does not see the RX580. ROCm appears to be happy, other than not seeing the GPU.

After lots of Googling, the ROCm github site suggested to a user with a similar situation to do this:

dmesg |grep kfd

And see if there were any kfd errors. Indeed there was:

kfd skipped device 1002:67df, PCI rejects atomics

More Googling to see what that meant. Apparently you have to have a CPU that supports PCI atomics. Things after Ivy Bridge are supported. Ivy Bridge support looks iffy. And anything earlier than that (i.e. my Sandy Bridge CPU) won't work.

That's just swell. Would be nice if rocminfo mentioned that.

Since the current AMD driver apparently uses rocr, part of the AMD HSA architecture, I suspect that's why the AMD driver doesn't work.

Would an older AMD driver work? Probably not with a current OS version.
Dwaine Maggart
Blackmagic Design DaVinci Support
Offline

smunaut

  • Posts: 258
  • Joined: Sat Jan 30, 2021 6:15 pm
  • Real Name: Sylvain Munaut

Re: DaVinci Resolve on Linux - Install issues

PostWed Feb 17, 2021 7:11 am

So for my RX570 card the only thing that worked for resolve for me is the current 20.45 AMD driver ( https://www.amd.com/en/support/kb/relea ... inux-20-45 ).

And you need to install both the OpenCL and the OpenGL component. With DVR16 you could get away with just the OpenCL component and keep the opensource OpenGL driver. This combination is often easier to install/get working but results in CL/GL interop not working, which was fine for DVR16 because it had a fallback mechanism if CL/GL worked independently but couldn't share data, but it looks like DVR17 doesn't.

As you discovered, RoCM needs "pcie atomics" and even in my recent Ryzen 3700X, due to the motherboard pcie lane wiring, I don't have PCIe atomics support on that card. Technically AMD could make it working (they released an update so that some newer card don't need pcie atomics to work), but since that line of card is old and this would required some microcode update, they said they won't bother.

Also, I'm not sure if anyone actually got DVR17 running with RoCM at all, even on newer cards / newer system. I have no idea how good their support for OpenCL/OpenGL Interop is.

So I'd focus on getting the AMD driver to run. What exactly doesn't work ? On my system I don't think the latest driver is using RoCR, I get OpenCL through the old "orca" driver and only OpenCL 1.2 but that's enough.
Ryzen 3700X - AMD R570X / NVidia RTX2700Super (switching between the 2) - Linux
Offline
User avatar

Dwaine Maggart

Blackmagic Design

  • Posts: 7820
  • Joined: Wed Aug 22, 2012 2:53 pm

Re: DaVinci Resolve on Linux - Install issues

PostWed Feb 17, 2021 8:37 am

OK, I gave the AMD amdgpu-pro-20.45-1188099-rhel-8.2.tar driver another shot.

I used this install argument:

./amdgpu-pro-install -y --opencl=rocr,legacy

That seemed to work.

So both Resolve 16.2.7 and 17b9 Studio work with the RX580.

You do get H.264 and H.265 playback. 8 and 10 bit. HD and UHD.

You get no H.264/H.265 encode options. No H.264/5 under QuickTime and no MP4 selection.
Dwaine Maggart
Blackmagic Design DaVinci Support
Offline

smunaut

  • Posts: 258
  • Joined: Sat Jan 30, 2021 6:15 pm
  • Real Name: Sylvain Munaut

Re: DaVinci Resolve on Linux - Install issues

PostWed Feb 17, 2021 1:18 pm

@Dwaine Great, thanks for testing.

Encoding I'm not too worried about. With the output plugin support in v17 I should be able to plug any encoder I want at the output.
Ryzen 3700X - AMD R570X / NVidia RTX2700Super (switching between the 2) - Linux
Offline

smunaut

  • Posts: 258
  • Joined: Sat Jan 30, 2021 6:15 pm
  • Real Name: Sylvain Munaut

Re: DaVinci Resolve on Linux - Install issues

PostWed Feb 17, 2021 1:56 pm

BTW while you have a AMD Linux setup, can you check fairlight :

viewtopic.php?f=36&t=133739&p=726946

?
Ryzen 3700X - AMD R570X / NVidia RTX2700Super (switching between the 2) - Linux
Offline

AlynxZhou

  • Posts: 2
  • Joined: Mon Feb 22, 2021 12:53 am
  • Real Name: Alynx Zhou

Re: DaVinci Resolve on Linux - Install issues

PostMon Feb 22, 2021 1:01 am

Using Resolve Studio 17 Beta 7 on Arch Linux, I am unable to use iBus to input Chinese (or Japanese) in Resolve, it's very inconvenience to make subtitles in it. Is Resolve using Qt for it's interface? Could you enable Input Method support for it on Linux (e.g. iBus, Fcitx and Fcitx5), thanks.
Offline

lost_soul

  • Posts: 143
  • Joined: Fri May 31, 2019 12:30 am
  • Location: Vancouver
  • Real Name: Shawn Metheny

Re: DaVinci Resolve on Linux - Install issues

PostWed Feb 24, 2021 6:07 pm

For any one that is interested there is a very interesting discusion going on over at Phoronix about AMD ROCm support or lack there of. If you are in the market for a new AMD GPU and hope to be able to run it on any thing other than the distros supported by AMDGPU-pro you should give it a look before putting down money. I am posting the link to the article that started it but the forum is where the real action is. Link at the bottom of the page. It is a long read but well worth it to get a better idea of AMDs attitude towards consumers and compute.

https://www.phoronix.com/scan.php?page= ... or-AMD-HPC
Centos 8
RX 580
AMDGPU-pro
Studio 17.1
Offline
User avatar

Noel Sterrett

  • Posts: 507
  • Joined: Wed Aug 22, 2012 9:12 pm
  • Location: Atlanta

Re: DaVinci Resolve on Linux - Install issues

PostWed Feb 24, 2021 9:01 pm

Linux = Nvidia
Mac = AMD

Anything else is trouble.
Admit One Pictures
Ubuntu 20.04 | Asus Z10 Xeon*2 32G | GTX 1080 8G | Resolve Studio 17 | Desktop Video 12
Offline

bmmatbon

  • Posts: 40
  • Joined: Thu Aug 22, 2019 3:10 pm
  • Real Name: Roy Markham

Re: DaVinci Resolve on Linux - Install issues

PostFri Feb 26, 2021 1:14 pm

Noel Sterrett wrote:Linux = Nvidia
Mac = AMD

Anything else is trouble.

Yet Nvidia sucks for everything else on Linux. FWIW it's not hard to get Davinci working on AMD / Manjaro and the peformance gains are worth it.
viewtopic.php?f=21&t=126483

Just needs opencl-amd and AMDGPU-Pro opengl extracted. I've tested this easily on Arch, Manjaro, Ubuntu.
AMD 3900X, 32GB 3200Mhz HyperX, AMD 5700XT, Couple NVMes. ArcoLinux
Offline

smunaut

  • Posts: 258
  • Joined: Sat Jan 30, 2021 6:15 pm
  • Real Name: Sylvain Munaut

Re: DaVinci Resolve on Linux - Install issues

PostFri Feb 26, 2021 2:07 pm

Interesting that arch works.
I wanted to actually switch to that but was afraid that installing the GL part would be an issue ...
Ryzen 3700X - AMD R570X / NVidia RTX2700Super (switching between the 2) - Linux
Offline

pavelsiska

  • Posts: 6
  • Joined: Fri Sep 20, 2019 6:36 am
  • Real Name: Pavel Siska

Re: DaVinci Resolve on Linux - Install issues

PostFri Feb 26, 2021 11:44 pm

Hey guys,

Anyone else having troubles with Ubuntu 20.10? Davinci Resolve 17 worked like two days on my workstation and then due to a system update or something else I guess, I get a segmentation fault now. Right after running '/opt/resolve/bin/resolve' in terminal. Which outputs only "Segmentation fault" ... not much helpful.

Code: Select all
ldd '/opt/resolve/bin/resolve'

lists all the libraries as found.

I tried gdb tracing as well and got at least this:
Code: Select all
Starting program: /opt/resolve/bin/resolve
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".

Program received signal SIGSEGV, Segmentation fault.
__dlsym (handle=<optimized out>, name=0x7ffff4524860 "free") at dlsym.c:68
68   dlsym.c: No such file or directory.
(gdb) backtrace
#0  __dlsym (handle=<optimized out>, name=0x7ffff4524860 "free") at dlsym.c:68
#1  0x00007ffff4523fd5 in InitOrigPointers() () at ../../src/tbbmalloc/proxy.cpp:90
#2  free(void*) (object=0x7fffca9540b0) at ../../src/tbbmalloc/proxy.cpp:124
#3  0x00007fffec9ebbad in _dlerror_run (operate=operate@entry=0x7fffec9eb4a0 <dlsym_doit>, args=args@entry=0x7fffff7ff0a0) at dlerror.c:166
#4  0x00007fffec9eb52d in __dlsym (handle=<optimized out>, name=0x7ffff4524860 "free") at dlsym.c:70

But have no idea what it means.

My specs are:
AMD® Ryzen 9 3900x 12-core processor × 24
Nvidia GTX TITAN X
Memory 32 GB


Captured log attached
Attachments
log_archive.zip
(35 KiB) Downloaded 32 times
Offline

svenkispert

  • Posts: 1
  • Joined: Sat Feb 27, 2021 10:10 am
  • Location: Germany
  • Real Name: Sven Kispert

Re: DaVinci Resolve on Linux - Install issues

PostSat Feb 27, 2021 12:09 pm

Hey guys,

i've a problem on my Fedora machine... I can import mp4 h264 files etc. but i can't export them. It won't show up. I'm on DR Studio 17.

On Media Page:
Bildschirmfoto_2021-02-27_12-47-56.png
Bildschirmfoto_2021-02-27_12-47-56.png (672.84 KiB) Viewed 1425 times


and on deliver:
-no nvidia // h264/265
Bildschirmfoto_2021-02-27_12-51-13.png
Bildschirmfoto_2021-02-27_12-51-13.png (11.88 KiB) Viewed 1425 times


Here some logs:
Code: Select all
0x7f508d3a66c0 | Main                 | INFO  | 2021-02-27 12:28:59,383 | Running DaVinci Resolve Studio v17.0.0.0039 (Linux/Clang)
0x7f508d3a66c0 | Main                 | INFO  | 2021-02-27 12:28:59,383 | BMD_BUILD_UUID 8ed28157-d160-4bf4-b111-0a918ade5b1c
0x7f508d3a66c0 | Main                 | INFO  | 2021-02-27 12:28:59,383 | BMD_GIT_COMMIT ba9b92f484be9e33ae16d7ee945a56eabed8f12a
0x7f508d3a66c0 | GPUDetect            | INFO  | 2021-02-27 12:28:59,383 | Starting GPUDetect 1.1_1-a41
0x7f508d3a66c0 | GPUDetect            | INFO  | 2021-02-27 12:28:59,438 | Done in 55 ms.
0x7f508d3a66c0 | GPUDetect            | INFO  | 2021-02-27 12:28:59,439 | Detected System:
0x7f508d3a66c0 | GPUDetect            | INFO  | 2021-02-27 12:28:59,439 |   - OS: Linux Fedora release 33 (Thirty Three)
0x7f508d3a66c0 | GPUDetect            | INFO  | 2021-02-27 12:28:59,439 |   - Model: ASUSTeK CROSSHAIR VI HERO
0x7f508d3a66c0 | GPUDetect            | INFO  | 2021-02-27 12:28:59,439 |   - CPU: AMD Ryzen 7 1700X Eight-Core, 16 threads, x86-64
0x7f508d3a66c0 | GPUDetect            | INFO  | 2021-02-27 12:28:59,439 |   - RAM: 4.6 GiB used of 62.8 GiB
0x7f508d3a66c0 | GPUDetect            | INFO  | 2021-02-27 12:28:59,439 |   - NVIDIA Driver: 460.39, supports CUDA 11.2
0x7f508d3a66c0 | GPUDetect            | INFO  | 2021-02-27 12:28:59,439 | Detected 1 GPUs:
0x7f508d3a66c0 | GPUDetect            | INFO  | 2021-02-27 12:28:59,439 |   - "NVIDIA GeForce GTX 1080 Ti" (gpu:fe5b1ede.44ad5459) <- Main Display GPU
0x7f508d3a66c0 | GPUDetect            | INFO  | 2021-02-27 12:28:59,439 |     Discrete, 1.6 GiB used of 10.4 GiB VRAM, PCI:11:0.0
0x7f508d3a66c0 | GPUDetect            | INFO  | 2021-02-27 12:28:59,439 |     Matches: CUDA, NVML, OpenCL, XOrg
0x7f508d3a66c0 | GPUDetect            | INFO  | 2021-02-27 12:28:59,439 | Detected 1 monitors:
0x7f508d3a66c0 | GPUDetect            | INFO  | 2021-02-27 12:28:59,439 |   - "Monitor" <- Main Monitor
0x7f508d3a66c0 | GPUDetect            | INFO  | 2021-02-27 12:28:59,439 |     2560x1440, connected to "NVIDIA GeForce GTX 1080 Ti" (gpu:fe5b1ede.44ad5459)
0x7f508d3a66c0 | Main.GPUConfig       | INFO  | 2021-02-27 12:28:59,439 | Compute API set to automatic, defaulting to CUDA.
0x7f508d3a66c0 | Main.GPUConfig       | INFO  | 2021-02-27 12:28:59,439 | Selected compute API: CUDA
0x7f508d3a66c0 | Main.GPUConfig       | INFO  | 2021-02-27 12:28:59,439 | Automatic GPU Selection:
0x7f508d3a66c0 | Main.GPUConfig       | INFO  | 2021-02-27 12:28:59,439 |   - "NVIDIA GeForce GTX 1080 Ti" (gpu:fe5b1ede.44ad5459)
0x7f508d3a66c0 | IO                   | INFO  | 2021-02-27 12:28:59,439 | RED InitializeSdk with library path at /opt/resolve/libs
0x7f508d3a66c0 | IO                   | INFO  | 2021-02-27 12:28:59,527 | R3DAPI 7.3.5-48A04 (20201023 L64S) R3DSDK 7.3.5-48A04 (20201023 L64D C3B1) RED CUDA 7.3.5-50124 (20201026) [/opt/resolve/libs/] init is successful
0x7f508d3a66c0 | Main                 | INFO  | 2021-02-27 12:28:59,527 | 0 RED rocket cards available
libDeckLinkAPI.so: Kann die Shared-Object-Datei nicht öffnen: Datei oder Verzeichnis nicht gefunden
0x7f508d3a66c0 | Main                 | INFO  | 2021-02-27 12:28:59,527 | Decklink model name: '', version: ''
0x7f508d3a66c0 | DVIP                 | INFO  | 2021-02-27 12:28:59,527 | DVIP release/17.0 build 59 (b66c6827fd37a75f6900a15cb1f1edb4331a12ba). Release, version 17.0.0.
0x7f508d3a66c0 | Main                 | INFO  | 2021-02-27 12:28:59,550 | Installed custom font: Open Sans
0x7f508d3a66c0 | Main                 | INFO  | 2021-02-27 12:28:59,551 | Installed custom font: Open Sans
0x7f508d3a66c0 | Main                 | INFO  | 2021-02-27 12:28:59,551 | Installed custom font: Open Sans
0x7f508d3a66c0 | Main                 | INFO  | 2021-02-27 12:28:59,557 | Finished loading Application style sheet


And when open a project:
Code: Select all
0x7f508d3a66c0 | BtCommon             | WARN  | 2021-02-27 12:57:23,932 | Invalid object in s_IsNeedAnySharing() function
0x7f508d3a66c0 | SyManager.ProjectManager | INFO  | 2021-02-27 12:57:23,936 | Loading project (DNG_Test) from database (Local Database) took 542 ms
0x7f508d3a66c0 | UI.ActionManager     | WARN  | 2021-02-27 12:57:24,097 | Action [fairlightImmersiveRendererSettings] is not a valid global action
0x7f508d3a66c0 | UI.ActionManager     | WARN  | 2021-02-27 12:57:24,127 | Action [fairlightImmersiveRendererSettings] is not a valid global action
0x7f508d3a66c0 | UI                   | ERROR | 2021-02-27 12:57:24,187 | Failed to find text 'Apple ProRes' in combo-box
0x7f508d3a66c0 | UI                   | WARN  | 2021-02-27 12:57:24,187 | Failed to find value '203' in combo-box
0x7f508d3a66c0 | UI                   | ERROR | 2021-02-27 12:57:24,188 | Failed to find text 'Apple ProRes' in combo-box
0x7f508d3a66c0 | UI                   | WARN  | 2021-02-27 12:57:24,188 | Failed to find value '49' in combo-box
0x7f508d3a66c0 | UI                   | ERROR | 2021-02-27 12:57:24,190 | Failed to find text 'Apple ProRes' in combo-box
0x7f508d3a66c0 | UI                   | WARN  | 2021-02-27 12:57:24,190 | Failed to find value '203' in combo-box
0x7f508d3a66c0 | UI                   | WARN  | 2021-02-27 12:57:24,191 | Failed to find value '0' in combo-box
0x7f508d3a66c0 | SyManager.Gallery    | INFO  | 2021-02-27 12:57:24,274 | Start purging still caches
0x7f508d3a66c0 | SyManager.Gallery    | INFO  | 2021-02-27 12:57:24,274 | Finish purging still caches
0x7f508d3a66c0 | SyManager.Signals    | INFO  | 2021-02-27 12:57:24,294 | Media pool relink status changed to 0
0x7f508d3a66c0 | SyManager.Signals    | INFO  | 2021-02-27 12:57:24,325 | Current project pointer (DNG_Test) is changed
0x7f508d3a66c0 | SyManager.Signals    | INFO  | 2021-02-27 12:57:24,325 | Current timeline pointer (Timeline 1) is changed
0x7f508d3a66c0 | SyManager.Signals    | INFO  | 2021-02-27 12:57:24,345 | Main view page is changed to 11
0x7f508d3a66c0 | UI                   | INFO  | 2021-02-27 12:57:24,434 | Lock project DNG_Test
0x7f508d3a66c0 | UI                   | INFO  | 2021-02-27 12:57:24,450 | Initializing wipe texture of size 3840 x 2160 (old 1920 x 1080)
0x7f508d3a66c0 | UI                   | INFO  | 2021-02-27 12:57:24,450 | PBO is initialized with size [3840x2160], bitDepth=[8], hasAlpha=[1].
0x7f508d3a66c0 | UI                   | INFO  | 2021-02-27 12:57:24,470 | Gallery pointer is changed, refreshing color gallery
0x7f508d3a66c0 | UI                   | INFO  | 2021-02-27 12:57:24,488 | Gallery pointer is changed, refreshing gallery browser


So anyone know what is going on here? i don't know any further more... And sorry for my english. :?
DaVinci Resolve Studio 17.0
Fedora 33
Kernel: 5.10.18
AMD Ryzen 1700X
64GB RAM
GeForce GTX 1080 Ti
NVIDIA Driver 460.39
CUDA 11.2
www.svenkispert.com
Offline

bmmatbon

  • Posts: 40
  • Joined: Thu Aug 22, 2019 3:10 pm
  • Real Name: Roy Markham

Re: DaVinci Resolve on Linux - Install issues

PostSun Feb 28, 2021 10:26 am

smunaut wrote:Interesting that arch works.
I wanted to actually switch to that but was afraid that installing the GL part would be an issue ...

1. yay -S opencl-amd
2. Do the AMD GPU Pro workaround listed somewhere here
~/pro/drivers/
~/pro/drivers/dri
~/pro/drivers/libEGL.so
~/pro/drivers/libEGL.so.1
~/pro/drivers/libGL.so
~pro/drivers/libGL.so.1
~pro/drivers/libGL.so.1.2
~pro/drivers/libglapi.so
~/pro/drivers/libglapi.so.1
~/pro/drivers/libGLESv2.so
~pro/drivers/libGLESv2.so.2
3. Call Davinci via script
#!/bin/bash

progl() {
export LD_LIBRARY_PATH="${HOME}/pro/drivers:${LD_LIBRARY_PATH}"
export LIBGL_DRIVERS_PATH="${HOME}/pro/drivers/dri"
export dri_driver="amdgpu"
} && progl && /opt/resolve/bin/resolve

I use this on Manjaro, Arch, Garuda - any arch based. Also works on Ubuntu types. I just copy and paste the pro folder to each distro and same for the script. I'd be happy to post a zip file of the contents if you want?
AMD 3900X, 32GB 3200Mhz HyperX, AMD 5700XT, Couple NVMes. ArcoLinux
Offline

Scyten

  • Posts: 1
  • Joined: Tue Mar 02, 2021 7:32 pm
  • Real Name: Philipp Berres

Re: DaVinci Resolve on Linux - Install issues

PostTue Mar 02, 2021 7:51 pm

Hi,
I am able to run Resolve on an AMD Renoir APU in my laptop.
It is a T14 with AMD Ryzen 7 PRO 4750U with Radeon Graphics.
Using:
Manjaro +
amdgpu-pro-installer 20.45_1188099-5 commit f83f821ff893ba16a26768329d4088afdee626fb (parts of it)
opencl-amd 20.45.1164792-4 https://aur.archlinux.org/opencl-amd.git commit 99929da87153c0f36a2a9497c38221c12307ecfc

Here is how:

yay -S opencl-amd
git clone https://aur.archlinux.org/amdgpu-pro-installer.git
cd amdgpu-pro-installer
makepkg

search an copy files from the created folders to
~/pro/drivers/{libEGL.so libEGL.so.1 libglapi.so libglapi.so.1 libGLESv2.so libGLESv2.so.2 libGL.so libGL.so.1 libGL.so.1.2}
~/pro/drivers/dri/amdgpu_dri.so
echo '#!/bin/bash

progl() {
export LD_LIBRARY_PATH="${HOME}/pro/drivers:${LD_LIBRARY_PATH}"
export LIBGL_DRIVERS_PATH="${HOME}/pro/drivers/dri"
#export dri_driver="amdgpu"
} && progl && /opt/resolve/bin/resolve
. >> runDavinci.sh

sh ./runDavinci.sh

my system crashes if the "#" is removed from this line #export dri_driver="amdgpu".
Offline

Kris Limbach

  • Posts: 46
  • Joined: Sun Mar 05, 2017 9:07 am

Re: DaVinci Resolve on Linux - Install issues

PostFri Mar 05, 2021 1:22 am

seems to me that even in resolve studio i cannot render to h264 or h265 in a quicktime container. anyone here has the same experience? it will just crash after a while and that s it. I wonder if there is any other encoder or workaround.. i would like to have small file size just to make some drafts and dailies from projects , without rendering huge cineform files inbetween... I m on ubuntu 20, nvidia 450 drivers
Offline
User avatar

vitaminx

  • Posts: 11
  • Joined: Thu Jun 06, 2019 12:59 pm
  • Real Name: Roman Schmidt

Re: DaVinci Resolve on Linux - Install issues

PostSun Mar 07, 2021 1:33 am

With Davinci Resolve 17 (both 17.0 and 17.1b10) I get "Your GPU memory is full" without even opening anything, just with an empty project. Also, when previewing media in the media manager, even with still images, the preview window shows garbage. The edit window also shows garbage when moving a video to the timeline and playing back.

For some weird reason the playback in Fusion and Fairlight is OK, I can see the video normally.

The "Your GPU memory is full" must be some kind of bug, because I have a Vega 64 with 8G of RAM, and it's around 7% used and the error comes constantly up (with an empty project!).

My system is Debian Linux, the graphics drivers are the builtin amdgpu one's in linux kernel 5.10.0-3-amd64, for OpenCL I use amdgpu-pro 20.45.

Any help would be really appreciated.

BTW. other programs work just fine with OpenCL, like blender.
Offline

smunaut

  • Posts: 258
  • Joined: Sat Jan 30, 2021 6:15 pm
  • Real Name: Sylvain Munaut

Re: DaVinci Resolve on Linux - Install issues

PostSun Mar 07, 2021 7:50 am

You can't use the built-in amdgpu drivers, you need the amdgpu-pro for the OpenGL part as well.

That used to work in v16 but no longer in v17 since a working CL/GL interop (i.e. sharing of data between CL and GL) is required and no longer just independent CL and GL parts.

There is a way to use the amdgpu-pro OpenGL part only with resolve, see a couple of posts above for the GL and DRI files to extract and the env vars to setup.
Ryzen 3700X - AMD R570X / NVidia RTX2700Super (switching between the 2) - Linux
Offline

Walter Sonius

  • Posts: 103
  • Joined: Wed May 03, 2017 9:53 am

Re: DaVinci Resolve on Linux - Install issues

PostMon Mar 08, 2021 10:32 am

smunaut wrote:You can't use the built-in amdgpu drivers, you need the amdgpu-pro for the OpenGL part as well.

That used to work in v16 but no longer in v17 since a working CL/GL interop (i.e. sharing of data between CL and GL) is required and no longer just independent CL and GL parts.

There is a way to use the amdgpu-pro OpenGL part only with resolve, see a couple of posts above for the GL and DRI files to extract and the env vars to setup.


Thanks "smunaut" for your insight, just like to share some thoughts about the amdgpu-pro opengl and opencl driver need for DR 17. The "interop" match?

The amdgpu pro driver from the amd website comes in 2 parts (All-Open / Pro):
amdgpu(mesa + seperate radv or open compiler amdvlk)
amdgpu-pro(opengl + opencl + prop. closed compiler vulkan(amdvlk).

https://amdgpu-install.readthedocs.io/e ... k-variants

However most distributions comes with a recent up to date amdgpu, kfd and mesa driver so in the past we only had to add a amdgpu-pro opencl "headless" component and after DR 16.1 we had to use h33p his patch. In other words the Opencl driver from the amdgpu-pro part could catch up with the older amdgpu+mesa combination from its own distro.

If you look at the extracted AMDGPU driver packages you notice that it also ships its own kernel amdgpu and mesa version slightly off from the one of your distro. Maybe the amdgpu-pro opencl part works again if we use it as an addition on the free amdgpu part of the amd website drivers by first replacing the distro's own kernel and mesa versions from the free part of the driver?

Just take ubuntu 20.04 clean install as an example:
Check current distro amdgpu and mesa versions: packet manager/inxi -G

Download the amdgpu-pro driver, and only install the free part: ./amdgpu-install

Than after reboot install the amdgpu-pro --headless opencl part?

UPDATE1:
Just tested this on a clean ubuntu 20.04 install with default radeon(not amdgpu) kernel driver (r390 user) and its easier than speculated:

./amdgpu-install --opencl=legacy #not the pro installer

The funny thing is that it even downgrades ubuntu 20.2.6 mesa to 20.1.6 mesa driver from the amdgpu-pro website driver. However you still have to use "h33p" interop patch to run DR16.x and DR17/17.1 is not starting at all...
Last edited by Walter Sonius on Fri Mar 12, 2021 2:08 pm, edited 1 time in total.
Offline

smunaut

  • Posts: 258
  • Joined: Sat Jan 30, 2021 6:15 pm
  • Real Name: Sylvain Munaut

Re: DaVinci Resolve on Linux - Install issues

PostMon Mar 08, 2021 12:16 pm

With DR16 it worked because either it wasn't using the interop mechanism between CL/GL or it had a fallback path where to send data across, it would download the compute results rom OpenCL back to the main memory, then re-upload it as a texture for OpenGL back into the GPU. That's obviously not ideal ... and so it doesn't do that now, it all stays in the GPU always, but that requires close interaction between the OpenCL driver and the OpenGL one. Which doesn't work unless you install all of amdgpu-pro.

There might be someway to use less components than the full install, feel free to try and report but for my part, I just installed the full pro package and be done with it.
Ryzen 3700X - AMD R570X / NVidia RTX2700Super (switching between the 2) - Linux
Offline

JamesMaynardGelinas

  • Posts: 20
  • Joined: Thu Nov 16, 2017 10:27 am

Re: DaVinci Resolve on Linux - Install issues

PostMon Mar 08, 2021 10:11 pm

smunaut wrote:There might be someway to use less components than the full install, feel free to try and report but for my part, I just installed the full pro package and be done with it.


AMDGPU-Pro GL driver doesn't support vaapi hw accel decode/encode drivers, doesn't work with OBS or Natron, there have been numerous recent viewport and render bugs with Blender, is generally slow for games and use, and you still have to deal with the waveform display bug in Fairlight w/ DR-17.

I mean, f******ck!

I'm on an EVGA waiting list for a new NVIDIA card.
Offline

JamesMaynardGelinas

  • Posts: 20
  • Joined: Thu Nov 16, 2017 10:27 am

Re: DaVinci Resolve on Linux - Install issues

PostTue Mar 09, 2021 2:11 am

Scyten wrote:
~/pro/drivers/{libEGL.so libEGL.so.1 libglapi.so libglapi.so.1 libGLESv2.so libGLESv2.so.2 libGL.so libGL.so.1 libGL.so.1.2}
~/pro/drivers/dri/amdgpu_dri.so

...

export LD_LIBRARY_PATH="${HOME}/pro/drivers:${LD_LIBRARY_PATH}"
export LIBGL_DRIVERS_PATH="${HOME}/pro/drivers/dri"
#export dri_driver="amdgpu"
} && progl && /opt/resolve/bin/resolve



OK, so I tried this on Ubuntu 20.04. I've got the OpenCL hack everyone's talked about. And it starts Resolve 16.2. But Resolve doesn't work well, it's super slow. I don't have yay, so I went through the PKGSRC of the script and manually extracted each of the amdgpu-pro GL packages, put the requisite libs and dri file, set the LD_LIBRARY_PATH and LIBGL_DRIVERS_PATH, and started resolve.

CRASH! (the application, not my system) It asked me if I wanted to inform Blackmagic and I thought they'd rather not waste their time on my foolishness.

EDIT: I wrong. I made a typo. It does start Resolve 16, and performance is dramatically improved. And probably would start Resolve 17, which I assume because the Fairlight waveform bug is present. Also, the amdocl_fix.so by h33p doesn't work to fix that, which I think is the expected behavior in amdgpu_pro 20.45 (if I'm reading forum messages right).

EDIT 2: If anyone cares, this is on a 1950x TR w/ VEGA FE 16GB card.

EDIT 3: 17.1b10 starts but never loads media and ultimately crashes. Second time it starts and loads media!?! Also, Fairlight bug persists, but that's expected. Resolve 17 interface is more snappy than 16.
Offline

manjaroMan

  • Posts: 7
  • Joined: Fri Jan 25, 2019 5:29 pm
  • Real Name: Neil Dudman

Re: DaVinci Resolve on Linux - Install issues

PostSun Mar 14, 2021 7:25 am

Hello

I have Studio 17 install on ArchLinux everything works well, however importing certain MP4's the audio waveform isn't displayed, and won't play of course. These projects which are on a db, with shared nas filesystem work fine on win10. I can use ffmpeg to get the audio, but this dosn't work well with collaberation where win10 uses don't need to do this.
Code: Select all
ffmpeg -i in.mp4 -vn -acodec pcm_s16le audio_only.wav


Is this just a resolve 17 issue ? It used to be fine in 16 ?

Thanks for any help
N
Offline

smunaut

  • Posts: 258
  • Joined: Sat Jan 30, 2021 6:15 pm
  • Real Name: Sylvain Munaut

Re: DaVinci Resolve on Linux - Install issues

PostSun Mar 14, 2021 10:32 am

Linux version of resolve doesn't support AAC audio codec.
Ryzen 3700X - AMD R570X / NVidia RTX2700Super (switching between the 2) - Linux
Offline

Kitosch

  • Posts: 7
  • Joined: Sun Dec 13, 2020 10:29 am
  • Real Name: Chris Keller

Re: DaVinci Resolve on Linux - Install issues

PostSun Mar 14, 2021 11:12 am

Since I never got a reply in a separate thread let me ask here again if there are any Linux users working with clean feed to a second monitor without issues.

For me the clean feed monitor works but the other monitor basically freezes. For example, if I click somewhere in the timeline, the image on the clean feed changes accordingly but the play head on the first screen doesn't change to the new position and remains in the first position. Same with color wheels and everything else. I can change values but I can't see the current values updated on the first screen. If I drag the dot all the way to cyan, the image in the clean feed turns cyan, but the dot still sits in the very centre. Impossible to work that way.

Thanks!

Gesendet von meinem Aquaris X Pro mit Tapatalk
Offline

didier.villevalois

  • Posts: 31
  • Joined: Fri Nov 13, 2020 12:54 pm
  • Real Name: Didier Villevalois

Re: DaVinci Resolve on Linux - Install issues

PostSun Mar 14, 2021 2:15 pm

Dwaine Maggart wrote:OK, I gave the AMD amdgpu-pro-20.45-1188099-rhel-8.2.tar driver another shot.
[...]

That seemed to work.
[...]


Hi Dwaine,

So as it seemed to work for you with the OpenCL part of amdgpu-pro-20.45, I tried installing DR Studio 17.1 using the same recipe on Fedora 33 (i.e. in-kernel amdgpu + opencl from amdgpu-pro-20.45, cf viewtopic.php?f=21&t=56878&p=739104&hilit=linux#p695301).

It doesn't crash anymore at boot or when loading media which is great! Everything seems to work (even the audio waveforms on the Fairlight page), except the playback surface. :( Indeed, the playback surface is black in all pages when you launch the playback. (Except in the fusion page where it is the transparent checkerboard background.) The fullscreen playback window is also black.

I can observe when I change pages that the playback surface flickers, showing the video for an instant and then going to black again.

I attached two log archives generated by DR (one with dual viewers and one with single viewer, both in the edit page) and a screenshot.
Attachments
log_archive_20210314-141600.tgz
Log archive 1
(205.2 KiB) Downloaded 26 times
dr17-screenshot.png
Screenshot
dr17-screenshot.png (990.25 KiB) Viewed 822 times
log_archive_20210314-151229.tgz
Log archive 2
(192.39 KiB) Downloaded 28 times
Resolve 16.2.7 – Fedora 33 – Wayland – Kernel 5.10.22-200.fc33 – opencl-amd-20.45.1188099-3.fc33
AMD Ryzen Threadripper 3960X – AMD Radeon RX 5700 – 64GB DDR4 3200 – Samsung 980 Pro 1TB
Offline

smunaut

  • Posts: 258
  • Joined: Sat Jan 30, 2021 6:15 pm
  • Real Name: Sylvain Munaut

Re: DaVinci Resolve on Linux - Install issues

PostSun Mar 14, 2021 4:04 pm

You need the OpenGL part of AMDGPU pro too, not just OpenCL.
It used to work for v16. Doesn't work for v17.
Ryzen 3700X - AMD R570X / NVidia RTX2700Super (switching between the 2) - Linux
Offline

didier.villevalois

  • Posts: 31
  • Joined: Fri Nov 13, 2020 12:54 pm
  • Real Name: Didier Villevalois

Re: DaVinci Resolve on Linux - Install issues

PostSun Mar 14, 2021 7:08 pm

smunaut wrote:You need the OpenGL part of AMDGPU pro too, not just OpenCL.
It used to work for v16. Doesn't work for v17.


OK, my bad. I had not catch the `pro` in his command-line...

Well, this is not satisfying at all. The "pro" version of amdgpu is buggy and does not work with modern linux distributions. It seems that BMD is working to fix the Fairlight black-hole bug with amdgpu-pro. It is working fine with amdgpu on DR17. So why not rather fix the preview for amdgpu??

I don't want to have to use a special distro to use DR!!
Resolve 16.2.7 – Fedora 33 – Wayland – Kernel 5.10.22-200.fc33 – opencl-amd-20.45.1188099-3.fc33
AMD Ryzen Threadripper 3960X – AMD Radeon RX 5700 – 64GB DDR4 3200 – Samsung 980 Pro 1TB
Offline

smunaut

  • Posts: 258
  • Joined: Sat Jan 30, 2021 6:15 pm
  • Real Name: Sylvain Munaut

Re: DaVinci Resolve on Linux - Install issues

PostSun Mar 14, 2021 9:21 pm

The problem is not the preview ... it's a lot deeper than that.

CL/GL interop (i.e. sharing of data between OpenCL and OpenGL) only works if you use both components of the "pro" driver. Nobody implemented it in the oss driver ...

Some people managed to just the the GL part from the pro and only use it for Resolve and not for the other components in the system by extracting more libs from the pro package, putting them in some other path and then tweaking env variables before launching resove so it would use DRI/libGL from pro package. I haven't tried that yet ... it's on my TODO.

Checkout viewtopic.php?f=21&t=56878&start=1850#p732699

EDIT: Seeing your signature I have my doubts this would work with wayland though .... but worth a shot, no idea how wayland GL works really.
Ryzen 3700X - AMD R570X / NVidia RTX2700Super (switching between the 2) - Linux
Offline

Walter Sonius

  • Posts: 103
  • Joined: Wed May 03, 2017 9:53 am

Re: DaVinci Resolve on Linux - Install issues

PostMon Mar 15, 2021 11:16 am

smunaut wrote:...
Some people managed to just the the GL part from the pro and only use it for Resolve and not for the other components in the system by extracting more libs from the pro package, putting them in some other path and then tweaking env variables before launching resove so it would use DRI/libGL from pro package. I haven't tried that yet ... it's on my TODO.

Checkout viewtopic.php?f=21&t=56878&start=1850#p732699


Can confirm this is sortof working and now even the 17/17.x branch started to work for the first time, on a system with the same setup which worked for DR16! Still running the default ubuntu 20.04 amdgpu kernel and mesa 20.2.6 with the same older only OpenCL=legacy addition of the PRO driver, but I mixed it with non installed (extracted) OpenGL PRO lib components from the newest AMDGPU driver and am amazed it started playing braw 6k 50fps clips via the environment variable wrapper script!!!

To test the environment variable script for the first time and see if does anything just replace the line "/opt/resolve/bin/resolve" at the end with the program+argument "inxi -G" without the quotes. Now compare that to just running "inxi -G" without the environment variable and you should the difference in OpenGL engine. You may replace resolve/inxi -G with any other OpenGL reliant thing and it might work.

This even works with free FPS game which runs OpenGL called "sauerbraten" (available in most repo's) the framerate trippled in that game using the Pro OpenGL using the env script.

Besides resolve I was looking for this seperate OpenGL script solution for a long time, because it gives so much more flexibility per app basis with a amdgpu setup!

BTW wayland may run xwayland in the background for resolve?
Offline

esoxx_13

  • Posts: 43
  • Joined: Fri Sep 18, 2020 10:20 am
  • Real Name: pierre berthion

Re: DaVinci Resolve on Linux - Install issues

PostSun Mar 21, 2021 3:21 pm

Hello,

I'm on ubuntustudio 20.10. I have openCL running, I can open DVR 17.1 (free version), but... Nothing plays in DVR. If I import a video file it is blank, I tried h224, proressHQ (from my atomos ninja V), all of those files are blank and do not play. I tried top import a wav file, I can see the waveform, but it doesn't play, if I import a jpg image, it is also blank...


As 20.45 amdgpu doesn't install on 20.10 I ran the following command to install from 20.40 amdgpu drivers :

Code: Select all
sudo amdgpu-install  --opencl=pal,legacy --headless --no-dkms


opencl is really running, it is seen in darktable and blender as it is seen in DVR, I ran a luxmark benchmark that gave me a better result than the same benchmark on OSX (on the same computer).

I installed DVR directly from the install file wich is now compatible with ubuntu

I have 2x RX580 4 Go Gpus

Do someone have an idea ?
Offline

smunaut

  • Posts: 258
  • Joined: Sat Jan 30, 2021 6:15 pm
  • Real Name: Sylvain Munaut

Re: DaVinci Resolve on Linux - Install issues

PostSun Mar 21, 2021 3:42 pm

Read above ...

CL isn't enough.

You need CL/GL interop and that only works when using the closed source GL library tool. DVR16 used to work without it, that's not the case anymore.
Ryzen 3700X - AMD R570X / NVidia RTX2700Super (switching between the 2) - Linux
Offline

Smoerrebroed

  • Posts: 1
  • Joined: Mon Mar 22, 2021 6:41 am
  • Real Name: Smoerrebroed Roempoempoem

Re: DaVinci Resolve on Linux - Install issues

PostMon Mar 22, 2021 6:49 am

So I just installed DVR 17.1 on my Arch box. Installation was a breeze thanks to a good AUR package. However, I cannot get it to import h.264 material in an mp4 container coming from my DJI drone. It will simply ignore the file and not even spit out any error/info. Running the same import on macOS, this works like a charm. On top of this, I found a document that claims compatibility with h.264 (for decoding) also on Linux, but it certainly doesn't look like it.

Converting the file to prores actually works, but why is it ignoring the h.264 under Linux only? Am I missing any dependencies for that? (I'd expect some kind of message in that case.)

Thanks for enlightening me!

Cheers,

Smoerrebroed
Offline

esoxx_13

  • Posts: 43
  • Joined: Fri Sep 18, 2020 10:20 am
  • Real Name: pierre berthion

Re: DaVinci Resolve on Linux - Install issues

PostMon Mar 22, 2021 11:24 am

bmmatbon wrote:
smunaut wrote:Interesting that arch works.
I wanted to actually switch to that but was afraid that installing the GL part would be an issue ...

1. yay -S opencl-amd
2. Do the AMD GPU Pro workaround listed somewhere here
~/pro/drivers/
~/pro/drivers/dri
~/pro/drivers/libEGL.so
~/pro/drivers/libEGL.so.1
~/pro/drivers/libGL.so
~pro/drivers/libGL.so.1
~pro/drivers/libGL.so.1.2
~pro/drivers/libglapi.so
~/pro/drivers/libglapi.so.1
~/pro/drivers/libGLESv2.so
~pro/drivers/libGLESv2.so.2
3. Call Davinci via script
#!/bin/bash

progl() {
export LD_LIBRARY_PATH="${HOME}/pro/drivers:${LD_LIBRARY_PATH}"
export LIBGL_DRIVERS_PATH="${HOME}/pro/drivers/dri"
export dri_driver="amdgpu"
} && progl && /opt/resolve/bin/resolve

I use this on Manjaro, Arch, Garuda - any arch based. Also works on Ubuntu types. I just copy and paste the pro folder to each distro and same for the script. I'd be happy to post a zip file of the contents if you want?


Yes, would love a zip of that ! On what version on ubuntu and DVR ? When did you get the file from ? 20.45 or 20.40 ?

I don't have the yay command on ubuntu
Offline

JamesMaynardGelinas

  • Posts: 20
  • Joined: Thu Nov 16, 2017 10:27 am

Re: DaVinci Resolve on Linux - Install issues

PostMon Mar 22, 2021 9:02 pm

esoxx_13, I just dug through the script and used that to extract the libs manually. DR17 works on Ubuntu 20.04 as long as you include both the AMDGPU-Pro 20.45 OpenCL and OpenGL libs, then launch Resolve with the correct wrapper script to load the right libs. However, the Fairlight bug with no waveforms displayed is still present. I have been able to cut, mask, and color though. And Fusion seems to work well enough, though I haven't used it for much more than titles. It is much faster than the old way with DR16. Very noticable. I don't know if this is due to the new ROCm based CL libs or what, but display performance and playback is much improved.
Offline
User avatar

Dwaine Maggart

Blackmagic Design

  • Posts: 7820
  • Joined: Wed Aug 22, 2012 2:53 pm

Re: DaVinci Resolve on Linux - Install issues

PostMon Mar 22, 2021 11:01 pm

@Smoerrebroed: Only Resolve Studio supports H.264/265 files on Linux. Are you using the Studio version?
Dwaine Maggart
Blackmagic Design DaVinci Support
Offline

esoxx_13

  • Posts: 43
  • Joined: Fri Sep 18, 2020 10:20 am
  • Real Name: pierre berthion

Re: DaVinci Resolve on Linux - Install issues

PostTue Mar 23, 2021 8:44 pm

JamesMaynardGelinas wrote:esoxx_13, I just dug through the script and used that to extract the libs manually. DR17 works on Ubuntu 20.04 as long as you include both the AMDGPU-Pro 20.45 OpenCL and OpenGL libs, then launch Resolve with the correct wrapper script to load the right libs. However, the Fairlight bug with no waveforms displayed is still present. I have been able to cut, mask, and color though. And Fusion seems to work well enough, though I haven't used it for much more than titles. It is much faster than the old way with DR16. Very noticable. I don't know if this is due to the new ROCm based CL libs or what, but display performance and playback is much improved.


Thanks for your answer. The problem is that I'm on 20.10, can't use 20.04 because of jack support on this 20.04, the jackd implementation of the FFADO (FW audio) driver is very poor and I need it, it works perfectly on 20.10. Anyway I tried to install 20.04 on a disk but it is now 20.04-2 and the AMD 20.45 drivers are for 20.04-1... I had errors trying to install the 20.45 drivers on 20.04-2 ! So I managed to install openCL from the 20.40, that worked on my 20.10 and got openCV support also, I have openCL in Blender and Darktable and good benchmark test. Furthermore, 20.04 in a real pain in the neck for UEFI installation. At least for me, I'm not a pro Linux administrator.

This a bit of an endless nightmare, I don't have the Linux knowledge you have.
Offline

JamesMaynardGelinas

  • Posts: 20
  • Joined: Thu Nov 16, 2017 10:27 am

Re: DaVinci Resolve on Linux - Install issues

PostWed Mar 24, 2021 2:25 am

Hi esoxx_13

I'm using jack on 20.04 with the Low Latency official HWE kernel 5.8. It seems pretty good. But I don't use a firewire audio interface, so I'm not in your boat there. Have a Zoom H6 and an old Creative E-MU 0404, both of which have XLR interfaces and work well enough for my limited recording needs.

Anyway, let's assume there's a kernel or library or whatever in Ubuntu 20.10 you really need for jackd. And for that reason, the AMDGPU-Pro installer won't work. There's a file:

/etc/os-release

Which you could edit to trick the AMDGPU-Pro installer into installing. But you may have to run one of the older kernels for it to build the specified kernel bits for their Pro driver. The proprietary GL driver is terrible too. It's slow and doesn't work with common software like OBS and Natron. (No OBS is a deal killer for me).

This is really not the best way to do this. You're much better off using the FOSS driver and MesaGL. Then copying the proprietary OpenCL and OpenGL libs somewhere, and using that wrapper script to start resolve. This gives you MesaGL running normally. I do have the proprietary OpenCL libs installed normally using AMDGPU-Pro, though I think you can get away with installing the latest ROCm-4 packages and then using the proprietary GL libs.

BUT. No matter how you approach this, you're in for a nightmare tweaking session. All of us using Resolve regularly ought to just bite the bullet and buy NVIDIA cards. As obnoxious as that is, especially now with insane GPU prices. I have a VEGA FE 16GB and when it works it's great with Resolve. But more often than not, I've had endless driver problems due to AMD's insanity.

That said, you can get it to mostly work. With the caveat that the Fairlight bug will still bite you. And I have no idea if or when that will get fixed. Seems like it's a driver problem and not Blackmagic's fault. That said, they may need to code a workaround just to get Fairlight to work right. Because who knows if or when AMD will ever fix their "Pro" Linux driver.
PreviousNext

Return to DaVinci Resolve

Who is online

Users browsing this forum: Google [Bot], pluggy and 64 guests