A guide on how to install DaVinci Resolve on CentOS Linux
Here are some notes on how to install DaVinci Resolve on CentOS 7.6. Though Blackmagic Design distributes a build of CentOS that’s pre-installed with DaVinci Resolve and some other software required for DaVinci Resolve to run, Blackmagic Design’s build can’t be used to create a bootable USB drive—it can only be used to create a DVD. Upstream builds of “generic” CentOS straight from the CentOS project suffer no such limitation.
Because software is constantly changing, this document is hosted on GitHub Pages. If you find something wrong or outdated, please do open a pull request.
These particular notes were originally worked out from installations to multiple HP Z8 G4 workstations with single GTX 1080 Ti cards installed, but the information should be useful for other x86_64 systems as well.
rootaccount and create just one administrator account
Install the kernel source:
$ sudo yum install "kernel-devel-uname-r == $(uname -r)"
$ sudo yum install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm
$ sudo yum install dkms
Import the GPG key:
$ sudo rpm --import https://www.elrepo.org/RPM-GPG-KEY-elrepo.org
Install for CentOS 7:
$ sudo rpm -Uvh http://www.elrepo.org/elrepo-release-7.0-3.el7.elrepo.noarch.rpm
Installing EPEL should have downloaded and installed
gcc, but just in case, make sure:
$ sudo yum install gcc
Install NVIDIA driver from ElRepo:
$ sudo yum install kmod-nvidia-390xx.x86_64
Download and install the latest DeckLink driver
$ su -
When prompted, enter your
root user’s password.
If you already have an older DeckLink driver installed, uninstall it:
# rpm -qa | grep desktopvideo | xargs rpm -e
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
cd into the
rpm folder, since this is CentOS
# cd /Blackmagic_Desktop_Video_Linux_<driver_version>/rpm/<yourarchitecture>
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
The installer might fail and tell you that you
libGLU.so.1, so install
libGLU and try again:
# yum install mesa-libGLU
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
DaVinci_Resolve_Studio_15.3_Linux.zip(if you have a DaVinci Resolve license dongle or key) or
DaVinci_Resolve_15.3_Linux.zipfrom the Blackmagic Design website.
.runfile to use the GUI installer
/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
Install the repository RPM:
$ sudo yum install yum install https://download.postgresql.org/pub/repos/yum/reporpms/EL-7-x86_64/pgdg-redhat-repo-latest.noarch.rpm
Install the client packages:
$ sudo yum install postgresql95
Install the server packages:
$ sudo yum install postgresql95-server
Initialize the database and enable automatic start:
$ sudo /usr/pgsql-9.5/bin/postgresql95-setup initdb $ sudo systemctl enable postgresql-9.5 $ sudo systemctl start postgresql-9.5
$ ifconfig aor
$ ip ato view the name of the connected ethernet device.
Modify the specific parameters:
BOOTPROTO=none # Here, after the =, you can enter whatever you had previously with DHCP, since we know that the address assigned via DHCP worked IPADDR=<yourIPaddress> # Here's the subnet mask. Mine is 255.255.255.0, but your network might be different NETMASK=255.255.255.0 # This one is going to depend on your particular router. Check your router GATEWAY=<yourgatewayIPaddress> # This will depend on your ISP. Since mine is Comcast, I use 126.96.36.199 DNS1=188.8.131.52 DEFROUTE=yes IPV4_FAILURE_FATAL=no # Disable IPv6 IPV6INIT=no # Activate on Boot ONBOOT=yes
Restart the network service for these changes to take effect.
$ sudo systemctl restart network
$ sudo su - postgres
# cd 9.5/data/
If you check
# pwd, you’ll see that you’re in
Make a copy of
pg_hba.conf, just in case anything goes wrong:
# cp pg_hba.conf pg_hba.conf.backup
pg_hba.conf and modify it so as to enable sharing by adding in this line to the very bottom of the file:
host all all <your workstation's static IP>/24 md5
postgresql.conf to allow incoming TCP/IP sockets:
Scroll all the way to the bottom, and add the uncommented line:
listen_addresses = '*'
Create a password for the user
postgres by entering:
psqlshell will prompt you to reenter the password to confirm that you’ve typed it correctly.
psqlshell by entering
postgressuperuser and get back to your regular user account by entering
Disable and stop the default CentOS firewall:
$ sudo systemctl disable firewalld $ sudo systemctl stop firewalld
Reboot the system.
cat /etc/services | grep 5432
You should see:
``` postgres 5432/tcp postgresql # POSTGRES postgres 5432/udp postgresql # POSTGRES ```
This means that PostgreSQL is good to go through port 5432.
You can also check:
$ netstat -tulpn | grep 5432
Which should show that
0.0.0.0:5432 is good to go for TCP.
$ service postgresql-9.5 status
Here you’ll see some information about how TCP connections are listening through port 5432, with IPv4 IP addresses:
```tcp 0 0 0.0.0.0:5432 0.0.0.0:* LISTEN```