A few years ago I wrote a post on this when I managed to solve the problem... then I wasn't really using DaVinci Resolve for a while. Fast forward to today, I was happy that Linux Mint has updated to 22, and DaVinci Resolve has grown to be 19 (beta), I thought things would become easier but nope, not at all! After naively trusting things would work like a charm, I managed to destroy my newly installed Linux Mint 22 with all things extra copied and configured nicely to my satisfaction, only to discover installing libraries required for DaVinci Resolve 19 Beta would totally destroy the whole booting process! Now I am forced to reinstall Linux Mint 22 totally from scratch, the first thing I do is to fix DaVinci Resolve first and this time I am going to do my research, experiment, and write things down!
My hardware for your reference:
1. Make DaVinci Resolve a deb for Linux Mint
If you go to DaVinci Resolve's website for download, you will find the linux version ends with .run which is made for CentOS and not debian system, such as Ubuntu or Linux Mint. Daniel Tufvesson has done a good job making a tool to convert it. Here is the link.
https://www.danieltufvesson.com/makeresolvedeb
Follow the instruction there, until you get the deb.
2. run script
sudo apt install build-essential checkinstall
3. add your user to the video and the render group
sudo usermod -a -G render,video [username]
4. install ROCm
Reference: https://rocm.docs.amd.com/projects/install-on-linux/en/latest/install/native-install/ubuntu.html
You don't need to install kernel driver, just the ones that are needed.
4.1 Package signing key
Download and convert the package signing key.
# Make the directory if it doesn't exist yet.
# This location is recommended by the distribution maintainers.
sudo mkdir --parents --mode=0755 /etc/apt/keyrings
# Download the key, convert the signing-key to a full
# keyring required by apt and store in the keyring directory
wget https://repo.radeon.com/rocm/rocm.gpg.key -O - | \
gpg --dearmor | sudo tee /etc/apt/keyrings/rocm.gpg > /dev/null
4.2 Register ROCm packages
Add the ROCm repository.Makes sure it is ubuntu 24.04 as that's what LM22 is based on.
echo "deb [arch=amd64 signed-by=/etc/apt/keyrings/rocm.gpg] https://repo.radeon.com/rocm/apt/6.2 noble main" \
| sudo tee --append /etc/apt/sources.list.d/rocm.list
echo -e 'Package: *\nPin: release o=repo.radeon.com\nPin-Priority: 600' \
| sudo tee /etc/apt/preferences.d/rocm-pin-600
sudo apt update
4.3 install the rocm6.2 (this might take a bit time)
sudo apt install rocm-libs6.2.0 rocm-opencl-sdk6.2.0 rocminfo6.2.0
5. add /opt/rocm/bin to your PATH
6. reboot
7. now we need to install the deb
sudo dpkg -i davinci-resolve_19.0b6-mrd1.7.1_amd64.deb
8. start the program
By now you should see the davinci resolve buttons shown up in the menu like below. However, if you click on them it will not work.
Because it ships versions of some system libraries that are incompatible with current Linux Mint. But these libraries exist on your system, so you can force Resolve to use the ones provided by the system rather than it's own. Additionally it won't find your graphics card unless it looks for libraries in the rocm directory. Use this command to start DaVinci Resolve:
LD_PRELOAD=/lib/x86_64-linux-gnu/libglib-2.0.so.0:/lib/x86_64-linux-gnu/libgio-2.0.so.0:/lib/x86_64-linux-gnu/libgdk_pixbuf-2.0.so.0:/lib/x86_64-linux-gnu/libgmodule-2.0.so.0 LD_LIBRARY_PATH=/opt/rocm/lib /opt/resolve/bin/resolve
then you get something like this:
9. change menu entry
On the menu, find Sound & Video -> DaVinci Resolve -> right click and in the dropdown you will find Properties, click on that -> A window will show up, you will find an input called command, paste the following command into that input. Now when you click this button in the menu, DaVinci Resolve will finally start as expected!
env LD_PRELOAD=/lib/x86_64-linux-gnu/libglib-2.0.so.0:/lib/x86_64-linux-gnu/libgio-2.0.so.0:/lib/x86_64-linux-gnu/libgdk_pixbuf-2.0.so.0:/lib/x86_64-linux-gnu/libgmodule-2.0.so.0 LD_LIBRARY_PATH=/opt/rocm/lib /opt/resolve/bin/resolve
Voila that's it...Now I only hope things will run from now on.
Top comments (0)