VIDIOC_QBUF: Device or resource busy

Question

Hi, I'm attempting to get motion working on Debian 5.0.2 with a Hauppauge ImpactVCB capture card. I get the following error messages (full output appears below):

[1] VIDIOC_QBUF: Device or resource busy

[1] ioctl(VIDIOCGMBUF) - Error device does not support memory map

[1] V4L capturing using read is deprecated!

[1] Motion only supports mmap.

[1] Capture error calling vid_start [1] Thread finishing...

I've also list the contents of motion.conf. Thanks for all help! Larry Younkins

[0] Processing thread 0 - config file /home/larry/.motion/motion.conf
[0] Motion 3.2.9 Started
[0] ffmpeg LIBAVCODEC_BUILD 3355136 LIBAVFORMAT_BUILD 3409664
[0] Thread 1 is from /home/larry/.motion/motion.conf
[1] Thread 1 started
[1] cap.driver: "bttv"
[1] cap.card: "BT878 video (Hauppauge (bt878))"
[1] cap.bus_info: "PCI:0000:00:09.0"
[1] cap.capabilities=0x05010015
[1] - VIDEO_CAPTURE
[1] - VIDEO_OVERLAY
[1] - VBI_CAPTURE
[1] - TUNER
[1] - READWRITE
[1] - STREAMING
[1] Supported palettes:
[1] 0: GREY (8 bpp, gray)
[1] 1: HI24 (8 bpp, dithered color)
[1] 2: RGBO (15 bpp RGB, le)
[1] 3: RGBQ (15 bpp RGB, be)
[1] 4: RGBP (16 bpp RGB, le)
[1] 5: RGBR (16 bpp RGB, be)
[1] 6: BGR3 (24 bpp RGB, le)
[1] 7: BGR4 (32 bpp RGB, le)
[1] 8: RGB4 (32 bpp RGB, be)
[1] 9: YUYV (4:2:2, packed, YUYV)
[1] 10: YUYV (4:2:2, packed, YUYV)
[1] 11: UYVY (4:2:2, packed, UYVY)
[1] 12: 422P (4:2:2, planar, Y-Cb-Cr)
[1] 13: YU12 (4:2:0, planar, Y-Cb-Cr)
[1] 14: YV12 (4:2:0, planar, Y-Cr-Cb)
[1] 15: 411P (4:1:1, planar, Y-Cb-Cr)
[1] 16: YUV9 (4:1:0, planar, Y-Cb-Cr)
[1] 17: YVU9 (4:1:0, planar, Y-Cr-Cb)
[1] Test palette YU12 (320x240)
[1] Using palette YU12 (320x240) bytesperlines 320 sizeimage 115200 colorspace 00000000
[1] found control 0x00980900, "Brightness", range 0,65535 
[1]    "Brightness", default 32768, current 32768
[1] found control 0x00980901, "Contrast", range 0,65535 
[1]    "Contrast", default 32768, current 32768
[1] found control 0x00980902, "Saturation", range 0,65535 
[1]    "Saturation", default 32768, current 32768
[1] found control 0x00980903, "Hue", range 0,65535 
[1]    "Hue", default 32768, current 32768
[1] found control 0x00000000, "42", range 0,0 !DISABLED!
[1]    "42", default 0, current 0
[1] found control 0x00000000, "42", range 0,0 !DISABLED!
[1]    "42", default 0, current 0
[1] found control 0x00000000, "42", range 0,0 !DISABLED!
[1]    "42", default 0, current 0
[1] found control 0x00000000, "42", range 0,0 !DISABLED!
[1]    "42", default 0, current 0
[1] found control 0x00000000, "42", range 0,0 !DISABLED!
[1]    "42", default 0, current 0
[1] found control 0x00000000, "42", range 0,0 !DISABLED!
[1]    "42", default 0, current 0
[1] found control 0x08000000, "chroma agc", range 0,1 
[1]    "chroma agc", default 0, current 0
[1] found control 0x08000001, "combfilter", range 0,1 
[1]    "combfilter", default 0, current 0
[1] mmap information:
[1] frames=4
[1] 0 length=118784
[1] 1 length=118784
[1] 2 length=118784
[1] 3 length=118784
[1] VIDIOC_QBUF: Device or resource busy
[1] ioctl(VIDIOCGMBUF) - Error device does not support memory map
[1] V4L capturing using read is deprecated!
[1] Motion only supports mmap.
[1] Capture error calling vid_start
[1] Thread finishing...

Contents of motion.conf:
input 1
height 240
width 320
norm 1
framerate 10
target_dir /home/larry/Pictures

Environment

Motion version:	3.2.9-7
ffmpeg version:
Libraries:	ffmpeg, mysql, postgresql
Server OS:	Debian 5.0.1

-- LarryYounkins - 17 May 2009

Answer

- 1. You must use the latest version of Motion (v.3.2.11).

- 2. You must read here :

http://www.lavrsen.dk/foswiki/bin/view/Motion/MotionWinTVPVRCardSupport

http://www.lavrsen.dk/foswiki/bin/view/Motion/WorkingDevices

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

- 3. Anyway, your motion.conf looks to be incomplete, and you must be sure that you load the correct driver for your camera, before trying to run Motion...

-- FlorinAnton - 17 May 2009