DaVinci Resolve on Linux - Install issues

... the driver mentioned by Walter is provided via the AUR and I just installed it. (Source: https://aur.archlinux.org/packages/opencl-amd/ )

Unfortunately, Resolve still does not start.

...

I used the kernel arguments mentioned by Walter.
My card is a Radeon RX 570.

OpenCL != OpenGL

Besides the right driver requirements "Radeon vs AMDGPU (both opensource)" I mentioned the closed source other TWO components: OpenGL and OpenCL. The first, OpenGL can be taken care off by "Mesa" which is the default for most linux distributions and did work until Davinci Resolve 16.0 but it must be replaced with closed source proprietary OpenGL (if you use the amdgpu pro driver) which is a requirment for Davince Resolve 16.1 and higher.

The kernel arguments I gave are for early GCN AMDGPU's lower than Rx4xx series like R9-290x or R9-390x (which uses by default RADEON driver) and you have RX570 (default AMDGPU driver). The later AMDGPU driver can be assisted with closed source OpenCL modules or replaced OpenGL modules(only one OpenGL system can be installed). For Vulkan and OpenCL multiple backends can be installed and used with AMDGPU on the same system.

You already answered one of my question, that is you are running with a RX5xx card with only OpenCL provided by AMDGPU pro driver (pal/orca/legacy) and still cannot run current Resolve 16.xx because you probably miss the AMDGPU pro OpenGL driver... so for confirmation?

@Andreas56
Please try the older first 16.00 release of Davinci resolve and see if that works with only having OpenCL installed, or install the proprietary closed AMDGPU pro OpenGL component which (removes Mesa OpenGL) but you have to find the archlinux/manjora equivalent package:https://aur.archlinux.org/packages/amdgpu-pro-libgl/

OpenCL != OpenGL

Besides the right driver requirements "Radeon vs AMDGPU (both opensource)" I mentioned the closed source other TWO components: OpenGL and OpenCL. The first, OpenGL can be taken care off by "Mesa" which is the default for most linux distributions and did work until Davinci Resolve 16.0 but it must be replaced with closed source proprietary OpenGL (if you use the amdgpu pro driver) which is a requirment for Davince Resolve 16.1 and higher.

The kernel arguments I gave are for early GCN AMDGPU's lower than Rx4xx series like R9-290x or R9-390x (which uses by default RADEON driver) and you have RX570 (default AMDGPU driver). The later AMDGPU driver can be assisted with closed source OpenCL modules or replaced OpenGL modules(only one OpenGL system can be installed). For Vulkan and OpenCL multiple backends can be installed and used with AMDGPU on the same system.

You already answered one of my question, that is you are running with a RX5xx card with only OpenCL provided by AMDGPU pro driver (pal/orca/legacy) and still cannot run current Resolve 16.xx because you probably miss the AMDGPU pro OpenGL driver... so for confirmation?

@Andreas56
Please try the older first 16.00 release of Davinci resolve and see if that works with only having OpenCL installed, or install the proprietary closed AMDGPU pro OpenGL component which (removes Mesa OpenGL) but you have to find the archlinux/manjora equivalent package:https://aur.archlinux.org/packages/amdgpu-pro-libgl/

Hi Walter,

I tried the proprietary OpenGL driver and Resolve still does not start. Here is the log.

Code: Select all

[0x7fdfef64a5c0] | Main                 | INFO  | 2020-09-02 23:11:00,089 | Running DaVinci Resolve v16.0.0.060 (Linux/Clang)
[0x7fdfef64a5c0] | Main                 | INFO  | 2020-09-02 23:11:00,089 | Updating display GPU information...
[0x7fdfef64a5c0] | Main                 | INFO  | 2020-09-02 23:11:00,228 | Detecting Main Display properties
[0x7fdfef64a5c0] | Main                 | INFO  | 2020-09-02 23:11:00,235 | Process to detect main display has finished
[0x7fdfef64a5c0] | Main                 | INFO  | 2020-09-02 23:11:00,242 | Fallback process to detect main display has finished
[0x7fdfef64a5c0] | Main                 | INFO  | 2020-09-02 23:11:00,242 | GPU Name = 'Radeon RX 570 Series', Main display = 0
[0x7fdfef64a5c0] | Main                 | INFO  | 2020-09-02 23:11:00,242 | 1 GPUs (excluding display GPU) found. Using OpenCL for processing.
[0x7fdfef64a5c0] | Main                 | INFO  | 2020-09-02 23:11:00,242 | Not GLmap capable. GPUs: 1 discrete, 0 integrated, 0 external. Auto mapping, OpenCL processing, main display not on external GPU.
[0x7fdfef64a5c0] | Main                 | INFO  | 2020-09-02 23:11:00,242 | Setting LsManager.3.NumGPUs = 1
[0x7fdfef64a5c0] | IO                   | INFO  | 2020-09-02 23:11:00,242 | RED InitializeSdk with library path at /opt/resolve/libs
[0x7fdfef64a5c0] | IO                   | INFO  | 2020-09-02 23:11:00,268 | R3DAPI 7.1.0-3YM06 (20180720 L64S) R3DSDK 7.1.0-3YM06 (20180720 L64D) RED CUDA 7.1.0-45494 (20180721) RED OPENCL 7.1.0-45494 (20180721) [/opt/resolve/libs/] init is successful
[0x7fdfef64a5c0] | Main                 | INFO  | 2020-09-02 23:11:00,268 | 0 RED rocket cards available
There are 1 GPUs in the system.
libDeckLinkAPI.so: Kann die Shared-Object-Datei nicht öffnen: Datei oder Verzeichnis nicht gefunden
[0x7fdfef64a5c0] | Main                 | INFO  | 2020-09-02 23:11:00,268 | Decklink model name: '', version: ''
[0x7fdfef64a5c0] | DVIP                 | INFO  | 2020-09-02 23:11:00,268 | DVIP Version : 16.0.0, Revision = 88204 (Release)
[0x7fdfef64a5c0] | Main                 | INFO  | 2020-09-02 23:11:00,492 | Installed custom font: Open Sans
[0x7fdfef64a5c0] | Main                 | INFO  | 2020-09-02 23:11:00,492 | Installed custom font: Open Sans
[0x7fdfef64a5c0] | Main                 | INFO  | 2020-09-02 23:11:00,492 | Installed custom font: Open Sans
[0x7fdfef64a5c0] | Main                 | INFO  | 2020-09-02 23:11:00,507 | Finished loading Application style sheet
Local.Speed.Debug switched OFF - ''
[0x7fdfc282b640] | LeManager            | INFO  | 2020-09-02 23:11:00,556 | 521, 38
[0x7fdfef64a5c0] | BtCommon             | INFO  | 2020-09-02 23:11:01,074 | Memory config: reserved=6000M pinned=4000M log=0
[0x7fdfef64a5c0] | BtCommon             | INFO  | 2020-09-02 23:11:01,074 | Using default pooled memory manager
[0x7fdfc202a640] | BtCommon             | INFO  | 2020-09-02 23:11:01,074 | BtResourceManager Process Thread Started
[0x7fdfef64a5c0] | BtCommon             | INFO  | 2020-09-02 23:11:01,074 | Daemon DPDecoder is started 89443
[0x7fdfef64a5c0] | BtCommon             | INFO  | 2020-09-02 23:11:01,074 | Daemon DPDecoder is started 89444
[0x7fdfef64a5c0] | BtCommon             | INFO  | 2020-09-02 23:11:01,074 | Daemon DPDecoder is started 89445
[0x7fdfef64a5c0] | BtCommon             | INFO  | 2020-09-02 23:11:01,074 | Daemon DPDecoder is started 89446
[0x7fdfef64a5c0] | BtCommon             | INFO  | 2020-09-02 23:11:01,075 | Daemon DPDecoder is started 89447
[0x7fdfef64a5c0] | BtCommon             | INFO  | 2020-09-02 23:11:01,075 | Daemon DPDecoder is started 89448
[0x7fdfef64a5c0] | BtCommon             | INFO  | 2020-09-02 23:11:01,075 | Daemon DPDecoder is started 89449
[0x7fdfef64a5c0] | BtCommon             | INFO  | 2020-09-02 23:11:01,075 | Daemon DPDecoder is started 89450
[0x7fdfef64a5c0] | SyManager            | INFO  | 2020-09-02 23:11:01,079 | Total: 20, NumDtThreads: 8, NumComms: 0, NumSites: 1

[0x7fdfef64a5c0] | SyManager            | INFO  | 2020-09-02 23:11:01,079 | Lookaheads -> playback = 20, record = 20, stop = 2

Sy High Command Handler Thread ----- (140598975817280)
SY high priority cmd handler thread starts: C0026640
Sy Low Command Handler Thread ----- (140598967424576)
SY low priority cmd handler thread starts: BF825640
Sy Data Handler Thread ----- (140598959031872)
SY data handler thread starts: BF024640
Gs High Command Handler Thread ----- (140598933853760)
GS high priority cmd handler thread starts: BD821640
Gs Low Command Handler Thread ----- (140598925461056)
GS low priority cmd handler thread starts: BD020640
Dp High Command Handler Thread ----- (140598908675648)
[0x7fdfbc81f640] | GsManager            | INFO  | 2020-09-02 23:11:01,079 | Gs Processor Thread ----- (140598917068352)

Dp Low Command Handler Thread ----- (140598900282944)
DP low priority cmd handler thread starts: BB81D640
DP high priority cmd handler thread starts: BC01E640
GS processor thread starts: BC81F640
Local.Speed.Verbose switched OFF - ''
Dt High Command Handler Thread ----- (140598891890240)
Dt Low Command Handler Thread ----- (140598883497536)
DT high priority cmd handler thhread starts: BB01C640
DT low priority cmd handler thread starts: BA81B640
[0x7fdfbe022640] | SyManager            | ERROR | 2020-09-02 23:11:01,079 | Failed to connect to panel socket
[0x7fdfef64a5c0] | DtManager            | INFO  | 2020-09-02 23:11:01,079 | Using 8 generic IO threads
[0x7fdfba01a640] | DtManager            | INFO  | 2020-09-02 23:11:01,079 | Dt Data Handler Thread Started
DT data handler thread starts: BA01A640
[0x7fdfbe022640] | SyManager            | ERROR | 2020-09-02 23:11:01,079 | DRIVER: open /var/tmp/davinci_socket failed
[0x7fdfef64a5c0] | DtManager            | INFO  | 2020-09-02 23:11:01,080 | Total of 16 IO threads (including 8 generic and 8 Red decode threads)
[0x7fdfb9018640] | DtManager            | INFO  | 2020-09-02 23:11:01,080 | Dt Worker Thread Started
[0x7fdfb8817640] | DtManager            | INFO  | 2020-09-02 23:11:01,080 | Dt Worker Thread Started
[0x7fdfb6813640] | DtManager            | INFO  | 2020-09-02 23:11:01,080 | Dt Worker Thread Started
[0x7fdfb7815640] | DtManager            | INFO  | 2020-09-02 23:11:01,080 | Dt Worker Thread Started
[0x7fdfb480f640] | DtManager            | INFO  | 2020-09-02 23:11:01,080 | Dt Worker Thread Started
[0x7fdfb380d640] | DtManager            | INFO  | 2020-09-02 23:11:01,080 | Dt Worker Thread Started
[0x7fdfb9819640] | DtManager            | INFO  | 2020-09-02 23:11:01,080 | Dt Worker Thread Started
Ls High Command Handler Thread ----- (140598724036160)
[0x7fdfb6012640] | DtManager            | INFO  | 2020-09-02 23:11:01,080 | Dt Worker Thread Started
Ls Low Command Handler Thread ----- (140598715643456)
LS low priority cmd handler thread starts: B0807640
Ls Data Handler Thread ----- (140598707250752)
[0x7fdfb5811640] | DtManager            | INFO  | 2020-09-02 23:11:01,080 | Dt Worker Thread Started
Ls High Command Handler Thread ----- (140598698858048)
Ls Low Command Handler Thread ----- (140598690465344)
LS data handler thread starts: B0006640
LS low priority cmd handler thread starts: AF004640
[0x7fdfb5010640] | DtManager            | INFO  | 2020-09-02 23:11:01,080 | Dt Worker Thread Started
Ls Data Handler Thread ----- (140598682072640)
Ls High Command Handler Thread ----- (140598673679936)
LS data handler thread starts: AE803640
Ls Low Command Handler Thread ----- (140598665287232)
LS low priority cmd handler thread starts: AD801640
[0x7fdfb8016640] | DtManager            | INFO  | 2020-09-02 23:11:01,080 | Dt Worker Thread Started
Ls Data Handler Thread ----- (140598656894528)
Mem Data Transmitter Thread ----- (140598648501824)
[0x7fdfef64a5c0] | DbCommon2            | INFO  | 2020-09-02 23:11:01,080 | Loading dblist file: /home/christian/.local/share/DaVinciResolve/configs/.dblist
Mem data transmitter thread starts: AC7FF640
[0x7fdfb7014640] | DtManager            | INFO  | 2020-09-02 23:11:01,080 | Dt Worker Thread Started
[0x7fdfb300c640] | DtManager            | INFO  | 2020-09-02 23:11:01,080 | Dt Worker Thread Started
[0x7fdfb280b640] | DtManager            | INFO  | 2020-09-02 23:11:01,080 | Dt Worker Thread Started
[0x7fdfb200a640] | DtManager            | INFO  | 2020-09-02 23:11:01,080 | Dt Worker Thread Started
[0x7fdfb1809640] | DtManager            | INFO  | 2020-09-02 23:11:01,080 | Dt Worker Thread Started
[0x7fdfb400e640] | DtManager            | INFO  | 2020-09-02 23:11:01,080 | Dt Worker Thread Started
[0x7fdfad000640] | GPUManager           | INFO  | 2020-09-02 23:11:01,080 | Let There Be OpenCL Light!
[0x7fdfad000640] | GPUManager           | INFO  | 2020-09-02 23:11:01,084 | Start detecting OpenCL boards
[0x7fdfad000640] | GPUManager           | INFO  | 2020-09-02 23:11:01,084 | Skipping unqualified OpenCL platform: Clover
[0x7fdfad000640] | GPUManager           | INFO  | 2020-09-02 23:11:01,084 | Found qualified OpenCL board 0: platform - AMD Accelerated Parallel Processing, vendor - Advanced Micro Devices, Inc., id - 0x7fdfd0298e50, device name - Radeon RX 570 Series id - 0x7fdfe8982b10, global memory size (MB) - 7868, local memory size (KB) - 32, max global memory alloc size (MB) - 6491
[0x7fdfad000640] | GPUManager           | INFO  | 2020-09-02 23:11:01,084 | 1 OpenCL boards detected
[0x7fdfad000640] | GPUManager           | INFO  | 2020-09-02 23:11:01,084 | Board manager thread id 0xaae78640 policy 0 priority 0
[0x7fdfaae78640] | GPUManager           | INFO  | 2020-09-02 23:11:01,084 | Initializing GPU board 0 with context thread 0
[0x7fdfef64a5c0] | IO                   | ERROR | 2020-09-02 23:11:01,092 | Braw HRESULT = 0x80000004
[0x7fdfef64a5c0] | IO                   | INFO  | 2020-09-02 23:11:01,092 | Using DNxHR library v2.4.0.57r
[0x7fdfaae78640] | GPUManager           | INFO  | 2020-09-02 23:11:01,159 | Setting channel cache size on GPU board 0 to 4
[0x7fdfaae78640] | GPUManager           | INFO  | 2020-09-02 23:11:01,159 | Board manager 0 on thread 0 initialization done on GPU Radeon RX 570 Series

MidiInDummy: This class provides no functionality.


MidiOutDummy: This class provides no functionality.

[0x7fdfef64a5c0] | Fairlight            | INFO  | 2020-09-02 23:11:02,188 | 00.00.00.975(000): Running Fairlight (r011941-a2024b7)
[0x7fdfef64a5c0] | UI.GLContext         | INFO  | 2020-09-02 23:11:02,194 | Creating shared OpenGL context for this thread (2 total).
[0x7fdfef64a5c0] | UI.GLContext         | INFO  | 2020-09-02 23:11:02,200 | Initialized OpenGL 4.6 (requested 2.0) on device 'ATI Technologies Inc. Radeon RX 570 Series'
[0x7fdf3e9ff640] | UI.GLContext         | INFO  | 2020-09-02 23:11:02,200 | Creating shared OpenGL context for this thread (3 total).


==========[CRASH DUMP]==========
Please send this to support:

#TIME Wed Sep  2 23:11:02 2020 - Uptime 00:00:01 (hh:mm:ss)
#PROGRAM_NAME DaVinci Resolve v16.0.0.060 (Linux/Clang)

/opt/resolve/bin/resolve() [0x509f8b9]
/opt/resolve/bin/resolve() [0x509f0aa]
/usr/lib/libpthread.so.0(+0x140f0) [0x7fdff436c0f0]
Signal Number = 11

================================
[0x7fdfaae78640] | GPUManager           | INFO  | 2020-09-02 23:11:08,918 | Completed prebuild of basic OpenCL kernels in 7759 msec
[0x7fdfaae78640] | GPUManager           | INFO  | 2020-09-02 23:11:08,918 | Entering loop to wait for commands
[0x7fdfad000640] | GPUManager           | INFO  | 2020-09-02 23:11:08,918 | Finished initializing OpenCL board 0 <Radeon RX 570 Series> on platform <AMD Accelerated Parallel Processing> clock rate <1284> multiprocessor count <32> global mem size (MB) 7868, available mem size (MB) 0, shared mem size (KB) 32, on SBM[0|0]
[0x7fdfad000640] | GPUManager           | INFO  | 2020-09-02 23:11:08,918 | Hired OpenCL board 0 <Radeon RX 570 Series>
[0x7fdfad000640] | GPUManager           | INFO  | 2020-09-02 23:11:08,918 | Let There Be OpenCL Light, Done!!
Board 0 - Radeon_RX_570_Series
1 REACTOR GPU NAMES = Radeon_RX_570_Series,
LS data handler thread starts: AD000640
[0x7fdf3e9ff640] | CrashReport          | ERROR | 2020-09-02 23:11:09,205 | Compress() : Failed to add file to archive.
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
ActCCMessage Already in Table: Code= 2282, Mode=  0, Level=  0, CmdKey= 8, Option= 0
PnlMsgActionStringAdapter Already in Table: Code= 615e, Mode=  0, Level=  0, CmdKey= -1, Option= 0
log4cxx: No appender could be found for logger (Main).
log4cxx: Please initialize the log4cxx system properly.


Now, as you suggested, I downgraded to Resolve 16.0 and removed the proprietary OpenGL driver. That still did not help. I also tried old Resolve 16.0 + proprietary OpenGL and that caused the same error as in the log above.

All three variants with proprietary OpenCL.

@Andreas56

You are sure Mesa OpenGL was also removed/setup functioning correctly when switching to/from AMDGPU Proprietary legacy OpenGL?

Something on my system got updated and now I can neither run Davinci or the installer. I had a working Resolve Studio 12.6.3 installation working fine. I'm not sure what got updated but today I could no longer launch the program.

I tried downloading 12.6.6 but could not launch the installer.

I realized both the app and the installer run "genconfig", this is segfaulting on `libqxcb.so` which is part of Qt5's `libqt5gui5` package. I updated this package from 15.12.5 to the latest 15.4.2 but am getting the same segfault.

Anyone else seeing this? Is there a way to work around genconfig?

Here is the gdb backtrace:

Code: Select all

Starting program: /opt/resolve/bin/genconfig
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7ffff56c8700 (LWP 49227)]

Thread 1 "genconfig" received signal SIGSEGV, Segmentation fault.
0x00007ffff599bb4a in ?? () from /opt/resolve/libs/plugins/platforms/libqxcb.so
(gdb) bt
#0  0x00007ffff599bb4a in ?? () from /opt/resolve/libs/plugins/platforms/libqxcb.so
#1  0x00007ffff599bb0e in ?? () from /opt/resolve/libs/plugins/platforms/libqxcb.so
#2  0x00007ffff5983395 in ?? () from /opt/resolve/libs/plugins/platforms/libqxcb.so
#3  0x00007ffff5987c5b in ?? () from /opt/resolve/libs/plugins/platforms/libqxcb.so
#4  0x00007ffff599bf6e in ?? () from /opt/resolve/libs/plugins/platforms/libqxcb.so
#5  0x00007ffff74a6051 in QPlatformIntegrationFactory::create(QString const&, QStringList const&, int&, char**, QString const&) () from /opt/resolve/bin/../libs/libQt5Gui.so.5
#6  0x00007ffff74b04ab in QGuiApplicationPrivate::createPlatformIntegration() () from /opt/resolve/bin/../libs/libQt5Gui.so.5
#7  0x00007ffff74b159b in QGuiApplicationPrivate::createEventDispatcher() () from /opt/resolve/bin/../libs/libQt5Gui.so.5
#8  0x00007ffff709ba45 in QCoreApplication::init() () from /opt/resolve/bin/../libs/libQt5Core.so.5
#9  0x00007ffff709b9b4 in QCoreApplication::QCoreApplication(QCoreApplicationPrivate&) () from /opt/resolve/bin/../libs/libQt5Core.so.5
#10 0x00007ffff74ae939 in QGuiApplication::QGuiApplication(QGuiApplicationPrivate&) () from /opt/resolve/bin/../libs/libQt5Gui.so.5
#11 0x00007ffff7aa20a2 in QApplication::QApplication(int&, char**, int) () from /opt/resolve/bin/../libs/libQt5Widgets.so.5
#12 0x0000000000400973 in main (argc=-173703288, argv=0x0) at main.cpp:7

I'm running Resolve 16.1 on Ubuntu 19.10 with old ROCM OpenCL drivers because previously the AMDGPUPRO drivers didn't work with Fusion. While these older ROCM drivers do work with Fusion, they are very buggy in the color grading tab - often causing program crashes doing the simplest things.

Question: Is AMDGPUPRO 20.30 + AMD OpenCL libs finally working with Resolve? If I upgrade to Ubuntu 20.04 and install the latest AMDGPU is this known to work? Will I have to wipe everything and install a suppoerted CENTOS?

I'm even thinking of installing Windows just to keep Resolve functional. But I'd much rather run Linux.

Am a licensed Resolve Studio owner, if that matters.

My Operating System is Manjaro (Gnome) and while it appears that I was able to install the AUR package of DaVinci Resolve through yay, it crashes while loading. In the loading screen, it says "Looking for Control Surface".

https://files.catbox.moe/gw0hos.png

I believe it's talking about one of these: https://files.catbox.moe/jk1jcd.png
It has worked fine on Windows 10, so this piece of Hardware is not essential. The software does not seem to be available on other outlets such as snap, flatpak. Is there an additional package I can install that will fix this?

I've succesfully installed Resolve 16.2.6 in my Ubuntu 20.04 with Radeon RX480 according to this youtube video tutorial installation process titled: "Installing AMD OpenCL ROCm driver Ubuntu 20.04"

I have this only one issue: I don't see nothing on the video preview window ( Cut and Edit ) otherwise I can see the video preview window on the Color tab.

Posted Images:

Um, guys. I don't think they're listening.

I've succesfully installed Resolve 16.2.6 in my Ubuntu 20.04 with Radeon RX480 according to this youtube video tutorial installation process titled: "Installing AMD OpenCL ROCm driver Ubuntu 20.04"
...

Interresting to see that with only the OpenCL supplement from ROCm(instead of the AMDGPU pro OpenCL), you we're able to start Davinci resolve. Could you check if you really run OpenGL from Mesa and not AMDGPU pro propietary legacy OpenGL, because that also seem to be a requirement since DR 16.1 or higher?

Please run the following command in the terminal and post the output:

Code: Select all

glxinfo | grep Mesa

Have you also tried installing only the AMDGPU OpenCL drivers and see if that worked?

Question: Is AMDGPUPRO 20.30 + AMD OpenCL libs finally working with Resolve? If I upgrade to Ubuntu 20.04 and install the latest AMDGPU is this known to work? Will I have to wipe everything and install a suppoerted CENTOS?

If you have enough RAM, you may just try ubuntu 20.04.1 from USB live RAM session and test if Fusion Tab/Page is working for you?

I haven't tested Fusion part but in 20.04.1 with AMDGPU pro (OpenGL & OpenCL) install DR 16.2.x was playing 4k&6k braw examples fine including intensity-pro output (DesktopVideo 11.6.0 driver).

I've succesfully installed Resolve 16.2.6 in my Ubuntu 20.04 with Radeon RX480 according to this youtube video tutorial installation process titled: "Installing AMD OpenCL ROCm driver Ubuntu 20.04"
...

Interresting to see that with only the OpenCL supplement from ROCm(instead of the AMDGPU pro OpenCL), you we're able to start Davinci resolve. Could you check if you really run OpenGL from Mesa and not AMDGPU pro propietary legacy OpenGL, because that also seem to be a requirement since DR 16.1 or higher?

Please run the following command in the terminal and post the output:

Code: Select all

glxinfo | grep Mesa

Have you also tried installing only the AMDGPU OpenCL drivers and see if that worked?

Here is my: glxinfo output:
client glx vendor string: Mesa Project and SGI
OpenGL core profile version string: 4.6 (Core Profile) Mesa 20.1.7 - kisak-mesa PPA
OpenGL version string: 4.6 (Compatibility Profile) Mesa 20.1.7 - kisak-mesa PPA
OpenGL ES profile version string: OpenGL ES 3.2 Mesa 20.1.7 - kisak-mesa PPA

AMDGPU OpenCL drivers doen't worked for me at all, in fact I don't recommend AMDGPU drivers for any use, games, 3D apps, etc.

...
Here is my: glxinfo output:
client glx vendor string: Mesa Project and SGI
OpenGL core profile version string: 4.6 (Core Profile) Mesa 20.1.7 - kisak-mesa PPA
OpenGL version string: 4.6 (Compatibility Profile) Mesa 20.1.7 - kisak-mesa PPA
OpenGL ES profile version string: OpenGL ES 3.2 Mesa 20.1.7 - kisak-mesa PPA
...

Again very interesting to see you have replaced the default Mesa stack with kisak-mesa PPA. This may indeed fix the AMDGPU propieraty OpenGL requirement for Davinci Resolve 16.1 & higher, still have to test/confirm that.

Did you also replace more default graphics/xorg or kernel related modules with other PPA's, because that may be the reason the default Ubuntu 20.04 amdgpu kernel driver did not work with the default AMDGPU 20.04 proprietary driver (OpenGL & OpenCL components)?

Did you also replace more default graphics/xorg or kernel related modules with other PPA's, because that may be the reason the default Ubuntu 20.04 amdgpu kernel driver did not work with the default AMDGPU 20.04 proprietary driver (OpenGL & OpenCL components)?

According to the Rocm installation website, I summarize the steps to install the opencl drivers:

Code: Select all

sudo apt update
sudo apt install libnuma-dev libncurses5
sudo reboot
wget -q -O - http://repo.radeon.com/rocm/rocm.gpg.key | sudo apt-key add -
echo 'deb [arch=amd64] http://repo.radeon.com/rocm/apt/debian/ xenial main' | sudo tee /etc/apt/sources.list.d/rocm.list
sudo apt update
sudo apt install rocm-dkms && sudo reboot
sudo usermod -a -G video $LOGNAME
sudo usermod -a -G render $LOGNAME
echo 'export PATH=$PATH:/opt/rocm/bin:/opt/rocm/profiler/bin:/opt/rocm/opencl/bin' | sudo tee -a /etc/profile.d/rocm.sh

For testing de correct rocm opencl installation type:

Code: Select all

rocminfo
clinfo

For Davinci Resolve 16.2.6 installation I used the original DaVinci_Resolve_Studio_16.2.6_Linux.run, thats it, no makeresolvedeb or whatethever

About kisak-mesa, I've installed this drivers to be able to play Steam games with the proton launcher (steamplay), for certain games it's needed, but I think that with the original mesa drivers that come in ubuntu 20.04, everything would work the same way.

Hello,
I posted a thread yesterday but maybe if I write here it makes more sense. I am migrating form Macbook Pro to a new PC for editing and I'm considering Linux.
I wonder if someone here can give some feedback on running DR on Linux for professional editing, if it's more or less the same of other OS or still lacking, because I've seen a lot have been changed since the start of this thread.
What distro would be better, considering I'm devoting this PC to video editing on DR?
If you also can provide a link to some installing tutorial or procedure it would be very appreciated as well.
I hope this was the right place to ask this questions, couldn't find a more specific thread, maybe DR/linux users are not so many, so many thanks to anyone can help or just give some info about it, cheers:)!

Hi,

if you want a dedicated Linux-PC for editing I'd consider using CentOS as provided by Blackmagic Design - installation is also available from Blackmagic Design. If instead you like to have a general purpose Linux Box then you might consider a more popular distribution like Ubuntu or Linux Mint. I am using Resolve Studio on Linux Mint and did not have any problems whatsoever. It also depends on your hardware - you should avoid AMD graphic cards and use Nvidia instead because Resolve is using CUDA and that's only available on Nvidia cards. If you don't have Nvidia you will rely on OpenCL which is way slower than CUDA.

Blackmagic Dsign also has a list of minimum system requirements on their web site.

It's all a matter of a good balance between hardware and software.

Hi,
pretty much what Dieter said

also, please do bear in mind that on Linux you have limitations on the supported codecs, especially audio codecs: you cannot import AAC and MP3 on both free and Studio, h26x export is available only on Studio with Nvidia GPUs.
Not a real problem since material can be easily transcoded to be ingested with ffmpeg and other free and open source tools easily available on Linux.

I will have an NVIDIA card, still building it... I guess that I will continue to use macbook for browsing and simple stuff and using the PC mainly for editing, though linux looks very beautiful to me. Now I find Centos a little intimidating and server oriented, so, since I see that there are Debian users, I will probably go there. Your experience with Mint is encouraging, thank you very much!

You're welcome
Have fun.

@Andreas56

You are sure Mesa OpenGL was also removed/setup functioning correctly when switching to/from AMDGPU Proprietary legacy OpenGL?

@Walter Sonius
Yes. I additionally tried a method recommended in the Arch Wiki to use specific drivers for a single application, so yeah, no Mesa for Resolve. Still the same error.

Hi All, I tried a few years ago and gave up, but now I really wanna try again so : I can install davinci resolve well on my machine via the makeresolve .deb , version 16.2.1 , starting is fine, then it wont find CUDA and will be running with open GL , and when loading video files, no matter what file format: I can see the thumbnail for a bit, then it greys out and it wont play any more.. any suggestions?

attached the log file and here the clinfo;

Code: Select all

clinfo
Number of platforms                               1
  Platform Name                                   NVIDIA CUDA
  Platform Vendor                                 NVIDIA Corporation
  Platform Version                                OpenCL 1.2 CUDA 10.2.185
  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 cl_khr_int64_base_atomics cl_khr_int64_extended_atomics
  Platform Extensions function suffix             NV

  Platform Name                                   NVIDIA CUDA
Number of devices                                 1
  Device Name                                     GeForce RTX 2070 with Max-Q Design
  Device Vendor                                   NVIDIA Corporation
  Device Vendor ID                                0x10de
  Device Version                                  OpenCL 1.2 CUDA
  Driver Version                                  440.100
  Device OpenCL C Version                         OpenCL C 1.2
  Device Type                                     GPU
  Device Topology (NV)                            PCI-E, 01:00.0
  Device Profile                                  FULL_PROFILE
  Device Available                                Yes
  Compiler Available                              Yes
  Linker Available                                Yes
  Max compute units                               36
  Max clock frequency                             1125MHz
  Compute Capability (NV)                         7.5
  Device Partition                                (core)
    Max number of sub-devices                     1
    Supported partition types                     None
    Supported affinity domains                    (n/a)
  Max work item dimensions                        3
  Max work item sizes                             1024x1024x64
  Max work group size                             1024
  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                              8370061312 (7.795GiB)
  Error Correction support                        No
  Max memory allocation                           2092515328 (1.949GiB)
  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                        1179648 (1.125MiB)
  Global Memory cache line size                   128 bytes
  Image support                                   Yes
    Max number of samplers per kernel             32
    Max size for 1D images from buffer            268435456 pixels
    Max 1D or 2D image array size                 2048 images
    Max 2D image size                             32768x32768 pixels
    Max 3D image size                             16384x16384x16384 pixels
    Max number of read image args                 256
    Max number of write image args                32
  Local memory type                               Local
  Local memory size                               49152 (48KiB)
  Registers per block (NV)                        65536
  Max number of constant args                     9
  Max constant buffer size                        65536 (64KiB)
  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                  3
  printf() buffer size                            1048576 (1024KiB)
  Built-in kernels                                (n/a)
  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 cl_khr_int64_base_atomics cl_khr_int64_extended_atomics

NULL platform behavior
  clGetPlatformInfo(NULL, CL_PLATFORM_NAME, ...)  NVIDIA CUDA
  clGetDeviceIDs(NULL, CL_DEVICE_TYPE_ALL, ...)   Success [NV]
  clCreateContext(NULL, ...) [default]            Success [NV]
  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)  Invalid device type for 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.11
  ICD loader Profile                              OpenCL 2.1


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


So it seems that Resolve (Studio) 16.2.7, when having been turned into a .deb archive with makeresolvedeb, no longer runs on Debian 10/stable with working CUDA because it requires a newer Nvidia driver.

Does anyone have experience with 16.2.7 under Debian testing (where newer Nvidia CUDA drivers are provided)?

So it seems that Resolve (Studio) 16.2.7, when having been turned into a .deb archive with makeresolvedeb, no longer runs on Debian 10/stable with working CUDA because it requires a newer Nvidia driver.

Does anyone have experience with 16.2.7 under Debian testing (where newer Nvidia CUDA drivers are provided)?

Yes, I have the same experience. 16.2.7 no longer runs on Debian 10 since the NVIDIA driver is too old. It does however work very well under Debian bullseye/sid that comes with NVIDIA driver 450.66.

first of all thanks for all the helpful info that is posted here!
I've read through this thread (and a couple more) which helped me in getting a better idea of my problem but unfortately not really coming to a solution. I succesfully installed Resolve 16.2.7 on a Debian 10 machine (Intel CPU, Nvidia GPU) via makeresolvedeb. I had installed the adequate Nvidia 450.66 driver beforehand via buster backports and it seemd to work fine (Nvidia X Server Settings App works and the card works fine in Blender as well).
I do have the GPU settings set to discrete in BIOS and run the system solely on the nvidia card (Quadro T2000).

When I try to run Resolve, it crashes, what seems to be due to missing OpenCL drivers.
Also clinfo command in terminal returns with: "0" which seems to be the issue..?

part of the Resolve log:

[0x7f48b001e400] | Main | INFO | 2020-10-14 22:12:09,682 | There is no OpenCL platform
[0x7f48b001e400] | Main | INFO | 2020-10-14 22:12:09,715 | Only 1 display GPU found. Using OpenCL for processing.
[0x7f48b001e400] | Main | INFO | 2020-10-14 22:12:09,715 | Not GLmap capable. GPUs: 0 discrete, 0 integrated, 0 external. Auto mapping, OpenCL processing, main display not on external GPU.

Interstingly, it seems to be able to "connect" to my gpu at a different stage:

[0x7f48b001e400] | Fairlight | INFO | 2020-10-14 22:12:11,825 | 00.00.00.969(000): Running Fairlight (r001014-43fe498b)
[0x7f48b001e400] | UI.GLContext | INFO | 2020-10-14 22:12:11,905 | Creating shared OpenGL context for this thread (2 total).
[0x7f48b001e400] | UI.GLContext | INFO | 2020-10-14 22:12:11,909 | Initialized OpenGL 4.6 (requested 2.0) on device 'NVIDIA Corporation Quadro T2000/PCIe/SSE2'
All textures are loaded : 1.
[0x7f48b001e400] | Fusion | INFO | 2020-10-14 22:12:12,064 | Fusion Build: r067722-ef6f045d_004 (Sep 15 2020 11:32:26)
[0x7f48b001e400] | Fusion | INFO | 2020-10-14 22:12:12,064 | fusionsystem: = "/opt/resolve/libs/Fusion/libfusionsystem.so"
[0x7f48b001e400] | Fusion | INFO | 2020-10-14 22:12:12,068 | FusionLibs: = "/opt/resolve/libs/Fusion/"
[0x7f48b001e400] | Fusion | INFO | 2020-10-14 22:12:12,068 | UserData: = "/home/user/.local/share/DaVinciResolve/Fusion"
[0x7f48b001e400] | Fusion | INFO | 2020-10-14 22:12:12,068 | Profiles: = "UserData:Profiles/"

dpkg -l | grep opencl returns:

user@user-pc:~$ dpkg -l | grep opencl
ii ocl-icd-libopencl1:amd64 2.2.12-2 amd64 Generic OpenCL ICD Loader
ii ocl-icd-opencl-dev:amd64 2.2.12-2 amd64 OpenCL development files
ii opencl-c-headers 2.2~2019.01.17-g49f07d3-1 all OpenCL (Open Computing Language) C header files

BM RAW Speed Test works flawlessly in accessing CUDA (and also shows that my system, although surely no high end machine, would -theoretically- be quite prepared to work from a performance point of view )

So while the nvidia installer seemed to have installed fine via Debian backports, it does not seem to have installed the necessary openCL libraries?

I was tempted to install nvidia-libopencl1 via synaptic but since this would automatically remove lots of my CUDA libraries i did not dare to do so (as I honestly still do not really understand why I need the OpenCL Framework if Resolve is anyway using CUDA? missing knowledge here..).

I would be grateful for any support or ideas. Thanks again to Daniel Tufvesson and others for providing easier access for this software on open source platforms and sharing their skills and knowledge with the lesser linux and command-line-experienced individuals like me.

first of all thanks for all the helpful info that is posted here!
I've read through this thread (and a couple more) which helped me in getting a better idea of my problem but unfortately not really coming to a solution. I succesfully installed Resolve 16.2.7 on a Debian 10 machine (Intel CPU, Nvidia GPU) via makeresolvedeb. I had installed the adequate Nvidia 450.66 driver beforehand via buster backports and it seemd to work fine (Nvidia X Server Settings App works and the card works fine in Blender as well).
I do have the GPU settings set to discrete in BIOS and run the system solely on the nvidia card (Quadro T2000).

When I try to run Resolve, it crashes, what seems to be due to missing OpenCL drivers.
Also clinfo command in terminal returns with: "0" which seems to be the issue..?

part of the Resolve log:

[0x7f48b001e400] | Main | INFO | 2020-10-14 22:12:09,682 | There is no OpenCL platform
[0x7f48b001e400] | Main | INFO | 2020-10-14 22:12:09,715 | Only 1 display GPU found. Using OpenCL for processing.
[0x7f48b001e400] | Main | INFO | 2020-10-14 22:12:09,715 | Not GLmap capable. GPUs: 0 discrete, 0 integrated, 0 external. Auto mapping, OpenCL processing, main display not on external GPU.

Interstingly, it seems to be able to "connect" to my gpu at a different stage:

[0x7f48b001e400] | Fairlight | INFO | 2020-10-14 22:12:11,825 | 00.00.00.969(000): Running Fairlight (r001014-43fe498b)
[0x7f48b001e400] | UI.GLContext | INFO | 2020-10-14 22:12:11,905 | Creating shared OpenGL context for this thread (2 total).
[0x7f48b001e400] | UI.GLContext | INFO | 2020-10-14 22:12:11,909 | Initialized OpenGL 4.6 (requested 2.0) on device 'NVIDIA Corporation Quadro T2000/PCIe/SSE2'
All textures are loaded : 1.
[0x7f48b001e400] | Fusion | INFO | 2020-10-14 22:12:12,064 | Fusion Build: r067722-ef6f045d_004 (Sep 15 2020 11:32:26)
[0x7f48b001e400] | Fusion | INFO | 2020-10-14 22:12:12,064 | fusionsystem: = "/opt/resolve/libs/Fusion/libfusionsystem.so"
[0x7f48b001e400] | Fusion | INFO | 2020-10-14 22:12:12,068 | FusionLibs: = "/opt/resolve/libs/Fusion/"
[0x7f48b001e400] | Fusion | INFO | 2020-10-14 22:12:12,068 | UserData: = "/home/user/.local/share/DaVinciResolve/Fusion"
[0x7f48b001e400] | Fusion | INFO | 2020-10-14 22:12:12,068 | Profiles: = "UserData:Profiles/"

dpkg -l | grep opencl returns:

user@user-pc:~$ dpkg -l | grep opencl
ii ocl-icd-libopencl1:amd64 2.2.12-2 amd64 Generic OpenCL ICD Loader
ii ocl-icd-opencl-dev:amd64 2.2.12-2 amd64 OpenCL development files
ii opencl-c-headers 2.2~2019.01.17-g49f07d3-1 all OpenCL (Open Computing Language) C header files

BM RAW Speed Test works flawlessly in accessing CUDA (and also shows that my system, although surely no high end machine, would -theoretically- be quite prepared to work from a performance point of view )

So while the nvidia installer seemed to have installed fine via Debian backports, it does not seem to have installed the necessary openCL libraries?

I was tempted to install nvidia-libopencl1 via synaptic but since this would automatically remove lots of my CUDA libraries i did not dare to do so (as I honestly still do not really understand why I need the OpenCL Framework if Resolve is anyway using CUDA? missing knowledge here..).

I would be grateful for any support or ideas. Thanks again to Daniel Tufvesson and others for providing easier access for this software on open source platforms and sharing their skills and knowledge with the lesser linux and command-line-experienced individuals like me.

Hi Richard, welcome to the forum!

If you hold down ctrl+, ("control" + "comma") when you start Resolve you should be able to reach the configuration menu. Look under "Memory and GPU" -> "GPU configuration". Can you see your GPU there? It looks like there is something wrong with the driver installation. In your case Resolve should be using CUDA and not even mention OpenCL in the log.

Screenshot_select-area_20201015164159.png (38 KiB) Viewed 259 times

Which version of libcuda do you have installed? This is how it looks in Debian 11 (should be relatively close to the Debian 10 backport)

Code: Select all

$ dpkg -l | grep libcuda
ii  libcuda1:amd64           450.66-1          amd64        NVIDIA CUDA Driver Library


Thanks Daniel! I am able to reach the settings screen even without ctrl+ after Resolve let me know it was unable to find OpenCL. I can then also choose GPU Config: CUDA -> manual -> Quadro T2000. But shortly after clicking Save the program crashes. Alternatively I could choose a Storage Folder and crashes directly after that without even accessing the GPU config.

The log file does not seem to give any further hints, but maybe I am missing something:
https://paste.debian.net/1167311/

dpkg -l | grep libcuda returns:

$ dpkg -l | grep libcuda
ii libcuda1:amd64 450.66-1~bpo10+1 amd64 NVIDIA CUDA Driver Library
ii libcuda1:i386 450.66-1~bpo10+1 i386 NVIDIA CUDA Driver Library
ii libcudart10.1:amd64 10.1.243-6~bpo10+1 amd64 NVIDIA CUDA Runtime Library

could it be that that the 2 driver libraries amd64 and:i386 conflict while starting Resolve?

So I managed to get Resolve 16.2.7 working on Debian 10. I'm not sure if documenting my way of resolving the issue will be much help to others as I have the impression the issues might have been related to my specific setup (Debian 10 stable with a newer kernel due to specific hardware driver necessities) but here we go:

As mentioned, I had installed the 450.66 nvidia driver via backports stable. The installation went well but for some reason did not install any OpenCL ICD Profile (which appears to be needed by resolve, even though it's really crunching the numbers later with CUDA). It did install the nvidia cuda toolkit and using the GPU with Blender was working fine.
Trying to install the OpenCL ICD afterwards was not possible as it conflicted with some of the CUDA libraries (of the same 450.66 driver version) which I did not dare to remove.

I purged the whole nvidia drivers and reinstalled v 455.60 again via backports. This time, funny enough, the install left out even more libraries, not installing any OpenCL ICD but also not installing the CUDA toolkit. So I was running an xserver on my GPU but none of my programs were able to access it. But contrary to the previous situation I now could install the OpenCL icd (nvidia-openCL-icd) without any package conflicts. For people using synaptic: you can choose to install the newer version from backports via: Package -> Force Version. After doing this, Resolve started flawlessly.

I did some test renders and everything incl. GPU Scopes looks good so far. While I like to have a professional feature set, my NLE work is generally directed towards classic AB editing. So I am seldom in need of the more complex functionalities or very demanding grades, therefore can't tell you, if each and every function is working as good as it should.
If anybody wants me to test out something on the system I'd be happy to do it, just let me know (keep in mind at the moment I am not running the studio version).

Thanks to Daniel and others for sharing their thoughts and ideas on the issue!

so, returing back with a little update.
I've upgraded to the studio version for the convience of directly importing the occasional h.264 file among other things.
The system is running smooth so far, but there are two issues I've come across and would be interested if this happened to anybody else using the studio version on Linux:

Issue Nr.1: I do not find any h.264 export options on the deliver page. this seems weird as I can import h.264 just fine now and, judging from da vincis codec pdf lists, was under the impression I should be able to also export to h.264 with the studio version on Linux, right?
Also, using the Quick Export Option, Resolve puts loads of dpx files (1 per frame) into specified the output folder instead of a h.264 file.
The ffmpeg codecs are for sure on my system but I suppose Resolve should be using its proprietary codecs anyway?

Issue Nr.2: I am unable to export files with an alpha channel. Alpha output is set and the node is connected. Nevermind Cineform or DNxHR, both with "Individual Clips" and "Export Alpha" selected, Resolve always renders out the file with a black background.

Anybody with any ideas on this?

I should be able to also export to h.264 with the studio version on Linux, right?

Can be done, with certain Nvidia GPUs (NVENC for encoding).

Your Quadro T2000 (laptop GPU?) is a bit skimpy for Resolve. You may also experience weird glitches like the alpha channel export, sorry to say.

Thanks Sulo for your input. I was afraid that it had to do with GPU compatibility but was unable to find an actual list of compatible cards. Still not sure if that's really the only reason as the T2000, while it surely is not a power house, does actually support NVENC de- and encoding. And I thought 4GB memory, while certainly not being a lot by today's standards, should suffice for encoding these formats.
but yeah, maybe it's really still just a compatibility issue.

Alpha export works now btw leaving this -so far- the only issue as everything else works quite smoothly (surprisingly even without using proxies or optimized media yet...)

Sorry, forgot to add.

Here's Rohit from BMD.

The GPU also needs more than 3.5GB of VRAM to do HW accelerated encode... This is a Resolve imposed restriction. If we use up too much VRAM for h265 encoding, then you will have problems with Resolve processing.

Easy way out would be to export as DNx and use Handbrake for h264/5 encoding.

thanks for the heads up!
yes, i do usually use Handbrake or my very limited bash knowledge for ffmpeg transcoding and since I am not in a position where I have to transcode/deliver lots of material every day, this little extra step is not really a big issue.
and just to share it: apart from handbrake there's a also new open source ffmpeg gui frontend in development right now from rainbox laboratories called "DuME" which is currently in alpha still but is working fine on my machine for different transcoding tasks (but has no batch functionality yet).

after a little more research I found the problem: the NVENC library (libnvidia-encode1) was not installed. It simply failed to install during regular driver setup (see issues above..). Installed it now manually and h264 and h265 options are now showing and, judging from a quick test, seem to be working well.