Desktop Video 12.9 Not Working in Linux [Solved]

I've just rebuilt my home workstation for Resolve Studio around Linux Mint 21.3. The Studio 19.x Betas are working with Linux, but Desktop Video 12.9 is not. Desktop Video Setup says; "No Desktop Video Device Detected".

If I swap the boot disk back to Windows 10, Desktop Video 12.9-for-Windows finds my Intensity Shuttle and I get a picture on my external monitor.

Back in Mint, I did a USB scan. Here’s the Terminal output:

g6710@Predator-Mint:~$ lsusb
Bus 002 Device 002: ID 1edb:bd3b Blackmagic design Intensity Shuttle
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 006: ID 0bda:0153 Realtek Semiconductor Corp. 3-in-1 (SD/SDHC/SDXC) Card Reader
Bus 001 Device 005: ID 096e:0201 Feitian Technologies, Inc. USB DONGLE
Bus 001 Device 004: ID 1edb:da0e Blackmagic design DaVinci Resolve Speed Editor
Bus 001 Device 003: ID 062a:4102 MosArt Semiconductor Corp. Wireless Mouse
Bus 001 Device 007: ID 8087:0a2a Intel Corp. Bluetooth wireless interface
Bus 001 Device 002: ID 046d:c33a Logitech, Inc. G413 Gaming Keyboard
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
g6710@Predator-Mint:~$

Mint can see both the Intensity Shuttle and the Speed Editor. Resolve 19.x also sees and works with the Speed Editor just fine.

I then tested to see if the Desktop Video driver was loading. Here’s the Terminal output:

g6710@Predator-Mint:~$ lsmod | grep blackmagic
g6710@Predator-Mint:~$

No response, the Driver isn’t loading.

What can I do to get the driver to load and get Resolve 19’s picture out to the external monitor?

Log Archive can be found here: https://we.tl/t-l5xbcftK4O The link expires 05-16-2024

Thanks,
Mark

NVieville posted a fix for Desktop Video drivers for the 6.8 kernel here: viewtopic.php?f=12&t=199022#p1034293

And here's a .deb file with the Desktop Video v12.9 drivers with his 6.8 kernel fix already applied: https://uploadnow.io/f/HWWTl3d

I gave it the college try, but Desktop Video still can't see my Intensity hardware. I believe it failed because Linux Mint uses different Kernels. I'm currently running 5.15.0-105. I switched to 6.5.0-35 just to see if the DEB would work, but it's just too different.

Many thanks to NVieville for creating the v12.9 patch and to niber for leading me to it.

Mark

It saying your device is not there makes me think the driver had trouble installing. Did you get an error message when you tried to install the drivers? The Eddy (GUI Deb installer) on Pop!_OS didn't give me any errors, but when I installed from the terminal, I could see all the errors. If you install from the terminal, you can see the errors better. Guessing this might be the command to install it:

sudo dpkg -i ~/Downloads/Blackmagic_Desktop_Video_Linux_12.9/deb/X86_64/desktopvideo_12.9a3_amd64.deb

nilber,

Using the Terminal to expose errors was a good idea, here’s how it went.

I went back to Blackmagic’s official 12.9 release and chose the deb files from the x86_64 folder and started with desktopvideo_12.9a3_amd64.deb. Here’s the Terminal;

g6710@Predator-Mint:~/Downloads$ sudo dpkg -i desktopvideo_12.9a3_amd64.deb
(Reading database ... 646590 files and directories currently installed.)
Preparing to unpack desktopvideo_12.9a3_amd64.deb ...
Stopping systemd services...
DesktopVideoHelper
Disabling systemd services...
DesktopVideoHelper
Unloading modules...
Removing old drivers...
Unpacking desktopvideo (12.9a3) over (12.9a3) ...
Setting up desktopvideo (12.9a3) ...
Preparing new blackmagic driver for 5.15.0-107-generic kernel...
Adding to DKMS
Building
Installing
Preparing new blackmagic-io driver for 5.15.0-107-generic kernel...
Adding to DKMS
Building
Installing
Loading modules...
blackmagic
blackmagic_io
Enabling systemd services...
DesktopVideoHelper
Starting systemd services...
DesktopVideoHelper
Processing triggers for man-db (2.10.2-1) ...
Processing triggers for libc-bin (2.35-0ubuntu3.7) ...

There were no errors, plus the blackmagic-io driver was properly prepped for the 5.15.0-107 Kernel. I moved on to desktopvideo-gui_12.9a3_amd64.deb. Here’s the Terminal:

g6710@Predator-Mint:~/Downloads$ sudo dpkg -i desktopvideo-gui_12.9a3_amd64.deb
(Reading database ... 646590 files and directories currently installed.)
Preparing to unpack desktopvideo-gui_12.9a3_amd64.deb ...
Unpacking desktopvideo-gui (12.9a3) over (12.9a3) ...
Setting up desktopvideo-gui (12.9a3) ...
Processing triggers for hicolor-icon-theme (0.17-2) ...
Processing triggers for man-db (2.10.2-1) ...
Processing triggers for gnome-menus (3.36.0-1ubuntu3) ...
Processing triggers for desktop-file-utils (0.26+mint3+victoria) ...
Processing triggers for mailcap (3.70+nmu1ubuntu1) ...
g6710@Predator-Mint:~/Downloads$

Again, no errors. Then I checked to see the status of the Blackmagic io.

g6710@Predator-Mint:~$ dkms status -m blackmagic-io -k `uname -r`
blackmagic-io/12.9a3, 5.15.0-107-generic, x86_64: installed

The driver is installed. Next I tested to see if the driver was loaded;

g6710@Predator-Mint:~$ lsmod | grep blackmagic
blackmagic_io 2076672 0

The driver was loaded so, finally I checked to see if the Blackmagic Desktop app could see the Intensity hardware:

g6710@Predator-Mint:~$ lspci | grep Blackmagic
g6710@Predator-Mint:~$

No output, the Desktop app still can’t find the hardware.

As a double-check I re-scanned the USB bus:

g6710@Predator-Mint:~$ lsusb
Bus 002 Device 002: ID 1edb:bd3b Blackmagic design Intensity Shuttle
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 006: ID 0bda:0153 Realtek Semiconductor Corp. 3-in-1 (SD/SDHC/SDXC) Card Reader
Bus 001 Device 005: ID 096e:0201 Feitian Technologies, Inc. USB DONGLE
Bus 001 Device 004: ID 1edb:da0e Blackmagic design DaVinci Resolve Speed Editor
Bus 001 Device 003: ID 046d:c33a Logitech, Inc. G413 Gaming Keyboard
Bus 001 Device 007: ID 8087:0a2a Intel Corp. Bluetooth wireless interface
Bus 001 Device 002: ID 062a:4102 MosArt Semiconductor Corp. Wireless Mouse
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
g6710@Predator-Mint:~$

Mint can see the Blackmagic hardware. I just need to convince the Desktop Video app that it’s there.

Mark

I installed the new Desktop Video 14.0 this evening, but still failed to get the external monitor to work. Here's the Terminal output:

6710@Predator-Mint:~/Downloads$ sudo dpkg -i desktopvideo_*.deb
[sudo] password for g6710:
(Reading database ... 626754 files and directories currently installed.)
Preparing to unpack desktopvideo_14.0a1_amd64.deb ...
Stopping systemd services...
DesktopVideoHelper
Disabling systemd services...
DesktopVideoHelper
Unloading modules...
blackmagic_io
Removing old drivers...
blackmagic
blackmagic-io
Unpacking desktopvideo (14.0a1) over (14.0a1) ...
Setting up desktopvideo (14.0a1) ...
Preparing new blackmagic driver for 5.15.0-107-generic kernel...
Adding to DKMS
Building
Installing
Preparing new blackmagic-io driver for 5.15.0-107-generic kernel...
Adding to DKMS
Building
Installing
Loading modules...
blackmagic
blackmagic_io
Enabling systemd services...
DesktopVideoHelper
Starting systemd services...
DesktopVideoHelper
Processing triggers for man-db (2.10.2-1) ...
Processing triggers for libc-bin (2.35-0ubuntu3.7) ...
g6710@Predator-Mint:~/Downloads$

No Errors. The drivers for the Kernels were built and installed and services were started. I tested for the driver:

g6710@Predator-Mint:~/Downloads$ lsmod | grep blackmagic
blackmagic_io 2080768 0
blackmagic 630784 0

Both drivers are there. Next I tested if the Blackmagic hardware could be seen:

6710@Predator-Mint:~/Downloads$ lspci | grep Blackmagic
g6710@Predator-Mint:~/Downloads$

Still no output, the hardware cannot be seen. Linux Mint can see both the Intensity Shuttle and the Speed Editor:

g6710@Predator-Mint:~/Downloads$ lsusb
Bus 002 Device 002: ID 1edb:bd3b Blackmagic design Intensity Shuttle
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 006: ID 0bda:0153 Realtek Semiconductor Corp. 3-in-1 (SD/SDHC/SDXC) Card Reader
Bus 001 Device 005: ID 096e:0201 Feitian Technologies, Inc. USB DONGLE
Bus 001 Device 004: ID 1edb:da0e Blackmagic design DaVinci Resolve Speed Editor
Bus 001 Device 003: ID 046d:c33a Logitech, Inc. G413 Gaming Keyboard
Bus 001 Device 007: ID 8087:0a2a Intel Corp. Bluetooth wireless interface
Bus 001 Device 002: ID 062a:4102 MosArt Semiconductor Corp. Wireless Mouse
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
g6710@Predator-Mint:~/Downloads$

Resolve 19 Beta 2 can see and use the Speed Editor. I'm still missing something that will get Desktop Video working.

[Dwaine Maggart]

If you run:

BlackmagicFirmwareUpdater status

Does it see the device?

Hi Dwaine,
No, it doesn't see it. Here's the Terminal:

g6710@Predator-Mint:~$ lsmod | grep blackmagic
blackmagic 630784 0
blackmagic_io 2080768 0

g6710@Predator-Mint:~$ BlackmagicFirmwareUpdater status
No devices available

g6710@Predator-Mint:~$ lsusb
Bus 002 Device 002: ID 1edb:bd3b Blackmagic design Intensity Shuttle
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 006: ID 0bda:0153 Realtek Semiconductor Corp. 3-in-1 (SD/SDHC/SDXC) Card Reader
Bus 001 Device 005: ID 096e:0201 Feitian Technologies, Inc. USB DONGLE
Bus 001 Device 004: ID 1edb:da0e Blackmagic design DaVinci Resolve Speed Editor
Bus 001 Device 003: ID 046d:c33a Logitech, Inc. G413 Gaming Keyboard
Bus 001 Device 007: ID 8087:0a2a Intel Corp. Bluetooth wireless interface
Bus 001 Device 002: ID 062a:4102 MosArt Semiconductor Corp. Wireless Mouse
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
g6710@Predator-Mint:~$

Following up, I'm wondering if there are missing instructions that are usually written in a file that Distros like CentOS and Rocky use to load the installed blackmagic-io drivers and make them available to Linux to then be used by the Blackmagic applications. If so, what are the instructions and what file should they be placed in?

[Dwaine Maggart]

I don't think there is an issue with Desktop Video. Digging a USB Intensity Shuttle out of the archives, I see the same behavior on Rocky 8.6. But it's not a Desktop Video issue, because it's working fine with the DeckLink 8K Pro card that's in the system. But it doesn't see the Intensity Shuttle. I suspect something USB related, perhaps. This device has been EOL for several years, so not sure there is much that will be done. It does work on Windows and Mac with Desktop Video 12.9. So apparently only a Linux issue.

Yes, swapping my boot drive back to Windows 10, the Intensity Shuttle works fine with Desktop Video 12.9 and the new 14.0. Beyond the 16-lane slot for the nVidia GPU, this motherboard only has two single-lane slots so the USB-3 Intensity Shuttle was a good solution at the time. Thanks for taking the time to find and test an Intensity Shuttle with Rocky Linux.

I don't think there is an issue with Desktop Video. Digging a USB Intensity Shuttle out of the archives, I see the same behavior on Rocky 8.6. But it's not a Desktop Video issue, because it's working fine with the DeckLink 8K Pro card that's in the system. But it doesn't see the Intensity Shuttle. I suspect something USB related, perhaps. This device has been EOL for several years, so not sure there is much that will be done. It does work on Windows and Mac with Desktop Video 12.9. So apparently only a Linux issue.

The USB Intensity Shuttle just wasn't going to work, so to get my external monitor working, this is what I did:

I put a 1x to 16x riser in a single-lane slot on the motherboard and placed a Decklink Mini-Monitor 4K, that I pulled from another workstation, into the 16x riser.

g6710@Predator-Mint:~$ lsmod | grep blackmagic
blackmagic_io 2080768 2

Linux Mint loaded the driver

g6710@Predator-Mint:~$ lspci | grep Blackmagic
05:00.0 Multimedia video controller: Blackmagic Design DeckLink Mini Monitor 4K

Mint could see the Decklink card, Desktop Video 14.0 could see the DeckLink card and Resolve 19 B3 could see the DeckLink card.

And I have Resolve output on my external monitor!

Thank you to everyone who pitched in with suggestions as to how to fix this problem.

Mark