- Posts: 3
- Joined: Wed Apr 14, 2021 10:59 am
- Real Name: Fred Cooke
I found this:
Which would be really sad news for me and also contradicts this:
But aligns with this:
Which I'm forced to paraphrase:
I wasn't expecting stellar performance But having it work at all would be good.
Since then I went on a binge of installing different versions:
16.2.6 (pre nvidia-only "requirement")
16.2.8 (post that "requirement", latest 16.X version)
16.2.3 (original one that I tried a while back)
17.1.1 (latest one)
Different bad behaviour. Some seem to get close then crash, others just straight crash.
As a professional software developer with 30 years coding in all sorts of languages from embedded to web front end and bank backends and all sorts of other stuff, that I understand even less. Come up cleanly, scan for the OS/HW features you need, report to the user that they're not there, tell them what is there, tell them why it's not okay, refuse to enter the app further. Don't fail to come up and look bad for crashing immediately because of hard coded assumptions about the execution environment.
Is an understatement
Looked everywhere as advised, found not much. Especially not given the encouraging "hey, your gpu is a bit slow, but it should work" output from the app itself during the setup sequence (when that works).
I also upgraded to 18.04 Ubuntu and upgraded a spare machine to 20.04 (however that's a bit of a train wreck for various reasons so won't be on this machine any time soon).
18.04 didn't help.
I had high hopes for this and might try again in future or if anyone has any tips/ideas/etc, but the only app that ever sold me on going proprietary has so far let me down. Oh well, it was worth a shot!
Thanks for your work, Daniel! Appreciated.
Dwaine Maggart wrote:Resolve 16.2.7 and higher requires an NVIDIA GPU with CUDA Compute Capability of 3.5 or higher.
The GTX 750Ti has 5.0 Compute Capability. So there is no issue with the card from that standpoint.
The CUDA wiki has a handy chart of the compute capability of various NVIDIA cards:
https://en.wikipedia.org/wiki/CUDA
Which would be really sad news for me and also contradicts this:
Daniel Tufvesson wrote:Running Resolve using an Intel GPU under Linux is unsupported but this situation has improved slightly for Resolve 17 and Resolve now starts but performance and stability can not be guaranteed.
But aligns with this:
Peter Chamberlain wrote:Can you install a much more powerful GPU?
Which I'm forced to paraphrase:
NOT Peter Chamberlain wrote:Our software isn't written to be reliable, only to be fast, without a powerful GPU it will crash!
I wasn't expecting stellar performance But having it work at all would be good.
Since then I went on a binge of installing different versions:
16.2.6 (pre nvidia-only "requirement")
16.2.8 (post that "requirement", latest 16.X version)
16.2.3 (original one that I tried a while back)
17.1.1 (latest one)
Different bad behaviour. Some seem to get close then crash, others just straight crash.
As a professional software developer with 30 years coding in all sorts of languages from embedded to web front end and bank backends and all sorts of other stuff, that I understand even less. Come up cleanly, scan for the OS/HW features you need, report to the user that they're not there, tell them what is there, tell them why it's not okay, refuse to enter the app further. Don't fail to come up and look bad for crashing immediately because of hard coded assumptions about the execution environment.
Daniel Tufvesson wrote:Resolve is quite picky when it comes to GPU drivers and versions. Make sure you have working CUDA and OpenCL libraries installed.
Is an understatement
Daniel Tufvesson wrote:Segmentation fault on startup or abrupt exit before reaching the project window usually means missing GPU drivers, unsupported GPU driver version or unsupported GPU hardware. Check log files for clues.
Looked everywhere as advised, found not much. Especially not given the encouraging "hey, your gpu is a bit slow, but it should work" output from the app itself during the setup sequence (when that works).
I also upgraded to 18.04 Ubuntu and upgraded a spare machine to 20.04 (however that's a bit of a train wreck for various reasons so won't be on this machine any time soon).
18.04 didn't help.
I had high hopes for this and might try again in future or if anyone has any tips/ideas/etc, but the only app that ever sold me on going proprietary has so far let me down. Oh well, it was worth a shot!
Thanks for your work, Daniel! Appreciated.
Shoot: GH5, GX9, GM5, GM1, GF1, OP3T, OP5T
Edit: 9th i9 8c/16t, Intel UHD 630 IGPU, 32GB, NVMe x2 (1.5TB total + NAS)
S/W: Lubuntu 16.04 + HWE Kernel/Xorg + Intel OpenCL + makeresolvedeb
Monitor: Samsung S32D850T WQHD/1440p
Edit: 9th i9 8c/16t, Intel UHD 630 IGPU, 32GB, NVMe x2 (1.5TB total + NAS)
S/W: Lubuntu 16.04 + HWE Kernel/Xorg + Intel OpenCL + makeresolvedeb
Monitor: Samsung S32D850T WQHD/1440p