You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Try modprobe v4l2loopback and see if the v4l2loopback module is available for the current kernel.
I had the same error due to the absence of headers for the active kernel updated by rpi-update. If you're in the same situation, try to revert kernel & header versions to stable ones:
Hello! I get the following error:
pi@raspberrypi:~ $ cd /dev/video99
-bash: cd: /dev/video99: No such file or directory
Im sure that i did every step right and can open the cam via homekit but without pictures. The camera doesn't answer.
Maybe someone can help me. Thanks!
pi@raspberrypi:/etc/modprobe.d $ cd /dev/
pi@raspberrypi:/dev $ ls
autofs loop5 ram2 tty18 tty42 ttyAMA0 vcsu2
block loop6 ram3 tty19 tty43 ttyprintk vcsu3
btrfs-control loop7 ram4 tty2 tty44 uhid vcsu4
bus loop-control ram5 tty20 tty45 uinput vcsu5
cachefiles mapper ram6 tty21 tty46 urandom vcsu6
cec0 media0 ram7 tty22 tty47 v4l vhci
char media1 ram8 tty23 tty48 v4l-subdev0 video0
console media2 ram9 tty24 tty49 vchiq video1
cuse media3 random tty25 tty5 vcio video10
disk mem rfkill tty26 tty50 vc-mem video11
dma_heap mmcblk0 serial1 tty27 tty51 vcs video12
dri mmcblk0p1 shm tty28 tty52 vcs1 video13
fd mmcblk0p2 snd tty29 tty53 vcs2 video14
full mqueue stderr tty3 tty54 vcs3 video15
fuse net stdin tty30 tty55 vcs4 video16
gpiochip0 null stdout tty31 tty56 vcs5 video18
gpiomem ppp tty tty32 tty57 vcs6 video20
hwrng ptmx tty0 tty33 tty58 vcsa video21
initctl pts tty1 tty34 tty59 vcsa1 video22
input ram0 tty10 tty35 tty6 vcsa2 video23
kmsg ram1 tty11 tty36 tty60 vcsa3 video31
log ram10 tty12 tty37 tty61 vcsa4 watchdog
loop0 ram11 tty13 tty38 tty62 vcsa5 watchdog0
loop1 ram12 tty14 tty39 tty63 vcsa6 zero
loop2 ram13 tty15 tty4 tty7 vcsm-cma
loop3 ram14 tty16 tty40 tty8 vcsu
loop4 ram15 tty17 tty41 tty9 vcsu1
pi@raspberrypi:/dev $
The text was updated successfully, but these errors were encountered: