/dev/video1: No such file or directory about hkcam

[brutella]

/dev/video1 is created by the v4l2loopback kernel extension and is needed to allow multiple access to the camera stream.

If /dev/video1 is not available, please verify that the camera is correctly connected to the RPi as shown in the wiki.

[xd94402002]

I have the exact same issue with both my v2 v1 pi camera
I’m sure that the camera is connected to the RPi
It is able to see video and take picture with the “raspistill -o image.png” command

[brutella]

@xd94402002 Did you install the pre-configured Raspbian image or just installed the hkcam binary?

[xd94402002]

I installed on my pi3 through playbook
I found that it doesn’t install the v4l2loopback module
After manually install v4l2loopback the cam start streaming

[xd94402002]

Additionally,the FPS just 5. Is that the performance limit on rpi ? The average cpu usage is under 5%. It seem like it doesn’t make full use of the resources.

[AndreaCCIE]

I've got the same /dev/video1 error, the camera cable wasn't plugged correctly.

[benbeton]

I facing the same issue. camera is plugged in correctly. I'm using the provided Image 0.0.8.
I guess it happened after I expanded the disk

[dfbills]

@benbeton - I also expanded my disk as I'm running on a 64GB card. I haven't had a chance to rebuild from scratch yet.

[beckmx]

hello @brutella I have the same problem with these specs:

• raspi 3
• suggeted image on 8gig sd
• raspi cam 1.3 well connected

I could connect it to wifi and ssh, I also could add the camera in “Home” but no image is shown. Then I connected another USB camera and that one did create the video1 and could stream from there, but the raspi cam seems to fail to work.

[AndreaCCIE]

So, a quick update. I've got this error a couple of times on a working camera after the reboot.
The solution I found was to kill the hkcam processes:

pi@raspicam:~ ps aux | grep hkcam
root 558 0.0 0.0 1684 364 ? Ss 14:15 0:00 runsv hkcam
root 564 0.0 0.0 1828 324 ? S 14:15 0:00 svlogd -tt /var/log/hkcam
root 565 0.7 1.3 801948 10256 ? Sl 14:15 0:00 hkcam --min_video_bitrate=2048 --data_dir=/var/lib/hkcam/data --verbose=true
pi 736 0.0 0.0 3492 396 pts/1 S+ 14:17 0:00 tail -f /var/log/hkcam/current
pi 742 0.0 0.0 4368 536 pts/0 S+ 14:17 0:00 grep --color=auto hkcam

pi@raspicam:~ sudo kill -9 558 564 565

hkcam will restart by itself and the error disappeared

[beckmx]

after killing the processes, did u rerun again the process?

[AndreaCCIE]

No, it restarts by itself. But now I have to do it after each reboot. It looks like a wrong order of operations.

[pleasantone]

I'm seeing the same thing, and raspistill gets the image just fine. I -also- did a disk expansion followed by an apt-get update/dist-upgrade. The loopback module is not being loaded properly in the kernel. The problem is that the version supplied with raspbian stretch is incompatible with the current raspbian-stretch kernel (the kernel developers removed a backwards compatible kernel API (setup_timer) during a linux point release).

@brutella solved this by picking up a new version from GitHub, instead of using v4l2loopback-dkms.

I think the correct solution, really, is to upgrade this whole mess to buster, since stretch is ancient anyway (and it will ensure we continue to get security updates).

However, the temporary way to solve this is to use the ansible playbook, or issue the commands from the playbook to download the version from GitHub and compile/install that version of v4l2loopback. You'll need to do this any time you update the kernel (which is an annoying problem).

[CaseyRo]

After manually install v4l2loopback the cam start streaming

Did this as well (on top of apt-get upgrade/update, and expanding my SD card) and that brought the camera back to life. Pretty much what @pleasantone said here.

[brutella]

Yeah, getting the v4l2loopback kernel extension working is no fun.

[Velkas]

@pleasantone Is there any chance you could detail your fix a little more?

I flashed my Pi Zero W with the latest pre-built from this repo. Added Wifi and SSH to remote manage it. After first boot, I expanded the filesystem and ran apt-get update/upgrade.

I wound up with OP's problem but I'm having trouble following your repair steps. I've never used ansible and after installing it on the Pi and copying over the ansible folder-- it fails to run.

The error I get is:

ERROR! no action detected in task. This often indicates a misspelled module name, or incorrect module path.
The error appears to have been in '/home/pi/hkcam-master/ansible/roles/hkcam/tasks/configure.yml': line 41, column 3, but may be elsewhere in the file depending on the exact syntax problem.
The offending line appears to be:
- name: Reboot
    ^ here
The error appears to have been in '/home/pi/hkcam-master/ansible/roles/hkcam/tasks/configure.yml': line 41, column 3, but may be elsewhere in the file depending on the exact syntax problem.
The offending line appears to be:
- name: Reboot
    ^ here