Open lukellyk opened 1 year ago
For me this seems to be an issue with the loopback device not being available, which in turn is because the ffmpeg process gets killed by the scheduler - it's requesting too much memory and I can see it being killed in dmesg
@borfd do you know how to solve it?
I had the same problem. I use the ribbon cable camera module. Raspberry Pi isn't my domain of expertise so I didn't understand what it meant to "enable Legacy Camera Support". The link in the README certainly wasn't helpful.
After installing Raspbian lite, I assumed that since "libcamera-jpeg -o test.jpg" worked, there was no need to explicitly enable legacy support. I was wrong. The real verification checks which I got from 0xPr0xy's post on this closed bug are below.
Before enabling Legacy Camera Support:
$ vcgencmd get_camera
supported=0 detected=0, libcamera interfaces=0
$ raspistill -o test.jpg
ERROR: the system should be configured for the legacy camera stack
Legacy Camera Support can be enabled like so:
sudo raspi-config nonint get_legacy
sudo raspi-config nonint do_legacy 0
sudo reboot
Afterwards, you should get output similar to the following:
$ vcgencmd get_camera
supported=1 detected=1, libcamera interfaces=0
$ raspistill -o test.jpg
$ echo $?
0
Then hkcam ought to work with CSI ribbon cable camera module
Have tried both manual install and using Ansible to no avail, still receiving this error:
[video4linux2,v4l2 @ 0x1d68930] ioctl(VIDIOC_G_FMT): Invalid argument /dev/video99: Invalid argument
Camera is plugged in and working Successfully added to Home app
RasPi Zero W Rev 1.1 RasPi Camera Module 3 - Wide Running v0.2.0