My question was if someone else have the same bug when doing whats described here: https://forum.blackmagicdesign.com/viewtopic.php?f=32&t=73490

After all this discussions about various Linux OS I guess all the CentOS users here can use the Fusion tab with fully GPU support and without any crashes.

BTW.Before I decided to fully switch from OSX to Linux, I tried CentOS and Fedora, but my old MacPro Hardware only gets all the needed drivers with Debian/Ubuntu. Next I will try the docker solution of Martin, hoping to get full GPU support.

I've found the Fusion tab to be very temperamental even under CentOS. Can't say I've done exactly what you describe but it sounds similar to my experience as well.

Sometimes I imagine it works better when I add nodes without having any other nodes selected so that they are not inserted into the chain automatically when they are added, and then connect them manually. Have you tried that?

Marc Gasser wrote:@Martin:Thanks. Struggling with installing nvidia-docker2, but I might get this solved...

the installation instructions on the nvidia-docker2 webpage will not work for debian testing, because the used command to get the version number does not work in this case. but you can work around by simple typing:

I've followed carefully the instructions at the first page of this topic (Ubuntu first , and then CentOS). In all the cases made clean installations of the OS's , and also updated to the latest GPU drivers.

Also run as "ldd /opt/resolve/bin/resolve " but 'libCg.so' and 'libCgGL.so' are not missing.

also found many users with similar issues, but their solutions didn't help. Even read that "the libCG and libCgGL errors can be safely ignored."

Thanks in advance for any reply, because I can't figure out how to run it.Maybe my GPU it's not supported by Resolve?

What needs to be done? I need it to work on Ubuntu, not CentOS but I think the same issue would come up on CentOS.Do I need to provide any more information or any other logs? If I do, please list the commands for the things you want me to check.

version 15.0b2 had this same issue but would show the splash screen and some initial setup but wouldn't bring up the editor and after that setup it wouldn't eve show the splash. 15.0b.4 doesn't show anything on the screen, I just get the logs when I run it trough cli.

Those libCg.so and libCgGL.so warnings plainly refer to unavailable version information, which basically means Resolve finds them and is puzzled. This is something that has cropped up in the 15 betas, and will hopefully be fixed by RC. But I doubt they are the genuine culprit.

I'd say the crashes are GPU-related. 14 often showed exact same behaviour, by allowing the user up to the Project Manager and crashing, with the unhelpful "ActCCMessage..." in the logs. The inherent problem was that it distracted people from the real issues, as I think those libs are doing now.

On 14, the issue generally went away by updating the graphics drivers, provided the GPU was sufficient to begin with. If both are good, we take a step further. AMD or Nvidia? A startup with CUDA requires OpenCL to be installed just as well, otherwise Resolve will abort the sequence. Really hope BMD would fix this nagging issue by now.

You have a Vega, so that's curious.

HealthWyzeMedia wrote:I am running Ubuntu 16.04, and I ran into the same problem. I fixed it and was able to run Davinci 15 by installing nvidia-modprobe (apt-get install nvidia-modprobe).

While the poster unfortunately failed to provide the used GPU, it's an interesting proposal. On it's own, nvidia-modprobe will load the Nvidia kernel module and exit. Which would be similar to OpenCL keeping up appearances in a Resolve/CUDA config.

Kristijan definitely faces some segmentation fault! that doesn't have much in common with misleading warnings and strange behavior. it's a much more serious issue. and it looks very unlikely, that anybody will be able to analyze the produced core dump without access to the source code or an unstripped debug version of the application.

I have Resolve 15b4 studio running OK (minor problems below) with Ubuntu Studio 17.10 on two machinesOne 2xCPU Xeon, one AMD Threadripper (have tried BMD Centos on both earlier with some problems, also a later 'clean' Centos with more problems...)Both machines with Nvidia 1080 ti

I had problems with Ubuntu Studio v16 and v18, complains in Resolve about missing Cuda, but OpenGL worked as much as I tried functionwiseFrom advise in this thread I downloaded the Cuda developer package from Nvidia, they didn't have Ubuntu v18 supportTried the Nvidia v17 support on Ubuntu Studio 16/18 - lots of problemBut with clean install Ubuntu Studio 17.10, Nvidia developer package for Ubuntu 17, it works!Also added their repo as instructed, now update brings newer Nvidia things down too

I let the Ubuntu Studio do a net update after install (did not allow it to fetch 3rd party things which might have caused problems in earlier tests)

Also installed BMD Desktop video 10.10 on the AMD (which has a BMD Decklink Mini Monitor 4k pci card), it complained about libpango, ran apt-get on that and tried again, works now!

When things seemed OK I also installed (apt-get) VLC and ffmpeg---Days later I have allowed Ubuntu to update again - after it finished it suggests me to go up to v18 which I refuse right now

Resolve studio works fine, video/sound out through SDi on AMD, sound to a headphone on Xeon---Remaining issues- The AMD included a pci 10 gbit ethernet card, doesn't work now, didn't work with Centos but it worked on Ubuntu Studio v18, no rush to fix it but performance will be better (not a BMD issue)

- None of the Linux machines work with the Micro grading panel, but it works fine on an iMac 5k with v15b4 studio - not sure how to search for the problem - tips?Both Linux accept the dongle, the AMD was even installed via extern DVD to USB so I know USB is active on both and I've tested both USB 2/3 ports

- The AMD with Decklink Mini Monitor 4k pci card doesn't output sound with the video via HDMI, but via SDI it doesWhile testing with a BMD Video Assist 7" which has both SDI and HDMI in/out I can hear and see sound level from SDIJust by intuition (or whatever I tried the HDMI out to TV in the Video Assist when it received via SDI - and it outputs sound on HDMI too!!!Seems to be a bug by BMD, the card obviously receives sound, why not output sound on both...

---Positive things:- Stabilisation flies on 4k from drone and Sony RX10, same things on the iMac is so slow...- Playing things graded on both Linux just plays, iMac quick to stutter with just few nodesAll three machines have SSD, right now resolve just use the system SSD on all three---Kristijan

I have a spare disk ready, easy for me to repeat/confirm a clean installationPlease make a try as above, tell me if you get stuck/how/where and I can do a repeat install on one of the machines and take more detailed notes

Sulo, Martin, Bjorn I don't think installing any Nvidia specific software will help since I run AMD Radeon RX Vega 64 Liquid 8GB gpu. It might get Resolve to show up in the gui but won't work correctly since the workaround would just be a hack to fool Resolve into thinking it has some deps which won't actually do anything?

I forgot to mention explicitly that I am running the open source amdgpu driver from the kernel.The support for Ubuntu 18.04 is coming in the amdgpu-pro 18.20 but that driver is still in early preview.I don't thing it supports OpenCL but it will come with ROCM which is a thing worth exploring for running Resolve with Vega.

I don't know who the maintainer of that script is but I was thinking if it would be possible to create a DaVinci Resolve Snap package. That way it would basically be a sandboxed application with all dependencies and paths included in the snap package so it wouldn't conflict or complain on any distro.

The thing is, I'm not really that technical and that's why I'm not doing it already. I basically know how to package a node snap and that's it.For anyone else willing to explore this route here is the link to snap package and it's tool snapcraft's page

Sulo, Martin, Bjorn I don't think installing any Nvidia specific software will help since I run AMD Radeon RX Vega 64 Liquid 8GB gpu. It might get Resolve to show up in the gui but won't work correctly since the workaround would just be a hack to fool Resolve into thinking it has some deps which won't actually do anything?

I forgot to mention explicitly that I am running the open source amdgpu driver from the kernel.The support for Ubuntu 18.04 is coming in the amdgpu-pro 18.20 but that driver is still in early preview.I don't thing it supports OpenCL but it will come with ROCM which is a thing worth exploring for running Resolve with Vega.

I don't know who the maintainer of that script is but I was thinking if it would be possible to create a DaVinci Resolve Snap package. That way it would basically be a sandboxed application with all dependencies and paths included in the snap package so it wouldn't conflict or complain on any distro.

The thing is, I'm not really that technical and that's why I'm not doing it already. I basically know how to package a node snap and that's it.For anyone else willing to explore this route here is the link to snap package and it's tool snapcraft's page

KristijanZic, I'm afraid you still need to have CUDA installed for Resolve to run properly even if you are running OpenCL and vice versa.

Also, that script you linked to looks like a modified version of my makeresolvedeb. Please use the latest makeresolvedeb from this thread (links to related posts are on the first post) or from my website http://www.danieltufvesson.com/makeresolvedeb

Peter, I hope that's not the case with everyone. I have projects to complete, what good is the community support if I can't get it immediately while I'm working on the issue. 3 days later is unacceptable. This delay greatly impacts the UX of this forum in the negative way. I would hope for BM to at least open a Discourse forum for Linux users or even better for all users. Discourse has great anti spam capabilities like "Built in Akismet spam protection and heuristics including new user sandboxing, user flag blocking, and standard nofollow." so for me it would be a no-brainer decision. So you could focus on Linux compatibility rather than forum maintenance.

The absolute best thing would be to accept bug reports on an empty GitLab repository or something like that. This one forum thread is not good for the purpose it's being used for.

Daniel, thank you so much for the script. Could you please open a GitLab repository and host it there? That way you could accept patches and pull requests from other people who may be willing to help. Plus every paid GitLab feature is free for open source repositories unlike GitHub.

Also, a good idea would be if you could just replace all script text version numbers and DaVinci Resolve text version numbers with two javascript variables, that way instead of changing the string on the download button on your website, you could just change those two variables and every version number on that page would be updated.

KristijanZic wrote:Peter, I hope that's not the case with everyone. I have projects to complete, what good is the community support if I can't get it immediately while I'm working on the issue. 3 days later is unacceptable.

Every new user’s first post is moderated. This is pretty standard across phpBB forums. If you are looking for responsive feedback, keep in mind your post was on a Friday and BMD is an Australian company. I don’t know your time zone but your post might have ended up on the weekend for them.

I realised that when I removed the opencl-mesa package from my system (and keep compute-runtime, Intel opencl driver for its gpu) I reach the splashscreen, but then I have an error message that says no supported graphic card was found.

Looks like my Intel GPU is not supported.What I don't understand is why when I have the right opencl driver for my second GPU (Radeon) it stops at the "Updating display GPU information..." step.

I have PRIME installed and running properly on my machine (I can start programs to use the main GPU instead of Intel's), and this problem happens also when I force Resolve to start on the main GPU (with DRI_PRIME=1 environment variable).

I'm going to try more combination (like removing compute-engine and keeping only opencl-mesa) but I'm a bit at loss I have to admit.

Neil Preston wrote:I take it from this then that its not a problem with my installation. These codecs are just not supported and the only solution is to transcode. is this likely to change in future 15 beta releases?

Glad I could point you in the right direction. I and others do hope that it’s something that does change in the future, it is really annoying to have to do far more transcoding than our Win/macOS counterparts. But if it’s in the cards BMD employees are keeping their mouths sealed in a nuclear bunker several miles under the ice caps.

While I realize that Resolve was intended for high level use and not for consumer use, now that it does support mp4 and mts video it seems obvious that audio codecs must follow for Linux systems.

I have thousands of mp4 and mts clips filmed over long periods that I would like to edit, but it’s seems unnecessary to spend the time transcoding them if the capability will soon be available in Linux. To ask for some indication of when this might happen is understandaable. I know I can do this in Windows, but I have waited for years for the right Linux based software. I have bought an unlock key for Resolve Studio and I now want to get away from Windows.

The recent price reduction for Resolve Studio has made Resolve available to a much wide range of users including amateurs and hobbyists like myself who want to raise their level of work.

I agree that MakeResolveDeb could be made more universal and, at least in theory, be made to support both current and future versions of Resolve.

The tricky thing with that approach is test and verification. BMD may at any point change things in Resolve or the installer that can cause the conversion to fail in one way of the other.

What I offer to the community is that I stand behind my product and I maintain it for free for everyone to use. Whenever there is a new release of Resolve I manually go through new installer, track the eventual changes and test *.deb creation and installation of Resolve and Resolve Studio on several Debian based distributions. All my versions of MakeResolveDeb are verified working on my test setups before they are released. It may take a little bit of extra time for me to do this however.

I get questions daily about Resolve and Debian, and it's taking up more and more of my spare time. By limiting every release to a specific Resolve version life gets a little bit easier for me and it ends up being more reliable for the end user as well.

My focus has been to provide something that just works for now with the hopes that BMD will address this situation in the future. Hope you understand.

It installed Resolve 15.ob5 beta with no problems and it is looking good.

I hope that my last post did not give the impression that I was implying that you should fix the AAC audio problems in your deb packages. What I was trying to say was that we would like BMD to give us an estimate of when they expect the audio problems to be rectified, i.e, a sort of roadmap.

I understand that you cannot alter their software, but that your debs are taking care of the technicalities of ensuring that each new beta of Resolve installs correctly on Debian and Ubuntu based distributions, for those of us who don’t have the necessary knowledge to do it.

Daniel Tufvesson wrote:The tricky thing with that approach is test and verification. BMD may at any point change things in Resolve or the installer that can cause the conversion to fail in one way of the other.

yes -- that's indeed a very important point!

i was also puzzling over this issue, how i could test my resolve containers automatically by typical CI/CD means? until now i couldn't figure out a satisfaying solution. it's very hard to provide the required hardware preconditions to successfully start resolve in this kind of typical DevOps environments somewhere in the cloud and examine at least a few elementary test automatically. but even if we could figure out a minimalist setup, which would work, it hardly could be taken as a representative inspection, because most of the real world troubles are at least partially caused by the interplay with various graphic cards and their proprietary drivers and can not be realistically tested in this kind of synthetic envrionments...

Does installing the driver yourself not work? I never use repository modules, always do it by hand. It’s a bit easier to manage in CentOS land as the kernel doesn’t change often and DKMS saves things from breaking completely. I realize not everyone will agree with this strategy, however.

Cheers,Mike

Last edited by MikeRochefort on Mon Jul 02, 2018 8:53 pm, edited 1 time in total.

OPERATION:DaVinci starts up nicely, shows 1xGPU as AMD RX550. I can edit UHD, grade, playback..shows Fusion tab but didn't want to push it too much till I add some more memory. Actually rocks along much better than expected Even the AMD RX 550 OpenCL seems very fast and so far quite stable. A surprise was that DR spans both DVI & HDMI GUI monitors perfectly without any setup or effort.

ISSUES: * playback audio sometimes dropping out over Intensity HDMI audio output. * h.265/HEVC UHD source footage is "very slow" to playback compared with h.264 (realtime) (probably since h.265/HEVC decoding is not GPU accelerated compared to my iMac where the i7/MacOS does super fast hardware h.265 (macOS->Intel iGPU) decode/encode. I expected DR would do the HEVC hardware decode via the system GPU(s). Checking with Linux VLC, they use the VDPAU (AMD/nVidia/Intel) API seems available for HEVC hardware decoding (and appears encoding) but Linux DR15b6 does not appear to use it - BMB DR dev team - possible Linux version enhancement * DaVinci crashed with a log about Fusion server disconnected when I set a non-typical or >SD Playback resolution and frame rate for Intensity. I did install the v10.11 DEB package latest BMD Desktop Video suite. I'm guessing system/GPU memory shortage to do so much ? I had to remove the Intensity card, restart Resolve and reduce & save the playback resolution playback setting to NTSC, than re-installl the Intensity card and we seemed good.* DR pops up a Report Problem box every time I quit DR app normally, but nothing failed ?* Both DR v15b5 or b6 can not send out the email for Report Problem popup box. Firefox on the same box works. The onscreen error message says: Unable to connect. Please check your network connectivity and try again. Hmmm ?

INSTALLATION:Install was easy - need the libssl dependancy & sym linking, note: target dir: is /usr/lib on Linux Mint. Also installed the xserver-xorg-hwe as discussed in many places. Months ago I did tried to install DaVinci Resolve v14_free on Linux Mint 18 and gave up - too many OS/GPU bits not working, even the RX550 was a mess, and finally no Open CL. Besides even working, I expect DR on Linux on a modern system would really rock for little $. Great job BMD team !

AMD GPU Caution Note:Sadly I learnt the hard way that my RX550 is not supported by macOS High Sierra due to the possibility that the card can have one of either chipset that is not easily recognised from the retail packaging - one RX550 uses the Lexa chip (PCI DeviceID: 0x699F) (which isn't supported in macOS, but is in Windows and Linux, and the other RX550 uses the Baffin chip (PCI DeviceID: 0x67FF) which is supported in macOS.

It's also here on my website along with some more detailed instructions.

This time my testing took a bit longer that usual. Mostly because of other work but also because I discovered an audio related problem in one of my test setups that I in the end realized I've had all along everywhere.

Resolve appears to be constantly creating and destroying it's audio connection when I run Pulseaudio+ALSA. This can happen hundreds of times per second and may cause audio glitches and impact real-time playback performance. I'm currently having a bit of a struggle deciphering the Pulseaudio debug log.

[EDIT] Also : each time I quit the app, it crashes. I'll be glad to send a report, but you'll have to tell me how And is there a way to use the audio with something else than Alsa or Pulseaudio, if it is the issue ? (When I open the sound pref, in the Application tab, I can see the Alsa Resolve plug, but it seems to be unstable : the icon is flickering...). Which could be also related to the issue noted by Daniel.

But anyway, it seems to be pretty close to a working solution for Resolve on a main distro...

The audio situation described by Alexandre sounds exactly like what I'm seeing also. The flickering is very familiar. I'm actually not sure when it started but I have verified that the problem exist in both b5 and b6.

As far as I know Resolve only uses ALSA for system audio. The Decklink output works fine though.

The "Resolve quit unexpectedly" situation is known. It happens on all distributions. I think the best workaround for now is to uncheck "Send report when application quits unexpectedly" in general preferences.

The full screen viewer goes black for me as well in b6. In b5 it works.

So Resolve doesn't like h.264 on Linux. Seems like this is unavoidable until BMD decides to add support.

One of my cameras (a Canon T3i) records h.264 and there's no getting out of it. Anyone have a good, reliable ffmpeg command to run so I can transcode footage to DNxHD or ProRes? I've tried fiddling with the settings and I can never get it to work right.

Hi folks.I'm testing out Resolve 15b6 (and if I get it to work well enough I may even invest in this), but have trouble getting it to start from Ubuntu Studio 18.04. (Sales guys, please: Good video editors for Linux are rare, and I'm not very fond of the alternatives. Which I believe to be a market segment, and yes people like me will pay if it's good enough.)

But I get segmentation fault when I'm trying to run it. My GPU is an Nvidia Quadro K5200 (i really needed the drivers), running on top of an AMD APU (which has it's own small video support) but that shouldn't run now with the NVIDIA GPU.

I ran Daniels makeresolvedeb, latest edition, and installed the deb. I also read the start of this thread and ldd claims there are no missing libraries. When it comes to logs, rollinglogs.txt reports some hundred lines of

Hmm. nvidia-opencl-icd is a virtual package pointing to either libnvidia-compute-390 390.48-0ubuntu3, that I have already installed, or nvidia-opencl-icd-340 340.106-0ubuntu3, which seems like a deprecated version.It seems ubuntu has renamed the package, for whatever reason.

I can try reinstalling libnvidia-compute-390, as I have a faulty drive (and the new one is still in the mail), so I may have lost some files. It breaks the whole package hierarchy for the nvidia drivers however, so I'll wait till I'm ready for reboot.

you should perhaps try the 'clinfo' command, to get some report about the available/working OpenCL services on your system.

it maybe related to nvideo opencl installation, but it could be also very likely caused by the AMD components. mixed GPU setups are always rather error prone.

That was interesting, yes.Running clinfo gave Number of platforms 0no matter if I ran it as clinfo -a, clinfo -a --offline or using sudo.Seems there was nothing registered to run opencl, despite the whole nvidia driver repository being installed (sans some i386 packages).

So I wonder what has happened here.The package nvidia-opencl-icd-384 is a transitional package depending on nvidia-headless-390, and that's the last we've seen of that. Has the Nvidia Opencl library been lost somehow?

and this section also doesn't look like the proprietary nvidia-driver.

maybe you didn't blacklist the open source "nouveau" driver module and it blocks the initialization of the proprietary nvidia-driver? this is usually not necessary, if you use the distribution specific nvidia-driver installation packages, because they handle most of this tasks for you, but it could be necessary, if you used the nvidia original installer or messed up your system by any similar manual installation action. anyhow you'll need the proprietary nvidia driver to run resolve, not noveau!

haraldthi wrote:The package nvidia-opencl-icd-384 is a transitional package depending on nvidia-headless-390, and that's the last we've seen of that. Has the Nvidia Opencl library been lost somehow?

i use debian testing instead of ubuntu, therefore i can not tell you the exact packages names and working versions, but on debian you only need:

nvidia-kernel-dkms libcudart9.1 nvidia-opencl-icd

and all their "required" dependencies... -- and you can even avoid the installation of the nvidia specific xserver packages by more restrictive installation commands, if you don't use the nvidea cards for the actual video output.