Re: [Motion-user] Problems with motion and DC10+ capture card.

[Andy <an...@th...>]

Hello,

Gabriele Tirelli wrote:
> Hi there!
> 
> Trying to run motion using as a source a pinnacle DC10+ capture card
> with a camera connectet via the composite input, it terminates with
> the following output:
> 
> $ motion
> [0] Processing thread 0 - config file /etc/motion/motion.conf
> [0] Motion 3.2.9 Started
> [0] ffmpeg LIBAVCODEC_BUILD 3345152 LIBAVFORMAT_BUILD 3278080
> [0] Motion running in setup mode.
> [0] Thread 1 is from /etc/motion/motion.conf
> [0] Thread 1 is device: /dev/video0 input 4
> [0] Waiting for threads to finish, pid: 5571
> [1] Thread 1 started
> [0] motion-httpd/3.2.9 running, accepting connections
> [0] motion-httpd: waiting for data on port TCP 8080
> [1] cap.driver: "zoran"
> [1] cap.card: "DC10plus[0]"
> [1] cap.bus_info: "PCI:0000:00:11.0"
> [1] cap.capabilities=0x04000007
> [1] - VIDEO_CAPTURE
> [1] - VIDEO_OUTPUT
> [1] - VIDEO_OVERLAY
> [1] - STREAMING
> [1] Unable to query input 4.
> [1] VIDIOC_ENUMINPUT: Invalid argument
> [1] ioctl (VIDIOCGCHAN): Invalid argument
> [1] Failed with YUV420P, trying YUV422 palette: Invalid argument
> [1] Failed with YUV422, trying YUYV palette: Invalid argument
> [1] Failed with YUYV, trying RGB24 palette: Invalid argument
> [1] Failed with RGB24, trying GREYSCALE palette: Invalid argument
> [1] Failed with all supported palettes - giving up: Invalid argument
> [1] Capture error calling vid_start
> [1] Thread finishing...
> [1] Error removing pid file: No such file or directory
> 
> Can anyone tell me what's wrong?

The DC10+ is a very annoying capture card, and this has been covered 
many times.
I'll tell you what I do to make mine work, its all to do with memory 
allocations/holes that the DC10 needs.
The first thing you need to do is allocate some memory to use for video 
capture on the board, to do that edit your /boot/grub/menu.lst
Look for your current kernel and add something like:
mem=500M bigphysarea=4096
Onto the end of the 'kernel' line. What that means is that I've got a 
machine with 512Mb of RAM so I'm reserving 12Mb of RAM for capture 
allocation.

I'm assuming you're using the zr36067 kernel module?
As in that case I load the module manually using the following 2 lines:

cd /lib/modules/`cat /proc/version | cut -d " " -f 
3`/kernel/drivers/media/video
/sbin/insmod zr36067.ko card=2 v4l_bufsize=1296 debug=0

After that, try running motion and see how it goes. Otherwise, do a few 
searches on the zr36067 and you'll find this is probably one of the most 
awkard (and old) cards to get working!

Good luck!

-- 
Andy
e: an...@th...
e: an...@br...

w: http://www.thebmwz3.co.uk
w: http://www.broadcast-tech.co.uk