Quantcast
Channel: Raspberry Pi Forums
Viewing all articles
Browse latest Browse all 3546

Raspberry Pi OS • Re: Trixie and motion software

$
0
0
I don't see anything helpful in motion.log:

Code:

[1:ml1] [NTC] [VID] [Oct 28 18:36:00] vid_start: Opening V4L2 device[1:ml1] [NTC] [VID] [Oct 28 18:36:00] v4l2_device_open: Using videodevice /dev/video0 and input -1[1:ml1] [ERR] [VID] [Oct 28 18:36:00] v4l2_device_capability: Not a V4L2 device?[1:ml1] [ERR] [VID] [Oct 28 18:36:00] vid_start: V4L2 device failed to open[1:ml1] [WRN] [ALL] [Oct 28 18:36:10] mlp_retry: Retrying until successful connection with camera[1:ml1] [NTC] [VID] [Oct 28 18:36:10] vid_start: Opening V4L2 device[1:ml1] [NTC] [VID] [Oct 28 18:36:10] v4l2_device_open: Using videodevice /dev/video0 and input -1[1:ml1] [ERR] [VID] [Oct 28 18:36:10] v4l2_device_capability: Not a V4L2 device?[1:ml1] [ERR] [VID] [Oct 28 18:36:10] vid_start: V4L2 device failed to open[1:ml1] [WRN] [ALL] [Oct 28 18:36:20] mlp_retry: Retrying until successful connection with camera[1:ml1] [NTC] [VID] [Oct 28 18:36:20] vid_start: Opening V4L2 device[1:ml1] [NTC] [VID] [Oct 28 18:36:20] v4l2_device_open: Using videodevice /dev/video0 and input -1[1:ml1] [ERR] [VID] [Oct 28 18:36:20] v4l2_device_capability: Not a V4L2 device?[1:ml1] [ERR] [VID] [Oct 28 18:36:20] vid_start: V4L2 device failed to open[1:ml1] [NTC] [ALL] [Oct 28 18:36:21] mlp_capture: Video signal lost - Adding grey image[1:ml1] [WRN] [ALL] [Oct 28 18:36:30] mlp_retry: Retrying until successful connection with camera[1:ml1] [NTC] [VID] [Oct 28 18:36:30] vid_start: Opening V4L2 device[1:ml1] [NTC] [VID] [Oct 28 18:36:30] v4l2_device_open: Using videodevice /dev/video0 and input -1[1:ml1] [ERR] [VID] [Oct 28 18:36:30] v4l2_device_capability: Not a V4L2 device?[1:ml1] [ERR] [VID] [Oct 28 18:36:30] vid_start: V4L2 device failed to open[1:ml1] [WRN] [ALL] [Oct 28 18:36:40] mlp_retry: Retrying until successful connection with camera[1:ml1] [NTC] [VID] [Oct 28 18:36:40] vid_start: Opening V4L2 device[1:ml1] [NTC] [VID] [Oct 28 18:36:40] v4l2_device_open: Using videodevice /dev/video0 and input -1[1:ml1] [ERR] [VID] [Oct 28 18:36:40] v4l2_device_capability: Not a V4L2 device?[1:ml1] [ERR] [VID] [Oct 28 18:36:40] vid_start: V4L2 device failed to open[1:ml1] [WRN] [ALL] [Oct 28 18:36:50] mlp_retry: Retrying until successful connection with camera[1:ml1] [NTC] [VID] [Oct 28 18:36:50] vid_start: Opening V4L2 device[1:ml1] [NTC] [VID] [Oct 28 18:36:50] v4l2_device_open: Using videodevice /dev/video0 and input -1[1:ml1] [ERR] [VID] [Oct 28 18:36:50] v4l2_device_capability: Not a V4L2 device?[1:ml1] [ERR] [VID] [Oct 28 18:36:50] vid_start: V4L2 device failed to open
As the rpicam-vid command is perfectly capable of recording pics and vids, I don't assume the problem to be as low-level as with device trees or so...

When installed with apt, I have in motion.conf:

Code:

  GNU nano 8.4                                             /etc/motion/motion.conf                                                      # Rename this distribution example file to motion.conf## This config file was generated by motion 4.7.0# Documentation:  /usr/share/doc/motion/motion_guide.html## This file contains only the basic configuration options to get a# system working.  There are many more options available.  Please# consult the documentation for the complete list of all options.############################################################## System control configuration parameters############################################################# Start in daemon (background) mode and release terminal.daemon off# Start in Setup-Mode, daemon disabled.setup_mode off# File to store the process ID.; pid_file value# File to write logs messages into.  If not defined stderr and syslog is used.log_file /var/log/motion/motion.log# Level of log messages [1..9] (EMG, ALR, CRT, ERR, WRN, NTC, INF, DBG, ALL).log_level 6# Target directory for pictures, snapshots and moviestarget_dir /var/lib/motion# Video device (e.g. /dev/video0) to be used for capturing.video_device /dev/video0....
So why expecting a v4l2 device in the first place?

When installing motion with make and sudo make install the motion.conf is:

Code:

; This config file was generated by motion 5.0.0-git-20251009-8bc2260; Documentation:  /usr/local/share/doc/motion/motion_guide.html;; This file contains only the basic configuration options to get a; system working.  There are many more options available.  Please; consult the documentation for the complete list of all options.;;*************************************************;*****   System;*************************************************daemon off;log_filelog_level 6log_type ALL;*************************************************;*****   Camera;*************************************************device_namedevice_idtarget_dir /usr/local/var/lib/motion/media;*************************************************;*****   Source;*************************************************video_device /dev/video0;netcam_url;*************************************************;*****   Image;*************************************************width 640height 480framerate 15;*************************************************;*****   Overlays;*************************************************text_right %Y-%m-%d\n%T
so same question, why is v4l2 device expected?

Code:

$ /usr/bin/libcamerify motion[NTC][ALL][mo00] process: Processing config file /home/user/motion.conf[ALR][ALL][mo00] edit_set_depr: "video_device" replaced with "v4l2_device" after version 5.0.0[ALR][ALL][mo00] camera_add: Camera config file /usr/local/var/lib/motion/camera1.conf not found: No such file or directory[NTC][ALL][mo00] set_log_file: Logging to syslog[NTC][ALL][mo00] mytranslate_init: Language: English[NTC][ALL][mo00] pid_write: Motion pid: 914[NTC][ENC][mo00] av_init: libavcodec  version 61.19.101[NTC][ENC][mo00] av_init: libavformat version 61.7.100[NTC][STR][mo00] startup: Starting webcontrol on port 8083[NTC][STR][mo00] start_daemon_port1: Started webcontrol on port 8083[NTC][VID][cl01] start_cam: Opening V4L2 device[NTC][VID][cl01] device_open: Opening video device /dev/video0[0:03:33.586655159] [921]  INFO Camera camera_manager.cpp:330 libcamera v0.5.2+99-bfd68f78[0:03:33.694925671] [922]  INFO IPAProxy ipa_proxy.cpp:180 Using tuning file /usr/share/libcamera/ipa/rpi/vc4/ov5647.json[0:03:33.708998022] [922]  INFO Camera camera_manager.cpp:220 Adding camera '/base/soc/i2c0mux/i2c@1/ov5647@36' for pipeline handler rpi/vc4[0:03:33.709155991] [922]  INFO RPI vc4.cpp:440 Registered camera /base/soc/i2c0mux/i2c@1/ov5647@36 to Unicam device /dev/media0 and ISP device /dev/media1[ERR][VID][cl01] device_open: Not a V4L2 device?[ERR][VID][cl01] start_cam: V4L2 device failed to open[NTC][VID][cl01] stop_cam: Closing video device /dev/video0[ERR][ALL][cl01] init_cam_start: Failed to start camera.[NTC][ALL][cl01] ring_resize: Resizing buffer to 4 items[ERR][ALL][cl01] init_firstimage: Unable to open camera[NTC][NET][cl01] noimage: Camera did not reconnect.[NTC][NET][cl01] noimage: Checking for camera every 30 seconds.
Hmm, I read in the log now:

Code:

...edit_set_depr: "video_device" replaced with "v4l2_device" after version 5.0.0...
So it automagically expects v4l2 device, but why is it not able to open?

Statistics: Posted by pi-anazazi — Mon Nov 03, 2025 10:54 am



Viewing all articles
Browse latest Browse all 3546

Trending Articles