Upstream switched from putting versioned files on their website, to using a fixed name that has no version information. It only says "latest". So, everytime they update their version on the website, the checksum on the PKGBUILD will be outdated. This is not an issue with the package itself, but with the way upstream release. I plan on changing to a pure source package soon, once I get this building from source but, until then, if you get a checksum error, download from their website and change the PKGBUILD.
Search Criteria
Package Details: v4l2loopback-dc-dkms 1:2.1.3-2
Package Actions
Git Clone URL: | https://aur.archlinux.org/droidcam.git (read-only, click to copy) |
---|---|
Package Base: | droidcam |
Description: | v4l2-loopback kernel module - DroidCam version |
Upstream URL: | https://github.com/dev47apps/droidcam-linux-client |
Keywords: | android ios webcam |
Licenses: | GPL-2.0-or-later |
Provides: | V4L2LOOPBACK-MODULE |
Submitter: | marquicus |
Maintainer: | mhdi |
Last Packager: | mhdi |
Votes: | 139 |
Popularity: | 0.42 |
First Submitted: | 2011-06-29 20:31 (UTC) |
Last Updated: | 2024-06-14 19:38 (UTC) |
Dependencies (10)
- dkms (dkms-gitAUR)
- alsa-lib (make)
- ffmpeg (ffmpeg-nvcodec-11-1-gitAUR, ffmpeg-amd-full-gitAUR, ffmpeg-cudaAUR, ffmpeg-full-gitAUR, ffmpeg-gitAUR, ffmpeg-fullAUR, ffmpeg-decklinkAUR, ffmpeg-headlessAUR, ffmpeg-amd-fullAUR, ffmpeg-libfdk_aacAUR, ffmpeg-obsAUR, ffmpeg-ffplayoutAUR) (make)
- gtk3 (gtk3-no_deadkeys_underlineAUR, gtk3-classicAUR, gtk3-classic-xfceAUR, gtk3-patched-filechooser-icon-viewAUR) (make)
- libappindicator-gtk3 (make)
- libjpeg-turbo (mozjpeg-gitAUR, libjpeg-turbo-gitAUR, mozjpegAUR) (make)
- libusbmuxd (libusbmuxd-rr-compatibleAUR, libusbmuxd-gitAUR) (make)
- speex (speex-gitAUR) (make)
- android-tools (android-sdk-platform-tools-dummyAUR, android-sdk-platform-toolsAUR) (optional) – for Android USB connection
- usbmuxd (usbmuxd2-gitAUR, usbmuxd-gitAUR) (optional) – for iOS USB connection
Required by (3)
- droidcam (requires V4L2LOOPBACK-MODULE)
- immersed (requires V4L2LOOPBACK-MODULE) (optional)
- simple-droidcam-client (requires V4L2LOOPBACK-MODULE)
Sources (3)
Latest Comments
« First ‹ Previous 1 .. 13 14 15 16 17 18 19 20 21 22 23 .. 37 Next › Last »
grazzolini commented on 2020-05-25 16:06 (UTC)
t0m5k1 commented on 2020-05-25 15:52 (UTC) (edited on 2020-05-25 15:53 (UTC) by t0m5k1)
Managed to get this to install after side stepping verification (Big Trust issue!!)
I see the following:
:: Running post-transaction hooks...
(1/3) Arming ConditionNeedsUpdate...
(2/3) Install DKMS modules
==> dkms install droidcam/6.7.7 -k 5.6.14-arch1-1
(3/3) Updating the desktop file MIME type cache...
❯ sudo insmod v4l2loopback-dc.ko width=320 height=240
insmod: ERROR: could not load module v4l2loopback-dc.ko: No such file or directory
❯ file /lib/modules/5.6.14-arch1-1/v4l2loopback-dc.ko
/lib/modules/5.6.14-arch1-1/v4l2loopback-dc.ko: cannot open `/lib/modules/5.6.14-arch1-1/v4l2loopback-dc.ko' (No such file or directory)
I see others having a similar issue, Why is this failing to build the module? What's missing from your package that's stopping this?
This is the only kernel I use so no need to ask "Is that the kernel you've booted?"
I decided to do a system wide find: sudo find / -name "v4l2loopback-dc.ko"
Still not found!!!!
What are you doing?
yura121 commented on 2020-05-25 07:17 (UTC)
rus ==> ОШИБКА: Исходные файлы не прошли проверку целостности! Не удалось собрать droidcam-dkms
en ==> ERROR: Source files did not pass the integrity check! Failed to collect droidcam-dkms
Arndroid commented on 2020-05-17 18:43 (UTC)
@grazzolini
Of course, sorry for being so cryptic. When I run "sudo modprobe v4l2loopback-dc" I get that error message, like @artemklevtsov.
It could possibly fix the issue I'm having currently on Manjaro 20.0.1. (on 5.4, 5.5, 5.6 and 5.7) The issue is; if I start DroidCam I get the following error: Error: Device not found (/dev/video[0-9]). Did you install? [OK]
I totally assume it is something I butchered in my environment, somehow, but I thought, since @artemklevtsov is trying a solution similar to what I've found elsewhere, it might be somehow related to recent updates kernel side.
grazzolini commented on 2020-05-17 13:30 (UTC)
@Arndroid
Never got any errors like this, can you be more specific?
Arndroid commented on 2020-05-17 13:08 (UTC)
Has there ever been a solution for the v4l2loopback_dc Exec / Bad address errors?
Pinned Comments