Blackmagic Forum


https://forum.blackmagicdesign.com/

Unsupported GPU Processing Mode-Linux

https://forum.blackmagicdesign.com/viewtopic.php?f=21&t=178508

Page 1 of 1

Unsupported GPU Processing Mode-Linux

PostPosted: Thu Mar 30, 2023 9:33 pm
by PhoenixRose
When I attempt to open DaVinci Resolve 18 I get an Unsupported GPU Processing Mode message. Next when I attempt to update the configuration DaVinci does not show any GPU for my computer. I am running Linux Mint 21 on a newly purchased Vipr Tech gaming computer. Am I correct in assuming that I need to update my GPU driver in order for DaVinci Resolve to work? If so which driver? Will it work with the Linux OS I have on my computer? Attached is a jpg image of my computer specs.
Vipr Belarc specs-1st pg.jpg
Vipr Belarc specs-1st pg.jpg (157.74 KiB) Viewed 66017 times


Thank you for your assistance.

Re: Unsupported GPU Processing Mode-Linux

PostPosted: Fri Mar 31, 2023 7:41 am
by Peter Chamberlain
What is the exact model of the GPU in that system?

Re: Unsupported GPU Processing Mode-Linux

PostPosted: Fri Mar 31, 2023 10:53 am
by Gordonjcp
It doesn't say exactly what GPU you have, but you will need one that is supported by the amdgpu-pro binary drivers rather than the amdgpu open-source ones. You'll also need to make sure you have the correct opencl libraries installed.

It's a lot less hassle to use NVidia.

Re: Unsupported GPU Processing Mode-Linux

PostPosted: Sun Apr 02, 2023 4:14 am
by ZRGARDNE
Open the side panel and make sure you actually have a GPU.

That screenshot looks like you only have integrate graphics, which is not supported by Resolve in Linux.

Re: Unsupported GPU Processing Mode-Linux

PostPosted: Wed Apr 05, 2023 4:35 pm
by PhoenixRose
My GPU is a Gigabyte AB350M-Gaming 3 and my Processor is an AMD Ryzen 5 5600G with Raedon Graphics.

Re: Unsupported GPU Processing Mode-Linux

PostPosted: Wed Apr 05, 2023 11:06 pm
by Dwaine Maggart
That's not the GPU, that's your motherboard model number.

It looks like you don't have an NVIDIA or AMD GPU then, and that means Resolve is not going to work on that system as it sits.

The good news is, you can add an NVIDIA or AMD GPU to that motherboard, and then it could work.

If you want to pursue that, an NVIDIA GPU is generally easier to configure for Resolve on a Linux system, than an AMD GPU.

Re: Unsupported GPU Processing Mode-Linux

PostPosted: Wed Jul 19, 2023 3:07 pm
by settermjd
I have the same issue after just now upgrading from DaVinci Resolve Studio 17 to 18.1.4. I'm running Ubuntu 23.04 with a NVIDIA GeForce RTX™ 2060 GPU. There is no option to choose a GPU in the UI.

Re: Unsupported GPU Processing Mode-Linux

PostPosted: Wed Jul 19, 2023 4:34 pm
by Dwaine Maggart
In the Applications menu, you should see an app called DaVinci Resolve Capture Logs. It will have a gear icon. Run that and provide the file it creates on your desktop.

Re: Unsupported GPU Processing Mode-Linux

PostPosted: Wed Aug 02, 2023 7:23 pm
by rjarauta
Good afternoon all:
I am trying to test Davinci Resolve Software on my Ubuntu 22.04.2 LTS

I am using an ASUS:
ASUSTeK COMPUTER INC. Zenbook UP6502ZD_Q539ZD
Processor:
12th Gen Intel® Core™ i7-12700H × 20
Graphics:
Mesa Intel® Graphics (ADL GT2)

I followed all installations steps, upgraded libraries and still having the same issue since I installed the software.
The message is showing Unsupported GPU Processing Mode.

Reading some POSTS here is saying that I have to open Davinci Resolve Capture Logs. I can see the application in my aaplications but is not open it.
Also, once I open the software Davinci Resolve the window showing the message Unsupported GPU Processing Mode has 2 buttons. One says quit and the other button says update configuration.
Once I open update configuration inside Memory and GPU Configuration is not showing any GPU.

I will appreciate any assistance on this matter.

Thank you, Rafael.

Re: Unsupported GPU Processing Mode-Linux

PostPosted: Thu Aug 03, 2023 2:53 am
by ZRGARDNE
rjarauta wrote:Good afternoon all:
I am trying to test Davinci Resolve Software on my Ubuntu 22.04.2 LTS

Graphics:
Mesa Intel® Graphics (ADL GT2)




This is an integrated GPU. Resolve on Linux requires a discrete GPU.

Buy a different laptop or run windows.

Re: Unsupported GPU Processing Mode-Linux

PostPosted: Thu Aug 03, 2023 5:14 pm
by rjarauta
Thank you for your prompt answer.

Re: Unsupported GPU Processing Mode-Linux

PostPosted: Thu Oct 05, 2023 12:09 am
by mshirey
I've run into similar issue. This is a desktop machine running up to date Manjaro using an NVidia GeForce 3090 Ti video card. Using current, and update to date, 6.1 kernel and nvidia driver v.535.113.01

When Resolve starts I run into the "Unsupported GPU Processing Mode" error. I select "Update Configuration", but under "Memory and GPU" it doesn't seem to see my video card. This is the only video card in the system, and the nVidia drivers are the only video drivers installed.

Any help would be appreciated.

Thank you,

-- Matthew

Here's the info from the bottom of the output.txt file from your own Capture Logs application:
==
************************************NVidia Graphics Card Info***********************************
NVRM version: NVIDIA UNIX x86_64 Kernel Module 535.113.01 Tue Sep 12 19:41:24 UTC 2023
GCC version: gcc version 13.2.1 20230801 (GCC)
Model: NVIDIA GeForce RTX 3090 Ti
IRQ: 238
GPU UUID: GPU-bf9f224f-af2a-e02f-8644-4c6e1c53f9f0
Video BIOS: 94.02.a0.00.36
Bus Type: PCIe
DMA Size: 47 bits
DMA Mask: 0x7fffffffffff
Bus Location: 0000:01:00.0
Device Minor: 0
GPU Excluded: No
==

Re: Unsupported GPU Processing Mode-Linux

PostPosted: Thu Oct 05, 2023 6:00 pm
by Dwaine Maggart
In the Applications menu, you should see an app called DaVinci Resolve Capture Logs. It will have a gear icon. Run that and provide the file it creates on your desktop.

Re: Unsupported GPU Processing Mode-Linux

PostPosted: Sun Oct 08, 2023 2:59 pm
by canezila
Hi. I am in the same boat as others. I had resolve working on this computer for years when running Ubuntu Studio 20.04 and 22.04. I am now running MXLinux MX21. I think it only sees device 1 (intel) and not device 2(nvidia).

************************************NVidia Graphics Card Info***********************************
NVRM version: NVIDIA UNIX x86_64 Kernel Module 525.125.06 Tue May 30 05:11:37 UTC 2023
GCC version: gcc version 10.2.1 20210110 (Debian 10.2.1-6)
Model: NVIDIA GeForce RTX 2070 Super with Max-Q Design
IRQ: 197
GPU UUID: GPU-3dc39cad-fb79-8830-6777-41d97cf12e34
Video BIOS: 90.04.96.00.6a
Bus Type: PCIe
DMA Size: 47 bits
DMA Mask: 0x7fffffffffff
Bus Location: 0000:01:00.0
Device Minor: 0
GPU Excluded: No

***DONE***

But the resolve 18.6 studio doesn't show anything at all to select. No CUDA and no OPEN_GL.

Within the attachment, I have added my sysinfo. Hope it helps.

Re: Unsupported GPU Processing Mode-Linux

PostPosted: Sun Oct 08, 2023 8:03 pm
by smunaut
@canezila You're on a laptop right ? Did you run with prime-run or whatever equivalent to make sure the dGPU is used ?

Re: Unsupported GPU Processing Mode-Linux

PostPosted: Sun Oct 08, 2023 9:54 pm
by canezila
smunaut wrote:@canezila You're on a laptop right ? Did you run with prime-run or whatever equivalent to make sure the dGPU is used ?


Hi. Yes, it is a laptop. and No, That is exactly what I need to find. I am missing that. I had that option before and I need to find out how to select that.

Re: Unsupported GPU Processing Mode-Linux

PostPosted: Sun Oct 08, 2023 10:25 pm
by canezila
smunaut wrote:@canezila You're on a laptop right ? Did you run with prime-run or whatever equivalent to make sure the dGPU is used ?


I went to here: https://wiki.debian.org/NVIDIA%20Optimu ... rimary_GPU
and followed the steps. Thought that was it but not there yet.

Re: Unsupported GPU Processing Mode-Linux

PostPosted: Sun Oct 08, 2023 10:56 pm
by canezila
smunaut wrote:@canezila You're on a laptop right ? Did you run with prime-run or whatever equivalent to make sure the dGPU is used ?


[Solved]!!!!!
I did the steps in: https://www.danieltufvesson.com/makeresolvedeb

Might have been some or all of the steps within. Glorious!

Re: Unsupported GPU Processing Mode-Linux

PostPosted: Sun Oct 15, 2023 6:39 am
by tegaidogun
I am getting the same issue as the others, my system specifications are:

```
02:37 ~ inxi -F
System:
Host: CHIBUDOM Kernel: 6.5.6-300.fc39.x86_64 arch: x86_64 bits: 64
Desktop: GNOME v: 45.0 Distro: Fedora release 39 (Thirty Nine)
Machine:
Type: Laptop System: LENOVO product: 82K2 v: IdeaPad Gaming 3 15ACH6
serial: <superuser required>
Mobo: LENOVO model: LNVNB161216 v: SDK0T76465 WIN
serial: <superuser required> UEFI: LENOVO v: H3CN36WW(V2.06)
date: 09/30/2022
Battery:
ID-1: BAT1 charge: 38.7 Wh (100.0%) condition: 38.7/45.0 Wh (85.9%)
CPU:
Info: 6-core model: AMD Ryzen 5 5600H with Radeon Graphics bits: 64
type: MT MCP cache: L2: 3 MiB
Speed (MHz): avg: 2249 min/max: 400/4280 cores: 1: 400 2: 3283 3: 400
4: 400 5: 3802 6: 3268 7: 400 8: 3621 9: 3629 10: 4118 11: 3270 12: 400
Graphics:
Device-1: NVIDIA GA107M [GeForce RTX 3050 Ti Mobile] driver: nvidia
v: 535.113.01
Device-2: AMD Cezanne [Radeon Vega Series / Radeon Mobile Series]
driver: amdgpu v: kernel
Device-3: Bison Integrated Camera driver: uvcvideo type: USB
Display: wayland server: X.Org v: 23.2.1 with: Xwayland v: 23.2.1
compositor: gnome-shell driver: X: loaded: amdgpu,nvidia
unloaded: fbdev,modesetting,nouveau,vesa dri: radeonsi gpu: amdgpu
resolution: 1920x1080~120Hz
API: OpenGL v: 4.6 Mesa 23.2.1 renderer: AMD Radeon Graphics (renoir LLVM
16.0.6 DRM 3.54 6.5.6-300.fc39.x86_64)
Audio:
Device-1: AMD Renoir Radeon High Definition Audio driver: snd_hda_intel
Device-2: AMD ACP/ACP3X/ACP6x Audio Coprocessor driver: N/A
Device-3: AMD Family 17h/19h HD Audio driver: snd_hda_intel
API: ALSA v: k6.5.6-300.fc39.x86_64 status: kernel-api
Server-1: PipeWire v: 0.3.80 status: active
Network:
Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
driver: r8169
IF: enp2s0 state: down mac: 7c:8a:e1:98:71:14
Device-2: Intel Wi-Fi 6 AX210/AX211/AX411 160MHz driver: iwlwifi
IF: wlo1 state: up mac: 2c:0d:a7:1d:ff:dd
Bluetooth:
Device-1: Intel AX210 Bluetooth driver: btusb type: USB
Report: btmgmt ID: hci0 state: up address: 2C:0D:A7:1D:FF:E1 bt-v: 5.3
Drives:
Local Storage: total: 2.32 TiB used: 86.2 GiB (3.6%)
ID-1: /dev/nvme0n1 vendor: Western Digital model: WDS500G2B0C
size: 465.76 GiB
ID-2: /dev/nvme1n1 model: JAJP600M1TB size: 953.87 GiB
ID-3: /dev/sda model: SSD 1TB size: 953.87 GiB
Partition:
ID-1: / size: 920.37 GiB used: 85.83 GiB (9.3%) fs: btrfs
dev: /dev/nvme1n1p4
ID-2: /boot size: 973.4 MiB used: 352.4 MiB (36.2%) fs: ext4
dev: /dev/nvme1n1p1
ID-3: /boot/efi size: 511 MiB used: 17.4 MiB (3.4%) fs: vfat
dev: /dev/nvme1n1p2
Swap:
ID-1: swap-1 type: partition size: 32 GiB used: 0 KiB (0.0%)
dev: /dev/nvme1n1p3
ID-2: swap-2 type: zram size: 8 GiB used: 256 KiB (0.0%) dev: /dev/zram0
Sensors:
System Temperatures: cpu: 53.5 C mobo: N/A gpu: amdgpu temp: 45.0 C
Fan Speeds (rpm): N/A
Info:
Processes: 398 Uptime: 47m Memory: total: 16 GiB note: est.
available: 13.24 GiB used: 3.56 GiB (26.9%) Shell: fish inxi: 3.3.29
02:37 ~
```

I seem to getting issues saying that there is Unsupported GPU Processing Mode, but both GPUs seem fairly responsive.

Re: Unsupported GPU Processing Mode-Linux

PostPosted: Sun Oct 15, 2023 6:52 am
by tegaidogun
This is also my log file:

Re: Unsupported GPU Processing Mode-Linux

PostPosted: Tue Oct 17, 2023 5:24 pm
by Dwaine Maggart
@Oghenetega:

On 10-15 at 02:02, the oldest Resolve log shows this:

0x7f792ca13000 | GPUDetect | INFO | 2023-10-15 02:02:20,388 | Detected System:
0x7f792ca13000 | GPUDetect | INFO | 2023-10-15 02:02:20,388 | - OS: Linux Fedora release 39 (Thirty Nine)
0x7f792ca13000 | GPUDetect | INFO | 2023-10-15 02:02:20,388 | - Model: LENOVO LNVNB161216
0x7f792ca13000 | GPUDetect | INFO | 2023-10-15 02:02:20,388 | - System ID: 70b3300c01954a3dbf3ca302c68b6078
0x7f792ca13000 | GPUDetect | INFO | 2023-10-15 02:02:20,388 | - CPU: AMD Ryzen 5 5600H with Radeon Graphics, 12 threads, x86-64
0x7f792ca13000 | GPUDetect | INFO | 2023-10-15 02:02:20,388 | - RAM: 3.5 GiB used of 13.2 GiB
0x7f792ca13000 | GPUDetect | INFO | 2023-10-15 02:02:20,388 | Detected 1 GPUs:
0x7f792ca13000 | GPUDetect | INFO | 2023-10-15 02:02:20,388 | - "NVIDIA GeForce RTX 3050 Ti Laptop GPU" (gpu:2a4a2bbc.f91e8f0c) <- Main Display GPU
0x7f792ca13000 | GPUDetect | INFO | 2023-10-15 02:02:20,388 | Discrete, 3.8 GiB VRAM, PCI:1:0.0
0x7f792ca13000 | GPUDetect | INFO | 2023-10-15 02:02:20,388 | Matches: CUDA, NVML, OpenCL, XOrg
0x7f792ca13000 | GPUDetect | INFO | 2023-10-15 02:02:20,388 | Detected 1 monitors:
0x7f792ca13000 | Main.GPUConfig | INFO | 2023-10-15 02:02:20,388 | Compute API set to automatic, defaulting to CUDA.
0x7f792ca13000 | Main.GPUConfig | INFO | 2023-10-15 02:02:20,388 | Selected compute API: CUDA
0x7f792ca13000 | Main.GPUConfig | INFO | 2023-10-15 02:02:20,388 | Automatic GPU Selection:
0x7f792ca13000 | Main.GPUConfig | INFO | 2023-10-15 02:02:20,388 | - "NVIDIA GeForce RTX 3050 Ti Laptop GPU" (gpu:2a4a2bbc.f91e8f0c)

So at that time it was properly detecting the OS and the GPU. But something on the system changed shortly after that time, and the OS and GPU were no longer detected in all the subsequent logs.

Any idea what you might have changed on the system between 02:02 and 02:09?

Re: Unsupported GPU Processing Mode-Linux

PostPosted: Tue Oct 17, 2023 11:50 pm
by JamesMaynardGelinas
I'm seeing this too. We're all running unsupported OS revisions here. I've got an ancient Ubutu 20.04 I keep running because it and Resolve 17.2 keep working and later versions don't.

I'm running a VEGA card, so that explains a whole lot. But I also have an NVIDIA RTX 3060 running headless and I'd hoped Resolve 18.6 could use that for compute and the VEGA card just to display. That has not worked out well at all. So I'm back to 17.2 which does actually work.

Kindof considering running the supported CENTOS release in a virtual container and passing through the RTX card. Could even run Windows there, I guess.

Resolve is now a must have for clients so I'm considering such radical options as Windows. lol

Re: Unsupported GPU Processing Mode-Linux

PostPosted: Sat Dec 23, 2023 10:35 am
by KheshedCini
So after running into the issue with libpango, and having to get rid of a bunch of the shipped libraries:
Code: Select all
libgio-2.0.so* libglib-2.0.so* libgmodule-2.0.so* libgobject-2.0.so*

... I ended up with the same "Unsupported GPU Processing Mode" -dialog, and the settings not showing any options. I have a perfectly fine Nvidia GPU that I know to work with Davinci Resolve, so looked more like a software side issue again.

Turns out as typical, software on Linux is really bad at explaining what is wrong. I had to install "opencl-nvidia" package from my package manager. If you're not using Arch, it's possibly called something else but likely with a combination of "opencl" and "nvidia" in the name.

Re: Unsupported GPU Processing Mode-Linux

PostPosted: Wed Jun 26, 2024 7:41 pm
by kirenpillay
For my AMD RX 5700, I installed rocm-opencl-runtime, and it worked.

Re: Unsupported GPU Processing Mode-Linux

PostPosted: Tue Jul 09, 2024 10:22 am
by Der-Vinci
Hello,
I also have exactly this problem.

I'm using debian 12 stable and the debian nvidia drivers.
They are active, they work, nvidia-smi confirms they are used.

DR installation works as in the instruction - like a charm
Unfortunately at startup I get the GPUDetect error.

Xeon 2697
GTX 1080 8GB
64GB ECC
nvidia drivers: 535.183.01

0x7f6ac02c7000 | Main | INFO | 2024-07-09 09:25:40,513 | Running DaVinci Resolve v19.0.0b.0043 (Linux/Clang x86_64)
0x7f6ac02c7000 | Main | INFO | 2024-07-09 09:25:40,513 | BMD_BUILD_UUID edb39019-4fd4-4111-953b-43bb3de7affe
0x7f6ac02c7000 | Main | INFO | 2024-07-09 09:25:40,513 | BMD_GIT_COMMIT 9351379ebdb063a0345a3ec168cd162aa09e0c3e
0x7f6ac02c7000 | GPUDetect | INFO | 2024-07-09 09:25:40,514 | Starting GPUDetect 1.2_5-a6
0x7f6ac02c7000 | GPUDetect | ERROR | 2024-07-09 09:25:40,555 | No matched GPUs found.
0x7f6ac02c7000 | Main.GPUConfig | INFO | 2024-07-09 09:25:40,555 | Compute API set to automatic, defaulting to Unknown.
0x7f6ac02c7000 | Main.GPUConfig | INFO | 2024-07-09 09:25:40,555 | Unsupported API Unknown, defaulting to Unknown.
0x7f6ac02c7000 | Main.GPUConfig | ERROR | 2024-07-09 09:25:40,555 | Failed to select a valid compute API.
0x7f6ac02c7000 | Main.GPUConfig | INFO | 2024-07-09 09:25:40,555 | Automatic GPU Selection:
0x7f6ac02c7000 | Main.GPUConfig | ERROR | 2024-07-09 09:25:40,555 | No GPUs selected!
0x7f6ac02c7000 | IO | INFO | 2024-07-09 09:25:40,555 | RED InitializeSdk with library path at /opt/resolve/libs
0x7f6ac02c7000 | IO | INFO | 2024-07-09 09:25:40,594 | R3DAPI 8.5.1-53601 (20240308 Lx64S) R3DSDK 8.5.1-53601 (20240308 Lx64D C3B1) [/opt/resolve/libs/] init is successful
0x7f6ac02c7000 | Main | INFO | 2024-07-09 09:25:40,594 | 0 RED rocket cards available
libDeckLinkAPI.so: cannot open shared object file: No such file or directory
0x7f6ac02c7000 | Main | INFO | 2024-07-09 09:25:40,594 | Decklink model name: '', version: ''
0x7f6ac02c7000 | DVIP | INFO | 2024-07-09 09:25:40,594 | DVIP release/19.0 build 90 (1131135699e00a4ce955a12182d2e8aea368f93c). Release, version 19.0.0.
0x7f6a75290000 | IO | INFO | 2024-07-09 09:25:40,595 | Using DNxHR library v2.7.5.873r
0x7f6a73ef6000 | SyManager | ERROR | 2024-07-09 09:25:40,793 | GetProjectLibraries() - Access token is empty
0x7f6a75a91000 | Fusion | INFO | 2024-07-09 09:25:40,972 | Fusion Build: 8f0c7a58_0039 (Jun 25 2024 10:10:40)
0x7f6a4fbf0000 | Fusion | INFO | 2024-07-09 09:25:40,976 | fusionsystem: = "/opt/resolve/libs/Fusion/libfusionsystem.so"
0x7f6a4fbf0000 | Fusion | INFO | 2024-07-09 09:25:40,980 | FusionLibs: = "/opt/resolve/libs/Fusion/"
0x7f6a4fbf0000 | Fusion | INFO | 2024-07-09 09:25:40,980 | UserData: = "/home/micro/.local/share/DaVinciResolve/Fusion"
0x7f6a4fbf0000 | Fusion | INFO | 2024-07-09 09:25:40,980 | Profiles: = "UserData:Profiles/"
0x7f6ac02c7000 | UI | INFO | 2024-07-09 09:25:40,993 | UI language is set to "en".
0x7f6a43a5c000 | DbCommon2 | INFO | 2024-07-09 09:25:40,994 | Loading dblist file: /home/micro/.local/share/DaVinciResolve/configs/.dblist
0x7f6ac02c7000 | Main | INFO | 2024-07-09 09:25:41,043 | Finished loading Application style sheet
0x7f6ac02c7000 | Main | INFO | 2024-07-09 09:25:41,056 | Show splash screen
0x7f6ac02c7000 | Main | INFO | 2024-07-09 09:25:41,056 | Show splash screen message: Starting Up
0x7f6a75290000 | IO | INFO | 2024-07-09 09:25:41,112 | NVDEC is using upto (1014) MB
0x7f6a75290000 | IO | INFO | 2024-07-09 09:25:41,130 | NVDEC decodes VP9, chroma 4:2:0, bitdepth 8, upto 8192 x 8192
0x7f6a75290000 | IO | INFO | 2024-07-09 09:25:41,137 | Nvidia GPU (0) is initialised as decoding and encoding device.
0x7f6a75290000 | IO | INFO | 2024-07-09 09:25:41,137 | IO codec library load completed in 542 ms.
0x7f6ac02c7000 | UI.GLContext | INFO | 2024-07-09 09:25:41,231 | Creating shared OpenGL context for this thread (1 total).
0x7f6ac02c7000 | UI.GLContext | INFO | 2024-07-09 09:25:41,236 | Initialized OpenGL 4.5 (requested 4.5) on device 'NVIDIA Corporation NVIDIA GeForce GTX 1080/PCIe/SSE2'
0x7f6ac02c7000 | BtCommon | INFO | 2024-07-09 09:25:41,241 | Memory config: reserved=12040M pinned=0M log=0
0x7f6ac02c7000 | BtCommon | INFO | 2024-07-09 09:25:41,241 | Using default pooled memory manager
0x7f6a2b7fd000 | LeManager | INFO | 2024-07-09 09:25:41,241 | 521, 29
0x7f6a2affc000 | BtCommon | INFO | 2024-07-09 09:25:41,241 | BtResourceManager Process Thread Started
0x7f6ac02c7000 | IO | INFO | 2024-07-09 09:25:41,245 | Setting codec capacity (0)
0x7f6ac02c7000 | SyManager | INFO | 2024-07-09 09:25:41,246 | Total: 20, NumDtThreads: 8, NumComms: 0, NumSites: 1

0x7f6ac02c7000 | SyManager | INFO | 2024-07-09 09:25:41,246 | Lookaheads -> playback = 20, record = 20, stop = 1

Sy High Command Handler Thread ----- (140093926895616)
SY high priority cmd handler thread starts: 28BF7000
Sy Low Command Handler Thread ----- (140093918502912)
SY low priority cmd handler thread starts: 283F6000
Sy Data Handler Thread ----- (140093910110208)
SY data handler thread starts: 27BF5000
Gs High Command Handler Thread ----- (140093893324800)
GS high priority cmd handler thread starts: 26BF3000
Gs Low Command Handler Thread ----- (140093884932096)
GS low priority cmd handler thread starts: 263F2000
0x7f6a25bf1000 | GsManager | INFO | 2024-07-09 09:25:41,247 | Gs Processor Thread ----- (140093876539392)

GS processor thread starts: 25BF1000
Dp High Command Handler Thread ----- (140093868146688)
DP high priority cmd handler thread starts: 253F0000
Dp Low Command Handler Thread ----- (140093859753984)
DP low priority cmd handler thread starts: 24BEF000
Dt High Command Handler Thread ----- (140093851361280)
DT high priority cmd handler thhread starts: 243EE000
0x7f6ac02c7000 | DtManager | INFO | 2024-07-09 09:25:41,247 | Using 8 generic IO threads
0x7f6ac02c7000 | DtManager | INFO | 2024-07-09 09:25:41,247 | Total of 16 IO threads (including 8 generic and 8 Red decode threads)
Dt Low Command Handler Thread ----- (140093842968576)
DT low priority cmd handler thread starts: 23BED000
0x7f6a223eb000 | DtManager | INFO | 2024-07-09 09:25:41,249 | Dt Worker Thread Started
0x7f6a233ec000 | DtManager | INFO | 2024-07-09 09:25:41,249 | Dt Data Handler Thread Started
DT data handler thread starts: 233EC000
0x7f6a213ea000 | DtManager | INFO | 2024-07-09 09:25:41,249 | Dt Worker Thread Started
0x7f6a1ffe9000 | DtManager | INFO | 2024-07-09 09:25:41,249 | Dt Worker Thread Started
0x7f6a1f7e8000 | DtManager | INFO | 2024-07-09 09:25:41,249 | Dt Worker Thread Started
0x7f6a1efe7000 | DtManager | INFO | 2024-07-09 09:25:41,249 | Dt Worker Thread Started
0x7f6a1e7e6000 | DtManager | INFO | 2024-07-09 09:25:41,249 | Dt Worker Thread Started
0x7f6a1dfe5000 | DtManager | INFO | 2024-07-09 09:25:41,249 | Dt Worker Thread Started
0x7f6a1d7e4000 | DtManager | INFO | 2024-07-09 09:25:41,250 | Dt Worker Thread Started
0x7f6a1cfe3000 | DtManager | INFO | 2024-07-09 09:25:41,250 | Dt Worker Thread Started
0x7f6a1c7e2000 | DtManager | INFO | 2024-07-09 09:25:41,250 | Dt Worker Thread Started
0x7f6a1bfe1000 | DtManager | INFO | 2024-07-09 09:25:41,250 | Dt Worker Thread Started
0x7f6a1b7e0000 | DtManager | INFO | 2024-07-09 09:25:41,250 | Dt Worker Thread Started
0x7f6a1afdf000 | DtManager | INFO | 2024-07-09 09:25:41,250 | Dt Worker Thread Started
0x7f6a1a7de000 | DtManager | INFO | 2024-07-09 09:25:41,250 | Dt Worker Thread Started
0x7f6a19fdd000 | DtManager | INFO | 2024-07-09 09:25:41,250 | Dt Worker Thread Started
0x7f6a197dc000 | DtManager | INFO | 2024-07-09 09:25:41,250 | Dt Worker Thread Started
0x7f6a18ce6000 | DtManager | INFO | 2024-07-09 09:25:41,250 | Dt Worker Thread Started
0x7f6a184e5000 | DtManager | INFO | 2024-07-09 09:25:41,251 | Dt Worker Thread Started
Ls High Command Handler Thread ----- (140093642653696)
Ls Low Command Handler Thread ----- (140093634260992)
LS low priority cmd handler thread starts: 174E3000
Ls Data Handler Thread ----- (140093625868288)
LS data handler thread starts: 16CE2000
Ls High Command Handler Thread ----- (140093617475584)
Ls Low Command Handler Thread ----- (140093609082880)
LS low priority cmd handler thread starts: 15CE0000
Ls Data Handler Thread ----- (140093600690176)
LS data handler thread starts: 154DF000
Ls High Command Handler Thread ----- (140093592297472)
Ls Low Command Handler Thread ----- (140093583904768)
LS low priority cmd handler thread starts: 144DD000
Ls Data Handler Thread ----- (140093575512064)
Mem Data Transmitter Thread ----- (140093567119360)
Mem data transmitter thread starts: 134DB000
0x7f6ac02c7000 | Main | INFO | 2024-07-09 09:25:41,252 | Show splash screen message: Loading Project Libraries
sh: 1: python2: not found
0x7f6a13cdc000 | GPU.MultiBoardMgr | ERROR | 2024-07-09 09:25:41,254 | Fatal error: "Unsupported GPU Processing Mode", "Please review the GPU drivers and GPU configuration under preferences."
Urgent message: CRITICAL_PREF: Unsupported GPU Processing Mode||Please review the GPU drivers and GPU configuration under preferences.
0x7f6a13cdc000 | IP | ERROR | 2024-07-09 09:25:41,254 | Failed to initialize multi board manager
LS data handler thread starts: 13CDC000
0x7f6ac02c7000 | Main | INFO | 2024-07-09 09:25:41,287 | Show splash screen message: Initializing system components
0x7f6ac02c7000 | Main | INFO | 2024-07-09 09:25:41,288 | Show splash screen message: Loading video codecs
0x7f6a75290000 | IO | INFO | 2024-07-09 09:25:41,291 | IO codec initialization completed in 0 ms.
0x7f6ac02c7000 | Main | INFO | 2024-07-09 09:25:41,291 | Show splash screen message: Loading video plugins
0x7f6ac02c7000 | Main | INFO | 2024-07-09 09:25:41,292 | Show splash screen message: Loading Fairlight Engine
Unable to read VR Path Registry from /home/micro/.config/openvr/openvrpaths.vrpath
0x7f6a10784000 | Fusion | INFO | 2024-07-09 09:25:42,676 | 276 templates scanned in 0.28 secs
0x7f6ac02c7000 | Fairlight | INFO | 2024-07-09 09:25:43,146 | 00.00.01.715(001): Running Fairlight (820be8101871b447914f485065a99946b6a0ec8b)
0x7f6ac02c7000 | FairlightLoader | INFO | 2024-07-09 09:25:43,146 | Fairlight lib initialized in 1853 ms.
0x7f6a75a91000 | UI.GLContext | INFO | 2024-07-09 09:25:43,147 | Creating shared OpenGL context for this thread (2 total).
0x7f6a75a91000 | UI.GLIO | ERROR | 2024-07-09 09:25:43,163 | MainPlayer: Failed to create DVIP context.
0x7f6ac02c7000 | UI.GLIO | ERROR | 2024-07-09 09:25:43,163 | MainPlayer: Failed to initialize worker thread.
0x7f697c1b0000 | UI.GLContext | INFO | 2024-07-09 09:25:43,163 | Creating shared OpenGL context for this thread (3 total).
0x7f697c1b0000 | UI.Scopes | ERROR | 2024-07-09 09:25:43,185 | Failed to create DVIP context.
0x7f6ac02c7000 | UI.Scopes | ERROR | 2024-07-09 09:25:43,185 | Failed to initialize worker thread.
0x7f6ac02c7000 | Main | ERROR | 2024-07-09 09:25:43,185 | Failed to initialize OpenGL texture pool, no valid contexts available.
libScannerAPI.so: cannot open shared object file: No such file or directory
0x7f6ac02c7000 | UI.MenuBar | WARN | 2024-07-09 09:25:43,200 | Main menu action [workspaceLayoutFusion_sub001Default]'s slot is not defined: workspaceLayoutFusion_sub001Default_triggered()
0x7f6ac02c7000 | FusionUtils | WARN | 2024-07-09 09:25:43,208 | Fusion DoAction ACTION_SET_FUSION_HOTKEY ignored, init not completed
0x7f696a9ad000 | SyManager | ERROR | 2024-07-09 09:25:43,211 | Failed to connect to panel socket
0x7f696a9ad000 | SyManager | ERROR | 2024-07-09 09:25:43,211 | DRIVER: open /var/tmp/davinci_socket failed
SY panel handler thread starts: 6A9AD000
0x7f69681aa000 | SyManager | INFO | 2024-07-09 09:25:43,217 | Starting keyboard device monitor thread...
Opening communication to resolve..
*** WARNING *** The program 'resolve' uses the Apple Bonjour compatibility layer of Avahi.
*** WARNING *** Please fix your application to use the native API of Avahi!

DaVinci Panel API Version: 1.0
0x7f6ac02c7000 | Main | INFO | 2024-07-09 09:25:43,226 | Show splash screen message: Loading Project Settings
0x7f6ac02c7000 | Main | INFO | 2024-07-09 09:25:43,789 | Show splash screen message: Loading Media Page
0x7f6ac02c7000 | UI.ActionManager | WARN | 2024-07-09 09:25:43,846 | Action [fairlightImmersiveAmbisonicsMetering] is not a global action
0x7f6ac02c7000 | UI.ActionManager | WARN | 2024-07-09 09:25:43,846 | Action [fairlightImmersiveGenerateImmersiveMaster] is not a valid global action
0x7f6ac02c7000 | UI.ActionManager | WARN | 2024-07-09 09:25:43,846 | Action [fairlightImmersiveRendererSettings] is not a valid global action
0x7f6ac02c7000 | UI.ActionManager | WARN | 2024-07-09 09:25:43,846 | Action [fairlightImmersiveEditADMScene] is not a valid global action
0x7f6ac02c7000 | UI.ActionManager | WARN | 2024-07-09 09:25:43,846 | Action [fairlightImmersiveAmbisonicsMetering] is not a valid global action
0x7f6ac02c7000 | UI.FairlightInterface | WARN | 2024-07-09 09:25:43,961 | SetActionEnabled: Failed to find action [viewTimelineScrollingFixed]'s action connector for handler Id [1]
0x7f6ac02c7000 | Main | INFO | 2024-07-09 09:25:44,143 | Show splash screen message: Loading Cut Page
0x7f6ac02c7000 | UI.SpeedTimeline | INFO | 2024-07-09 09:25:44,243 | Replay UI is enabled.
0x7f6ac02c7000 | Main | INFO | 2024-07-09 09:25:44,452 | Show splash screen message: Loading Edit Page
0x7f6ac02c7000 | Main | INFO | 2024-07-09 09:25:44,700 | Show splash screen message: Loading Fusion Page
0x7f6ac02c7000 | Main | INFO | 2024-07-09 09:25:44,778 | Show splash screen message: Loading Fairlight Page
0x7f6ac02c7000 | Main | INFO | 2024-07-09 09:25:44,944 | Show splash screen message: Loading Color Page
0x7f6ac02c7000 | Main | INFO | 2024-07-09 09:25:46,488 | Show splash screen message: Loading Waveform Monitor
0x7f696a9ad000 | SyManager | INFO | 2024-07-09 09:25:46,580 | Connected to panel socket at 147
0x7f696a9ad000 | SyManager | INFO | 2024-07-09 09:25:46,580 | Connection to the panel server has been re-established
Resolve discovery
****************** Flushing GPU Buffers
0x7f6ac02c7000 | Main | INFO | 2024-07-09 09:25:46,832 | Show splash screen message: Loading Audio Plugins
0x7f6ac02c7000 | SyManager | INFO | 2024-07-09 09:25:46,909 | Collaboration IP Port 0
0x7f6ac02c7000 | DbCommon2 | INFO | 2024-07-09 09:25:46,909 | Sm2SysIdEntry is not supported in local project library (xml) mode
0x7f6ac02c7000 | SyManager | ERROR | 2024-07-09 09:25:46,910 | Failed to parse key (SkipVersion) from JsonObject
0x7f6ac02c7000 | Main | INFO | 2024-07-09 09:25:46,910 | Show splash screen message: Ready
0x7f6ac02c7000 | Main | INFO | 2024-07-09 09:25:46,916 | Close splash screen
0x7f6ac02c7000 | SyManager.Signals | INFO | 2024-07-09 09:25:47,394 | Fusion templates changed
0x7f6ac02c7000 | IO | INFO | 2024-07-09 09:25:55,401 | RED rocket decode has been disabled in the config file
Resolve discovery
0x7f6ac02c7000 | UI | WARN | 2024-07-09 09:25:55,619 | Failed to find value '0' in combo-box
0x7f6ac02c7000 | UI | WARN | 2024-07-09 09:25:55,619 | Failed to find value '0' in combo-box
0x7f6ac02c7000 | UI | WARN | 2024-07-09 09:25:55,619 | Failed to find value '0' in combo-box
Resolve discovery
0x7f6ac02c7000 | Main | INFO | 2024-07-09 09:25:55,650 | Launching main loop
0x7f6ac02c7000 | UI | WARN | 2024-07-09 09:27:23,720 | Failed to find value '0' in combo-box
0x7f6ac02c7000 | UI | WARN | 2024-07-09 09:27:23,721 | Failed to find value '0' in combo-box
0x7f6ac02c7000 | UI | WARN | 2024-07-09 09:27:23,721 | Failed to find value '0' in combo-box
0x7f69681aa000 | SyManager | INFO | 2024-07-09 09:27:23,966 | Exiting keyboard device monitor thread.
0x7f6ac02c7000 | SyManager | INFO | 2024-07-09 09:27:23,967 | Thread release successful.
0x7f6ac02c7000 | DbCommon2 | INFO | 2024-07-09 09:27:24,136 | Sm2SysIdEntry is not supported in local project library (xml) mode
Assertion 'close_nointr(fd) != -EBADF' failed at src/basic/fd-util.c:75, function safe_close(). Aborting.



Can anyone help?

Re: Unsupported GPU Processing Mode-Linux

PostPosted: Tue Jul 09, 2024 1:53 pm
by smunaut
Latest 19 beta needs nvidia drivers 550+

Re: Unsupported GPU Processing Mode-Linux

PostPosted: Tue Jul 09, 2024 2:24 pm
by Der-Vinci
Thank you for your reply. I have nowhere found any information an driver numbers yet.

I uninstalled the 19 beta and installed the latest 18 final.
-> but the same error

I could use Windows but I do not do anything else with it.
And because of the Studio licence I would like to take advantage of GPU acceleration of course.

Re: Unsupported GPU Processing Mode-Linux

PostPosted: Tue Jul 09, 2024 3:56 pm
by smunaut
Mmm, ok. Make sure you have the nvidia opencl drivers installed too. I know on ubuntu it was in a separate package.

Even if Resolve doesn't use OpenCL for nvidia (it uses cuda), it uses it to detect GPUs ...

`clinfo -l` should show your nvidia gpu.

Re: Unsupported GPU Processing Mode-Linux

PostPosted: Tue Jul 09, 2024 4:46 pm
by Der-Vinci
I installed some more opencl and cuda related meta packages.
Everything from the official debain repo

Now clinfo -l gives a proper output and Resolve is starting.

Great so far !!

So I have to uninstall and install the studio version, right?

Re: Unsupported GPU Processing Mode-Linux

PostPosted: Tue Jul 09, 2024 7:30 pm
by Dwaine Maggart
No, you can install the Studio version over top of the free version on Linux and Mac.

On Windows, you can install a newer Studio version over an older free version. But if the free version is the same, it has to be uninstalled first.

Re: Unsupported GPU Processing Mode-Linux

PostPosted: Wed Jul 10, 2024 5:34 am
by Der-Vinci
Thank you for clarifying this.

I'm not sure exactly which package was needed but I can tell the meta-package name:

"nvidia-driver-full" contains:
libcudadebugger1 libnvidia-api1 libnvidia-fbc1 libnvidia-ngx1 libnvidia-nvvm4 libnvidia-opticalflow1 libnvoptix1 nvidia-cuda-mps nvidia-opencl-common nvidia-opencl-icd nvidia-powerd

[FIXED] Re: Unsupported GPU Processing Mode-Linux

PostPosted: Sat Sep 07, 2024 8:54 pm
by emilie
I have a Samsung Galaxybook 2. This has an i7 with an integrated GPU (Mesa Intel(R) Graphics - ADL GT2).

Edit 2: Fixed
I got this working. Warning, it was a pain in the butt:
- Updated linux mint to 22 Wilma
- Installed the oibaf graphics drivers ppa in order to get Mesa 24.1+ https://launchpad.net/~oibaf/+archive/ubuntu/graphics-drivers
- Compiled and installed https://github.com/intel/compute-runtime
-----> I used the https://github.com/smunaut/compute-runtime/tree/fix-arc branch, I don't think this was actually necessary for my card
-----> There are a ton of annoying dependencies. Notably intel-graphics-compiler is the worst. Try following these instructions: https://github.com/intel/intel-graphics ... _ubuntu.md with some creativity and grit.

BUT... IT WORKS! Hooray. 1920x1080 editing seems pretty smooth so far. Rendering looks good.

***
Initial post:

I got the same error. I assume Resolve is looking for opencl on start-up. Despite this being an integrated GPU, it supports opencl. I was able to run Resolve on Linux Mint by installing the intel opencl loader:

Code: Select all
sudo apt install intel-opencl-icd


Edit: not fully working after all. I am able to run the program and, after installing the latest experimental intel drivers (24.31.30508.7 - follow https://github.com/intel/compute-runtime/releases), I can see media thumbnails and timeline thumbnails, but the preview window is black and I continually get a "your GPU memory is full", even when showing still images on a 720 timeline with 1/4 resolution previews. I guess it's the preview rendering pipeline that isn't even working with intel. Looks like the opengl context isn't making it to opencl compute or vice-versa, not actually a memory problem. No preview == not really useable.

Logs:
Code: Select all
0x7745320ba180 | SyManager.Signals    | INFO  | 2024-09-08 00:26:32,702 | Current project pointer changed to (Untitled Project 2024-09-08_002631) from DB (Local Database : Local)
0x7745320ba180 | SyManager.Signals    | INFO  | 2024-09-08 00:26:32,702 | Current timeline pointer () is changed
0x7745320ba180 | UI                   | INFO  | 2024-09-08 00:26:32,712 | Gallery pointer is changed, refreshing color gallery
0x7745320ba180 | UI                   | INFO  | 2024-09-08 00:26:32,720 | Gallery pointer is changed, refreshing gallery browser
0x774482c00600 | DVIP                 | ERROR | 2024-09-08 00:26:34,871 | Failed to register OpenGL object for OpenCL interop: CL_INVALID_GL_OBJECT.
0x774482c00600 | UI.GLTexPool         | ERROR | 2024-09-08 00:26:34,871 | Failed to register OpenGL texture to compute API.
0x774482c00600 | UI.GLInterop         | ERROR | 2024-09-08 00:26:34,872 | MainPlayer: Failed to un-map texture, Handle2 is unknown.
0x774482c00600 | GPU.SingleBoardMgr   | ERROR | 2024-09-08 00:26:34,872 | Out-of-memory exception caught, purging memory: Packer OpenGL interop failed.
0x774482c00600 | GPU.SingleBoardMgr   | INFO  | 2024-09-08 00:26:34,872 | Flushing GPU memory...
0x774482c00600 | UI.GLTexPool         | INFO  | 2024-09-08 00:26:34,872 | Released 0 MiB in 0 unused textures.
0x774482c00600 | DVIP                 | ERROR | 2024-09-08 00:26:34,918 | Failed to register OpenGL object for OpenCL interop: CL_INVALID_GL_OBJECT.
0x774482c00600 | UI.GLTexPool         | ERROR | 2024-09-08 00:26:34,918 | Failed to register OpenGL texture to compute API.
0x774482c00600 | UI.GLInterop         | ERROR | 2024-09-08 00:26:34,918 | MainPlayer: Failed to un-map texture, Handle2 is unknown.
0x774482c00600 | GPU.SingleBoardMgr   | ERROR | 2024-09-08 00:26:34,918 | Out-of-memory exception caught, purging memory: Packer OpenGL interop failed.
0x774482c00600 | GPU.SingleBoardMgr   | INFO  | 2024-09-08 00:26:34,920 | Flushing GPU memory...
0x774482c00600 | UI.GLTexPool         | INFO  | 2024-09-08 00:26:34,920 | Released 0 MiB in 0 unused textures.
0x774482c00600 | DVIP                 | ERROR | 2024-09-08 00:26:35,055 | Failed to register OpenGL object for OpenCL interop: CL_INVALID_GL_OBJECT.
0x774482c00600 | UI.GLTexPool         | ERROR | 2024-09-08 00:26:35,056 | Failed to register OpenGL texture to compute API.
0x774482c00600 | UI.GLInterop         | ERROR | 2024-09-08 00:26:35,056 | MainPlayer: Failed to un-map texture, Handle3 is unknown.
0x774482c00600 | GPU.SingleBoardMgr   | ERROR | 2024-09-08 00:26:35,056 | Out-of-memory exception caught, purging memory: Packer OpenGL interop failed.
0x774482c00600 | GPU.SingleBoardMgr   | INFO  | 2024-09-08 00:26:35,056 | Flushing GPU memory...

Re: Unsupported GPU Processing Mode-Linux

PostPosted: Wed Jan 08, 2025 7:44 am
by trochi
I have exactly the same issue on my laptop albeit having different specs. (see attachment)
I tried your fix, but unfortunately it did not work. Should it work for my setup after all, or am I doing something wrong?

Help is greatly appreciated :)

Re: Unsupported GPU Processing Mode-Linux

PostPosted: Mon Jan 13, 2025 6:23 pm
by Dwaine Maggart
Resolve on Linux does not support Intel GPUs. Apparently Emile has found a solution that works around that.

But in your case, you have an NVIDIA GPU. So that CAN work, if you get a proper NVIDIA driver installed. The default open source Nouveau NVIDIA driver will not work with Resolve.

If you could provide a Resolve diagnostics log file, that could be helpful. In your Apps menu, you should have a "DaVinci Resolve Capture Logs" app, which has a gear icon. You can generate the Resolve diagnostics log with that.

Re: Unsupported GPU Processing Mode-Linux

PostPosted: Thu Feb 06, 2025 11:52 pm
by trochi
I did not find the app you asked for but when I right clicked the Davinci Resolve app I got the option to launch it with the dedicated GPU and that seems to have done the trick.

So thank you for pointing me in the right direction :)

Re: Unsupported GPU Processing Mode-Linux

PostPosted: Sun Jun 01, 2025 3:10 am
by dacunamo
Hello All!
I Had this issue, did so many things, reading this allowed me to resolve.

First of all I Installed nvidia-drivers, the GPU appeared but Grayed out, reinstalled several times no luck.
Sometimes did not show at all.

Finally I was able to make the GPU available by installing nvidia-drivers-full
FIRST UNINSTALL nvidia-driver

Code: Select all
sudo apt remove nvidia-driver

Then Install the full
Code: Select all
sudo apt install nvidia-driver-full


This seemed to do the trick, I still had the Unsupported GPU Processing Mode pop up, but went to configuration and deselected the options:
GPU Processing Mode
GPU Selection

Was able to select the NVIDIA Card, and VOILA!

It worked!

My SPECS:
Host: HP Pavilion Gaming Laptop 15-ec2xxx
CPU: AMD Ryzen 5 5600H with Radeon Graphics (12)
OS: Debian GNU/Linux 12 (bookworm) x86_64
GPU: NVIDIA GeForce GTX 1650
NVRM version: NVIDIA UNIX x86_64 Kernel Module 535.247.01

Re: Unsupported GPU Processing Mode-Linux

PostPosted: Mon Jun 02, 2025 8:30 pm
by Dwaine Maggart
OpenCL mode does not properly work with NVIDIA GPUs. Selecting that may allow Resolve to launch, but GPU operations will be crippled. CUDA must be used with NVIDIA GPU's for proper Resolve operation.