Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Needs more GPU testing #21

Closed
zelikos opened this issue Sep 30, 2023 · 32 comments
Closed

Needs more GPU testing #21

zelikos opened this issue Sep 30, 2023 · 32 comments
Labels
help wanted Extra attention is needed

Comments

@zelikos
Copy link
Owner

zelikos commented Sep 30, 2023

The docs are ever a work-in-progress as it is, but one big thing we're completely lacking right now is information on GPUs that work with what's provided here.

Right now, we're using AMD ROCm for AMD graphics cards. In my own testing, RX 6000 series cards---or at least, 6600 XT and up---should work OK. Other cards that are officially supported in ROCm should work too, but this isn't something I can verify alone. Older AMD cards are less likely to work.

For Nvidia and Intel, I can't test the former myself, and I have no idea on the latter whatsoever.

tl;dr: More testers needed with varying graphics cards

Edit:
GTX 10XX cards seem to work fine

Edit 2023-12-18:
As of ROCm 5.7.1, Resolve crashes on launch on my RX 6600 XT. Mesa's OpenCL (i.e. rusticl) lets Resolve launch successfully, but in an unusable state as video playback doesn't function and some of my projects don't load

@zelikos zelikos added the help wanted Extra attention is needed label Sep 30, 2023
@zelikos zelikos pinned this issue Sep 30, 2023
@ahoneybun
Copy link

It seems to work fine for me on Pop!_OS 22.04. It does still seem to have the issue with certain codex but I think that's because it's the non-paid version which is Studio.

Screenshot from 2023-10-09 11-29-14

@rothgar
Copy link

rothgar commented Oct 10, 2023

I have the studio version of davinci (18.6) on bluefin and this looks like it's detecting my GTX 1070 without any issues.
image

I also see resolve GPU usage from nvidia-smi

nvidia-smi
Tue Oct 10 10:17:14 2023       
+---------------------------------------------------------------------------------------+
| NVIDIA-SMI 535.113.01             Driver Version: 535.113.01   CUDA Version: 12.2     |
|-----------------------------------------+----------------------+----------------------+
| GPU  Name                 Persistence-M | Bus-Id        Disp.A | Volatile Uncorr. ECC |
| Fan  Temp   Perf          Pwr:Usage/Cap |         Memory-Usage | GPU-Util  Compute M. |
|                                         |                      |               MIG M. |
|=========================================+======================+======================|
|   0  NVIDIA GeForce GTX 1070        Off | 00000000:01:00.0  On |                  N/A |
|  0%   50C    P2              36W / 151W |   3063MiB /  8192MiB |      1%      Default |
|                                         |                      |                  N/A |
+-----------------------------------------+----------------------+----------------------+
                                                                                         
+---------------------------------------------------------------------------------------+
| Processes:                                                                            |
|  GPU   GI   CI        PID   Type   Process name                            GPU Memory |
|        ID   ID                                                             Usage      |
|=======================================================================================|
|    0   N/A  N/A      2839      G   /usr/bin/gnome-shell                        335MiB |
|    0   N/A  N/A      3802      G   /usr/bin/Xwayland                           817MiB |
|    0   N/A  N/A    180004    C+G   /opt/resolve/bin/resolve                   1131MiB |
+---------------------------------------------------------------------------------------+

@ahoneybun
Copy link

@rothgar can it play MP4 video files and such?

@rothgar
Copy link

rothgar commented Oct 12, 2023

MP4 video plays just fine but aac audio doesn't work with or without distrobox. That's a licensing issue with resolve on Linux in general.

I convert all of my videos to .MOV container with PCM audio.

ffmpeg -i "${1}" -vcodec dnxhd -acodec:0 pcm_s16le -acodec:1 pcm_s16le -s 1920x1080 -r 30000/1001 -b:v 36M -pix_fmt yuv422p -f mov "${1%.*}".mov

@zelikos zelikos changed the title GPU testing Needs more GPU testing Nov 21, 2023
@flexagoon
Copy link

flexagoon commented Nov 27, 2023

On a laptop with Nvidia, DaVinci doesn't use the dGPU by default, and GNOME's "launch with discrete GPU" option doesn't work because it sets environment variables which don't get passed through by distrobox. The fix I found was editing the desktop file and replacing

Exec=/usr/bin/distrobox-enter -n davincibox -- /opt/resolve/bin/resolve %u

with

Exec=/usr/bin/distrobox-enter -n davincibox -- env __NV_PRIME_RENDER_OFFLOAD=1 __GLX_VENDOR_LIBRARY_NAME=nvidia /opt/resolve/bin/resolve %u

@tjbbjt
Copy link

tjbbjt commented Dec 23, 2023

Resolve is crashing with davincibox running 18.6.4 Studio version on a Radeon VII

Also experimeted with installing drivers in the container:
https://repo.radeon.com/amdgpu-install/23.30.2/rhel/9.2/amdgpu-install-5.7.50702-1.el9.noarch.rpm
https://copr.fedorainfracloud.org/coprs/xxmitsu/mesa-git/

After installing either of these Resolve stopped crashing but gives a GPU Initialization Failed error

opengl error

Was experimenting with building Rocky Linux containers before finding your project and will gladly help test future builds.

@trafotin
Copy link

trafotin commented Jan 1, 2024

Screenshot from 2023-12-31 21-11-43
If you use a Nvidia GPU, add the flag "--nvidia" when manually building in Distrobox. I'm testing with a 4060M, on Fedora with Wayland/GNOME.

Getting past the "make your sure no displays are plugged into your discrete GPU" requires you run DaVinci in X11 first with the Nvidia drivers on your host, then open it in Wayland and then it works.

After this point, the above warning shows because there's somewhere in the pipeline where switcheroo can't give Podman access to a dGPU. You can still make edits, but nothing plays.

Running natively on Fedora, Resolve works, so it's not an issue with the container or its build quality as much as it is discrete Nvidia GPUs not playing ball.

@flexagoon
Copy link

@trafotin have you tried my solution?

#21 (comment)

This worked for me even without the --nvidia option

@trafotin
Copy link

trafotin commented Jan 1, 2024

@trafotin have you tried my solution?

We're further along, but I'm still getting crashes. Crash is identical on both Wayland and X11.

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
18.6.0.0009 Linux/Clang x86_64
Main thread starts: 0E20E000
Failed to load config file "%u".Warning: Ignoring XDG_SESSION_TYPE=wayland on Gnome. Use QT_QPA_PLATFORM=wayland to run on Wayland anyway.
resolve: /home/jenkins/jenkins/workspace/resolve/Resolve/Cyclone/Main/AppConfig.cpp:296: void AppConfig::LoadAllSiteInfo(): Assertion `m_SiteEnabledIdx > 0' failed.
log4cxx: No appender could be found for logger (Main).
log4cxx: Please initialize the log4cxx system properly.


==========[CRASH DUMP]==========
#TIME Mon Jan  1 15:50:08 2024 - Uptime 00:00:00 (hh:mm:ss)
#PROGRAM_NAME DaVinci Resolve v18.6.0.0009 (Linux/Clang x86_64)
#BMD_ARCHITECTURE x86_64
#BMD_BUILD_UUID 445d7d93-25e8-4e6d-a54e-1bb3ee745c58
#BMD_GIT_COMMIT 2541dac8b8ea4bd08de600b58edcb7d95aa657bc
#BMD_UTIL_VERSION 18.6.0.0009
#OS Linux

/opt/resolve/bin/resolve() [0x48069c9]
/opt/resolve/bin/resolve() [0x24c8b82]
/lib64/libc.so.6(+0x3e9a0) [0x7f5e0f25c9a0]
/lib64/libc.so.6(+0x90834) [0x7f5e0f2ae834]
/lib64/libc.so.6(raise+0x1e) [0x7f5e0f25c8ee]
/lib64/libc.so.6(abort+0xdf) [0x7f5e0f2448ff]
/lib64/libc.so.6(+0x2681b) [0x7f5e0f24481b]
/lib64/libc.so.6(+0x36c57) [0x7f5e0f254c57]
/opt/resolve/bin/resolve() [0x24f9dec]
/opt/resolve/bin/resolve() [0x24f6f53]
/opt/resolve/bin/resolve() [0x24f68a8]
/opt/resolve/bin/resolve() [0x40df168]
/opt/resolve/bin/resolve() [0x3ac4196]
/opt/resolve/bin/resolve() [0x3ac3fce]
/opt/resolve/bin/resolve() [0x251cbc8]
/opt/resolve/bin/resolve() [0x251cad1]
/opt/resolve/bin/resolve() [0x24c6740]
/opt/resolve/bin/resolve() [0x24c15fe]
/lib64/libc.so.6(+0x2814a) [0x7f5e0f24614a]
/lib64/libc.so.6(__libc_start_main+0x8b) [0x7f5e0f24620b]
/opt/resolve/bin/resolve() [0x24c024b]
Signal Number = 6

================================
resolve: /home/jenkins/jenkins/workspace/resolve/Resolve/Cyclone/Main/AppConfig.cpp:296: void AppConfig::LoadAllSiteInfo(): Assertion `m_SiteEnabledIdx > 0' failed.


==========[CRASH DUMP]==========
#TIME Mon Jan  1 15:50:08 2024 - Uptime 00:00:00 (hh:mm:ss)
#PROGRAM_NAME DaVinci Resolve v18.6.0.0009 (Linux/Clang x86_64)
#BMD_ARCHITECTURE x86_64
#BMD_BUILD_UUID 445d7d93-25e8-4e6d-a54e-1bb3ee745c58
#BMD_GIT_COMMIT 2541dac8b8ea4bd08de600b58edcb7d95aa657bc
#BMD_UTIL_VERSION 18.6.0.0009
#OS Linux

/opt/resolve/bin/resolve() [0x48069c9]
/opt/resolve/bin/resolve() [0x24c8b82]
/lib64/libc.so.6(+0x3e9a0) [0x7f5e0f25c9a0]
/lib64/libc.so.6(+0x90834) [0x7f5e0f2ae834]
/lib64/libc.so.6(raise+0x1e) [0x7f5e0f25c8ee]
/lib64/libc.so.6(abort+0xdf) [0x7f5e0f2448ff]
/lib64/libc.so.6(+0x2681b) [0x7f5e0f24481b]
/lib64/libc.so.6(+0x36c57) [0x7f5e0f254c57]
/opt/resolve/bin/resolve() [0x24f9dec]
/opt/resolve/bin/resolve() [0x24f6f53]
/opt/resolve/bin/resolve() [0x24f68a8]
/opt/resolve/bin/resolve() [0x250d8f9]
/opt/resolve/bin/resolve() [0x24c8d93]
/lib64/libc.so.6(+0x3e9a0) [0x7f5e0f25c9a0]
/lib64/libc.so.6(+0x90834) [0x7f5e0f2ae834]
/lib64/libc.so.6(raise+0x1e) [0x7f5e0f25c8ee]
/lib64/libc.so.6(abort+0xdf) [0x7f5e0f2448ff]
/lib64/libc.so.6(+0x2681b) [0x7f5e0f24481b]
/lib64/libc.so.6(+0x36c57) [0x7f5e0f254c57]
/opt/resolve/bin/resolve() [0x24f9dec]
/opt/resolve/bin/resolve() [0x24f6f53]
/opt/resolve/bin/resolve() [0x24f68a8]
/opt/resolve/bin/resolve() [0x40df168]
/opt/resolve/bin/resolve() [0x3ac4196]
/opt/resolve/bin/resolve() [0x3ac3fce]
/opt/resolve/bin/resolve() [0x251cbc8]
/opt/resolve/bin/resolve() [0x251cad1]
/opt/resolve/bin/resolve() [0x24c6740]
/opt/resolve/bin/resolve() [0x24c15fe]
/lib64/libc.so.6(+0x2814a) [0x7f5e0f24614a]
/lib64/libc.so.6(__libc_start_main+0x8b) [0x7f5e0f24620b]
/opt/resolve/bin/resolve() [0x24c024b]
Signal Number = 6

================================

I haven't tried without the Nvidia option, but will respond to this post and tag you when I do.

@tjbbjt
Copy link

tjbbjt commented Jan 11, 2024

Was able to get an Arch Linux distrobox working, the amdgpu-pro-oglp using progl prefix would crash but opencl-amd and mesa-rusticl-git with "export OCL_ICD_VENDORS= export OCL_ICD_FILENAMES=/usr/lib64/libRusticlOpenCL.so export RUSTICL_ENABLE=radeonsi" works.

So Mesa Rusticl 24 should fix media not playing in Resolve on Fedora with AMD cards.

@RojJuan
Copy link
Contributor

RojJuan commented Jan 16, 2024

the software is fully functional on my GTX 760 card
image

@shubhisroking
Copy link

shubhisroking commented Jan 23, 2024

image
I am having same issue as @trafotin where nothing plays on an NVIDIA laptop even after applying the fix mentioned in issue #40 , local installation seems to work fine

@flexagoon
Copy link

@shubhisroking what does this command output for you?

podman run \
    --user 1000:1000 \
    --security-opt=no-new-privileges \
    --cap-drop=ALL \
    --security-opt label=type:nvidia_container_t  \
    --device=nvidia.com/gpu=all \
    docker.io/nvidia/samples:vectoradd-cuda11.2.1

I am using uBlue, which has support for nvidia in containers out of the box. If the above command doesn't work and you tried building the distrobox both with the --nvidia flag and without it, try setting nvidia container runtime up.

@shubhisroking
Copy link

@shubhisroking what does this command output for you?

podman run \
    --user 1000:1000 \
    --security-opt=no-new-privileges \
    --cap-drop=ALL \
    --security-opt label=type:nvidia_container_t  \
    --device=nvidia.com/gpu=all \
    docker.io/nvidia/samples:vectoradd-cuda11.2.1

I am using uBlue, which has support for nvidia in containers out of the box. If the above command doesn't work and you tried building the distrobox both with the --nvidia flag and without it, try setting nvidia container runtime up.

2024-01-24_10-57
seems to run fine after setting up nvidia container toolkit, but still nothing plays in davinci resolve even, tested with and without --nvidia option

@flexagoon
Copy link

@shubhisroking weird. Can you provide Davinci logs please?

@shubhisroking
Copy link

@shubhisroking weird. Can you provide Davinci logs please?

Hey I just did a reboot and it works fine now
2024-01-24_13-20

@aldecrat
Copy link

aldecrat commented Feb 2, 2024

image
image

Using Radeon RX 5500XT. Installation worked but on startup the graphics card does not appear in the list. Any help would be welcome. I also haven't a baldy what I am doing and my son is in despair... and so am I.
Thanks.

@trafotin
Copy link

trafotin commented Feb 3, 2024

Using Radeon RX 5500XT. Installation worked but on startup the graphics card does not appear in the list. Any help would be welcome. I also haven't a baldy what I am doing and my son is in despair... and so am I. Thanks.

If you are on Wayland (guessing because no titlebars), try start Resolve in X11 once, then start it up again in Wayland. Although I wonder if that is a thing with AMD users. I use Nvidia and Nvidia is still hard-dependent on X11.

There's also the possibility your GPU isn't being seen by container. Are you using a discrete AMD card?

@aldecrat
Copy link

aldecrat commented Feb 3, 2024

I am using X11 on Debian testing with XFCE. Yeah, I am using a discrete AMD card.
My son says that the GPU is not being seen by the container and CLinfo.
Thanks.

@tjbbjt
Copy link

tjbbjt commented Feb 3, 2024

I am using X11 on Debian testing with XFCE. Yeah, I am using a discrete AMD card. My son says that the GPU is not being seen by the container and CLinfo. Thanks.

After entering the davincibox you could try

export OCL_ICD_VENDORS= export OCL_ICD_FILENAMES=/usr/lib64/libRusticlOpenCL.so export RUSTICL_ENABLE=radeonsi

and then

/opt/resolve/bin/resolve

This will more than likely allow Resolve to start but no media will decode. Personally I could not get davincibox, flatpak or any flavor of Linux distrobox working with Resolve and my Radeon VII other than Arch Linux. I wrote out steps on how to get that working in another forum here. Hope any of this helps!

@aldecrat
Copy link

aldecrat commented Feb 4, 2024

Thanks very much for your efforts. It appears that Davinci is not really ready for Linux yet.

@flexagoon
Copy link

@aldecrat davinci is very much ready for Linux, it just isn't intended to be run inside of a container

It also generally just works better with Nvidia GPUs

@RojJuan
Copy link
Contributor

RojJuan commented Feb 4, 2024

@aldecrat i got this answer from reddit :

Sharing my experience on Arch. Up to DR 18.1.1, Mesa 22 and ROCm OpenCL 5.3.3 (installed from CN repo, as 5.4 got adopted into official repo) I was able to use DR just fine, including Fusion. Starting from DR 18.1.2 and later versions of ROCm OpenCL I noticed crashes as you described.

Last night I decided to use both AMDGPU-PRO OpenGL and OpenCL packages (meaning, all-proprietary graphic components) and upgrade to DR 18.5. It run, Fusion works! Downside was it's took soooooo long for preview to cached up and display.

I should try again with Mesa OpenGL, cause I don't feel comfortable using proprietary OpenGL. If Mesa OpenGL works with opencl-amd then maybe something went wrong with rocm-opencl-runtime packaging on Arch repo.

@queequeg0925
Copy link

Has anyone tried this with an RX580? I know that ROCM support was dropped from these cards a while ago and there have been various workarounds. Not sure if i am better off trying this or running a rocky linux virtual machine

@randogoth
Copy link

Works on my Gigabyte Aero 15 X-9 running Bluefin (F39). I had the black screen issue (#65) and had to edit the desktop file.

Launching the app froze at the splash screen until I rebooted.

image

nvidia-smi

+-----------------------------------------------------------------------------------------+
| NVIDIA-SMI 550.78                 Driver Version: 550.78         CUDA Version: 12.4     |
|-----------------------------------------+------------------------+----------------------+
| GPU  Name                 Persistence-M | Bus-Id          Disp.A | Volatile Uncorr. ECC |
| Fan  Temp   Perf          Pwr:Usage/Cap |           Memory-Usage | GPU-Util  Compute M. |
|                                         |                        |               MIG M. |
|=========================================+========================+======================|
|   0  NVIDIA GeForce RTX 2070 ...    Off |   00000000:01:00.0  On |                  N/A |
| N/A   53C    P8              8W /   80W |      28MiB /   8192MiB |      0%      Default |
|                                         |                        |                  N/A |
+-----------------------------------------+------------------------+----------------------+
                                                                                         
+-----------------------------------------------------------------------------------------+
| Processes:                                                                              |
|  GPU   GI   CI        PID   Type   Process name                              GPU Memory |
|        ID   ID                                                               Usage      |
|=========================================================================================|
|    0   N/A  N/A      5593      G   /usr/bin/gnome-shell                            1MiB |
+-----------------------------------------------------------------------------------------+

@tmarplatt
Copy link

Host: Mint Cinnamon 21.3 (based on Ubuntu jammy)
GPU: RX 5500 XT

First off, Resolve doesn't launch without elevated privileges, so I need:

distrobox enter -n davincibox -- sudo /usr/bin/run-davinci

Unfortunately, same issue as @aldecrat Resolve can't see my GPU, the GPU list is empty.

I saw the amdgpu kernel module is loaded in the container, but I'm not sure how to verify OpenGL is working as I'm no Fedora user. For some reason there is no glxinfo available on $PATH, even though mesa seems to be installed. Or how to verify the container system sees my GPU. Would appreciate some help here.

@user7z
Copy link

user7z commented May 19, 2024

i have and intel iGPUs , iam welcome to help test this project

@badlydrawnface
Copy link

My RX580 was detected, but it used OpenCL, and video playback did not seem to be working. Resolve seemed to only be using about 45-50 MB of RAM.

OS: CachyOS with this container

Might be time for a new GPU soon, the 580 is still a sleeper even in 2024 tho...
image

@ricardopiloto
Copy link

Host: Fedora 40
GPU: RX 6750 XT

Managed to install without any problems but whenever I try to add a video to the media pool I get an error regarding GPU processing (error -57). Tried second option with rusticl but got the same result only difference being that with rusticl only one GPU is shown.

image

Screenshot_20240528_132420

@zelikos
Copy link
Owner Author

zelikos commented May 28, 2024

@ricardopiloto Can confirm the same issue on my end; neither ROCm nor rusticl working with Resolve right now.

@BluedragonMask
Copy link

image
Yup, same issue here. I thought I was going crazy till I scrolled down to the end of this

@zelikos
Copy link
Owner Author

zelikos commented Jun 16, 2024

I'll be closing this issue.

When this project was just beginning, having a "call to action" issue thread like this to have various GPUs tested was great, and I want to thank each and everyone who reported test results here. I think we've determined that Nvidia generally seems to work, AMD has its issues, and...Intel is somewhat unknown, but we have a separate issue for Intel now anyway.

That being said, we're at a point where it'd be better to have separate issues opened for specific problems, to make sure things don't get lost in the shuffle (such as #21 (comment), which sounds like a similar issue as #76?).

If you've posted about a problem in this thread that doesn't already have an open issue report, please open a new issue about it.

@zelikos zelikos closed this as completed Jun 16, 2024
@zelikos zelikos unpinned this issue Jun 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests