Package Details: v4l2loopback-dkms-git 0.12.5.r232.g2fa9d6d-1

Git Clone URL: (read-only, click to copy)
Package Base: v4l2loopback-dkms-git
Description: v4l2-loopback device
Upstream URL:
Licenses: GPL2
Conflicts: v4l2loopback-dkms
Provides: v4l2loopback-dkms
Submitter: hipersayan_x
Maintainer: hipersayan_x
Last Packager: hipersayan_x
Votes: 19
Popularity: 0.44
First Submitted: 2016-04-01 15:50 (UTC)
Last Updated: 2022-01-11 10:50 (UTC)

Required by (28)

Sources (1)

Latest Comments

meijin commented on 2022-05-15 05:29 (UTC)

I can see this note after latest upgrade:

 7/14) Install DKMS modules
==> dkms install --no-depmod v4l2loopback/0.12.5 -k 5.17.7-arch1-1
Deprecated feature: REMAKE_INITRD
==> depmod 5.17.7-arch1-1

is this fine?

endesse commented on 2021-09-18 08:32 (UTC)

I've had success installing after installing the linux-headers package and using pikaur to install this package.

hipersayan_x commented on 2021-08-11 13:19 (UTC)

Ok, if v4l2loopback-dkms adds that field, I will add that field. Take in mind that this package should have the same features as the original package, if v4l2loopback-dkms does not have such field, I can't add it.

post-factum commented on 2021-08-11 11:31 (UTC)

Yes, that'd work, but there's another format used for this across other 3rd-party kernel modules. See ksmbd-dkms, ntfs3-dkms etc for example.

hipersayan_x commented on 2021-08-10 15:40 (UTC)

@post-factum if linux-pf provides v4l2loopback just put v4l2loopback-dkms in the provides field of linux-pf, that is more than enough to avoid conflicts with this package or v4l2loopback-dkms.

post-factum commented on 2021-08-09 06:06 (UTC) (edited on 2021-08-09 06:08 (UTC) by post-factum)

linux-pf is providing this module out of the box, and I'd like to make all the packages that provide the module exposing this information properly.

I'll also work with the v4l2loopback-dkms maintainer for the same.

hipersayan_x commented on 2021-08-08 21:31 (UTC)

@post-factum is there an actual reason for doing that? v4l2loopback-dkms does not have such provide.

post-factum commented on 2021-08-08 18:14 (UTC)

Mind also adding provides=(V4L2LOOPBACK-MODULE)?

dizzle commented on 2021-07-01 14:51 (UTC)

I'm experiencing the same issue as many before have commented:

(2/2) Install DKMS modules
==> dkms install --no-depmod -m v4l2loopback -v 0.12.5.r226.g81b8df7 -k 5.12.13-arch1-2
==> depmod 5.12.13-arch1-2
==> Unable to install module v4l2loopback/0.12.5.r226.g81b8df7 for kernel 5.12.12-arch1-1: Missing kernel headers.

I installed the linux-headers package, as @Jrbo mentioned, but that doesn't seem to have worked. I should note, I haven't restarted since installing that package. If that resolves the issue I'll comment again.

hipersayan_x commented on 2021-03-01 15:14 (UTC)

@mazieres I hadn't such problem, but I've pointed the source link to the main branch anyway.

@jcelerier v4l2loopback doesn't depends on such program, just install it manually.

mazieres commented on 2021-02-28 23:01 (UTC)

This no longer builds for me, possibly because the main branch now seems to be called main instead of master. I can still install it if I run:

makepkg -so
git -C src/v4l2loopback checkout main
makepkg -ei

But it doesn't built automatically anymore.

jcelerier commented on 2021-02-18 10:18 (UTC)

Hello, I had to install the "pahole" package to be able to build this, else make.log had this error:

/bin/sh: ligne 1: pahole : command not found

Jrbo commented on 2021-01-29 13:42 (UTC) (edited on 2021-01-29 13:45 (UTC) by Jrbo)

@OllyHearn, you should try to install the linux-headers package; had the same problem and everything worked afterwards. Not sure why linux-headers is not listed as a runtime dependency.

OllyHearn commented on 2020-12-03 16:41 (UTC) (edited on 2020-12-03 16:41 (UTC) by OllyHearn)

Installed without issues, but when i try sudo modprobe v4l2loopback it returns Module v4l2loopback not found in directory /lib/modules/5.9.10-arch1-1 What I'm doing wrong?

Mozai commented on 2020-11-20 20:14 (UTC)

Seems to be missing a requirement. pamac install v4l2loopback-dkms-git ends with:

Install DKMS modules [2/2]
==> Unable to install module v4l2loopback/0.12.5.r198.g9c965bd for kernel 5.8.16-2-MANJARO: Missing kernel headers.
==> Unable to install module v4l2loopback/0.12.5.r198.g9c965bd for kernel 5.8.18-1-MANJARO: Missing kernel headers.

bartus commented on 2020-09-22 13:38 (UTC) (edited on 2020-09-22 13:40 (UTC) by bartus)

Jus noticed that since v4l2loopback:0.11 I'm getting some warnings when upgrading package. Package works fine, but still it's kind a worrying. Is this the normal behavior?

[2018-06-11 19:05] [ALPM] upgraded v4l2loopback-dkms-git (0.11.0.r0.g05a03e2-1 -> 0.11.0.r6.gb2b33ee-1)
[2018-06-11 19:05] [ALPM-SCRIPTLET]
[2018-06-11 19:05] [ALPM-SCRIPTLET] Creating symlink /var/lib/dkms/v4l2loopback/0.11.0.r6.gb2b33ee/source ->
[2018-06-11 19:05] [ALPM-SCRIPTLET]                  /usr/src/v4l2loopback-0.11.0.r6.gb2b33ee
[2018-06-11 19:05] [ALPM-SCRIPTLET]
[2018-06-11 19:05] [ALPM-SCRIPTLET] DKMS: add completed.
[2018-06-11 19:05] [ALPM-SCRIPTLET]
[2018-06-11 19:05] [ALPM-SCRIPTLET] Kernel preparation unnecessary for this kernel.  Skipping...
[2018-06-11 19:05] [ALPM-SCRIPTLET]
[2018-06-11 19:05] [ALPM-SCRIPTLET] Building module:
[2018-06-11 19:05] [ALPM-SCRIPTLET] cleaning build area...
[2018-06-11 19:05] [ALPM-SCRIPTLET] make -j8 KERNELRELEASE=4.16.13-2-ARCH KERNEL_DIR=/usr/lib/modules/4.16.13-2-ARCH/build all...
[2018-06-11 19:05] [ALPM-SCRIPTLET] cleaning build area...
[2018-06-11 19:05] [ALPM-SCRIPTLET] Kernel cleanup unnecessary for this kernel.  Skipping...
[2018-06-11 19:05] [ALPM-SCRIPTLET]
[2018-06-11 19:05] [ALPM-SCRIPTLET] DKMS: build completed.
[2018-06-11 19:05] [ALPM-SCRIPTLET]
[2018-06-11 19:05] [ALPM-SCRIPTLET] v4l2loopback.ko:
[2018-06-11 19:05] [ALPM-SCRIPTLET] Running module version sanity check.
[2018-06-11 19:05] [ALPM-SCRIPTLET]  - Original module
[2018-06-11 19:05] [ALPM-SCRIPTLET]    - No original module exists within this kernel
[2018-06-11 19:05] [ALPM-SCRIPTLET]  - Installation
[2018-06-11 19:05] [ALPM-SCRIPTLET]    - Installing to /usr/lib/modules/4.16.13-2-ARCH/extra/
[2018-06-11 19:05] [ALPM-SCRIPTLET]
[2018-06-11 19:05] [ALPM-SCRIPTLET] depmod....
[2018-06-11 19:05] [ALPM-SCRIPTLET]
[2018-06-11 19:05] [ALPM-SCRIPTLET] DKMS: install completed.

pkulak commented on 2020-07-14 16:32 (UTC)

No idea why, but this prompts me to install linux-headers even though I'm on linux-zen. I just removed that dep from the PKGBUILD, but I've never run into that before.

matmo commented on 2020-04-06 06:57 (UTC)

I am not quite sure what exactly is going on (let you know if I find time to debug), but I had to manually remove the dkms module (dkms remove) and could then build and dkms install from the source directory manually. Sounds like the paths in the .install file are maybe wrong...

190n commented on 2020-04-01 03:31 (UTC)

This fails to install for me. pacman output:

(1/1) installing v4l2loopback-dkms-git                                                                                                         [----------------------------------------------------------------------------------------] 100%

Creating symlink /var/lib/dkms/v4l2loopback/0.12.3.r10.g0569340/source ->

DKMS: add completed.

Kernel preparation unnecessary for this kernel.  Skipping...

Building module:
cleaning build area...(bad exit status: 2)
make -j8 KERNELRELEASE=5.5.13-arch2-1 KERNEL_DIR=/usr/lib/modules/5.5.13-arch2-1/build all...(bad exit status: 2)
Error! Bad return status for module build on kernel: 5.5.13-arch2-1 (x86_64)
Consult /var/lib/dkms/v4l2loopback/0.12.3.r10.g0569340/build/make.log for more information.
error: command failed to execute correctly
:: Running post-transaction hooks...
(1/2) Arming ConditionNeedsUpdate...
(2/2) Install DKMS modules
==> dkms install v4l2loopback/0.12.3.r10.g0569340 -k 5.5.13-arch2-1
Error! Bad return status for module build on kernel: 5.5.13-arch2-1 (x86_64)
Consult /var/lib/dkms/v4l2loopback/0.12.3.r10.g0569340/build/make.log for more information.

Contents of /var/lib/dkms/v4l2loopback/0.12.3.r10.g0569340/build/make.log:

DKMS make.log for v4l2loopback-0.12.3.r10.g0569340 for kernel 5.5.13-arch2-1 (x86_64)
Tue Mar 31 20:29:07 PDT 2020
make: pwd: No such file or directory
Building v4l2-loopback driver...
make -C /usr/lib/modules/5.5.13-arch2-1/build M= modules
make: make: No such file or directory
make: *** [Makefile:43: v4l2loopback.ko] Error 127

Anyone know what is going on?

teodord commented on 2020-03-15 18:04 (UTC)

Please change linux-headers from a make dep to a runtime dependency. When linux-headers gets uninstalled after build, this hook in dkms is run: dkms remove v4l2loopback/<version> -k <kernel> and undoes the install. At least that's what I think happens, maybe I'm wrong.

hipersayan_x commented on 2018-12-04 13:58 (UTC) (edited on 2018-12-04 13:58 (UTC) by hipersayan_x)

zootboy, it already conflict with v4l2loopback-dkms.
danger89, update or change your mirrors, also the name of the package is linux-headers not linux419-headers.

danger89 commented on 2018-12-02 20:47 (UTC)

Getting 'linux419-headers-4.19.4-1-x86_64.pkg.tar.xz' from is failed.

It can not find the linux header from some mirror.

zootboy commented on 2018-03-21 22:23 (UTC)

This should also conflict with v4l2loopback-dkms, not just v4l2loopback.

hipersayan_x commented on 2017-06-07 14:24 (UTC)

@Redi, works reasonably well and better than the stable version.

Redi commented on 2017-06-07 09:20 (UTC)

Does anybody knows how stable this is? The non-git version of this package is outdated for quite a while. Can I use this one instead or is the git version too unstable?

hipersayan_x commented on 2016-11-17 14:19 (UTC)

juancarlospaco, this usually happens if you upgrade the kernel without restarting the computer, before building v4l2loopback. Other reason could be that the repository was not cloned properly. If that's not the case let me know.

juancarlospaco commented on 2016-11-17 10:53 (UTC)

==> Starting build()... Building v4l2-loopback driver... make -C /lib/modules/`uname -r`/build M=/tmp/yaourt-tmp-juan/aur-v4l2loopback-dkms-git/src/v4l2loopback modules make[1]: Entering directory '/usr/lib/modules/4.8.7-1-ARCH/build' make[1]: *** No rule to make target 'modules'. Stop. make[1]: Leaving directory '/usr/lib/modules/4.8.7-1-ARCH/build' make: *** [Makefile:43: v4l2loopback.ko] Error 2 ==> ERROR: A failure occurred in build(). Aborting... ==> ERROR: Makepkg was unable to build v4l2loopback-dkms-git.