DaVinci Resolve on Debian Linux (and makeresolvedeb)

I found this:

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:

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:

Can you install a much more powerful GPU?

Which I'm forced to paraphrase:

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.

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

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.

Not sure if you've ever worked with OpenCL but having written some software for it, most driver just plain suck and _lie_ to the application. Reporting some capabilities as supported then when you try to use something that's required to be compliant just returns NULL or some invalid value that's not allowed per the spec ...

"Unsupported GPU Processing Mode" on Ubuntu 20.04.2 LTS

Hi, I am a noob so hopefully this post is not annoying. I am updating this post but still have the problems.

Everything was working fine using DRS17.1 on Ubuntu 20.04.1 LTS.
I had installed using the "3rd party" option which installed the nividia graphics drivers fine.
However, I upgraded to 20.04.2 and also used the makeresolvedeb 1.5 script to upgrade to DRS 17.1.1.
I must have done something wrong because even though my monitor works fine with 4k, DRS 17.1.1 won't open responding:

Unsupported GPU Processing Mode
Please review the GPU drivers and GPU configuration under preferences.

When I do that, I see that there is no GPU listed under "GPU Configuration" of "Memory and GPU"
I read some other posts but they related to Win 10.
One post recommended that I run:

Code: Select all

~$ apt list --installed | grep 460

which returned

Code: Select all

WARNING: apt does not have a stable CLI interface. Use with caution in scripts

as well as a bunch of ubuntu0.20.04.1 files including
libnividia-compute as well as nvidia-computer-utils
Strange to see 20.04.1 files when I am supposedly in 20.04.2.

I was told by the maker of makeresolvedeb that it is not necessary to uninstall or remove the license of an existing DRS version to update it so that is unlikely the cause of the error.
He directed me to run

Code: Select all

dpkg -l | grep nvidia

which seemed to show that

Code: Select all

ii nvidia-driver-460 460.39-0ubuntu0.20.04.1 amd64 NVIDIA driver metapackage

is installed.

Furthermore, under "Settings > Software & Updates > Additional Drivers > NVIDIA Corporation: Unknown" the box saying "Using NVIDIA driver metapackage from nvidia-driver-460 (proprietary)" is checked. And it says "1 proprietary driver in use"

Does the fact that it is 20.04.1 version versus the 20.04.2 that I actually have matter?
I am a bit stuck.
Because it seems that is should work or at least there should be the driver listed under the GPU window on Resolve.

BTW, if I were to want to completely uninstall one version of DRS on Ubuntu, how would I do that?

I have no intention of going back to Win 10 which had even more problems IMO.
Thanks for your help in advance.

Try running `clinfo`and make sure the card show up there.

It's kind of dumb but even if you're using CUDA, the OpenCL drivers need to be installed and working because it seems that's how Resolve detects what GPU are available ...

Try running `clinfo`and make sure the card show up there.

NO, clinfo returns:

Code: Select all

Number of platforms      0

I thought lsmod found out the drivers? That shows that I have the correct r8125 module/driver for my RTX 3070 graphics card

the OpenCL drivers need to be installed and working because it seems that's how Resolve detects what GPU are available ...

This seems similar to the problem seen by some Blender folk with the RTX 3070
https://developer.blender.org/T82603

I am a noob so not too familiar with OpenCL drivers (https://developer.nvidia.com/opencl)
Do I go to Nvidia to get the "OpenCL" drivers for the 3070 that I have?
Thanks for your help and advice.

Theses are the packages I have installed :

Also check you have `/etc/OpenCL/vendors/nvidia.icd`

Code: Select all

$ apt list --installed | grep nvidia

WARNING: apt does not have a stable CLI interface. Use with caution in scripts.

libnvidia-cfg1-460/focal-updates,focal-security,now 460.73.01-0ubuntu0.20.04.1 amd64 [installed]
libnvidia-common-460/focal-updates,focal-updates,focal-security,focal-security,now 460.73.01-0ubuntu0.20.04.1 all [installed,automatic]
libnvidia-compute-460/focal-updates,focal-security,now 460.73.01-0ubuntu0.20.04.1 amd64 [installed,automatic]
libnvidia-decode-460/focal-updates,focal-security,now 460.73.01-0ubuntu0.20.04.1 amd64 [installed]
libnvidia-encode-460/focal-updates,focal-security,now 460.73.01-0ubuntu0.20.04.1 amd64 [installed]
libnvidia-extra-460/focal-updates,focal-security,now 460.73.01-0ubuntu0.20.04.1 amd64 [installed,automatic]
libnvidia-fbc1-460/focal-updates,focal-security,now 460.73.01-0ubuntu0.20.04.1 amd64 [installed]
libnvidia-fbc1-460/focal-updates,focal-security,now 460.73.01-0ubuntu0.20.04.1 i386 [installed,automatic]
libnvidia-gl-460/focal-updates,focal-security,now 460.73.01-0ubuntu0.20.04.1 amd64 [installed]
libnvidia-gl-460/focal-updates,focal-security,now 460.73.01-0ubuntu0.20.04.1 i386 [installed,automatic]
libnvidia-ifr1-460/focal-updates,focal-security,now 460.73.01-0ubuntu0.20.04.1 amd64 [installed]
libnvidia-ifr1-460/focal-updates,focal-security,now 460.73.01-0ubuntu0.20.04.1 i386 [installed,automatic]
nvidia-compute-utils-460/focal-updates,focal-security,now 460.73.01-0ubuntu0.20.04.1 amd64 [installed]
nvidia-dkms-460/focal-updates,focal-security,now 460.73.01-0ubuntu0.20.04.1 amd64 [installed,automatic]
nvidia-driver-460/focal-updates,focal-security,now 460.73.01-0ubuntu0.20.04.1 amd64 [installed]
nvidia-kernel-common-460/focal-updates,focal-security,now 460.73.01-0ubuntu0.20.04.1 amd64 [installed,automatic]
nvidia-kernel-source-460/focal-updates,focal-security,now 460.73.01-0ubuntu0.20.04.1 amd64 [installed,automatic]
nvidia-prime/focal-updates,focal-updates,now 0.8.16~0.20.04.1 all [installed,automatic]
nvidia-settings/focal-updates,now 460.39-0ubuntu0.20.04.1 amd64 [installed,automatic]
nvidia-utils-460/focal-updates,focal-security,now 460.73.01-0ubuntu0.20.04.1 amd64 [installed,automatic]
xserver-xorg-video-nvidia-460/focal-updates,focal-security,now 460.73.01-0ubuntu0.20.04.1 amd64 [installed]

$ apt list --installed | grep opencl

WARNING: apt does not have a stable CLI interface. Use with caution in scripts.

ocl-icd-libopencl1/focal,now 2.2.11-1ubuntu1 amd64 [installed]
ocl-icd-opencl-dev/focal,now 2.2.11-1ubuntu1 amd64 [installed]
opencl-c-headers/focal,focal,now 2.2~2019.08.06-g0d5f18c-1 all [installed]
opencl-clhpp-headers/focal,focal,now 2.1.0~~git51-gc5063c3-1 all [installed,automatic]
opencl-headers/focal,focal,now 2.2~2019.08.06-g0d5f18c-1 all [installed]


$ apt list --installed | grep ocl-icd

WARNING: apt does not have a stable CLI interface. Use with caution in scripts.

ocl-icd-libopencl1/focal,now 2.2.11-1ubuntu1 amd64 [installed]
ocl-icd-opencl-dev/focal,now 2.2.11-1ubuntu1 amd64 [installed]

@Fred, I have Resolve 17.1.1 semi-running on the little Dell Latitude E7270 with Debian Buster by installing the beignet-opencl-icd package. Resolve starts up fine and no crashes yet but I can't say it's usable in any way. As soon as I try doing anything I get GPU out of memory errors and playback is a slide show with occasional garbage frames using BRAW and ProRes. But a beefier machine with more GPU memory may work better.

I would not expect OpenCL to work with anything not officially supported and tested however. OpenCL compatibility, while having the fine intention of being hardware agnostic and all, really does not live up to that promise. Also having done some OpenCL development in the past, I fully agree with smunaut's statement when it comes to drivers and reported capabilities. In general they suck. The only OpenCL implementation that I have found somewhat complete and reliable is NVIDIA and then you may go all-in CUDA anyway for even better performance.

Below is some info from the machine mentioned above. Any obvious differences?

Code: Select all

$ ls /etc/OpenCL/vendors/
intel-beignet-x86_64-linux-gnu.icd

Code: Select all

$ dpkg -l | grep beignet-opencl-icd
ii  beignet-opencl-icd:amd64                                    1.3.2-6+b10                                  amd64        OpenCL library for Intel GPUs

Code: Select all

$ cat /proc/cpuinfo | grep name | head -n 1
model name      : Intel(R) Core(TM) i7-6600U CPU @ 2.60GHz

Code: Select all

$ clinfo
Number of platforms                               1
  Platform Name                                   Intel Gen OCL Driver
  Platform Vendor                                 Intel
  Platform Version                                OpenCL 2.0 beignet 1.3
  Platform Profile                                FULL_PROFILE
  Platform Extensions                             cl_khr_global_int32_base_atomics cl_khr_global_int32_extended_atomics cl_khr_local_int32_base_atomics cl_khr_local_int32_extended_atomics cl_khr_byte_addressable_store cl_khr_3d_image_writes cl_khr_image2d_from_buffer cl_khr_depth_images cl_khr_spir cl_khr_icd cl_intel_accelerator cl_intel_subgroups cl_intel_subgroups_short cl_khr_gl_sharing
  Platform Extensions function suffix             Intel

  Platform Name                                   Intel Gen OCL Driver
Number of devices                                 1
  Device Name                                     Intel(R) HD Graphics Skylake ULT GT2
  Device Vendor                                   Intel
  Device Vendor ID                                0x8086
  Device Version                                  OpenCL 2.0 beignet 1.3
  Driver Version                                  1.3
  Device OpenCL C Version                         OpenCL C 2.0 beignet 1.3
  Device Type                                     GPU
  Device Profile                                  FULL_PROFILE
  Device Available                                Yes
  Compiler Available                              Yes
  Linker Available                                Yes
  Max compute units                               24
  Max clock frequency                             1000MHz
  Device Partition                                (core)
    Max number of sub-devices                     1
    Supported partition types                     None, None, None
    Supported affinity domains                    (n/a)
  Max work item dimensions                        3
  Max work item sizes                             512x512x512
  Max work group size                             512
  Preferred work group size multiple              16
  Preferred / native vector sizes                 
    char                                                16 / 8       
    short                                                8 / 8       
    int                                                  4 / 4       
    long                                                 2 / 2       
    half                                                 0 / 8        (cl_khr_fp16)
    float                                                4 / 4       
    double                                               0 / 2        (n/a)
  Half-precision Floating-point support           (cl_khr_fp16)
    Denormals                                     No
    Infinity and NANs                             Yes
    Round to nearest                              Yes
    Round to zero                                 No
    Round to infinity                             No
    IEEE754-2008 fused multiply-add               No
    Support is emulated in software               No
  Single-precision Floating-point support         (core)
    Denormals                                     No
    Infinity and NANs                             Yes
    Round to nearest                              Yes
    Round to zero                                 No
    Round to infinity                             No
    IEEE754-2008 fused multiply-add               No
    Support is emulated in software               No
    Correctly-rounded divide and sqrt operations  No
  Double-precision Floating-point support         (n/a)
  Address bits                                    32, Little-Endian
  Global memory size                              4294967296 (4GiB)
  Error Correction support                        No
  Max memory allocation                           3221225472 (3GiB)
  Unified memory for Host and Device              Yes
  Shared Virtual Memory (SVM) capabilities        (core)
    Coarse-grained buffer sharing                 Yes
    Fine-grained buffer sharing                   No
    Fine-grained system sharing                   No
    Atomics                                       No
  Minimum alignment for any data type             128 bytes
  Alignment of base address                       1024 bits (128 bytes)
  Preferred alignment for atomics                 
    SVM                                           0 bytes
    Global                                        0 bytes
    Local                                         0 bytes
  Max size for global variable                    65536 (64KiB)
  Preferred total size of global vars             65536 (64KiB)
  Global Memory cache type                        Read/Write
  Global Memory cache size                        8192 (8KiB)
  Global Memory cache line size                   64 bytes
  Image support                                   Yes
    Max number of samplers per kernel             16
    Max size for 1D images from buffer            65536 pixels
    Max 1D or 2D image array size                 2048 images
    Base address alignment for 2D image buffers   4096 bytes
    Pitch alignment for 2D image buffers          1 pixels
    Max 2D image size                             8192x8192 pixels
    Max 3D image size                             8192x8192x2048 pixels
    Max number of read image args                 128
    Max number of write image args                8
    Max number of read/write image args           8
  Max number of pipe args                         16
  Max active pipe reservations                    1
  Max pipe packet size                            1024
  Local memory type                               Local
  Local memory size                               65536 (64KiB)
  Max number of constant args                     8
  Max constant buffer size                        134217728 (128MiB)
  Max size of kernel argument                     1024
  Queue properties (on host)                     
    Out-of-order execution                        No
    Profiling                                     Yes
  Queue properties (on device)                   
    Out-of-order execution                        Yes
    Profiling                                     Yes
    Preferred size                                16384 (16KiB)
    Max size                                      262144 (256KiB)
  Max queues on device                            1
  Max events on device                            1024
  Prefer user sync for interop                    Yes
  Profiling timer resolution                      80ns
  Execution capabilities                         
    Run OpenCL kernels                            Yes
    Run native kernels                            Yes
    SPIR versions                                 1.2
  printf() buffer size                            1048576 (1024KiB)
  Built-in kernels                                __cl_copy_region_align4;__cl_copy_region_align16;__cl_cpy_region_unalign_same_offset;__cl_copy_region_unalign_dst_offset;__cl_copy_region_unalign_src_offset;__cl_copy_buffer_rect;__cl_copy_image_1d_to_1d;__cl_copy_image_2d_to_2d;__cl_copy_image_3d_to_2d;__cl_copy_image_2d_to_3d;__cl_copy_image_3d_to_3d;__cl_copy_image_2d_to_buffer;__cl_copy_image_3d_to_buffer;__cl_copy_buffer_to_image_2d;__cl_copy_buffer_to_image_3d;__cl_fill_region_unalign;__cl_fill_region_align2;__cl_fill_region_align4;__cl_fill_region_align8_2;__cl_fill_region_align8_4;__cl_fill_region_align8_8;__cl_fill_region_align8_16;__cl_fill_region_align128;__cl_fill_image_1d;__cl_fill_image_1d_array;__cl_fill_image_2d;__cl_fill_image_2d_array;__cl_fill_image_3d;
  Device Extensions                               cl_khr_global_int32_base_atomics cl_khr_global_int32_extended_atomics cl_khr_local_int32_base_atomics cl_khr_local_int32_extended_atomics cl_khr_byte_addressable_store cl_khr_3d_image_writes cl_khr_image2d_from_buffer cl_khr_depth_images cl_khr_spir cl_khr_icd cl_intel_accelerator cl_intel_subgroups cl_intel_subgroups_short cl_khr_gl_sharing cl_khr_fp16

NULL platform behavior
  clGetPlatformInfo(NULL, CL_PLATFORM_NAME, ...)  Intel Gen OCL Driver
  clGetDeviceIDs(NULL, CL_DEVICE_TYPE_ALL, ...)   Success [Intel]
  clCreateContext(NULL, ...) [default]            Success [Intel]
  clCreateContextFromType(NULL, CL_DEVICE_TYPE_DEFAULT)  Success (1)
    Platform Name                                 Intel Gen OCL Driver
    Device Name                                   Intel(R) HD Graphics Skylake ULT GT2
  clCreateContextFromType(NULL, CL_DEVICE_TYPE_CPU)  No devices found in platform
  clCreateContextFromType(NULL, CL_DEVICE_TYPE_GPU)  Success (1)
    Platform Name                                 Intel Gen OCL Driver
    Device Name                                   Intel(R) HD Graphics Skylake ULT GT2
  clCreateContextFromType(NULL, CL_DEVICE_TYPE_ACCELERATOR)  No devices found in platform
  clCreateContextFromType(NULL, CL_DEVICE_TYPE_CUSTOM)  No devices found in platform
  clCreateContextFromType(NULL, CL_DEVICE_TYPE_ALL)  Success (1)
    Platform Name                                 Intel Gen OCL Driver
    Device Name                                   Intel(R) HD Graphics Skylake ULT GT2

ICD loader properties
  ICD loader Name                                 OpenCL ICD Loader
  ICD loader Vendor                               OCL Icd free software
  ICD loader Version                              2.2.12
  ICD loader Profile                              OpenCL 2.2


Regarding the Onboarding feature of Resolve it really can't be trusted to judge GPU compatibility. It's not useful for much really. It also has rather old dependencies making it not even start properly on many current machines.
In makeresolvedeb 1.5.0 I added the optional argument "--skip-onboarding" to exclude the Onboarding feature from the deb file that makes Resolve startup directly.

@216ann, since you do not have working OpenCL on your machine you need to fix that first before messing with Resolve itself. I don't think that there is anything wrong with your actual Resolve install. Do what smunaut suggests and compare his package list with the packages you have installed.
Canonical/Ubuntu has a little unusual approach when it comes to drivers compared to standard Debian. In Debian the OpenCL/ICD parts are in a separate package nvidia-opencl-icd that must be installed separately but in Ubuntu the nvidia-driver-NNN packages seems to include the OpenCL dependencies.

Below is the same package list from my recently installed and working Ubuntu 20.04 setup. The packages below are the result of a fresh OS install and adding the nvidia-driver-460 package.

Code: Select all

$ apt list --installed | grep nvidia

WARNING: apt does not have a stable CLI interface. Use with caution in scripts.

libnvidia-cfg1-460/focal-updates,focal-security,now 460.73.01-0ubuntu0.20.04.1 amd64 [installed,automatic]
libnvidia-common-460/focal-updates,focal-updates,focal-security,focal-security,now 460.73.01-0ubuntu0.20.04.1 all [installed,automatic]
libnvidia-compute-460/focal-updates,focal-security,now 460.73.01-0ubuntu0.20.04.1 amd64 [installed,automatic]
libnvidia-compute-460/focal-updates,focal-security,now 460.73.01-0ubuntu0.20.04.1 i386 [installed,automatic]
libnvidia-decode-460/focal-updates,focal-security,now 460.73.01-0ubuntu0.20.04.1 amd64 [installed,automatic]
libnvidia-decode-460/focal-updates,focal-security,now 460.73.01-0ubuntu0.20.04.1 i386 [installed,automatic]
libnvidia-encode-460/focal-updates,focal-security,now 460.73.01-0ubuntu0.20.04.1 amd64 [installed,automatic]
libnvidia-encode-460/focal-updates,focal-security,now 460.73.01-0ubuntu0.20.04.1 i386 [installed,automatic]
libnvidia-extra-460/focal-updates,focal-security,now 460.73.01-0ubuntu0.20.04.1 amd64 [installed,automatic]
libnvidia-fbc1-460/focal-updates,focal-security,now 460.73.01-0ubuntu0.20.04.1 amd64 [installed,automatic]
libnvidia-fbc1-460/focal-updates,focal-security,now 460.73.01-0ubuntu0.20.04.1 i386 [installed,automatic]
libnvidia-gl-460/focal-updates,focal-security,now 460.73.01-0ubuntu0.20.04.1 amd64 [installed,automatic]
libnvidia-gl-460/focal-updates,focal-security,now 460.73.01-0ubuntu0.20.04.1 i386 [installed,automatic]
libnvidia-ifr1-460/focal-updates,focal-security,now 460.73.01-0ubuntu0.20.04.1 amd64 [installed,automatic]
libnvidia-ifr1-460/focal-updates,focal-security,now 460.73.01-0ubuntu0.20.04.1 i386 [installed,automatic]
nvidia-compute-utils-460/focal-updates,focal-security,now 460.73.01-0ubuntu0.20.04.1 amd64 [installed,automatic]
nvidia-dkms-460/focal-updates,focal-security,now 460.73.01-0ubuntu0.20.04.1 amd64 [installed,automatic]
nvidia-driver-460/focal-updates,focal-security,now 460.73.01-0ubuntu0.20.04.1 amd64 [installed]
nvidia-kernel-common-460/focal-updates,focal-security,now 460.73.01-0ubuntu0.20.04.1 amd64 [installed,automatic]
nvidia-kernel-source-460/focal-updates,focal-security,now 460.73.01-0ubuntu0.20.04.1 amd64 [installed,automatic]
nvidia-prime/focal-updates,focal-updates,now 0.8.16~0.20.04.1 all [installed,automatic]
nvidia-settings/focal-updates,now 460.39-0ubuntu0.20.04.1 amd64 [installed,automatic]
nvidia-utils-460/focal-updates,focal-security,now 460.73.01-0ubuntu0.20.04.1 amd64 [installed,automatic]
xserver-xorg-video-nvidia-460/focal-updates,focal-security,now 460.73.01-0ubuntu0.20.04.1 amd64 [installed,automatic]

$ apt list --installed | grep opencl

WARNING: apt does not have a stable CLI interface. Use with caution in scripts.

ocl-icd-libopencl1/focal,now 2.2.11-1ubuntu1 amd64 [installed,automatic]

$ apt list --installed | grep ocl-icd

WARNING: apt does not have a stable CLI interface. Use with caution in scripts.

ocl-icd-libopencl1/focal,now 2.2.11-1ubuntu1 amd64 [installed,automatic]


If this is a dead end then perhaps just autoremove all nvidia-* and libnvidia-* packages and start fresh from a new install of the nvidia-driver-460 package?

Also something to pay attention with that I got hit with this morning is if the nvidia driver got updated between the time you booted the machine and the moment you try to start resolve ...

I had this happen this morning. I was running resolve. Then quit and try to restart it and it wouldn't start. And then in dmesg I see :

Code: Select all

[222059.665251] NVRM: API mismatch: the client has the version 460.73.01, but
                NVRM: this kernel module has the version 460.56.  Please
                NVRM: make sure that this kernel module and all NVIDIA driver
                NVRM: components have the same version.

That's because in the background ubuntu updated the nvidia driver, including all the userspace libraries but the kernel module was already loaded and was the old version ... I had to quit X and manually reload the new module to fix that.

Yes, good point. I also have been bit by the background updates more than once. I wish Canonical was more upfront about it. If you are unlucky the background updates can run into problems and actually remove needed module packages leaving you with whatever modules were loaded in memory. Then when eventually rebooting things go wrong and it can be difficult to track down what actually caused it.

@smunaut @Tufvesson
Running

Code: Select all

$ apt list --installed | grep nvidia

Shows that I have quite a few extra ones such as i386 ones

Code: Select all

$ apt list --installed | grep opencl

only ocl-icd-libopencl1/focal,now 2.2.11-1ubuntu1 amd64 [installed,automatic]
So I am missing a bunch

Code: Select all

$ apt list --installed | grep ocl-icd

Missing the rest like above.

the background ubuntu updated the nvidia driver, including all the userspace libraries but the kernel module was already loaded and was the old version

I think that is what happened in my case because it was working fine one minute and after I did sudo apt-get update/upgrade it did this
But, I am not sure based on the responses, how I can prevent this in the future.

... I had to quit X and manually reload the new module to fix that.

Never heard of "quit X"
And may I ask how to "manually reload the new module" so I can fix my issue (I would try this but free wheeling was what got me in trouble the last time?
Although I know I could probably completely reinstall the OS (using 3rd party option on install) and reinstall Resolve, I really want to get to a point where I don't have to constantly worry about update/upgrade screwing with the Resolve GPU function.
Thank you for your help.

May 12th update...still have not resolved this issue. Would appreciate some help. Thanks.

Hi Everyone,

This may save some of you a bit of digging......

I'm running Resolve 17.2 Studio, with a speed editor on Ubuntu, installed from the .deb created by Daniel's excellent script.

This morning, I got a message on starting Resolve saying there's and update for the speed editor.

Clicking the button to install it caused a crash in /opt/resolve/DaVinci Control Panels Setup/DaVinci Control Panels Setup

The issue appears to be caused by spaces in the path and filename.

I was able to manually start the program and install the update as follows:

Open a terminal
cd /opt/resolve/'DaVinci Control Panels Setup'
./'DaVinci Control Panels Setup'

My speed editor now has firmware v1.3.

Kind regards,
Tim.

Huh, interesting. I got the same message but there was no issue, it was able to start the Panel Setup utility directly with no crash. (Ubuntu 20.04 but not using makeresolvedeb, just manually installing)

Strange. I'm unable to reproduce the Speed Editor update problem that Tim mentions. Tested using Ubuntu 20.04 and Debian 11 (both installed using makeresolvedeb). Update reminder shows up and the panel setup utility starts just fine and can perform the update.

Odd, it's probably my system then.......

I am running Ubuntu 21.04, so maybe that's got something to do with it.

I have the crash log here:
/var/crash/_opt_resolve_DaVinci Control Panels Setup_DaVinci Control Panels Setup.399508567.crash

It's quite verbose, but I could post if if it'd be useful. A couple of excerpts are below.

Towards the end there's:

May 12 13:33:05 dell-t5600-ubuntu DaVinci Control[19355]: DaVinci Control Panels Setup: qt.qpa.xcb: could not connect to display :0.0
May 12 13:33:05 dell-t5600-ubuntu DaVinci Control[19355]: DaVinci Control Panels Setup: This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.

Available platform plugins are: xcb.
NonfreeKernelModules: nvidia_modeset nvidia
Package: davinci-resolve-studio 17.2-mrd1.5.0 [origin: unknown]


And further down:

Title: DaVinci Control Panels Setup crashed with SIGABRT in QMessageLogger::fatal()

This is just a guess but since Resolve, the Onboarding, the Panel Setup, the BRAW Player and the BRAW Speed Test all contain their own of set of Qt libraries and Qt platform plugins of various versions, I would not be surprised if there is an issue when one of them is calling the other. In this case of the xcb platform plugin initialization error maybe the Qt environment variables are inherited or not not setup correctly making the Panel Setup load the wrong xcb plugin or even in some case fall back to the one from the OS. That could explain why there was a crash with Ubuntu 21.04 and not with 20.04 for example.

Interesting.

I suppose that might explain why it worked when the panels utility was started from the command line, but not from within Resolve.

The environments were different......

The next time there's a speed editor update, I'll pay a lot more attention to what's going on!

Hello all! I have a bit of a mystery that I cannot figure out. Not sure if it is a configuration problem or a bug that i am running into. I am new to Resolve but have used it a bit on windows, mac, and the machine currently in question, a System76 Gazelle laptop running Pop_OS!. I used makeresolvedeb to install, and everything has gone smoothly (ran into the initial load window bug, but simply killing the process moved me forward into the launch proper of Resolve.). However, in trying to load videos in this machine, I have found that the audio does not appear to be importing correctly. There is no sound, and there is no waveform available when I try to view it. I have no problem with mp3 files loading properly, just with video files with audio. I appreciate any insights or suggestions anyone can offer.

PS. I recently updated to 17.2.1. Previously I was running 17.1.1 and had the same problem.

Bumping this thread, I dont feel starting a new one, not a Resolve fault though
Anyone having trouble with the latest Nvidia driver updates on *buntu?
tried 460.80 and the 465 both official repos and ppa
blank screen at boot, not hard freeze since I'm able to force a reboot with the magic sysrq keys.
hoping that the newly released 460.83 will fix this annoyance

460.80 is working fine for me on Ubuntu 20.10.

Solved installing the -server driver package instead of the regular one.
I'm on 21.04
Noel, chances are that you have the monitor connected via HDMI?
I use DP and read that the issue is affecting DP output, while HDMI is working fine
thank you

Hey Daniel,

After the last experience I set about testing EVERY open sauce video editor out there using appimage and flatpack which I hadn't previously considered even trying (originally a deb diehard since woody and before). I think I tested about 10 with the ONLY one being usable even for my simple case (adding 15 or so 4k 140MBPS GH5 clips from a dir, proxying them, and placing on the timeline easily), and that one, the most mature of the bunch, was kdenlive, which seemed to have solved the stability issues of old.

I just happened to see this as a completion in my browser and thought "I wonder what happened to that thread"

To your questions:

Code: Select all

ls /etc/OpenCL/vendors/
intel.icd

However not tooooo dissimilar to what you showed, I used to have this, no joy there, either:

Code: Select all

apt-cache show beignet-opencl-icd
Package: beignet-opencl-icd
Architecture: amd64
Version: 1.3.2-2

It's quite ironic that I went away from kdenlive about 10 years ago because of instability and am back to it now because of stability and performance The worst one I tested had a quite good UI but was written in python and actually managed to max out my 9th gen i9 octa core CPU and get it to 80C doing proxies multithreaded Nothing else came close to that bad but the intuitiveness/quality of interface varied a lot bewteen them and kdenlive smashed the rest by a long margin on the basics and ALSO has many of the more advanced things that I don't even need.

I hope you're well. Maybe I'll play around with this again in future and see how I get on, but I've been busy with a lot of other things. Cheers, Fred.

I'm on Pop OS 21.04 and have Resolve running but it starts maximized and once I no longer have it maximized, I can't move the window at all. It is just stuck in place. Anyone else been having this problem?

Hi, i just installed Debian 11 and DR17.2.2 studio using makeresolvedeb.
All fine so far, except for some codecs missing. On Debian 10 i had everything working just fine.
Any ideas? Thanks!

Update: Just worked after restart

Now i can't find my mic inside the app
Audio recording on linux

Hi Everyone,
I have installed DaVinci without any trouble using Daniel Tufvesson's script but when opening Resolve the preview appears messed up and the message "The GPU failed to perform image processing because of an error. Error Code: 999" is randomly displayed.

Preview messed up

preview-messed.png (618.58 KiB) Viewed 11999 times

Preview messed up

preview-messed.png (618.58 KiB) Viewed 11999 times

In the logs I found the message:

Code: Select all

Failed to register OpenGL object for CUDA interop: cudaErrorUnknown

Has anyone been through this or have any ideas where I can look for what's going on?

I'm running on Debian 11, with Resolve 17 and GeForce 940MX.

Are the nvidia cuda drivers installed on your system?

Code: Select all

sudo apt install nvidia-cuda-toolkit

I just updated to Resolve Studio 17.4.1 using mighty makeresolvedeb on my Ubuntu Studio 20.04.3 LTS. Woo Woo!

An issue I have had previously was running out of disk space in /tmp. Makeresolvedeb apparently needs 2+ GB free in /tmp as well as the space in the working directory.

I've not seen any problems with Resolve vs the GPU, but I already had the nvidia CUDA drivers installed for Blender.

Hello,

I'm getting the following issue during the installation of Davinci Resolve using MakeResolveDeb in a Debian 11 OS. Do you guys know how to solve it and complete the installation?

Code: Select all

cordeiro@debian:~/Downloads/empty$ ./makeresolvedeb_1.5.1_multi.sh DaVinci_Resolve_17.4.4_Linux.run
MakeResolveDeb 1.5.1

Detected DaVinci Resolve version 17.4.4

Checking for tar...found!
Checking for fakeroot...found!
Checking for dpkg-deb...found!

Using Resolve 17 conversion process
Extracting archive
Warning: Ignoring XDG_SESSION_TYPE=wayland on Gnome. Use QT_QPA_PLATFORM=wayland to run on Wayland anyway.
Found 2876 objects
Adding BlackmagicRAWPlayer
Adding BlackmagicRAWSpeedTest
Creating Debian package
dpkg-deb: building package 'davinci-resolve' in './davinci-resolve_17.4.4-mrd1.5.1_amd64.deb'.
dpkg-deb (subprocess): compressing tar member: lzma write error: No space left on device
dpkg-deb: error: <compress> from tar -cf subprocess returned error exit status 2

[DONE] errors reported 1



Obs: I'm following this tutorial danieltufvesson.com/makeresolvedeb

Thanks!!

Hello,

I'm getting the following issue during the installation of Davinci Resolve using MakeResolveDeb in a Debian 11 OS. Do you guys know how to solve it and complete the installation?

Code: Select all

cordeiro@debian:~/Downloads/empty$ ./makeresolvedeb_1.5.1_multi.sh DaVinci_Resolve_17.4.4_Linux.run
MakeResolveDeb 1.5.1

Detected DaVinci Resolve version 17.4.4

Checking for tar...found!
Checking for fakeroot...found!
Checking for dpkg-deb...found!

Using Resolve 17 conversion process
Extracting archive
Warning: Ignoring XDG_SESSION_TYPE=wayland on Gnome. Use QT_QPA_PLATFORM=wayland to run on Wayland anyway.
Found 2876 objects
Adding BlackmagicRAWPlayer
Adding BlackmagicRAWSpeedTest
Creating Debian package
dpkg-deb: building package 'davinci-resolve' in './davinci-resolve_17.4.4-mrd1.5.1_amd64.deb'.
dpkg-deb (subprocess): compressing tar member: lzma write error: No space left on device
dpkg-deb: error: <compress> from tar -cf subprocess returned error exit status 2

[DONE] errors reported 1



Obs: I'm following this tutorial danieltufvesson.com/makeresolvedeb

Thanks!!

Hi! Welcome to the forum! According to the message, dpkg-deb ended with the error "No space left on device" so you are running out of disk space during the conversion process. Free up space in the working directory and in /tmp and try again.

An alternative to repackaging the software into a dpkg is running it via a container:

https://github.com/fat-tire/resolve

Please note, the default location for your container cache needs at least 7GB free disk space (normally in /var for Docker) to build and run the Resolve (Studio) container.

An alternative to repackaging the software into a dpkg is running it via a container:

https://github.com/fat-tire/resolve

Please note, the default location for your container cache needs at least 7GB free disk space (normally in /var for Docker) to build and run the Resolve (Studio) container.

Cowmix, have you tested this on Linux Mint?

Cheers,

BC

Hello,
as I am new to the forum I want to say hello to all members.

I installed DaVinci Resolve 17.4.2 with Daniel's MultiMakedeb 1.5.1 successfully on Ubuntu 21.10 with a Nvidia Geforce GTX 960M using the Ubuntu nvidia-driver-470. According to Daniel's manual I installed nvidia-opencl-icd-340, libcuda1-340, libglu1-mesa. I also installed the nvidia-cuda-toolkit (11.3.1-4) as I read it should be necessary. In the preferences of DaVinci there is OpenCL and CUDA available. Everything working fine.

With a package-update I upgraded to nvidia-driver-510 using the Ubuntu "Additional driver tool". Everything is still working fine.

In Synaptic Paketmanager I see that the nvidia-cuda-toolkit package (11.3.1-4) was removed in Synaptic, but leaving some other packages from the nvidia-cuda-toolkit package installed.

If I try to do a "apt-get-autoremove" the following packages would be removed:
g++-10 javascript-common libaccinj64-11.3 libcub-dev libcublas11
libcublaslt11 libcudart11.0 libcufft10 libcufftw10 libcupti-dev libcupti-doc
libcupti11.3 libcurand10 libcusolver11 libcusolvermg11 libcusparse11
libjs-jquery libjs-sphinxdoc libjs-underscore libnppc11 libnppial11
libnppicc11 libnppidei11 libnppif11 libnppig11 libnppim11 libnppist11
libnppisu11 libnppitc11 libnpps11 libnvblas11 libnvjpeg11
libnvrtc-builtins11.3 libnvrtc11.2 libnvtoolsext1 libnvvm4 libstdc++-10-dev
libthrust-dev libvdpau-dev node-html5shiv nsight-compute
nsight-compute-target nvidia-cuda-gdb nvidia-cuda-toolkit-doc

If I run nvidia-smi it says:
NVIDIA-SMI 510.47.03 Driver Version: 510.47.03 CUDA Version: 11.6

If I try to reinstall nvidia-cuda-toolkit package (11.3.1-4), Synaptic tells me it will deinstall nvidia-driver-510 in order to install the cuda-toolkit again.

Honestly I am a bit confused. Does someone have an idea about this situation?

Is the nvidia-cuda-toolkit for running CUDA on Ubuntu necessary as Daniel only says in his manual to install "nvidia-opencl-icd-340, libcuda1-340 libglu1-mesa"?

I tried OpenCL, but CUDA works better.

Thanks a lot in advance. Have a great day!

Hi Jean! Welcome to the forum! I'm glad you got Resolve running. Not sure from where you got the reference to the 340 driver packages. It's not in my instruction. The 340 driver is very old by now. In general you should be using the latest driver available for your distro. In your case it's 510 so the package manager was probably correct to upgrade it (Canonical made it quite confusing when they included the driver version in the package name). Installing an old driver with its dependencies and then upgrading it will cause old (and unneeded) packages to be flagged for removal. This is to be expected. You don't need cuda-toolkit to run Resolve. It may even actually be that the toolkit is incompatible with the latest driver.

Hello Daniel,

thank you very much for your answer and for developping great MakeResolveDeb Multi!

1

"Not sure from where you got the reference to the 340 driver packages. It's not in my instruction."

Sorry, there was a misunderstanding on my side! You write "nvidia-opencl-icd libcuda1 libglu1-mesa", which is the situation for NVIDIA and Debian.

I checked in Synaptic for those packages and found nvidia-opencl-icd-340 libcuda1-340 and libglu1-mesa (9.0.1). So I thought the first two packages are the required ones in Ubuntu. BUT ... nvidia-opencl-icd-340 and libcuda1-340 are EMPTY Transitional packages. Maybe packaging was similar to Debian before, but changed in Ubuntu.

I checked the driver packages in Synaptic for CUDA and OpenCL and found "libnvidia-compute-510" and "libnvidia-compute-utils-510". See screenshots as attachments.

"libnvidia-compute-510"
This package provides a set of libraries which enable the NVIDIA driver
to use GPUs for parallel general purpose computation through CUDA and
OpenCL.

"libnvidia-compute-utils-510"
This package provides utility binaries for parallel general purpose
computing use cases with the NVIDIA driver.
CUDA MPS is a feature that allows multiple CUDA processes to share a single
GPU context. CUDA MPS should be transparent to CUDA programs.

As far as I understand the relevant CUDA and OpenCL components for parallel processing are in these two packages. Maybe therefore the name "compute" and "compute-utils". Is my assumtion correct?

When you install "nvidia-driver-510" these packages as well as "libnvidia-decode-510", "libnvidia-encode-510" and other relevant components will be installed automatically as necessary dependencies. So I need to choose in Synaptic only "nvidia-driver-510" and "libglu1-mesa (9.0.1)".

2

"You don't need cuda-toolkit to run Resolve. It may even actually be that the toolkit is incompatible with the latest driver."

As you said the "nvidia-cuda-toolkit" is then not necessary. In Ubuntu 21.10 it seems that "nvidia-cuda-toolkit (11.3.1)" has a dependancy to "libnvidia-compute-470", cause when I try to install the "nvidia-cuda-toolkit (11.3.1)" it offers me to install "libnvidia-compute-470", but wants to remove all packages with the "nvidia-driver-510".

Maybe this version of the cuda-toolkit is bound to driver nvidia-version-470?
Have a great day!

Hey guys!

Had a weird on going issue with resolve ever since i upgraded from 17.2.2. I'm on the newest build now 17.4.5 and resolve will sometimes get past the splash screen and sometimes it wont. If it doesn't get the splash screen i'm forced the restart the computer and hope that it'll start up next time everything loads. Sometimes it does. Sometimes it doesn't.

Here are things i've done:

1. Made a crash log that can be found here:
https://drive.google.com/file/d/1xpFczv ... sp=sharing

2. Looked over the makeresolvedeb tutorial and Run resolve from a prompt (/opt/resolve/bin/resolve) and check the output for error messages.

ActCCMessage Already in Table: Code= c005, Mode= 13, Level= 1, CmdKey= -1, Option= 0
ActCCMessage Already in Table: Code= c006, Mode= 13, Level= 1, CmdKey= -1, Option= 0
ActCCMessage Already in Table: Code= c007, Mode= 13, Level= 1, CmdKey= -1, Option= 0
ActCCMessage Already in Table: Code= 2282, Mode= 0, Level= 0, CmdKey= 8, Option= 0
PnlMsgActionStringAdapter Already in Table: Code= 615e, Mode= 0, Level= 0, CmdKey= -1, Option= 0

3. Made sure I have all required libraries installed. Ran "ldd /opt/resolve/bin/resolve" and verified that there are no missing libraries (ldd should give no lines with "not found" in them)

4. Checked to see what driver is installed for my GPU (Quadro RTX 5000) it's driver 510.47.03

The one thing i HAVEN'T done is bypass the on-boarding feature when i'm making resolve deb. Could that be it?

Please help me figure this out. It's alittle annoying.

Thanks everyone!!!

Has anyone had makeresolvedeb hang at creating the deb package?

Code: Select all

Creating Debian package
dpkg-deb: building package 'davinci-resolve-studio' in './davinci-resolve-studio_17.4.6-mrd1.6.0_amd64.deb'.

It's hanging there for a long time for me and doesn't complete. A single CPU thread sticks at 100%.

Has anyone had makeresolvedeb hang at creating the deb package?

Code: Select all

Creating Debian package
dpkg-deb: building package 'davinci-resolve-studio' in './davinci-resolve-studio_17.4.6-mrd1.6.0_amd64.deb'.

It's hanging there for a long time for me and doesn't complete. A single CPU thread sticks at 100%.

How long did you wait? I've found makeresolvedeb takes a very long time to run.

Not sure exactly how long, as I normally leave it running while doing other things, but certainly as long as 1 to 2 hours......

How long did you wait? I've found makeresolvedeb takes a very long time to run.
Not sure exactly how long, as I normally leave it running while doing other things, but certainly as long as 1 to 2 hours......

Ok thanks, good to know. I only waited about 15 minutes

How long did you wait? I've found makeresolvedeb takes a very long time to run.
Not sure exactly how long, as I normally leave it running while doing other things, but certainly as long as 1 to 2 hours......

Ok thanks, good to know. I only waited about 15 minutes

Last time I built the deb package (last week) it took about 25 min to process. YMMV.

However, my preferred method of running Resolve on ANY Linux distro is via this:

https://github.com/fat-tire/resolve

How long did you wait? I've found makeresolvedeb takes a very long time to run.
Not sure exactly how long, as I normally leave it running while doing other things, but certainly as long as 1 to 2 hours......

Ok thanks, good to know. I only waited about 15 minutes

Makeresolvedeb relies on the official tools to compress the final installer package. It's very single-thread-CPU and disk intensive and unfortunately provide no feedback on the progress. On my 10yo reference machine with i7-3930K and PCIe SSD the conversion takes roughly 4 minutes in total for Resolve 17.
Even 15 minutes is a very long time for a reasonably modern machine. What kind of storage are you using?

How long did you wait? I've found makeresolvedeb takes a very long time to run.
Not sure exactly how long, as I normally leave it running while doing other things, but certainly as long as 1 to 2 hours......

Ok thanks, good to know. I only waited about 15 minutes

Makeresolvedeb relies on the official tools to compress the final installer package. It's very single-thread-CPU and disk intensive and unfortunately provide no feedback on the progress. On my 10yo reference machine with i7-3930K and PCIe SSD the conversion takes roughly 4 minutes in total for Resolve 17.
Even 15 minutes is a very long time for a reasonably modern machine. What kind of storage are you using?

I'm using a Dell T5600 running Ubuntu 22.04. (The makeresolvedeb timings were similar before upgrading from 21.10).

The filing system where makeresolvedeb is running is ext4 on a SATA SSD. (Samsung 870 QVO).

I'm not at the machine right now, so can't get a detailed hardware listing. Will do that tomorrow.

[/quote]Makeresolvedeb relies on the official tools to compress the final installer package. It's very single-thread-CPU and disk intensive and unfortunately provide no feedback on the progress. On my 10yo reference machine with i7-3930K and PCIe SSD the conversion takes roughly 4 minutes in total for Resolve 17.
Even 15 minutes is a very long time for a reasonably modern machine. What kind of storage are you using?[/quote]

I'm using a Dell T5600 running Ubuntu 22.04. (The makeresolvedeb timings were similar before upgrading from 21.10).

The filing system where makeresolvedeb is running is ext4 on a SATA SSD. (Samsung 870 QVO).

I'm not at the machine right now, so can't get a detailed hardware listing. Will do that tomorrow.[/quote]

The disks are connected to a PERC H710P RAID controller.

There are 2 SATA SSDs, in RAID level 0.

Disk 0 has the system installed on it, Disk 1 is mounted on /home.

The system has 2 Intel Xeon E5-2620 CPUs and 64Gb of RAM.

The GPU is an NVIDIA GTX 1660.

If I get time, I'll try running makeresolvedeb on a different system later today.

lshw gives the following output (truncated by the character limit):


dell-t5600-ubuntu
description: Tower Computer
product: Precision T5600
vendor: Dell Inc.
version: 01
serial:
width: 64 bits
capabilities: smbios-2.6 dmi-2.6 smp vsyscall32
configuration: administrator_password=disabled boot=normal chassis=tower frontpanel_password=disabled keyboard_password=disabled power-on_password=disabled uuid=4c4c4544-0038-5710-8039-b2c04f5a5831
*-core
description: Motherboard
product: 0GN6JF
vendor: Dell Inc.
physical id: 0
version: A01
serial:
*-firmware
description: BIOS
vendor: Dell Inc.
physical id: 0
version: A19
date: 06/30/2019
size: 64KiB
capacity: 10MiB
capabilities: pci upgrade shadowing cdboot bootselect edd int13floppy1200 int13floppy720 int13floppy2880 int5printscreen int9keyboard int14serial int17printer acpi usb biosbootspecification netboot
*-cpu:0
description: CPU
product: Intel(R) Xeon(R) CPU E5-2620 0 @ 2.00GHz
vendor: Intel Corp.
physical id: 4
bus info: cpu@0
version: 6.45.7
serial: Not Specified
slot: CPU 1
size: 1197MHz
capacity: 4GHz
width: 64 bits
clock: 100MHz
capabilities: lm fpu fpu_exception wp vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp x86-64 constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm pcid dca sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer aes xsave avx lahf_lm epb pti ssbd ibrs ibpb stibp tpr_shadow vnmi flexpriority ept vpid xsaveopt dtherm ida arat pln pts md_clear flush_l1d cpufreq
configuration: cores=6 enabledcores=6 microcode=1818 threads=12
*-cache:0
description: L1 cache
physical id: 5
slot: L1-Cache
size: 384KiB
capacity: 384KiB
capabilities: internal write-back unified
configuration: level=1
*-cache:1
description: L2 cache
physical id: 6
slot: L2-Cache
size: 1536KiB
capacity: 1536KiB
capabilities: internal varies unified
configuration: level=2
*-cache:2
description: L3 cache
physical id: 7
slot: L3-Cache
size: 15MiB
capacity: 15MiB
capabilities: internal varies unified
configuration: level=3
*-cpu:1
description: CPU
product: Intel(R) Xeon(R) CPU E5-2620 0 @ 2.00GHz
vendor: Intel Corp.
physical id: 1
bus info: cpu@1
version: 6.45.7
serial: Not Specified
slot: CPU 2
size: 1197MHz
capacity: 4GHz
width: 64 bits
clock: 100MHz
capabilities: lm fpu fpu_exception wp vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp x86-64 constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm pcid dca sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer aes xsave avx lahf_lm epb pti ssbd ibrs ibpb stibp tpr_shadow vnmi flexpriority ept vpid xsaveopt dtherm ida arat pln pts md_clear flush_l1d cpufreq
configuration: cores=6 enabledcores=6 microcode=1818 threads=12
*-cache:0
description: L1 cache
physical id: 9
slot: L1-Cache
size: 384KiB
capacity: 384KiB
capabilities: internal write-back unified
configuration: level=1
*-cache:1
description: L2 cache
physical id: a
slot: L2-Cache
size: 1536KiB
capacity: 1536KiB
capabilities: internal varies unified
configuration: level=2
*-cache:2
description: L3 cache
physical id: b
slot: L3-Cache
size: 15MiB
capacity: 15MiB
capabilities: internal varies unified
configuration: level=3
*-memory
description: System Memory
physical id: 32
slot: System board or motherboard
size: 64GiB
capabilities: ecc
configuration: errordetection=multi-bit-ecc
*-bank:0
description: DIMM DDR3 1333 MHz (0.8 ns)
product: NT8GC72B4NB1NK-CG
vendor: Undefined-000B
physical id: 0
serial: 95582369
slot: DIMM1_CPU1
size: 8GiB
width: 64 bits
clock: 1333MHz (0.8ns)
*-bank:1
description: DIMM DDR3 1333 MHz (0.8 ns)
product: M393B1K70CH0-CH9
vendor: Samsung-00CE
physical id: 1
serial: 855BC2D6
slot: DIMM3_CPU1
size: 8GiB
width: 64 bits
clock: 1333MHz (0.8ns)
*-bank:2
description: DIMM DDR3 1333 MHz (0.8 ns)
product: NT8GC72B4NB1NK-CG
vendor: Undefined-000B
physical id: 2
serial: EF5E2A14
slot: DIMM2_CPU1
size: 8GiB
width: 64 bits
clock: 1333MHz (0.8ns)
*-bank:3
description: DIMM DDR3 1333 MHz (0.8 ns)
product: M393B1K70CH0-CH9
vendor: Samsung-00CE
physical id: 3
serial: 83C9891B
slot: DIMM4_CPU1
size: 8GiB
width: 64 bits
clock: 1333MHz (0.8ns)
*-bank:4
description: DIMM DDR3 1333 MHz (0.8 ns)
product: NT8GC72B4NB1NK-CG
vendor: Undefined-000B
physical id: 4
serial: FB622366
slot: DIMM1_CPU2
size: 8GiB
width: 64 bits
clock: 1333MHz (0.8ns)
*-bank:5
description: DIMM DDR3 1333 MHz (0.8 ns)
product: M393B1K70CH0-CH9
vendor: Samsung-00CE
physical id: 5
serial: 855BC263
slot: DIMM3_CPU2
size: 8GiB
width: 64 bits
clock: 1333MHz (0.8ns)
*-bank:6
description: DIMM DDR3 1333 MHz (0.8 ns)
product: NT8GC72B4NB1NK-CG
vendor: Undefined-000B
physical id: 6
serial: 5B353E1B
slot: DIMM2_CPU2
size: 8GiB
width: 64 bits
clock: 1333MHz (0.8ns)
*-bank:7
description: DIMM DDR3 1333 MHz (0.8 ns)
product: M393B1K70CH0-CH9
vendor: Samsung-00CE
physical id: 7
serial: 83C98AF4
slot: DIMM4_CPU2
size: 8GiB
width: 64 bits
clock: 1333MHz (0.8ns)
*-pci:0
description: Host bridge
product: Xeon E5/Core i7 DMI2
vendor: Intel Corporation
physical id: 100
bus info: pci@0000:00:00.0
version: 07
width: 32 bits
clock: 33MHz
*-pci:0
description: PCI bridge
product: Xeon E5/Core i7 IIO PCI Express Root Port 1a
vendor: Intel Corporation
physical id: 1
bus info: pci@0000:00:01.0
version: 07
width: 32 bits
clock: 33MHz
capabilities: pci msi pciexpress pm normal_decode bus_master cap_list
configuration: driver=pcieport
resources: irq:26
*-pci:1
description: PCI bridge
product: Xeon E5/Core i7 IIO PCI Express Root Port 1b
vendor: Intel Corporation
physical id: 1.1
bus info: pci@0000:00:01.1
version: 07
width: 32 bits
clock: 33MHz
capabilities: pci msi pciexpress pm normal_decode bus_master cap_list
configuration: driver=pcieport
resources: irq:27 ioport:8000(size=4096) memory:f7900000-f79fffff
*-raid
description: RAID bus controller
product: MegaRAID SAS 2208 [Thunderbolt]
vendor: Broadcom / LSI
physical id: 0
bus info: pci@0000:02:00.0
logical name: scsi1
version: 05
width: 64 bits
clock: 33MHz
capabilities: raid pm pciexpress vpd msi msix bus_master cap_list rom
configuration: driver=megaraid_sas latency=0
resources: irq:49 ioport:8000(size=256) memory:f7960000-f7963fff memory:f7900000-f793ffff memory:f7940000-f795ffff
*-disk:0
description: SCSI Disk
product: PERC H710P
vendor: DELL
physical id: 2.0.0
bus info: scsi@1:2.0.0
logical name: /dev/sda
version: 3.13
serial: 0015633102ba27eb2200a3d9d660f681
size: 223GiB (239GB)
capabilities: gpt-1.00 partitioned partitioned:gpt
configuration: ansiversion=5 guid=063f19aa-c14b-492a-9303-384100766670 logicalsectorsize=512 sectorsize=512
*-volume:0 UNCLAIMED
description: Windows FAT volume
vendor: mkfs.fat
physical id: 1
bus info: scsi@1:2.0.0,1
version: FAT32
serial: b8c0-277c
size: 951MiB
capacity: 952MiB
capabilities: boot fat initialized
configuration: FATs=2 filesystem=fat
*-volume:1
description: EXT4 volume
vendor: Linux
physical id: 2
bus info: scsi@1:2.0.0,2
logical name: /dev/sda2
logical name: /
version: 1.0
serial: 36bfab81-8c31-47c4-bf0b-2aa020f3a581
size: 222GiB
capabilities: journaled extended_attributes large_files huge_files dir_nlink recover 64bit extents ext4 ext2 initialized
configuration: created=2021-11-16 15:17:32 filesystem=ext4 lastmountpoint=/ modified=2022-05-06 09:43:20 mount.fstype=ext4 mount.options=rw,relatime,errors=remount-ro mounted=2022-05-06 09:43:20 state=mounted
*-disk:1
description: SCSI Disk
product: PERC H710P
vendor: DELL
physical id: 2.1.0
bus info: scsi@1:2.1.0
logical name: /dev/sdb
version: 3.13
serial: 0038846923f0ddec2700a3d9d660f681
size: 931GiB (999GB)
capabilities: gpt-1.00 partitioned partitioned:gpt
configuration: ansiversion=5 guid=82167329-5034-4e5e-b570-973768fe2d2e logicalsectorsize=512 sectorsize=512
*-volume:0
description: Linux swap volume
vendor: Linux
physical id: 1
bus info: scsi@1:2.1.0,1
logical name: /dev/sdb1
version: 1
serial: 31001a55-8f43-4b06-822b-b63e108e54db
size: 121GiB
capacity: 121GiB
capabilities: nofs swap initialized
configuration: filesystem=swap pagesize=4095
*-volume:1
description: EXT4 volume
vendor: Linux
physical id: 2
bus info: scsi@1:2.1.0,2
logical name: /dev/sdb2
logical name: /home
version: 1.0
serial: 62fbc157-f2db-4aa9-8efa-d7bca9a1b429
size: 809GiB
capabilities: journaled extended_attributes large_files huge_files dir_nlink recover 64bit extents ext4 ext2 initialized
configuration: created=2021-11-16 15:17:34 filesystem=ext4 lastmountpoint=/home modified=2022-05-06 09:43:21 mount.fstype=ext4 mount.options=rw,relatime mounted=2022-05-06 09:43:21 state=mounted
*-pci:2
description: PCI bridge
product: Xeon E5/Core i7 IIO PCI Express Root Port 2a
vendor: Intel Corporation
physical id: 2
bus info: pci@0000:00:02.0
version: 07
width: 32 bits
clock: 33MHz
capabilities: pci msi pciexpress pm normal_decode bus_master cap_list
configuration: driver=pcieport
resources: irq:28 ioport:7000(size=4096) memory:f6000000-f70fffff ioport:e0000000(size=303038464)
*-display
description: VGA compatible controller
product: TU116 [GeForce GTX 1660]
vendor: NVIDIA Corporation
physical id: 0
bus info: pci@0000:03:00.0
version: a1
width: 64 bits
clock: 33MHz
capabilities: pm msi pciexpress vga_controller bus_master cap_list rom
configuration: driver=nvidia latency=0
resources: irq:110 memory:f6000000-f6ffffff memory:e0000000-efffffff memory:f0000000-f1ffffff ioport:7000(size=128) memory:c0000-dffff
*-multimedia
description: Audio device
product: TU116 High Definition Audio Controller
vendor: NVIDIA Corporation
physical id: 0.1
bus info: pci@0000:03:00.1
logical name: card2
logical name: /dev/snd/controlC2
logical name: /dev/snd/hwC2D0
logical name: /dev/snd/pcmC2D10p
logical name: /dev/snd/pcmC2D11p
logical name: /dev/snd/pcmC2D3p
logical name: /dev/snd/pcmC2D7p
logical name: /dev/snd/pcmC2D8p
logical name: /dev/snd/pcmC2D9p
version: a1
width: 32 bits
clock: 33MHz
capabilities: pm msi pciexpress bus_master cap_list
configuration: driver=snd_hda_intel latency=0
resources: irq:109 memory:f7080000-f7083fff
*-input:0
product: HDA NVidia HDMI/DP,pcm=3
physical id: 0
logical name: input16
logical name: /dev/input/event10
*-input:1
product: HDA NVidia HDMI/DP,pcm=7
physical id: 1
logical name: input17
logical name: /dev/input/event11
*-input:2
product: HDA NVidia HDMI/DP,pcm=8
physical id: 2
logical name: input18
logical name: /dev/input/event12
*-input:3
product: HDA NVidia HDMI/DP,pcm=9
physical id: 3
logical name: input19
logical name: /dev/input/event13
*-input:4
product: HDA NVidia HDMI/DP,pcm=10
physical id: 4
logical name: input20
logical name: /dev/input/event14
*-input:5
product: HDA NVidia HDMI/DP,pcm=11
physical id: 5
logical name: input21
logical name: /dev/input/event15
*-usb
description: USB controller
product: TU116 USB 3.1 Host Controller
vendor: NVIDIA Corporation
physical id: 0.2
bus info: pci@0000:03:00.2
version: a1
width: 64 bits
clock: 33MHz
capabilities: msi pciexpress pm xhci cap_list
configuration: driver=xhci_hcd latency=0
resources: irq:40 memory:f2000000-f203ffff memory:f2040000-f204ffff
*-usbhost:0
product: xHCI Host Controller
vendor: Linux 5.15.0-27-generic xhci-hcd
physical id: 0
bus info: usb@3
logical name: usb3
version: 5.15
capabilities: usb-2.00
configuration: driver=hub slots=2 speed=480Mbit/s
*-usbhost:1
product: xHCI Host Controller
vendor: Linux 5.15.0-27-generic xhci-hcd
physical id: 1
bus info: usb@4
logical name: usb4
version: 5.15
capabilities: usb-3.10
configuration: driver=hub slots=4 speed=10000Mbit/s
*-serial
description: Serial bus controller
product: TU116 USB Type-C UCSI Controller
vendor: NVIDIA Corporation
physical id: 0.3
bus info: pci@0000:03:00.3
version: a1
width: 32 bits
clock: 33MHz
capabilities: msi pciexpress pm bus_master cap_list
configuration: driver=nvidia-gpu latency=0
resources: irq:38 memory:f7084000-f7084fff
*-pci:3
description: PCI bridge
product: Xeon E5/Core i7 IIO PCI Express Root Port 3a in PCI Express Mode
vendor: Intel Corporation
physical id: 3
bus info: pci@0000:00:03.0
version: 07
width: 32 bits
clock: 33MHz
capabilities: pci msi pciexpress pm normal_decode bus_master cap_list
configuration: driver=pcieport
resources: irq:30 memory:f7100000-f75fffff ioport:38000000(size=1048576)
*-network:0
description: Ethernet interface
product: I350 Gigabit Network Connection
vendor: Intel Corporation
physical id: 0
bus info: pci@0000:04:00.0
logical name: enp4s0f0
version: 01
serial: a0:36:9f:33:94:70
capacity: 1Gbit/s
width: 32 bits
clock: 33MHz
capabilities: pm msi msix pciexpress bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
configuration: autonegotiation=on broadcast=yes driver=igb driverversion=5.15.0-27-generic firmware=1.63, 0x80000a58 latency=0 link=no multicast=yes port=twisted pair
resources: irq:29 memory:f7400000-f74fffff memory:f750c000-f750ffff memory:38000000-3801ffff memory:38020000-3803ffff
*-network:1
description: Ethernet interface
product: I350 Gigabit Network Connection
vendor: Intel Corporation
physical id: 0.1
bus info: pci@0000:04:00.1
logical name: enp4s0f1
version: 01
serial: a0:36:9f:33:94:71
capacity: 1Gbit/s
width: 32 bits
clock: 33MHz
capabilities: pm msi msix pciexpress bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
configuration: autonegotiation=on broadcast=yes driver=igb driverversion=5.15.0-27-generic firmware=1.63, 0x80000a58 latency=0 link=no multicast=yes port=twisted pair
resources: irq:77 memory:f7300000-f73fffff memory:f7508000-f750bfff memory:38040000-3805ffff memory:38060000-3807ffff
*-network:2
description: Ethernet interface
product: I350 Gigabit Network Connection
vendor: Intel Corporation
physical id: 0.2
bus info: pci@0000:04:00.2
logical name: enp4s0f2
version: 01
serial: a0:36:9f:33:94:72
capacity: 1Gbit/s
width: 32 bits
clock: 33MHz
capabilities: pm msi msix pciexpress bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
configuration: autonegotiation=on broadcast=yes driver=igb driverversion=5.15.0-27-generic firmware=1.63, 0x80000a58 latency=0 link=no multicast=yes port=twisted pair
resources: irq:87 memory:f7200000-f72fffff memory:f7504000-f7507fff memory:38080000-3809ffff memory:380a0000-380bffff
*-network:3
description: Ethernet interface
product: I350 Gigabit Network Connection
vendor: Intel Corporation
physical id: 0.3
bus info: pci@0000:04:00.3
logical name: enp4s0f3
version: 01
serial: a0:36:9f:33:94:73
capacity: 1Gbit/s
width: 32 bits
clock: 33MHz
capabilities: pm msi msix pciexpress bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
configuration: autonegotiation=on broadcast=yes driver=igb driverversion=5.15.0-27-generic firmware=1.63, 0x80000a58 latency=0 link=no multicast=yes port=twisted pair
resources: irq:97 memory:f7100000-f71fffff memory:f7500000-f7503fff memory:380c0000-380dffff memory:380e0000-380fffff
*-generic:0 UNCLAIMED
description: System peripheral
product: Xeon E5/Core i7 Address Map, VTd_Misc, System Management
vendor: Intel Corporation
physical id: 5
bus info: pci@0000:00:05.0
version: 07
width: 32 bits
clock: 33MHz
capabilities: pciexpress cap_list
configuration: latency=0
*-generic:1 UNCLAIMED
description: System peripheral
product: Xeon E5/Core i7 Control Status and Global Errors
vendor: Intel Corporation
physical id: 5.2
bus info: pci@0000:00:05.2
version: 07
width: 32 bits
clock: 33MHz
capabilities: pciexpress cap_list
configuration: latency=0
*-generic:2 UNCLAIMED
description: PIC
product: Xeon E5/Core i7 I/O APIC
vendor: Intel Corporation
physical id: 5.4
bus info: pci@0000:00:05.4
version: 07
width: 32 bits
clock: 33MHz
capabilities: pm io_x_-apic bus_master cap_list
configuration: latency=0
resources: memory:f7a2d000-f7a2dfff
*-pci:4
description: PCI bridge
product: C600/X79 series chipset PCI Express Virtual Root Port
vendor: Intel Corporation
physical id: 11
bus info: pci@0000:00:11.0
version: 05
width: 32 bits
clock: 33MHz
capabilities: pci pciexpress pm msi normal_decode bus_master cap_list
configuration: driver=pcieport
resources: irq:16 ioport:6000(size=4096) memory:f7800000-f78fffff ioport:f2400000(size=5242880)
*-communication
description: Communication controller
product: C600/X79 series chipset MEI Controller #1
vendor: Intel Corporation
physical id: 16
bus info: pci@0000:00:16.0
version: 05
width: 64 bits
clock: 33MHz
capabilities: pm msi bus_master cap_list
configuration: driver=mei_me latency=0
resources: irq:107 memory:f7a2c000-f7a2c00f
*-network
description: Ethernet interface
product: 82579LM Gigabit Network Connection (Lewisville)
vendor: Intel Corporation
physical id: 19
bus info: pci@0000:00:19.0
logical name: eno1
version: 05
serial: b8:ca:3a:72:af:78
size: 1Gbit/s
capacity: 1Gbit/s
width: 32 bits
clock: 33MHz
capabilities: pm msi bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
configuration: autonegotiation=on broadcast=yes driver=e1000e driverversion=5.15.0-27-generic duplex=full firmware=0.13-4 ip=192.168.1.126 latency=0 link=yes multicast=yes port=twisted pair speed=1Gbit/s
resources: irq:76 memory:f7a00000-f7a1ffff memory:f7a29000-f7a29fff ioport:9040(size=32)
*-usb:0
description: USB controller
product: C600/X79 series chipset USB2 Enhanced Host Controller #2
vendor: Intel Corporation
physical id: 1a
bus info: pci@0000:00:1a.0
version: 05
width: 32 bits
clock: 33MHz
capabilities: pm debug ehci bus_master cap_list
configuration: driver=ehci-pci latency=0
resources: irq:16 memory:f7a28000-f7a283ff
*-usbhost
product: EHCI Host Controller
vendor: Linux 5.15.0-27-generic ehci_hcd
physical id: 1
bus info: usb@1
logical name: usb1
version: 5.15
capabilities: usb-2.00
configuration: driver=hub slots=2 speed=480Mbit/s
*-usb
description: USB hub
product: Integrated Rate Matching Hub
vendor: Intel Corp.
physical id: 1
bus info: usb@1:1
version: 0.00
capabilities: usb-2.00
configuration: driver=hub slots=6 speed=480Mbit/s
*-usb
description: Video
product: UVC Camera: UVC Camera
vendor: Ruision
physical id: 3
bus info: usb@1:1.3
logical name: card1
logical name: /dev/snd/controlC1
logical name: /dev/snd/pcmC1D0c
logical name: input15
logical name: /dev/input/event6
version: 4.09
serial: 20200622
capabilities: usb-2.00 usb
configuration: driver=snd-usb-audio maxpower=2mA speed=480Mbit/s
*-multimedia
description: Audio device
product: C600/X79 series chipset High Definition Audio Controller
vendor: Intel Corporation
physical id: 1b
bus info: pci@0000:00:1b.0
logical name: card0
logical name: /dev/snd/controlC0
logical name: /dev/snd/hwC0D0
logical name: /dev/snd/pcmC0D0c
logical name: /dev/snd/pcmC0D0p
version: 05
width: 64 bits
clock: 33MHz
capabilities: pm msi pciexpress bus_master cap_list
configuration: driver=snd_hda_intel latency=0
resources: irq:108 memory:f7a20000-f7a23fff
*-input:0
product: HDA Intel PCH Rear Mic
physical id: 0
logical name: input22
logical name: /dev/input/event16
*-input:1
product: HDA Intel PCH Front Mic
physical id: 1
logical name: input23
logical name: /dev/input/event17
*-input:2
product: HDA Intel PCH Line Out
physical id: 2
logical name: input24
logical name: /dev/input/event18
*-input:3
product: HDA Intel PCH Front Headphone
physical id: 3
logical name: input25
logical name: /dev/input/event19
*-pci:5
description: PCI bridge
product: C600/X79 series chipset PCI Express Root Port 4
vendor: Intel Corporation
physical id: 1c
bus info: pci@0000:00:1c.0
version: b5
width: 32 bits
clock: 33MHz
capabilities: pci pciexpress msi pm normal_decode bus_master cap_list
configuration: driver=pcieport
resources: irq:19
*-pci:6
description: PCI bridge
product: C600/X79 series chipset PCI Express Root Port 3
vendor: Intel Corporation
physical id: 1c.2
bus info: pci@0000:00:1c.2
version: b5
width: 32 bits
clock: 33MHz
capabilities: pci pciexpress msi pm normal_decode bus_master cap_list
configuration: driver=pcieport
resources: irq:18 memory:f7700000-f77fffff
*-usb
description: USB controller
product: uPD720200 USB 3.0 Host Controller
vendor: NEC Corporation
physical id: 0
bus info: pci@0000:07:00.0
version: 04
width: 64 bits
clock: 33MHz
capabilities: pm msi msix pciexpress xhci bus_master cap_list
configuration: driver=xhci_hcd latency=0
resources: irq:18 memory:f7700000-f7701fff
*-usbhost:0
product: xHCI Host Controller
vendor: Linux 5.15.0-27-generic xhci-hcd
physical id: 0
bus info: usb@5
logical name: usb5
version: 5.15
capabilities: usb-2.00
configuration: driver=hub slots=2 speed=480Mbit/s
*-usb
description: Human interface device
product: Wacom Intuos PT S 2 Pen
vendor: Wacom Co.,Ltd.
physical id: 2
bus info: usb@5:2
logical name: input13
logical name: /dev/input/event8
logical name: /dev/input/mouse2
logical name: input14
logical name: /dev/input/event9
logical name: /dev/input/js0
logical name: /dev/input/mouse3
logical name: input9
logical name: /dev/input/event7
logical name: /dev/input/mouse1
version: 1.00
capabilities: usb-2.00 usb
configuration: driver=usbhid maxpower=498mA speed=12Mbit/s
*-usbhost:1
product: xHCI Host Controller
vendor: Linux 5.15.0-27-generic xhci-hcd
physical id: 1
bus info: usb@6
logical name: usb6
version: 5.15
capabilities: usb-3.00
configuration: driver=hub slots=2 speed=5000Mbit/s
*-usb:1
description: USB controller
product: C600/X79 series chipset USB2 Enhanced Host Controller #1
vendor: Intel Corporation
physical id: 1d
bus info: pci@0000:00:1d.0
version: 05
width: 32 bits
clock: 33MHz
capabilities: pm debug ehci bus_master cap_list
configuration: driver=ehci-pci latency=0
resources: irq:17 memory:f7a27000-f7a273ff
*-usbhost
product: EHCI Host Controller
vendor: Linux 5.15.0-27-generic ehci_hcd
physical id: 1
bus info: usb@2
logical name: usb2
version: 5.15
capabilities: usb-2.00
configuration: driver=hub slots=2 speed=480Mbit/s
*-usb
description: USB hub
product: Integrated Rate Matching Hub
vendor: Intel Corp.
physical id: 1
bus info: usb@2:1
version: 0.00
capabilities: usb-2.00
configuration: driver=hub slots=8 speed=480Mbit/s
*-usb:0
description: Mass storage device
product: Portable Super Multi Drive
vendor: Hitachi-LG Data Storage Inc
physical id: 1
bus info: usb@2:1.1
logical name: scsi0
version: 0.00
serial: KX6Z5M01604
capabilities: usb-2.00 atapi emulated scsi-host
configuration: driver=usb-storage maxpower=500mA speed=480Mbit/s
*-cdrom
description: DVD-RAM writer
product: DVDRAM GP57ES40
vendor: HL-DT-ST
physical id: 0.0.0
bus info: scsi@0:0.0.0
logical name: /dev/cdrom
logical name: /dev/sr0
version: PB00
capabilities: removable audio cd-r cd-rw dvd dvd-r dvd-ram
configuration: status=nodisc
*-usb:1
description: Bluetooth wireless interface
product: CSR8510 A10
vendor: Cambridge Silicon Radio, Ltd
physical id: 2
bus info: usb@2:1.2
version: 88.91
capabilities: bluetooth usb-2.00
configuration: driver=btusb maxpower=100mA speed=12Mbit/s
*-usb:2
description: Human interface device
product: DaVinci Resolve Speed Editor
vendor: Blackmagic Design
physical id: 3
bus info: usb@2:1.3
version: 1.02
serial: 436ED47B8F494A51B6E82B4AE335C118
capabilities: usb-2.00
configuration: driver=usbhid maxpower=100mA speed=12Mbit/s
*-usb:3
description: Keyboard
product: Microsoft Wired Keyboard 600 System Control
vendor: Microsoft
physical id: 7
bus info: usb@2:1.7
logical name: input5
logical name: /dev/input/event3
logical name: input5::capslock
logical name: input5::compose
logical name: input5::kana
logical name: input5::numlock
logical name: input5::scrolllock
logical name: input6
logical name: /dev/input/event4
logical name: input7
logical name: /dev/input/event5
version: 3.00
capabilities: usb-2.00 usb
configuration: driver=usbhid maxpower=100mA speed=2Mbit/s
*-pci:7
description: PCI bridge
product: 82801 PCI Bridge
vendor: Intel Corporation
physical id: 1e
bus info: pci@0000:00:1e.0
version: a5
width: 32 bits
clock: 33MHz
capabilities: pci subtractive_decode bus_master cap_list
resources: ioport:5000(size=4096) memory:f7600000-f76fffff
*-firewire
description: FireWire (IEEE 1394)
product: VT6306/7/8 [Fire II(M)] IEEE 1394 OHCI Controller
vendor: VIA Technologies, Inc.
physical id: 4
bus info: pci@0000:08:04.0
version: 80
width: 32 bits
clock: 33MHz
capabilities: pm ohci bus_master cap_list
configuration: driver=firewire_ohci latency=64 maxlatency=32
resources: irq:16 memory:f7600000-f76007ff ioport:5000(size=128)
*-isa
description: ISA bridge
product: C600/X79 series chipset LPC Controller
vendor: Intel Corporation
physical id: 1f
bus info: pci@0000:00:1f.0
version: 05
width: 32 bits
clock: 33MHz
capabilities: isa bus_master cap_list
configuration: driver=lpc_ich latency=0
resources: irq:0
*-pnp00:00
product: PnP device PNP0c01
physical id: 0
capabilities: pnp
configuration: driver=system
*-pnp00:01
product: PnP device PNP0c02
physical id: 1
capabilities: pnp
configuration: driver=system
*-pnp00:02
product: PnP device PNP0b00
physical id: 2
capabilities: pnp
configuration: driver=rtc_cmos
*-pnp00:03
product: PnP device INT3f0d
physical id: 3
capabilities: pnp
configuration: driver=system
*-pnp00:04
product: PnP device PNP0c02
physical id: 4
capabilities: pnp
configuration: driver=system
*-pnp00:05
product: PnP device PNP0c01
physical id: 5
capabilities: pnp
configuration: driver=system
*-sata
description: SATA controller
product: C600/X79 series chipset 6-Port SATA AHCI Controller
vendor: Intel Corporation
physical id: 1f.2
bus info: pci@0000:00:1f.2
version: 05
width: 32 bits
clock: 66MHz
capabilities: sata msi pm ahci_1.0 bus_master cap_list
configuration: driver=ahci latency=0
resources: irq:75 ioport:9090(size=8) ioport:9080(size=4) ioport:9070(size=8) ioport:9060(size=4) ioport:9020(size=32) memory:f7a26000-f7a267ff
*-serial
description: SMBus
product: C600/X79 series chipset SMBus Host Controller
vendor: Intel Corporation
physical id: 1f.3
bus info: pci@0000:00:1f.3
version: 05
width: 64 bits
clock: 33MHz
configuration: driver=i801_smbus latency=0
resources: irq:18 memory:f7a25000-f7a250ff ioport:9000(size=32)
*-generic:0 UNCLAIMED
description: System peripheral
product: Xeon E5/Core i7 QPI Link 0
vendor: Intel Corporation
physical id: 6
bus info: pci@0000:3f:08.0
version: 07
width: 32 bits
clock: 33MHz
configuration: latency=0
*-generic:1 UNCLAIMED
description: System peripheral
product: Xeon E5/Core i7 QPI Link Reut 0
vendor: Intel Corporation
physical id: 7
bus info: pci@0000:3f:08.3
version: 07
width: 32 bits
clock: 33MHz
capabilities: pciexpress cap_list
configuration: latency=0
*-generic:2 UNCLAIMED
description: System peripheral
product: Xeon E5/Core i7 QPI Link Reut 0
vendor: Intel Corporation
physical id: 9
bus info: pci@0000:3f:08.4
version: 07
width: 32 bits
clock: 33MHz
capabilities: pciexpress cap_list
configuration: latency=0
*-generic:3 UNCLAIMED
description: System peripheral
product: Xeon E5/Core i7 QPI Link 1
vendor: Intel Corporation
physical id: a
bus info: pci@0000:3f:09.0
version: 07
width: 32 bits
clock: 33MHz
configuration: latency=0
*-generic:4 UNCLAIMED
description: System peripheral
product: Xeon E5/Core i7 QPI Link Reut 1
vendor: Intel Corporation
physical id: b
bus info: pci@0000:3f:09.3
version: 07
width: 32 bits
clock: 33MHz
capabilities: pciexpress cap_list
configuration: latency=0
*-generic:5 UNCLAIMED
description: System peripheral
product: Xeon E5/Core i7 QPI Link Reut 1
vendor: Intel Corporation
physical id: c
bus info: pci@0000:3f:09.4
version: 07
width: 32 bits
clock: 33MHz
capabilities: pciexpress cap_list
configuration: latency=0
*-generic:6 UNCLAIMED
description: System peripheral
product: Xeon E5/Core i7 Power Control Unit 0
vendor: Intel Corporation
physical id: d
bus info: pci@0000:3f:0a.0
version: 07
width: 32 bits
clock: 33MHz
configuration: latency=0
*-generic:7 UNCLAIMED
description: System peripheral
product: Xeon E5/Core i7 Power Control Unit 1
vendor: Intel Corporation
physical id: e
bus info: pci@0000:3f:0a.1
version: 07
width: 32 bits
clock: 33MHz
configuration: latency=0
*-generic:8 UNCLAIMED
description: System peripheral
product: Xeon E5/Core i7 Power Control Unit 2
vendor: Intel Corporation
physical id: f
bus info: pci@0000:3f:0a.2
version: 07
width: 32 bits
clock: 33MHz
configuration: latency=0
*-generic:9 UNCLAIMED
description: System peripheral
product: Xeon E5/Core i7 Power Control Unit 3
vendor: Intel Corporation
physical id: 10
bus info: pci@0000:3f:0a.3
version: 07
width: 32 bits
clock: 33MHz
configuration: latency=0
*-generic:10 UNCLAIMED
description: System peripheral
product: Xeon E5/Core i7 Interrupt Control Registers
vendor: Intel Corporation
physical id: 11
bus info: pci@0000:3f:0b.0
version: 07
width: 32 bits
clock: 33MHz
configuration: latency=0
*-generic:11 UNCLAIMED
description: System peripheral
product: Xeon E5/Core i7 Semaphore and Scratchpad Configuration Registers
vendor: Intel Corporation
physical id: 12
bus info: pci@0000:3f:0b.3
version: 07
width: 32 bits
clock: 33MHz
configuration: latency=0
*-generic:12 UNCLAIMED
description: System peripheral
product: Xeon E5/Core i7 Unicast Register 0
vendor: Intel Corporation
physical id: 13
bus info: pci@0000:3f:0c.0
version: 07
width: 32 bits
clock: 33MHz
configuration: latency=0
*-generic:13 UNCLAIMED
description: System peripheral
product: Xeon E5/Core i7 Unicast Register 0
vendor: Intel Corporation
physical id: 14
bus info: pci@0000:3f:0c.1
version: 07
width: 32 bits
clock: 33MHz
configuration: latency=0
*-generic:14 UNCLAIMED
description: System peripheral
product: Xeon E5/Core i7 Unicast Register 0
vendor: Intel Corporation
physical id: 15
bus info: pci@0000:3f:0c.2
version: 07
width: 32 bits
clock: 33MHz
configuration: latency=0
*-generic:15 UNCLAIMED
description: System peripheral
product: Xeon E5/Core i7 Integrated Memory Controller System Address Decoder 0
vendor: Intel Corporation
physical id: 16
bus info: pci@0000:3f:0c.6
version: 07
width: 32 bits
clock: 33MHz
configuration: latency=0
*-generic:16 UNCLAIMED
description: System peripheral
product: Xeon E5/Core i7 System Address Decoder
vendor: Intel Corporation
physical id: 17
bus info: pci@0000:3f:0c.7
version: 07
width: 32 bits
clock: 33MHz
configuration: latency=0
*-generic:17 UNCLAIMED
description: System peripheral
product: Xeon E5/Core i7 Unicast Register 0
vendor: Intel Corporation
physical id: 18
bus info: pci@0000:3f:0d.0
version: 07
width: 32 bits
clock: 33MHz
configuration: latency=0
*-generic:18 UNCLAIMED
description: System peripheral
product: Xeon E5/Core i7 Unicast Register 0
vendor: Intel Corporation
physical id: 19
bus info: pci@0000:3f:0d.1
version: 07
width: 32 bits
clock: 33MHz
configuration: latency=0
*-generic:19 UNCLAIMED
description: System peripheral
product: Xeon E5/Core i7 Unicast Register 0
vendor: Intel Corporation
physical id: 1a
bus info: pci@0000:3f:0d.2
version: 07
width: 32 bits
clock: 33MHz
configuration: latency=0
*-generic:20 UNCLAIMED
description: System peripheral
product: Xeon E5/Core i7 Integrated Memory Controller System Address Decoder 1
vendor: Intel Corporation
physical id: 1b
bus info: pci@0000:3f:0d.6
version: 07
width: 32 bits
clock: 33MHz
configuration: latency=0
*-generic:21 UNCLAIMED
description: System peripheral
product: Xeon E5/Core i7 Processor Home Agent
vendor: Intel Corporation
physical id: 1c
bus info: pci@0000:3f:0e.0
version: 07
width: 32 bits
clock: 33MHz
configuration: latency=0
*-generic:22
description: Performance counters
product: Xeon E5/Core i7 Processor Home Agent Performance Monitoring
vendor: Intel Corporation
physical id: 1d
bus info: pci@0000:3f:0e.1
version: 07
width: 32 bits
clock: 33MHz
configuration: driver=snbep_uncore latency=0
resources: irq:0
*-generic:23 UNCLAIMED
description: System peripheral
product: Xeon E5/Core i7 Integrated Memory Controller Registers
vendor: Intel Corporation
physical id: 1e
bus info: pci@0000:3f:0f.0
version: 07
width: 32 bits
clock: 33MHz
capabilities: pciexpress cap_list
configuration: latency=0
*-generic:24 UNCLAIMED
description: System peripheral
product: Xeon E5/Core i7 Integrated Memory Controller RAS Registers
vendor: Intel Corporation
physical id: 1f
bus info: pci@0000:3f:0f.1
version: 07
width: 32 bits
clock: 33MHz
capabilities: pciexpress cap_list
configuration: latency=0
*-generic:25 UNCLAIMED
description: System peripheral
product: Xeon E5/Core i7 Integrated Memory Controller Target Address Decoder 0
vendor: Intel Corporation
physical id: 20
bus info: pci@0000:3f:0f.2
version: 07
width: 32 bits
clock: 33MHz
capabilities: pciexpress cap_list
configuration: latency=0
*-generic:26 UNCLAIMED
description: System peripheral
product: Xeon E5/Core i7 Integrated Memory Controller Target Address Decoder 1
vendor: Intel Corporation
physical id: 21
bus info: pci@0000:3f:0f.3
version: 07
width: 32 bits
clock: 33MHz
capabilities: pciexpress cap_list
configuration: latency=0
*-generic:27 UNCLAIMED
description: System peripheral
product: Xeon E5/Core i7 Integrated Memory Controller Target Address Decoder 2
vendor: Intel Corporation
physical id: 22
bus info: pci@0000:3f:0f.4
version: 07
width: 32 bits
clock: 33MHz
capabilities: pciexpress cap_list
configuration: latency=0
*-generic:28 UNCLAIMED
description: System peripheral
product: Xeon E5/Core i7 Integrated Memory Controller Target Address Decoder 3
vendor: Intel Corporation
physical id: 23
bus info: pci@0000:3f:0f.5
version: 07
width: 32 bits
clock: 33MHz
capabilities: pciexpress cap_list
configuration: latency=0
*-generic:29 UNCLAIMED
description: System peripheral
product: Xeon E5/Core i7 Integrated Memory Controller Target Address Decoder 4
vendor: Intel Corporation
physical id: 24
bus info: pci@0000:3f:0f.6
version: 07
width: 32 bits
clock: 33MHz
capabilities: pciexpress
configuration: latency=0
*-generic:30
description: System peripheral
product: Xeon E5/Core i7 Integrated Memory Controller Channel 0-3 Thermal Control 0
vendor: Intel Corporation
physical id: 25
bus info: pci@0000:3f:10.0
version: 07
width: 32 bits
clock: 33MHz
capabilities: pciexpress cap_list
configuration: driver=snbep_uncore latency=0
resources: irq:0
*-generic:31
description: System peripheral
product: Xeon E5/Core i7 Integrated Memory Controller Channel 0-3 Thermal Control 1
vendor: Intel Corporation
physical id: 26
bus info: pci@0000:3f:10.1
version: 07
width: 32 bits
clock: 33MHz
capabilities: pciexpress cap_list
configuration: driver=snbep_uncore latency=0
resources: irq:0
*-generic:32 UNCLAIMED
description: System peripheral
product: Xeon E5/Core i7 Integrated Memory Controller ERROR Registers 0
vendor: Intel Corporation
physical id: 27
bus info: pci@0000:3f:10.2
version: 07
width: 32 bits
clock: 33MHz
capabilities: pciexpress cap_list
configuration: latency=0
*-generic:33 UNCLAIMED
description: System peripheral
product: Xeon E5/Core i7 Integrated Memory Controller ERROR Registers 1
vendor: Intel Corporation
physical id: 28
bus info: pci@0000:3f:10.3
version: 07
width: 32 bits
clock: 33MHz
capabilities: pciexpress cap_list
configuration: latency=0
*-generic:34
description: System peripheral
product: Xeon E5/Core i7 Integrated Memory Controller Channel 0-3 Thermal Control 2
vendor: Intel Corporation
physical id: 29
bus info: pci@0000:3f:10.4
version: 07
width: 32 bits
clock: 33MHz
capabilities: pciexpress cap_list
configuration: driver=snbep_uncore latency=0
resources: irq:0
*-generic:35
description: System peripheral
product: Xeon E5/Core i7 Integrated Memory Controller Channel 0-3 Thermal Control 3
vendor: Intel Corporation
physical id: 2a
bus info: pci@0000:3f:10.5
version: 07
width: 32 bits
clock: 33MHz
capabilities: pciexpress cap_list
configuration: driver=snbep_uncore latency=0
resources: irq:0
*-generic:36 UNCLAIMED
description: System peripheral
product: Xeon E5/Core i7 Integrated Memory Controller ERROR Registers 2
vendor: Intel Corporation
physical id: 2b
bus info: pci@0000:3f:10.6
version: 07
width: 32 bits
clock: 33MHz
capabilities: pciexpress cap_list
configuration: latency=0
*-generic:37 UNCLAIMED
description: System peripheral
product: Xeon E5/Core i7 Integrated Memory Controller ERROR Registers 3
vendor: Intel Corporation
physical id: 2c
bus info: pci@0000:3f:10.7
version: 07
width: 32 bits
clock: 33MHz
capabilities: pciexpress cap_list
configuration: latency=0
*-generic:38 UNCLAIMED
description: System peripheral
product: Xeon E5/Core i7 DDRIO
vendor: Intel Corporation
physical id: 2d
bus info: pci@0000:3f:11.0
version: 07
width: 32 bits
clock: 33MHz
capabilities: pciexpress
configuration: latency=0
*-generic:39 UNCLAIMED
description: System peripheral
product: Xeon E5/Core i7 R2PCIe
vendor: Intel Corporation
physical id: 2e
bus info: pci@0000:3f:13.0
version: 07
width: 32 bits
clock: 33MHz
configuration: latency=0
*-generic:40
description: Performance counters
product: Xeon E5/Core i7 Ring to PCI Express Performance Monitor
vendor: Intel Corporation
physical id: 2f
bus info: pci@0000:3f:13.1
version: 07
width: 32 bits
clock: 33MHz
configuration: driver=snbep_uncore latency=0
resources: irq:0
*-generic:41 UNCLAIMED
description: Performance counters
product: Xeon E5/Core i7 QuickPath Interconnect Agent Ring Registers
vendor: Intel Corporation
physical id: 30
bus info: pci@0000:3f:13.4
version: 07
width: 32 bits
clock: 33MHz
configuration: latency=0
*-generic:42
description: Performance counters
product: Xeon E5/Core i7 Ring to QuickPath Interconnect Link 0 Performance Monitor
vendor: Intel Corporation
physical id: 31
bus info: pci@0000:3f:13.5
version: 07
width: 32 bits
clock: 33MHz
configuration: driver=snbep_uncore latency=0
resources: irq:0
*-generic:43
description: System peripheral
product: Xeon E5/Core i7 Ring to QuickPath Interconnect Link 1 Performance Monitor
vendor: Intel Corporation
physical id: 33
bus info: pci@0000:3f:13.6
version: 07
width: 32 bits
clock: 33MHz
configuration: driver=snbep_uncore latency=0
resources: irq:0
*-pci:1
description: PCI bridge
product: Xeon E5/Core i7 DMI2 in PCI Express Mode
vendor: Intel Corporation
physical id: 101
bus info: pci@0000:40:00.0
version: 07
width: 32 bits
clock: 33MHz
capabilities: pci msi pciexpress pm normal_decode bus_master cap_list
configuration: driver=pcieport
resources: irq:32
*-pci:2
description: PCI bridge
product: Xeon E5/Core i7 IIO PCI Express Root Port 2a
vendor: Intel Corporation
physical id: 2
bus info: pci@0000:40:02.0
version: 07
width: 32 bits
clock: 33MHz
capabilities: pci msi pciexpress pm normal_decode bus_master cap_list
configuration: driver=pcieport
resources: irq:34
*-pci:3
description: PCI bridge
product: Xeon E5/Core i7 IIO PCI Express Root Port 3a in PCI Express Mode
vendor: Intel Corporation
physical id: 3
bus info: pci@0000:40:03.0
version: 07
width: 32 bits
clock: 33MHz
capabilities: pci msi pciexpress pm normal_decode bus_master cap_list
configuration: driver=pcieport
resources: irq:36
*-generic:44 UNCLAIMED
description: System peripheral
product: Xeon E5/Core i7 Address Map, VTd_Misc, System Management
vendor: Intel Corporation
physical id: 5
bus info: pci@0000:40:05.0
version: 07
width: 32 bits
clock: 33MHz
capabilities: pciexpress cap_list
configuration: latency=0

Ok, I've run makeresolvedeb v1.6.0 on Resolve 18b2 on the following system

Sony Vaio Pro laptop (SVP1321B4E)
i7-4500U CPU @1.8GHz
4GB RAM
SATA SSD

Overall, it took 40 minutes. I get these timings:

Extracting archive took 57 seconds
dpkg-deb: building package message issues at 1 minute 59 seconds
Process finished 39 minutes 43 seconds

During the package build, I could see tar reading from disk at between 3 and 4 MB/s
I could see dpkg-deb writing to disk at between 1.1 and 3.5MB/s for the first 18 minutes
After that, the dpkg-deb write speed dropped to about 150KB/s
At about 30 minutes, the write speed went back up to about 4MB/s.
At 38 minutes, tar stopped, and the dpkg-deb write speed went up to 100MB/s

BTW, on Ubuntu 22.04, it's necessary to install libfuse2 before running makeresolvedeb.

My studio dongle doesn't seem to be working on 18b or 18.0b2. When I attempt to launch a project that has high framerate or high resolution (that exceeds free version limits) I get the error message pictured below despite a studio dongle connected. I've tried connecting to different USB ports and controllers with no success. Also, when I find a project that will open, it will not play studio only codecs either (10-bit H.264 for example).



Pop!_OS 22.04 X11 GNOME 42
Kernel 5.17.5-76051705-generic
NVIDIA 3080 Ti 510.68.02-1pop0~1651161204~22.04~46a1f79
mrd1.6.0

My studio dongle doesn't seem to be working on 18b or 18.0b2. When I attempt to launch a project that has high framerate or high resolution (that exceeds free version limits) I get the error message pictured below despite a studio dongle connected. I've tried connecting to different USB ports and controllers with no success. Also, when I find a project that will open, it will not play studio only codecs either (10-bit H.264 for example).

Pop!_OS 22.04 X11 GNOME 42
Kernel 5.17.5-76051705-generic
NVIDIA 3080 Ti 510.68.02-1pop0~1651161204~22.04~46a1f79
mrd1.6.0

It looks like you may have accidentally installed the free version. The Studio version will not even start without a valid license from either a USB dongle or an online license key.

Thank you for the good information Tim! I'm surprised libfuse2 is not included in the new Ubuntu 22.04 release. Need to to some more testing now that 22.04 is released.

The disks are connected to a PERC H710P controller.

I think we may have part of the problem right here. I've had performance issues in the past with controllers like the PERC H710P. The problem is that the PERC H710P only has 1GB och cache that will saturate almost instantly (even with just two drives) during long running heavy random access, like what happens when running dpkg-deb.

I would actually recommend hooking up the SATA drives directly to the onboard controller of your T5600 instead and run them in an "md" software RAID configuration.

Did a quick test on a Dell Precision 7560 with a Xeon W-11855M, 64GB and single PCIe drive on Ubuntu 20.04. This completed in 3m35s for Resolve Studio 17.4.6 using makeresolvedeb 1.6.0.

Thank you for the good information Tim! I'm surprised libfuse2 is not included in the new Ubuntu 22.04 release. Need to to some more testing now that 22.04 is released.

The disks are connected to a PERC H710P controller.

I think we may have part of the problem right here. I've had performance issues in the past with controllers like the PERC H710P. The problem is that the PERC H710P only has 1GB och cache that will saturate almost instantly (even with just two drives) during long running heavy random access, like what happens when running dpkg-deb.

I would actually recommend hooking up the SATA drives directly to the onboard controller of your T5600 instead and run them in an "md" software RAID configuration.

Did a quick test on a Dell Precision 7560 with a Xeon W-11855M, 64GB and single PCIe drive on Ubuntu 20.04. This completed in 3m35s for Resolve Studio 17.4.6 using makeresolvedeb 1.6.0.

Thanks for the reply Daniel,

I'll look at re-configuring the storage, but am in no rush as I have quite a lot on that workstation, and it's all working!

Your work on makeresolvedeb is much appreciated:-)

It looks like you may have accidentally installed the free version. The Studio version will not even start without a valid license from either a USB dongle or an online license key.

Oh gosh, how embarrassing. I think you're correct, building a new .deb from the studio installer now. Thanks for your hard work and your reply here

Hello everyone,
Bumping this thread to report that generating the Resolve deb takes very long time on my machine also, while the Fusion deb is generated alot quicker
and does not seem to be proportional to the dimension of the packages
this on a Ryzen 3950x, nvme disk

Anyways this is not a problem for me, only to report another experience

I'm experiencing some problems building the Fusion 18 versions deb
builds and installs fine, but I'm not able to launch it, system menu wont show icons and cant find anything from the terminal.
17 versions works as expected
Ubuntu Studio 21.10 and 22.04
Thank you

Hi al,

first of all thanks you Daniel Tufvesson for the incrdible work with makeresolvedeb.

Actually we're trying to set up Resolve 18 in a Ubuntu 20.04 machine with the Mini Panel.

Studio installation went well , with no errors, and when we open Control Panel Setup, the panel is shown, and we can even change Panel Network configuration but when we try to configure it with resolve, it doesn't work. We have tryied to run as root and change it to ethernet configuration with no results.

in ResolveDebug.txt we can see

Code: Select all

| The DaVinci Control Panels Setup application is not compatible with this version of Resolve. Please re-install Resolve with the DaVinci Control Panels Setup application option enabled in the installer.

In panel.log

Code: Select all

opened log file
Opening communication to resolve..
Failed to create listener
Unsupported DaVinci Panel API Version (0.0), please update
Resolve discovery

Please any help or running configuration with linux/18/mini panel

Thanks