Motion dies with unknown cmd fd

Question

With camstream, everything is fine, with different size images etc. However with "motion", the threads finish as shown below. Is this a bug ? I am running Fedora Core 5 x86_64

[0] Processing thread 0 - config file /home/jparsons/.motion/motion.conf
[0] Processing config file /home/jparsons/.motion/thread1.conf
[0] Thread is from /home/jparsons/.motion/thread1.conf
[1] Thread started
[1] ioctl (VIDIOCGCAP): Invalid argument
[1] Capture error calling vid_start
[1] Thread finishing...

and dmesg shows:
ioctl32(motion:9979): Unknown cmd fd(3) cmd(803c7601){00} arg(f7fd0da8) on /dev/video0
ioctl32(motion:9984): Unknown cmd fd(3) cmd(803c7601){00} arg(f7fd0da8) on /dev/video0
ioctl32(motion:14129): Unknown cmd fd(3) cmd(803c7601){00} arg(f7fd0da8) on /dev/video0

Environment

Motion version:	3.2.6
ffmpeg version:
Libraries:
Server OS:	Fedora Core 5 x86_64

-- JeremyParsonsFedora - 16 Aug 2006

Follow Up

What driver & camera are you using with motion ?

Could you post your motion.conf and thread1.conf ?

Anyway i guess you have some problem related with your camera driver.

-- AngelCarpintero - 18 Aug 2006

Answer

I had this same problem, and it seemed to be due to the lack of V4L2 support in the current version of motion (see the bug report thread "SupportQuestion2005x07x06x143026: Error while initializing Motion". I even installed vloopback in hopes of using the output for motion, but that gave the same error (yours). Fortunately it looks like V4L2 support may soon be included in the motion package - and there is a patch in the meanwhile. I just compiled the daily snapshot, and now my $18 webcam works!

-- ChrisJenks - 27 Nov 2006

---

We are in the process of testing the V4L2 patch to be included in motion :

http://www.lavrsen.dk/twiki/bin/view/Motion/VideoForLinuxTwoDiscussion

So please test the last svn version of motion + V4L2 patch

-- AngelCarpintero - 07 Jan 2007