problems starting motion

Question

Hi,

I got problems starting the motion program. I was wondering: is motion supported on V4L2? cat /dev/video0 does give alot of binary output on my terminal screen. There is some initialisation problem. Don't know. Do you have a clue? Thanks beforehand! :-),

Kris

Kernel: 

Linux home-nas 2.6.15-kurobox #3 Sun Aug 6 16:33:59 CEST 2006 ppc 82xx GNU/Linux

Motion error text:

[0] Processing thread 0 - config file /etc/motion.conf
[0] Motion running in setup mode.
[0] Thread device: /dev/video0 input 8
[0] Thread is from /etc/motion.conf
[0] Waiting for threads to finish, pid: 8171
[1] Thread started
[0] motion-httpd/3.2.6 running, accepting connections
[0] motion-httpd: waiting for data on port TCP 8080
[1] ioctl (VIDIOCGCAP): Invalid argument
[1] Capture error calling vid_start
[1] Thread finishing...

dmesg usb device recognition messages:

sn9c102: V4L2 driver for SN9C10x PC Camera Controllers v1:1.24a
sn9c102 2-1:1.0: usb_probe_interface
sn9c102 2-1:1.0: usb_probe_interface - got id
usb 2-1: SN9C10[12] PC Camera Controller detected (vid/pid 0x0C45/0x6029)
usb 2-1: PAS106B image sensor detected
usb 2-1: Initialization succeeded
usb 2-1: V4L2 device registered as /dev/video0
usb 2-1: Optional device control through 'sysfs' interface ready
usbcore: registered new driver sn9c102

Environment

Motion version:	3.2.6
ffmpeg version:	Not installed
Libraries:
Server OS:	Gentoo, kernel 2.6.15

-- KrisSnoeijs - 06 Aug 2006

Answer

Motion currently does not support V4L2 devices.

There are some patches that enable V4L2 for specific camera but they are so incomplete that when I integrate them half of my own cameras stop working. So these V4L2 patches need much more work to be part of Motion.

I am very open to V4L2 contributions. It is on the top of my wish list.

-- KennethLavrsen - 06 Aug 2006

Hi,

Thanks for the quick answer! I forgot to mention that the vidcat (of w3cam packages) application also gives the [1] ioctl (VIDIOCGCAP): Invalid argument error message, which led me to believe that the underlying software layers were wrongly called. Anyways this saves me alot of time trying to get it to work. So, this leaves me with the problem of finding an application that can do frame grabbing that does support the V4L2. Do you have suggestions for that? Thanks,

Kris