Package Details: v4l2loopback-dkms 0.10.0-3

Git Clone URL: https://aur.archlinux.org/v4l2loopback-dkms.git (read-only)
Package Base: v4l2loopback-dkms
Description: v4l2-loopback device
Upstream URL: https://github.com/umlaeute/v4l2loopback
Licenses: GPLv2
Conflicts: v4l2loopback
Submitter: Artefact2
Maintainer: qwivan
Last Packager: qwivan
Votes: 25
Popularity: 0.362031
First Submitted: 2015-08-16 13:47
Last Updated: 2017-12-29 14:24

Latest Comments

braderhart commented on 2018-02-14 06:12

@j605: Thanks. I got it working by installing the Git pkg version and changing to build from master. Both packages should be updated hopefully, and I hope to see more support for virtual capture support in official packages or kernel.

j605 commented on 2018-02-10 14:26

Can you include this patch(https://github.com/umlaeute/v4l2loopback/commit/00eb0df20248d7a37594905d64030d0bd0b72eb8) in case upstream doesn't make a release. It is needed to make the module compile for 4.15

j605 commented on 2017-12-29 11:15

Install file is unnecessary due to pacman hooks for dkms.

JJK commented on 2017-12-14 18:03

The package works fine currently, problems as described by amatriain are probably caused by a kernel update without a reboot.

amatriain commented on 2017-12-14 08:53

0.10.0-2 is broken.

==> Starting build()... Building v4l2-loopback driver... make -C /lib/modules/uname -r/build M=/home/amatriain/AUR_builds/v4l2loopback-dkms/src/v4l2loopback-0.10.0 modules make[1]: /lib/modules/4.9.67-1-lts/build: No such file or directory. Stop. make: [Makefile:43: v4l2loopback.ko] Error 2 ==> ERROR: A failure occurred in build(). Aborting...

vonpupp commented on 2017-06-05 20:07

This package seems to be broken.

I get: failed to install. Check. SRCINFO for mismatching data with PKGBUILD.

Any help, please?

Redi commented on 2017-05-27 12:52

Could you please update it?

jaxad0127 commented on 2017-01-24 18:27

linux-headers is a dependency in the PKGBUILD, but not listed here.

agapito commented on 2016-12-19 13:51

0.10.0 is out.

schulmar commented on 2016-11-25 11:08

@juancarlospaco

I had the same problem and noticed that I had two versions in /lib/modules/ 4.8.10-1 and 4.8.8-2 and uname reported 4.8.8-2. Only the 4.8.10-1 folder contained build/Makefile.

The problem was that the current kernel version (4.8.10-1) was not yet installed on my system.

All comments