Closed Pragmer closed 1 year ago
The problem is here: Warning: could not parse clinfo data!
Have you tried running clinfo
?
What little I gathered from this is that it IS using OpenCL. I ran the script again and it finds stuff on OpenCL but it still cant find anything on OpenGL
Using locale en_US
DaVinci Resolve checker 5.2.3
Installed DaVinci Resolve package: davinci-resolve 18.1.4-1
Chassis type: desktop
Installed OpenCL drivers:
rocm-opencl-runtime 5.4.3-1
Presented GPUs:
Navi 22 [Radeon RX 6700/6700 XT/6750 XT / 6800M/6850M XT] (kernel driver in use: amdgpu)
Raphael (kernel driver in use: amdgpu)
OpenGL vendor string:
OpenGL renderer string:
clinfo detected platforms and devices:
AMD Accelerated Parallel Processing (roc) (number of devices: 2)
AMD Radeon Graphics
AMD Radeon Graphics
Unable to detect the OpenGL vendor string. Probably you are trying to use AMD Pro OpenGL while your primary GPU is Intel. Also probably you are launching script via ssh.
Idk if I should clarify, but I do NOT have an intel GPU and I am NOT trying to use AMD Pro OpenGL.
Have you followed the installation instructions to install dependencies such as mesa-demos? Try running glxinfo commands from script (lines 129 and 134 currently).
I don't know whether to feel embarrassed, ashamed, or both. Both of these problems with the script were caused by commands not being installed, I'm assuming due to my own incompetence. New output of the script:
Using locale en_US
DaVinci Resolve checker 5.2.3
Installed DaVinci Resolve package: davinci-resolve 18.1.4-1
Chassis type: desktop
Installed OpenCL drivers:
rocm-opencl-runtime 5.4.3-1
Presented GPUs:
Navi 22 [Radeon RX 6700/6700 XT/6750 XT / 6800M/6850M XT] (kernel driver in use: amdgpu)
Raphael (kernel driver in use: amdgpu)
OpenGL vendor string: AMD
OpenGL renderer string: AMD Radeon Graphics (navi22, LLVM 15.0.7, DRM 3.52, 6.4.2-arch1-1)
clinfo detected platforms and devices:
AMD Accelerated Parallel Processing (roc) (number of devices: 2)
AMD Radeon Graphics
AMD Radeon Graphics
You have several AMD GPUs. DR Studio can utilise several GPUs. Script will check if appropriate driver for your renderer GPU is used. But keep in mind that if you use prime offloading, than your primary gpu still need appropriate driver (script does not check it).
You should use ROC_ENABLE_PRE_VEGA=1 environment variable. Otherwise use pro stack (run checker with --pro), because legacy opencl requires progl to work.
The reason it says I have several AMD GPUs is likely because I have one ACTUAL GPU, an RX6700, and the CPU has an IGPU. I did look through a Davinci Resolve Log and it seems to me that it liked to use the IGPU not the actual GPU. I'm assuming "ROC_ENABLE_PRE_VEGA=1" is supposed to fix that.
Update: I think the recommendation given by the script is incorrect. From what I can find GFX9/Vega came out in 2017. My graphics card, was made in 2021. I don't know about you but 2021 seems like its AFTER that, not before, so I am unsure why it is recommending me to enable something only for graphics cards made before Vega. My CPU(which has an IGPU) was made in late 2022, further after Vega.
It is most likely some conditions error. Please use dump_lspci_list.py and share the dict. I will analyze it.
I think I am misunderstanding your request due to my own ignorance. I looked up what it meant to share the dict and it seemed like it would be the file in this directory: /usr/share/dict/, but I cannot upload it as it is not supported, so I probably got that wrong. Would you mind elaborating on what you want me to do?
I apologize If I am causing you frustration, this is not my intent. I am still in the learning stage of this distribution.
I mean, after running the dump_lspci_list.py
you should now have a lspci_devices_dump.bin
. This is a python dictionary in binary format. Can you upload it, so that I could debug the problem?
Oh, I didn't realize that's what that type of file was called. Unfortunately it did not let me upload the file directly, so I had to upload it as a tar file. lspci_devices_dump.tar.gz
Try with version 5.2.4
Both of these problems with the script were caused by commands not being installed, I'm assuming due to my own incompetence.
No, that happened because glxinfo
was moved to mesa-utils
recently. Fixed dependencies in 5.2.5. Thanks for mentioning this.
Thank you for your help. The script now identifies that I can run davinci resolve.
My partition is Arch Linux created using archinstall, there was an option asking about installing graphics drivers and because I know that I only have an AMD GPU(RX 6700) I selected amd all open source. I was following this guide: https://wiki.archlinux.org/title/DaVinci_Resolve to install resolve. I installed the free version that it lists via git clone >> makepkg >> pacman.
The guide states that both Open CL drivers and Open GL drivers are required and has a table listing available drivers, whether they are open source or not, and whether they have been tested to work with resolve or not. I installed "mesa" for Open GL, and "rocm-opencl-runtime" for Open CL. Both of these drivers are listed as having been tested to work on the latest version of Resolve. After this it links to this github and says to make sure that you get "All seems good. You should be able to run DaVinci Resolve successfully. " Unfortunately this is not what I get.
The output of this command(CDed into its folder): ./davinci-resolve-checker.py is the following.
Furthermore, I can verify that the drivers are actually installed by using the commands "pacman -Qs mesa" and "pacman -Qs rocm-opencl-runtime" of which the outputs are the following For Mesa:
For Rocm:
What is even more perplexing is that I actually CAN open Resolve. I just cant seem to properly import my video file. I have looked into that issue specifically for like 5 hours and all I really found were ways to check to make sure I was using a supported video format(which MKV is) and a supported codec(which is H.264, also supported) or people saying that I should make sure it has a constant framerate(which I verified with ffmpeg to be a constant 60). I even made sure that the FLAC audio format was supported which it is(my audio was recorded as FLAC).
Perhaps this is foolish of me but my conclusion after this was to go back to the resolve checker issue I had 5 hours prior that I ignored because the program had actually opened. I figured that maybe something else was going on that I was too dense to resolve, so, here I am, hoping that I can get some help of some kind. If any more information is required for diagnostic purposes request away. If I am being a foolish idiot, please say so and explain, so that maybe I don't make the same mistake in the future.