Installing drivers for blackmagic intensity pro 4K

Greetings my new found friends.
I’m switching from another distro as I’ve heard great things about tumbleweed.
One of the things I really need to use on my computer is this capture card, the drivers are available on the official website, the tar.gz files though only contain etc and usr folders, with subfolders inside.
Official installers are only available for fedora and debian based distros.
I’m a bit of a noob and coming from arch I confess I can’t do a lot without the help of aur. Usually I’d have to configure and make install I reckon, but in this case there’s no files to do that and the readme file sadly didn’t help me a lot.

You didn’t tell what you want to install especially. The homepage provides different drivers/software. Please point to the relevant software/driver. If you mean “Blackmagic_Desktop_Video_Linux” the explanations in the readme are good and complete and also relevant rpm’s are contained in the archive.

The file I’m trying to download and install is this: https://www.blackmagicdesign.com/support/download/2de27a45d5454a0aa37353b4a742c179/Linux

I also opened the pdf at https://documents.blackmagicdesign.com/UserManuals/DesktopVideoManual.pdf?_v=1657522810000

That, however, on page 14 suggests to refer to the readme file included in the archive.
In the readme there’s a section for installing on other linux based distributions, at like 232.
Leaving aside any joke I could make about the line saying experts only and me not being one, all I could gather was to check dependencies, which if I understand correctly is just having dkms installed, which I do.
It proceeds to say the files are structured in the binary tarball as they should be installed.

To my ignorant self this explains little, but I would be really happy to learn, learning is one of the main reasons why I don’t use a “noob distro”.
Or maybe I’m just missing something obvious that I didn’t notice.

Page 14 instructs you to install the 3 packages

The desktopvideo package provides the core drivers and API libraries.– 
The desktopvideo-gui package provides the Desktop Video Setup software.– 
The mediaexpress package provides a simple capture and playback utility.
Double click the packages you wish to install and follow the onscreen instructions.If you see any messages about missing dependencies, ensure they are installed firstand then rerun the Desktop Video installer

These three packages are in the /rpm/x86_64 directory of the unpacked archive. As openSUSE uses rpm this should be logic:

downloads/Blackmagic_Desktop_Video_Linux_12.4> ls -laR
.:
insgesamt 44
drwxr-xr-x 5 ich users  4096 13. Jul 01:25 **.**
drwxrwxr-x 4 ich  1000  4096 26. Aug 12:21 **..**
drwxr-xr-x 4 ich users  4096 13. Jul 01:24 **deb**
-rw-r--r-- 1 ich users  6200 13. Jul 01:25 License.txt
drwxr-xr-x 4 ich users  4096 13. Jul 01:24 **other**
-rw-r--r-- 1 ich users 13176 13. Jul 01:25 ReadMe.txt
drwxr-xr-x 3 ich users  4096 13. Jul 01:24 **rpm**

<snip>

./rpm:
insgesamt 12
drwxr-xr-x 3 ich users 4096 13. Jul 01:24 **.**
drwxr-xr-x 5 ich users 4096 13. Jul 01:25 **..**
drwxr-xr-x 2 ich users 4096 13. Jul 01:25 **x86_64**

./rpm/x86_64:
insgesamt 163260
drwxr-xr-x 2 ich users      4096 13. Jul 01:25 **.**
drwxr-xr-x 3 ich users      4096 13. Jul 01:24 **..**
-rw-r--r-- 1 ich users 117575488 13. Jul 01:24 desktopvideo-12.4a4.x86_64.rpm
-rw-r--r-- 1 ich users  35133720 13. Jul 01:24 desktopvideo-gui-12.4a4.x86_64.rpm
-rw-r--r-- 1 ich users  14458588 13. Jul 01:25 mediaexpress-3.8.1a4.x86_64.rpm


Ok, my bad. That explains it. I was under the impression that zypper was the only way to install and update packages, I didn’t realize rpm was also available.
Should I stop using zypper?
Thank you for your time.

You don’t need to stop using zypper. It is recommended to use instead!

In your case as example just issue following command to install the following package (zypper will pull necessary dependencys):

sudo zypper in /your_path_here/rpm/x86_64/desktopvideo-12.4a4.x86_64.rpm /your_path_here/rpm/x86_64/desktopvideo-gui-12.4a4.x86_64.rpm /your_path_here/rpm/x86_64/mediaexpress-3.8.1a4.x86_64.rpm  
Loading repository data...
Reading installed packages...
Resolving package dependencies...

The following 12 NEW packages are going to be installed:
  desktopvideo desktopvideo-gui dkms fipscheck kernel-syms libfipscheck1 mediaexpress mozilla-nss-tools openssl pesign pesign-obs-integration suse-module-tools-legacy

12 new packages to install.
Overall download size: 163.3 MiB. Already cached: 0 B. After the operation, additional 239.3 MiB will be used.

**Continue? [y/n/v/...? shows all options] (y):**

I understand, thank you very much!
I’m sorry if the question seemed stupid, I understand where you might be coming from.
But I appreciate your help.

BTW, you can NOT install an RPM by “double click” on it (as I think I read somewhere above).

Clicking on something assumes a GUI.
Installing an RPM in a system requires Superuser (root).

As root should never log in in the GUI, those two are incompatible.

You can install an RPM (as root) using rpm, but in openSUSE it is probably cleverer to use zypper for it. Because zypper will active check for dependencies and install them when available. It also will then have the package in it’s database.

zypper in ........rpm

It was mentioned on the blackmagic homepage to do so. Maybe with openSUSE this is not possible. Other rpm based distributions offer 3 options when you doubleclick a rpm:

  • Install (this will ask for root pw. other distributions make proper use of policykit to make this possible)
  • save
  • exit (do nothing)

With openSUSE you can also do a right click on the rpm and chose “Install with Yast”.

It may be me, but first I have a Linux desktop that does not know anything like the RSI generating “double click” (that is a silly Microsoft invention).
Second, I would never do such things as root from a GUI, but use a terminal emulator (like Konsole or xterm).

It is just old-fashioned me. Forget about it.

That means you would never use yast-software? Because that is the equivalent in other distributions when you double-click an rpm. It asks for your root pw and installs the rpm with the software management tools from the distribution. There is no other “GUI” than the one from the software management tool involved. And software management tools need root rights (or wheel group dependend on the distribution) to work, even on openSUSE (yast-software).

As example im using both variants. “zypper dup” and stuff like that from a console (as it is more verbose) for system updates, and yast-software (GUI) when i search for a package and want to install it afterwards…
So both worlds exists. Both worlds are valid and work as intended from the software distributors. And both are safe. Even if you need to put your root pw to open yast or yast-software (both are GUI-tools). So this is no valid argument…

  • I use YaST > Software.
  • Double click in my KDE session does probably start two of the same actions as defined in my KDE file type associations (or how it is called in the English language version) (that works in fact on file name suffices and not on types).
  • I was talking on this specific case about software downloaded from a third party site. I would download as normal user, unpack as normal user (though I probably would use the CLI to unpack a tar file using tar, surprise!). After that it depends very much on what you get by the unpack, but in this case, I would just use a “su -” CLI session to install using zypper.

But again, that is my very, very personal way of handling things. Apart from the “double click” that should not exist in Linux at all.

You can use the good old Yast2 with the mouse also.
Once you right click the rpm with the mouse yast2-software management is an option.

For me I will keep those 3 rpm packages on a folder named blackmagic.
Add the blackmagic folder as a repository.
Then install those packages using yast2-software management.
That will be a simple solution. Everyone seems to forget the beauty of yast.:slight_smile: this days.

ok…this was mentioned several posts ago lol!

Ok, my bad, it’s very different when you get old and both eye retinas were surgically reattached.
Reading is kinda a bit of a problem:(

Double click is available in KDE. You can set up KDE (Dolphin) to open *.rpm in YaST with double click.

Is that the RSI setting?rotfl!

I appreciate that this thread is from over a year ago, but I wondered whether after installing the Blackmagic_Desktop_Video_Linux drivers you could use the Blackmagic Intensity Pro 4K?

I’ve installed the drivers and they appear in dmesg at boot time and in lspci and lsmod but MediaExpress does not list the device at all.

[    3.833039] blackmagic_io: loading out-of-tree module taints kernel.
[    3.833043] blackmagic_io: module license 'Proprietary' taints kernel.
[    3.833044] Disabling lock debugging due to kernel taint
[    3.833045] blackmagic_io: module verification failed: signature and/or required key missing - tainting kernel
[    3.833046] blackmagic_io: module license taints kernel.
[    3.833325] ccp 0000:10:00.2: tee enabled
[    3.833333] ccp 0000:10:00.2: psp enabled
[    3.841560] BlackmagicIO: Driver version 12.7a4 loading
[    3.841594] blackmagic-io 0000:08:00.0: enabling device (0000 -> 0002)
[    3.841885] BlackmagicIO: Enabled device "Intensity Pro 4K" x4/5 GT/s (a4aa32e,4b0800) FW Date: 08-16 17:41
[    3.844281] BlackmagicIO: Intensity Pro 4K as blackmagic!io0 [0000:08:00.0]
[    3.844284] BlackmagicIO: Initialised serial driver for blackmagic!io0
$ lspci|grep -i blackmagic
08:00.0 Multimedia video controller: Blackmagic Design Intensity Pro 4K
$ lsmod|grep -i blackmagic
blackmagic_io        2330624  1

That means that I stumbled in it by incident (being a mod I try to glance through everything to keep things on track). But it does also mean that many other people will not see it.

When you want help from the volunteers here, the best thing is to start a new thread with a good title (and of course as tag the openSUSE version you use). Then your problem appears in the list of new topics, the best place to draw attention!

1 Like

Thank you for your advice, @hcvv.