Hi, background: at tumbleweed, kde (but its a non platform specific question) we use i-phones with "droidcam" for webcam and sound. since about a half year with firefox. working fine. now i have to use chromium because of some jitsi servers did not accept firefox. to use chromium with the v4l2loopback driver i have to use the driver with additional options (if no option chromium did not find the webcam): rmmod v4l2loopback modprobe v4l2loopback exclusive_caps=1 will do the trick. -------------- problem: something is loading the v4l2loopback kernel modul without this option. i checked my system: inside: /etc/modules-load.d i have had a file (made by me, half year ago) who has loaded the driver without options. - i removed the file /etc/modprobe.d nothing releated to v4l2loopback /usr/lib/modprobe.d is a file from package v4l2loopback-autoload.rpm - i uninstalled the rpm. - file is gone /usr/lib/modules-load.d is a file from package v4l2loopback-autoload.rpm - i uninstalled the rpm. - file is gone now i think the system should start without v4l2loopback. restart the system lsmod shows v4l2loopback is still loaded. i insered a file at /etc/modprobe.d 50-v4l2loopback.conf with contend: options v4l2loopback exclusive_caps=1 reboot, still same problem driver is loaded without options. so what is loading this driver? i searched /etc and /usr/lib but did not find the text string "v4l2loopback" could there some udev rules? is it inside initrd ? (did i have to recreate initrd, how to do?) how to find this out, and how to delete or give this kernel-modul-load-command the option "exclusive_caps=1" simoN -- www.becherer.de
On Wed, Feb 03, 2021 at 08:27:31AM +0100, Simon Becherer wrote:
Hi,
background: at tumbleweed, kde (but its a non platform specific question) we use i-phones with "droidcam" for webcam and sound. since about a half year with firefox. working fine. now i have to use chromium because of some jitsi servers did not accept firefox.
to use chromium with the v4l2loopback driver i have to use the driver with additional options (if no option chromium did not find the webcam):
rmmod v4l2loopback modprobe v4l2loopback exclusive_caps=1 will do the trick.
--------------
problem: something is loading the v4l2loopback kernel modul without this option.
i checked my system:
inside: /etc/modules-load.d i have had a file (made by me, half year ago) who has loaded the driver without options. - i removed the file
/etc/modprobe.d nothing releated to v4l2loopback
/usr/lib/modprobe.d is a file from package v4l2loopback-autoload.rpm - i uninstalled the rpm. - file is gone
/usr/lib/modules-load.d is a file from package v4l2loopback-autoload.rpm - i uninstalled the rpm. - file is gone
now i think the system should start without v4l2loopback. restart the system
lsmod shows v4l2loopback is still loaded.
i insered a file at /etc/modprobe.d 50-v4l2loopback.conf with contend: options v4l2loopback exclusive_caps=1 reboot, still same problem driver is loaded without options.
so what is loading this driver? i searched /etc and /usr/lib but did not find the text string "v4l2loopback"
could there some udev rules? is it inside initrd ? (did i have to recreate initrd, how to do?)
how to find this out, and how to delete or give this kernel-modul-load-command the option "exclusive_caps=1"
Only package I know is gphoto2-webcam, but it does not load it automatically. Ciao, Marcus
On Wed, Feb 3, 2021 at 10:27 AM Simon Becherer <simon@becherer.de> wrote:
i insered a file at /etc/modprobe.d 50-v4l2loopback.conf with contend: options v4l2loopback exclusive_caps=1 reboot, still same problem driver is loaded without options.
so what is loading this driver?
It may be dependent on another module or it may export an alias that matches your hardware. In both cases it will be autoloaded.
i searched /etc and /usr/lib but did not find the text string "v4l2loopback"
could there some udev rules?
Yes, it could.
is it inside initrd ?
Could be. Just run lsinitrd.
(did i have to recreate initrd, how to do?)
mkinitrd
how to find this out, and how to delete or give this kernel-modul-load-command the option "exclusive_caps=1"
v4l2loopback.exclusive_caps=1 on kernel command line may work but it is a really big hammer.
Simon Becherer wrote:
problem: something is loading the v4l2loopback kernel modul without this option.
i checked my system:
inside: /etc/modules-load.d i have had a file (made by me, half year ago) who has loaded the driver without options. - i removed the file
/etc/modprobe.d nothing releated to v4l2loopback
/usr/lib/modprobe.d is a file from package v4l2loopback-autoload.rpm - i uninstalled the rpm. - file is gone /usr/lib/modules-load.d is a file from package v4l2loopback-autoload.rpm - i uninstalled the rpm. - file is gone
My immediate impression - those two files would do exactly what you want, i.e. load the module with that option.
i insered a file at /etc/modprobe.d 50-v4l2loopback.conf with contend: options v4l2loopback exclusive_caps=1 reboot, still same problem driver is loaded without options. so what is loading this driver? i searched /etc and /usr/lib but did not find the text string "v4l2loopback"
Maybe try blacklisting it and see if something complains.
could there some udev rules? is it inside initrd ? (did i have to recreate initrd, how to do?)
It is unlikely to be in the initrd, it's not needed at boot-time. -- Per Jessen, Zürich (8.9°C)
Am 03.02.21 um 08:55 schrieb Per Jessen:
/usr/lib/modprobe.d is a file from package v4l2loopback-autoload.rpm - i uninstalled the rpm. - file is gone /usr/lib/modules-load.d is a file from package v4l2loopback-autoload.rpm - i uninstalled the rpm. - file is gone
My immediate impression - those two files would do exactly what you want, i.e. load the module with that option.
yes, but not in my case, i think because something is loading the module before. simoN -- www.becherer.de
Am 03.02.21 um 08:27 schrieb Simon Becherer: Thanks all here, problem solved, think i found a bug: 1) inside initrd the kernel-driver was load. thanks to lsinitrd (i have not known this command) so to get rid of it after modifying or deleting some kernel-driver i MUST "mkinitrd" 2) mkinitrd seems to be have a BUG: remember:
inside: /etc/modules-load.d i have had a file (made by me, half year ago) who has loaded the driver without options. - i removed the file
/etc/modprobe.d nothing releated to v4l2loopback
/usr/lib/modprobe.d is a file from package v4l2loopback-autoload.rpm - i uninstalled the rpm. - file is gone
/usr/lib/modules-load.d is a file from package v4l2loopback-autoload.rpm - i uninstalled the rpm. - file is gone
and the files in usr/lib/modprobe.d will NOT go into initrd with mkinitrd for this after installing the package: v4l2loopback-autoload.rpm everithing work as expected. up to the point where something is triggering "mkinitrd" after this its not working any more, the driver will be loaded into mkinitrd but without the aditional options. work around is to make a symlink from: usr/lib/modprobe.d/98-v4l2loppback.conf to etc/modprobe.d/98-v4l2loppback.conf then mkinitrd. now the directory+files are inside the initrd. this behavior is tested on tumbleweed 20210106 with ext4 i have made a bugreport: https://bugzilla.opensuse.org/show_bug.cgi?id=1181768 simoN -- www.becherer.de
Simon Becherer wrote:
Am 03.02.21 um 08:27 schrieb Simon Becherer: Thanks all here,
problem solved, think i found a bug:
1) inside initrd the kernel-driver was load. thanks to lsinitrd (i have not known this command) so to get rid of it after modifying or deleting some kernel-driver i MUST "mkinitrd"
Just an observation - it sounds pretty odd for something like v4l2loopback to go into the initrd. -- Per Jessen, Zürich (5.2°C)
Am 04.02.21 um 08:36 schrieb Per Jessen:
Simon Becherer wrote:
Am 03.02.21 um 08:27 schrieb Simon Becherer: Thanks all here,
problem solved, think i found a bug:
1) inside initrd the kernel-driver was load. thanks to lsinitrd (i have not known this command) so to get rid of it after modifying or deleting some kernel-driver i MUST "mkinitrd"
Just an observation - it sounds pretty odd for something like v4l2loopback to go into the initrd.
there is this bug related to: https://bugzilla.opensuse.org/show_bug.cgi?id=1180821 maybe you should commend there.
-- www.becherer.de
participants (5)
-
Andrei Borzenkov -
Carlos E. R. -
Marcus Meissner -
Per Jessen -
Simon Becherer