Error while initializing Motion

Question

Jul  6 18:32:19 server motion: [0] ioctl (VIDIOCGCAP): Invalid argument
Jul  6 18:32:19 server motion: [0] Capture error Invalid argument

This does mean that my camera driver is broken?

I'm using a camera based on Sonix SN9x102 chipset with a Kernel 2.6.12.2 built-in drivers. kernel messages after inserting usb-device:

Jul  6 18:31:24 server kernel: usb 1-2: new full speed USB device using uhci_hcd and address 3
Jul  6 18:31:25 server kernel: usb 1-2: SN9C10[12] PC Camera Controller detected (vid/pid 0x0C45/0x6028)
Jul  6 18:31:25 server kernel: usb 1-2: PAS202BCB image sensor detected
Jul  6 18:31:25 server usb.agent[6067]: ... no modules for USB product c45/6028/101
Jul  6 18:31:25 server kernel: usb 1-2: Initialization succeeded
Jul  6 18:31:25 server kernel: usb 1-2: V4L2 device registered as /dev/video0
Jul  6 18:31:25 server kernel: usb 1-2: Optional device control through 'sysfs' interface ready
Jul  6 18:31:27 server udev[6099]: configured rule in '/etc/udev/rules.d/udev.rules' at line 103 applied, added symlink '%k'
Jul  6 18:31:27 server udev[6099]: configured rule in '/etc/udev/rules.d/udev.rules' at line 103 applied, 'video0' becomes 'v4l/video%n'
Jul  6 18:31:27 server udev[6099]: creating device node '/dev/v4l/video0'

Environment

Motion version:	3.2.1
ffmpeg version:	0.4.9-pre1
Libraries:	ffmpeg, mysql, postgresql
Server OS:	Slackware 10.0 / Linux 2.6.12.2

-- IgorNov - 06 Jul 2005

Answer

I do not know the driver from personal use. Motion still only support the V4L API. Not V4L2 (Video for Linux version 2). PerJonsson is working on it and eventually Motion will support V4L2. So you need to use a driver which is backwards compatible - if it exists.

-- KennethLavrsen - 06 Jul 2005