Blackmagic Forum

Thu Oct 10, 2019 12:51 am

I have DaVinci Resolve Studio 16.0 up and running on CentOS 8.0 with the NVIDIA 430.50 driver for a single GTX 1080 Ti card.

For now, until ELRepo can get the NVIDIA driver packaged for CentOS 8, the NVIDIA driver can only be installed with the .run file, which is even more convoluted than previously, because CentOS 8 defaults to Wayland. Wayland must be disabled because NVIDIA doesn't yet have a driver compatible with Wayland.

N.B. using NVIDIA's .run file requires the use of a virtual console and perhaps even SSHing in from a different machine on your LAN at times. You should be comfortable with the CLI to attempt this.

I keep these notes hosted on GitHub, because software constantly changes. If and when ELRepo does package the NVIDIA driver for CentOS 8, I'll modify the instructions to take advantage of that, because that's much easier. Also, I had to temporarily remove my optional instructions for installing PostgreSQL on CentOS 8, just because I haven't yet done it, but I still have instructions available that should work for CentOS 7.7. When I do upgrade my PostgreSQL server from 7.7 to 8.0, I'll add instructions for how to do it back into my main document.

Create a bootable USB drive
1. On Windows:
  1. Download DVD ISO
  2. Verify the download
  3. Download and use Rufus to create the bootable USB drive
2. On Mac or Linux:
  1. Download DVD ISO
  2. Verify the download
  3. Use dd to create the bootable USB drive
UEFI settings
1. Set to boot to a USB drive first
2. Disable Secure Boot and disable Legacy BIOS mode
Install CentOS from USB
1. Software selection should be Workstation with only GNOME Applications checked.
2. Set up DHCP
  - Set password for root account and create just one administrator account
CentOS's installation interacts with HP's UEFI in such a way as to change the boot order, so reboot, and you'll boot to the M.2 SSD with the fresh installation
1. Reboot and you'll boot into the M.2 SSD with the fresh installation
2. Accept the CentOS license
3. You can then safely eject the USB installation disk
Install CentOS updates and reboot
Take note of the IP address on the LAN, because you might need to SSH into the machine later.
Install the kernel source:
- $ sudo yum install "kernel-devel-uname-r == $(uname -r)"
Install EPEL
- $ sudo yum install https://dl.fedoraproject.org/pub/epel/e ... noarch.rpm
Install DKMS
- $ sudo yum install dkms
Prepare for the NVIDIA driver
1. Download the .run file for 430.50 from NVIDIA's site.
2. Become the root user:
  - $ su -
3. Make the file executable:
  - # chmod +x NVIDIA-Linux-x86_64-430.50.run
4. Blacklist the nouveau module:
  - # echo 'blacklist nouveau' >> /etc/modprobe.d/blacklist.conf
5. Install dependencies:
  - # dnf groupinstall "Workstation" "base-x" "Legacy X Window System Compatibility" "Development Tools"
  - # dnf install elfutils-libelf-devel "kernel-devel-uname-r == $(uname -r)"
6. Back up and rebuild your initramfs:
  - # mv /boot/initramfs-$(uname -r).img /boot/initramfs-$(uname -r)-nouveau.img
  - # dracut -f
7. Change the default runlevel:
  - # systemctl set-default multi-user.target
8. Reboot the system:
  - # reboot
From the command-line, log into root, navigate to wherever you put the .run file, and then install the NVIDA driver:
1. # ./NVIDIA-Linux-x86_64-430.50.run
  - Be sure to install to DKMS
2. Test the new driver:
  - # systemctl isolate graphical.target
3. If the test is successful, correct your default runlevel:
  - # systemctl set-default graphical.target
4. Reboot:
  - # reboot
5. Confirm that you're running the NVIDIA driver at any time by running $ nvidia-smi
Download and install the latest DeckLink driver
1. Download the latest driver from the Blackmagic Design website
2. Become the root user:
  - $ su -
    - When prompted, enter your root user's password.
3. If you already have an older DeckLink driver installed, uninstall it:
  - # rpm -qa | grep desktopvideo | xargs rpm -e
4. If GNOME didn't uncompress it for you already, uncompress the downloaded driver package:
  - # tar xvfz /path/to/downloaded/driver/location/Blackmagic_Desktop_Video_Linux_<driver_version>.tar.gz
5. cd into the rpm folder, since this is CentOS
  - # cd /Blackmagic_Desktop_Video_Linux_<driver_version>/rpm/<yourarchitecture>
6. Install the latest Desktop Video driver, GUI, and Media Express. Type:
  - # rpm -ivh desktopvideo-<driver_version>.x86_64.rpm
  - # rpm -ivh desktopvideo-gui-<driver_version>.x86_64.rpm
  - # rpm -ivh mediaexpress-<version>.x86_64.rpm
7. The installer for Media Express might fail and tell you that you mediaexpress needs libGLU.so.1, so install libGLU and try again:
  - # dnf install mesa-libGLU
8. After the installation completes, you should see the terminal prompt. Reboot.
9. After the machine has rebooted, open a Terminal shell again
10. Become the root user again:
  - $ su -
    - When prompted, please enter your root user's password
  - You might need to update the firmware on your DeckLink card. Type:
    - # BlackmagicFirmwareUpdater update 0
  - If a firmware update was applied, reboot the machine after it completes. If no firmware update was required, a reboot is not necessary.
At this point, installing Desktop Video to DKMS will probably have "broken" the grub configuration again. If you try to log into the GUI, the screen will just go black. So we'll need to go rebuild the grub configuration again.
1. If you can get to a virtual console, log in. Otherwise, SSH into the root account from a different machine on the network.
2. vim into /etc/default/grub
3. For the GRUB_CMDLINE_LINUX line, remove rhgb and add rd.driver.blacklist=nouveau", so that the whole line is:
  - GRUB_CMDLINE_LINUX="crashkernel=auto resume=/dev/mapper/cl-swap rd.lvm.lv=cl/root rd.lvm.lv=cl/swap quiet rd.driver.blacklist=nouveau"
4. Write and close: :wq
5. Rebuild the grub configuration again:
  - # grub2-mkconfig -o /boot/efi/EFI/centos/grub.cfg
6. Reboot:
  - # reboot
Now we should be totally ready for DaVinci Resolve.
Install DaVinci Resolve
- Download and extract DaVinci_Resolve_Studio_16.0_Linux.zip (if you have a DaVinci Resolve license dongle or key) or DaVinci_Resolve_16.0_Linux.zip from the Blackmagic Design website.
- Double-click the .run file to use the GUI installer
- Resolve might not launch after the installation--if you run it via the command-line from /opt/resolve/bin/, you can look for clues as to why it might not be able to launch. If some program is missing, try figuring out what Resolve needs and install via dnf.

Thu Oct 10, 2019 3:42 am

Thank you for doing the legwork on this, Seth!

Fri Nov 08, 2019 8:38 pm

Sure thing, Marc!

Since I'm still figuring all this out, this thread seems like a good central place for some more information about NVIDIA, Wayland, and CentOS 8 for the confused and/or curious.

GNOME has started to provide some limited support for the use of a Wayland session on top of NVIDIA drivers, but only starting with in GNOME 3.32.

Meanwhile, as of this writing, I'm running CentOS Linux release 8.0.1905 (Core) with kernel 4.18.0-80.11.2.el8_0.x86_64, and that only has GNOME Version 3.28.2, so Wayland must be disabled and the legacy Xorg environment must be installed and enabled so that the NVIDIA drivers can work.

I suppose we'll get a heads-up about when GNOME 3.32 or higher might ship in RHEL 8/CentOS 8 by looking at the versions of GNOME that make it into CentOS Stream.

Right now, as I understand it, as of this writing, the packages in CentOS Stream are identical to what's in RHEL 8 and CentOS 8, aside from the kernel, but we'll know what's coming because newer packages will be hitting CentOS Stream first.

Fri Nov 08, 2019 8:47 pm

Happy to report that I've tested 440.31 and it's working quite well on CentOS 8.0.1905 with kernel 4.18.0-80.11.2.el8_0.x86_64. Everything feels a bit faster than 430.50.

Thu Nov 14, 2019 2:16 pm

Thanks for this!

At first I was naive and skimmed thinking I could take a shortcut getting away with RPM Fusion's kmod NVIDIA but learned the hard way that the current version isn't working.

But following your tuturial works perfectly!

I have to ask though. Sometime around the gpu driver install, it's been defaulting to booting straight to bash instead of going directly to GNOME. I can still get there, through a terminal command, but it's a bit roundabout. Do you have any ideas on what could be causing it?

Thu Nov 14, 2019 3:15 pm

Corey Ryan Hanson wrote:I have to ask though. Sometime around the gpu driver install, it's been defaulting to booting straight to bash instead of going directly to GNOME. I can still get there, through a terminal command, but it's a bit roundabout. Do you have any ideas on what could be causing it?

Sounds like you might just have the wrong systemd target set. To install the NVIDIA driver via the .run file, you probably set your default target to boot to the CLI with:

Code: Select all: # systemctl set-default multi-user.target

If the driver appeared to finish installing correctly, you can check to see if GNOME and GUI are working OK by running:

Code: Select all: # systemctl isolate graphical.target

That's just temporary, though. To permanently boot to the GUI, you'd set the target by running:

Code: Select all: # systemctl set-default graphical.target

Corey Ryan Hanson wrote:At first I was naive and skimmed thinking I could take a shortcut getting away with RPM Fusion's kmod NVIDIA but learned the hard way that the current version isn't working.

Yeah, I'm eagerly awaiting working packages from the RPM Fusion and the ELRepo folks, but until then, the .run files are the only way to go. I have made a few tweaks to the open-source notes since my first post on October 9th, so look there for the most current instructions. As soon as ELRepo has working packages again, I'll likely swap that in, since dealing with the .run file can be a bit convoluted for the uninitiated.

Fri Nov 15, 2019 4:48 am

Ah! I had a feeling it might have been that multi user commend (because I had no clue what that one did haha)

That systemcontrol set default did the trick. Here I was earlier searching aimlessly through my grub configuration thinking something was wrong there.

Now with the tip you gave me everything is running perfectly. Thanks!

Sat Jan 04, 2020 9:24 pm

Hey Seth, thanks for putting this together. I've always run resolve on Windows or Mac but thought I'd give this a shot.

I've got to step 11.2 (Test the new driver) and ran into an issue. I issued the command:
systemctl isolate graphical.target
The system rebooted, and it boots into the GUI rather than the CLI. I'm able to log in normally, except once I login the screen just goes black instead of going to the GUI desktop. Any ideas? I'd try running step 11.3 from the CLI but I have no idea how to get back to the CLI now that its booting into the (broken) GUI login automatically. Everything I'm reading online seems to be outdated or too confusing for my level of Linux experience.

Honestly, I'd probably be better suited with the Blackmagic CentOS build as it seems more straightforward and I'm a total Linux noob, but I don't have any way to currently burn a DVD.

Let me know if I'm missing something obvious.

Sat Jan 11, 2020 12:46 am

The system rebooted, and it boots into the GUI rather than the CLI. I'm able to log in normally, except once I login the screen just goes black instead of going to the GUI desktop

It's not just you. i think it worked for me the first time when I set the graphical.target as the defualt but subsequent installs (i use too much clonezilla) did the same thing.

The way you get out of that scenario back into terminal is type "e" on the initial boot screen comes up. Then on that grub menu insert a "3" after "quiet" which should get you to the command prompt.

Then for some weird reason, if you manually run that "isolate graphical target' command, the gui doesn't break (but it kind of sucks to have to log in twice every time).

It's a bit rough right now, but it seems like there is some work being done on the el-repo repository to make the process much easier.
https://elrepo.org/bugs/view.php?id=944
It looks like it may be hanging on some gcc compatibility mismatches to work with Centos 8.0. Hopefully the upcoming release of 8.1 will push things forward

Sat Jan 11, 2020 12:55 am

I just made all this a lot clearer in the doc today: https://github.com/sethgoldin/install-d ... lve-centos

The part with the grub configuration had been confusing.

Sent from my iPhone using Tapatalk

Wed Jan 15, 2020 3:17 pm

Thanks Corey and Seth. I'll try this on my next free day off.

Despite having no linux experience, I actually found the document fairly easy to follow and it was less intimidating than I originally expected. It would be absolutely amazing if someone made a video walkthrough of the whole process as I did have to google quite a few things that were "in-between the lines" that would be obvious to anyone with 5 minutes of Linux experience. But, now I know at least some of the basics.

The only portion I skipped was 3ii "Set up DHCP", I did not see this anywhere during the initial setup screens where you choose GNOME etc.

Again, I'll let you know how it goes once I get a free weekend.

Cheers

Sat Feb 22, 2020 7:09 am

Nice guide! However I'm running in to a problem when installing DKMS, halts at 89% and says "Unable to load the 'nvidia-drm' kernel module." Tried this version and the https://sethgoldin.github.io/install-davinci-resolve-centos/centos-8.1.html with the same result. Any tips?

Edit: Isatlling on a laptop with dual Gpus, one intel and one Nvidia. if i skip DKMS it asks to be signed and says install successful. But it still does not load the nvidia driver when running nvidia-smi or nvidia-settings

Code: Select all: nvidia-installer log file '/var/log/nvidia-installer.log' creation time: Sat Feb 22 01:55:16 2020 installer version: 440.44 PATH: /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/root/bin nvidia-installer command line: ./nvidia-installer Using: nvidia-installer ncurses v6 user interface -> Detected 4 CPUs online; setting concurrency level to 4. -> Tagging shared libraries with chcon -t textrel_shlib_t. -> Installing NVIDIA driver version 440.44. -> Would you like to register the kernel module sources with DKMS? This will allow DKMS to automatically build a new module, if you install a different kernel later. (Answer: Yes) -> Install NVIDIA's 32-bit compatibility libraries? (Answer: Yes) Looking for install checker script at ./libglvnd_install_checker/check-libglvnd-install.sh executing: '/bin/sh ./libglvnd_install_checker/check-libglvnd-install.sh'... Checking for libglvnd installation. Checking libGLdispatch... Checking libGLdispatch dispatch table Checking call through libGLdispatch All OK libGLdispatch is OK Checking for libGLX libGLX is OK Checking for libEGL libEGL is OK Checking entrypoint library libOpenGL.so.0 Checking call through libGLdispatch Checking call through library libOpenGL.so.0 All OK Entrypoint library libOpenGL.so.0 is OK Checking entrypoint library libGL.so.1 Checking call through libGLdispatch Checking call through library libGL.so.1 All OK Entrypoint library libGL.so.1 is OK Found libglvnd libraries: libGL.so.1 libOpenGL.so.0 libEGL.so.1 libGLX.so.0 libGLdispatch.so.0 Missing libglvnd libraries: libglvnd appears to be installed. Will not install libglvnd libraries. -> Skipping GLVND file: "libOpenGL.so.0" -> Skipping GLVND file: "libOpenGL.so" -> Skipping GLVND file: "libGLESv1_CM.so.1.2.0" -> Skipping GLVND file: "libGLESv1_CM.so.1" -> Skipping GLVND file: "libGLESv1_CM.so" -> Skipping GLVND file: "libGLESv2.so.2.1.0" -> Skipping GLVND file: "libGLESv2.so.2" -> Skipping GLVND file: "libGLESv2.so" -> Skipping GLVND file: "libGLdispatch.so.0" -> Skipping GLVND file: "libGLX.so.0" -> Skipping GLVND file: "libGLX.so" -> Skipping GLVND file: "libGL.so.1.7.0" -> Skipping GLVND file: "libGL.so.1" -> Skipping GLVND file: "libGL.so" -> Skipping GLVND file: "libEGL.so.1.1.0" -> Skipping GLVND file: "libEGL.so.1" -> Skipping GLVND file: "libEGL.so" -> Skipping GLVND file: "./32/libOpenGL.so.0" -> Skipping GLVND file: "libOpenGL.so" -> Skipping GLVND file: "./32/libGLdispatch.so.0" -> Skipping GLVND file: "./32/libGLESv2.so.2.1.0" -> Skipping GLVND file: "libGLESv2.so.2" -> Skipping GLVND file: "libGLESv2.so" -> Skipping GLVND file: "./32/libGLESv1_CM.so.1.2.0" -> Skipping GLVND file: "libGLESv1_CM.so.1" -> Skipping GLVND file: "libGLESv1_CM.so" -> Skipping GLVND file: "./32/libGL.so.1.7.0" -> Skipping GLVND file: "libGL.so.1" -> Skipping GLVND file: "libGL.so" -> Skipping GLVND file: "./32/libGLX.so.0" -> Skipping GLVND file: "libGLX.so" -> Skipping GLVND file: "./32/libEGL.so.1.1.0" -> Skipping GLVND file: "libEGL.so.1" -> Skipping GLVND file: "libEGL.so" Will install libEGL vendor library config file to /usr/share/glvnd/egl_vendor.d -> Searching for conflicting files: -> done. -> Installing 'NVIDIA Accelerated Graphics Driver for Linux-x86_64' (440.44): executing: '/usr/bin/chcon -t textrel_shlib_t /usr/lib64/libnvidia-glcore.so.440.44'... executing: '/usr/bin/chcon -t textrel_shlib_t /usr/lib64/xorg/modules/extensions/libglxserver_nvidia.so.440.44'... executing: '/usr/bin/chcon -t textrel_shlib_t /usr/lib64/libnvidia-tls.so.440.44'... executing: '/usr/bin/chcon -t textrel_shlib_t /usr/lib64/libGLX_nvidia.so.440.44'... executing: '/usr/bin/chcon -t textrel_shlib_t /usr/lib64/libnvidia-glvkspirv.so.440.44'... executing: '/usr/bin/chcon -t textrel_shlib_t /usr/lib64/xorg/modules/drivers/nvidia_drv.so'... executing: '/usr/bin/chcon -t textrel_shlib_t /usr/lib64/libnvidia-gtk2.so.440.44'... executing: '/usr/bin/chcon -t textrel_shlib_t /usr/lib64/libnvidia-gtk3.so.440.44'... executing: '/usr/bin/chcon -t textrel_shlib_t /usr/lib64/libnvidia-cfg.so.440.44'... executing: '/usr/bin/chcon -t textrel_shlib_t /usr/lib64/libnvidia-ml.so.440.44'... executing: '/usr/bin/chcon -t textrel_shlib_t /usr/lib64/vdpau/libvdpau_nvidia.so.440.44'... executing: '/usr/bin/chcon -t textrel_shlib_t /usr/lib64/libcuda.so.440.44'... executing: '/usr/bin/chcon -t textrel_shlib_t /usr/lib64/libnvidia-opencl.so.440.44'... executing: '/usr/bin/chcon -t textrel_shlib_t /usr/lib64/libOpenCL.so.1.0.0'... executing: '/usr/bin/chcon -t textrel_shlib_t /usr/lib64/libnvidia-fatbinaryloader.so.440.44'... executing: '/usr/bin/chcon -t textrel_shlib_t /usr/lib64/libnvidia-ptxjitcompiler.so.440.44'... executing: '/usr/bin/chcon -t textrel_shlib_t /usr/lib64/libnvcuvid.so.440.44'... executing: '/usr/bin/chcon -t textrel_shlib_t /usr/lib64/libnvidia-encode.so.440.44'... executing: '/usr/bin/chcon -t textrel_shlib_t /usr/lib64/libnvidia-ifr.so.440.44'... executing: '/usr/bin/chcon -t textrel_shlib_t /usr/lib64/libnvidia-fbc.so.440.44'... executing: '/usr/bin/chcon -t textrel_shlib_t /usr/lib64/libnvidia-compiler.so.440.44'... executing: '/usr/bin/chcon -t textrel_shlib_t /usr/lib64/libnvidia-eglcore.so.440.44'... executing: '/usr/bin/chcon -t textrel_shlib_t /usr/lib64/libnvidia-glsi.so.440.44'... executing: '/usr/bin/chcon -t textrel_shlib_t /usr/lib64/libEGL_nvidia.so.440.44'... executing: '/usr/bin/chcon -t textrel_shlib_t /usr/lib64/libGLESv2_nvidia.so.440.44'... executing: '/usr/bin/chcon -t textrel_shlib_t /usr/lib64/libGLESv1_CM_nvidia.so.440.44'... executing: '/usr/bin/chcon -t textrel_shlib_t /usr/lib64/libnvidia-egl-wayland.so.1.1.4'... executing: '/usr/bin/chcon -t textrel_shlib_t /usr/lib64/libnvidia-allocator.so.440.44'... executing: '/usr/bin/chcon -t textrel_shlib_t /usr/lib64/libnvidia-rtcore.so.440.44'... executing: '/usr/bin/chcon -t textrel_shlib_t /usr/lib64/libnvidia-cbl.so.440.44'... executing: '/usr/bin/chcon -t textrel_shlib_t /usr/lib64/libnvoptix.so.440.44'... executing: '/usr/bin/chcon -t textrel_shlib_t /usr/lib64/libnvidia-opticalflow.so.440.44'... executing: '/usr/bin/chcon -t textrel_shlib_t /usr/lib/libcuda.so.440.44'... executing: '/usr/bin/chcon -t textrel_shlib_t /usr/lib/libnvidia-fatbinaryloader.so.440.44'... executing: '/usr/bin/chcon -t textrel_shlib_t /usr/lib/libnvidia-ptxjitcompiler.so.440.44'... executing: '/usr/bin/chcon -t textrel_shlib_t /usr/lib/libnvidia-ml.so.440.44'... executing: '/usr/bin/chcon -t textrel_shlib_t /usr/lib/libOpenCL.so.1.0.0'... executing: '/usr/bin/chcon -t textrel_shlib_t /usr/lib/libnvidia-compiler.so.440.44'... executing: '/usr/bin/chcon -t textrel_shlib_t /usr/lib/libnvidia-opencl.so.440.44'... executing: '/usr/bin/chcon -t textrel_shlib_t /usr/lib/libGLX_nvidia.so.440.44'... executing: '/usr/bin/chcon -t textrel_shlib_t /usr/lib/libnvidia-glcore.so.440.44'... executing: '/usr/bin/chcon -t textrel_shlib_t /usr/lib/libnvidia-tls.so.440.44'... executing: '/usr/bin/chcon -t textrel_shlib_t /usr/lib/libnvidia-glvkspirv.so.440.44'... executing: '/usr/bin/chcon -t textrel_shlib_t /usr/lib/vdpau/libvdpau_nvidia.so.440.44'... executing: '/usr/bin/chcon -t textrel_shlib_t /usr/lib/libnvcuvid.so.440.44'... executing: '/usr/bin/chcon -t textrel_shlib_t /usr/lib/libnvidia-encode.so.440.44'... executing: '/usr/bin/chcon -t textrel_shlib_t /usr/lib/libnvidia-eglcore.so.440.44'... executing: '/usr/bin/chcon -t textrel_shlib_t /usr/lib/libnvidia-glsi.so.440.44'... executing: '/usr/bin/chcon -t textrel_shlib_t /usr/lib/libEGL_nvidia.so.440.44'... executing: '/usr/bin/chcon -t textrel_shlib_t /usr/lib/libGLESv2_nvidia.so.440.44'... executing: '/usr/bin/chcon -t textrel_shlib_t /usr/lib/libGLESv1_CM_nvidia.so.440.44'... executing: '/usr/bin/chcon -t textrel_shlib_t /usr/lib/libnvidia-ifr.so.440.44'... executing: '/usr/bin/chcon -t textrel_shlib_t /usr/lib/libnvidia-fbc.so.440.44'... executing: '/usr/bin/chcon -t textrel_shlib_t /usr/lib/libnvidia-allocator.so.440.44'... executing: '/usr/bin/chcon -t textrel_shlib_t /usr/lib/libnvidia-opticalflow.so.440.44'... executing: '/usr/sbin/ldconfig'... -> done. -> Driver file installation is complete. -> Installing DKMS kernel module: -> done. ERROR: Unable to load the 'nvidia-drm' kernel module. ERROR: Installation has failed. Please see the file '/var/log/nvidia-installer.log' for details. You may find suggestions on fixing installation problems in the README available on the Linux driver download page at www.nvidia.com.

Thu Apr 02, 2020 4:06 pm

Great news! ELRepo has now packaged the NVIDIA drivers for RHEL/CentOS 8.1! The packages have been moved from the testing repo to the main repo, so the mirrors should have them now, or will have them very soon, as soon as they refresh. https://elrepo.org/bugs/view.php?id=944#c6874

Will update the 8.1 guide when I get physically get back to a workstation. Delayed by a COVID-19 lockdown.

How to install DaVinci Resolve on CentOS 8

How to install DaVinci Resolve on CentOS 8

Re: How to install DaVinci Resolve on CentOS 8

Re: How to install DaVinci Resolve on CentOS 8

Re: How to install DaVinci Resolve on CentOS 8

Re: How to install DaVinci Resolve on CentOS 8

Re: How to install DaVinci Resolve on CentOS 8

Re: How to install DaVinci Resolve on CentOS 8

Re: How to install DaVinci Resolve on CentOS 8

Re: How to install DaVinci Resolve on CentOS 8

Re: How to install DaVinci Resolve on CentOS 8

Re: How to install DaVinci Resolve on CentOS 8

Re: How to install DaVinci Resolve on CentOS 8

Re: How to install DaVinci Resolve on CentOS 8

Who is online