Replies: 2 comments 2 replies
-
|
That doesn't quite look like enough information to diagnose the error. |
Beta Was this translation helpful? Give feedback.
-
|
Many thanks for responding. Output for libcamerify -d -d motion as requested Out of curiosity I connected a cheap webcam (adjusted the /dev/video accordingly), and used the prefix, libcamerify, for both a 32bit and 64bit pios distros. Success for the PIOS32 bit and failure for the 64bit. As expected, success without the prefix, i.e. motion command only for both. Regards, Martin pi@raspberrypi:~ $ libcamerify -d -d motion |
Beta Was this translation helpful? Give feedback.
-
|
Ah - the 32/64 bit test is interesting indeed. That sounds like something that needs to be investigated. |
Beta Was this translation helpful? Give feedback.
-
|
32bit Raspberry pi camera module v2 on Pi4 functional with Motion when using libcamerify. |
Beta Was this translation helpful? Give feedback.
-
Hello,
when prefixed with the libcamerify command, Motion works well on a Bullseye armhf (32bit) PiOS, with the new libcamera s/w, It is failing on a vanilla Pi OS64 Bullseye (latest release Motion, and Bullseye up to date). Is this a known issue on Pi OS64 or libcamerify builds?
My PI is a 4B 4M. The offending lines from the logs are:
[1:ml1] [NTC] [VID] vid_start: Opening V4L2 device
[1:ml1] [NTC] [VID] v4l2_device_open: Using videodevice /dev/video0 and input -1
[1:ml1] [ERR] [VID] v4l2_device_capability: Not a V4L2 device?
[1:ml1] [ERR] [VID] vid_start: V4L2 device failed to open
I can confirm that this is different to the logs for motion without libcamerify so libcamerify is doing something right.
I have posted on the Motion site and post here on the off chance that there may be a libcamera/ libcamerify challenge here. I have noted that you have been workiing closely with the Motion team. libcamera-hello works are advertised on the 64bit os.
Beta Was this translation helpful? Give feedback.
All reactions