-
Notifications
You must be signed in to change notification settings - Fork 531
Frequently Asked Questions for the v4l2loopback kernel module
A: Please read the documentation carefully: while it is not very long, it does contain some information that might help fixing your problem.
This FAQ and the wiki should provide some information as well :-)
A: If you have general questions or problems, please use the v4l2loopback tag on Stack Overflow:
https://unix.stackexchange.com/questions/tagged/v4l2loopback
The issue tracker is ill-suited for general help. Please do not use it.
A: use the 'devices' module parameter. e.g.
# modprobe v4l2loopback devices=3
will create 3 loopback devices. Make sure producers and consumers stream to/from the appropriate devices. Please refer to the Multiple Devices example to see how to do that.
A: Please refer to the MPlayer examples to see how to do that.
A: Please refer to the MPlayer examples to see how to do that.
A: Please refer to the Skype examples to see how to do that.
A: Depending on the color encoding, odd-sized frames can be problematic (eg YUV420p requires that the U and V planes are downsampled by a factor of 2, which works best if the width and height can be divided by 2). See also Issue #561
A: v4l2loopback is a kernel-module and thus runs in kernel-space. while you can do many a-thing in kernel-space that you cannot do in user-space, there are also some things that you only do in user-space (like using a dynamic library). what's more there are things that you shouldn't do in the privileged kernel-space (mostly all the things that you can easily do in user-space). scaling images and converting between colorspaces, is something that should be done in user-space, and thus cannot be done in the v4l2loopback module. See also Colorspace Issues.
A: Latest package v4l2loopback-dkms can be downloaded for example here:
https://launchpad.net/ubuntu/+source/v4l2loopback
Or you can use this PPA:
https://launchpad.net/~rayanayar/+archive/v4l2loopback
When running make, I get errors like the following:
make -C /lib/modules/uname -r/build M=/home/me/src/v4l2loopback modules_install
make[1]: Entering directory '/usr/src/linux-headers-5.0.0-0'
INSTALL /home/me/src/v4l2loopback/v4l2loopback.ko
At main.c:160:
SSL error:02001002:system library:fopen:No such file or directory: ../crypto/bio/bss_file.c:72
SSL error:2006D080:BIO routines:BIO_new_file:no such file: ../crypto/bio/bss_file.c:79
sign-file: certs/signing_key.pem: No such file or directory
DEPMOD 5.0.0-0
Warning: modules_install: missing 'System.map' file. Skipping depmod.
make[1]: Leaving directory '/usr/src/linux-headers-5.0.0-0'
A: Most often, You can safely ignore these "errors" (they only say, that the kernel-module could not be cryptographically signed).
To check whether the build actually succeeded, check the exit code of the build process. It should be 0:
$ make
[...]
$ echo $?
0
$
A: Sometimes these errors indicate a real problem, as some kernels will refuse to load modules that are not cryptographically signed.
The easiest way to make the kernel recognize the module, is by building the module via the dkms framework.
See the DKMS section in the README for instructions.
modprobe: ERROR: could not insert 'v4l2loopback': Operation not permitted
Lockdown: modprobe: unsigned module loading is restricted; see man kernel_lockdown.7
A: If you are running secure boot, that's most likely the reason you will see this error. See Secure Boot to see if it corrects the problem.