UVCcapture Error: Failed to Submit URB 0 (-4008)


17 posts
by pld7 » Fri Jun 15, 2012 10:48 am
When I try to use UVCcapute I get the error

root@raspberrypi:/home/pi# uvccapture -v -m
Using videodevice: /dev/video0
Saving images to: snap.jpg
Image size: 320x240
Taking snapshot every 0 seconds
Taking images using mmap
Resetting camera settings
ioctl reset control error
ioctl querycontrol error 22
Camera brightness level is -10
Camera contrast level is 20
Camera saturation level is 10
ioctl querycontrol error 22
Camera gain level is -1
Unable to start capture: 4008.
Error grabbing

dmesg gives me


root@raspberrypi:/home/pi# dmesg
[ 0.000000] Initializing cgroup subsys cpu
[ 0.000000] Linux version 3.1.9+ (dc4@dc4-arm-01) (gcc version 4.5.1 (Broadcom-2708) ) #110 PREEMPT Wed Jun 13 11:41:58 BST 2012
[ 0.000000] CPU: ARMv6-compatible processor [410fb767] revision 7 (ARMv7), cr=00c5387d
[ 0.000000] CPU: VIPT nonaliasing data cache, VIPT nonaliasing instruction cache
[ 0.000000] Machine: BCM2708
[ 0.000000] Memory policy: ECC disabled, Data cache writeback
[ 0.000000] On node 0 totalpages: 49152
[ 0.000000] free_area_init_node: node 0, pgdat c05f124c, node_mem_map c06c1000
[ 0.000000] Normal zone: 384 pages used for memmap
[ 0.000000] Normal zone: 0 pages reserved
[ 0.000000] Normal zone: 48768 pages, LIFO batch:15
[ 0.000000] pcpu-alloc: s0 r0 d32768 u32768 alloc=1*32768
[ 0.000000] pcpu-alloc: [0] 0
[ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 48768
[ 0.000000] Kernel command line: dma.dmachans=0x3c bcm2708_fb.fbwidth=1344 bcm2708_fb.fbheight=804 bcm2708.boardrev=0x2 bcm2708.serial=0xfa24575 smsc95xx.macaddr=B8:27:EB:A2:45:75 dwc_otg.lpm_enable=0 console=ttyAMA0,115200 kgdboc=ttyAMA0,115200 console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 rootwait
[ 0.000000] PID hash table entries: 1024 (order: 0, 4096 bytes)
[ 0.000000] Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
[ 0.000000] Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
[ 0.000000] Memory: 192MB = 192MB total
[ 0.000000] Memory: 187908k/187908k available, 8700k reserved, 0K highmem
[ 0.000000] Virtual kernel memory layout:
[ 0.000000] vector : 0xffff0000 - 0xffff1000 ( 4 kB)
[ 0.000000] fixmap : 0xfff00000 - 0xfffe0000 ( 896 kB)
[ 0.000000] DMA : 0xffc00000 - 0xffe00000 ( 2 MB)
[ 0.000000] vmalloc : 0xcc800000 - 0xd8000000 ( 184 MB)
[ 0.000000] lowmem : 0xc0000000 - 0xcc000000 ( 192 MB)
[ 0.000000] modules : 0xbf000000 - 0xc0000000 ( 16 MB)
[ 0.000000] .text : 0xc0008000 - 0xc0593fd4 (5680 kB)
[ 0.000000] .init : 0xc0594000 - 0xc05c5000 ( 196 kB)
[ 0.000000] .data : 0xc05c6000 - 0xc05f29b8 ( 179 kB)
[ 0.000000] .bss : 0xc05f29dc - 0xc06c06e4 ( 824 kB)
[ 0.000000] NR_IRQS:85
[ 0.000000] timer_set_mode: unhandled mode:1
[ 0.000000] timer_set_mode: unhandled mode:3
[ 0.000000] Console: colour dummy device 80x30
[ 0.000000] console [tty1] enabled
[ 3.705469] Calibrating delay loop... 697.95 BogoMIPS (lpj=3489792)
[ 3.764449] pid_max: default: 32768 minimum: 301
[ 3.765076] Mount-cache hash table entries: 512
[ 3.765727] Initializing cgroup subsys cpuacct
[ 3.765814] Initializing cgroup subsys devices
[ 3.765864] Initializing cgroup subsys freezer
[ 3.765908] Initializing cgroup subsys blkio
[ 3.766035] CPU: Testing write buffer coherency: ok
[ 3.766172] ftrace: allocating 14754 entries in 44 pages
[ 3.837144] hw perfevents: enabled with v6 PMU driver, 3 counters available
[ 3.839539] devtmpfs: initialized
[ 3.842048] NET: Registered protocol family 16
[ 3.843475] vc-mem: mm_vc_mem_phys_addr = 0x00000000
[ 3.843540] vc-mem: mm_vc_mem_size = 0x10000000 (256 MiB)
[ 3.844068] hw-breakpoint: found 6 breakpoint and 1 watchpoint registers.
[ 3.844140] hw-breakpoint: maximum watchpoint size is 4 bytes.
[ 3.844188] mailbox: Broadcom VideoCore Mailbox driver
[ 3.844303] bcm2708_vcio: mailbox at f200b880
[ 3.844411] bcm_power: Broadcom power driver
[ 3.844460] bcm_power_open() -> 0
[ 3.844492] bcm_power_request(0, 8)
[ 4.345184] bcm_mailbox_read -> 00000080, 0
[ 4.345232] bcm_power_request -> 0
[ 4.345265] Serial: AMBA PL011 UART driver
[ 4.345436] dev:f1: ttyAMA0 at MMIO 0x20201000 (irq = 83) is a PL011 rev3
[ 4.649498] console [ttyAMA0] enabled
[ 4.674300] bio: create slab <bio-0> at 0
[ 4.679867] SCSI subsystem initialized
[ 4.683904] usbcore: registered new interface driver usbfs
[ 4.689564] usbcore: registered new interface driver hub
[ 4.695307] usbcore: registered new device driver usb
[ 4.701348] Switching to clocksource stc
[ 4.715459] Switched to NOHz mode on CPU #0
[ 4.723955] FS-Cache: Loaded
[ 4.727356] CacheFiles: Loaded
[ 4.748589] NET: Registered protocol family 2
[ 4.753510] IP route cache hash table entries: 2048 (order: 1, 8192 bytes)
[ 4.762067] TCP established hash table entries: 8192 (order: 4, 65536 bytes)
[ 4.769604] TCP bind hash table entries: 8192 (order: 3, 32768 bytes)
[ 4.776314] TCP: Hash tables configured (established 8192 bind 8192)
[ 4.782698] TCP reno registered
[ 4.785911] UDP hash table entries: 256 (order: 0, 4096 bytes)
[ 4.791802] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
[ 4.798659] NET: Registered protocol family 1
[ 4.804031] RPC: Registered named UNIX socket transport module.
[ 4.810216] RPC: Registered udp transport module.
[ 4.814949] RPC: Registered tcp transport module.
[ 4.819716] RPC: Registered tcp NFSv4.1 backchannel transport module.
[ 4.826530] bcm2708_dma: DMA manager at cc808000
[ 4.831290] bcm2708_gpio: bcm2708_gpio_probe c05ce0a8
[ 4.836641] vc-mem: Videocore memory driver
[ 4.841738] audit: initializing netlink socket (disabled)
[ 4.847310] type=2000 audit(0.770:1): initialized
[ 4.959420] VFS: Disk quotas dquot_6.5.2
[ 4.963637] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[ 4.971680] FS-Cache: Netfs 'nfs' registered for caching
[ 4.978364] msgmni has been set to 367
[ 4.984766] io scheduler noop registered
[ 4.988946] io scheduler deadline registered
[ 4.993452] io scheduler cfq registered (default)
[ 4.998590] BCM2708FB: registering framebuffer (1344x804@16)
[ 5.005012] bcm2708_fb_set_par info(cb8dd400) 1344x804 (1344x804), 0, 16
[ 5.019982] BCM2708FB: start = ccc00000,4d385000 width=1344, height=804, bpp=16, pitch=2688 size=2193408 success=0
[ 5.035890] Console: switching to colour frame buffer device 168x50
[ 5.074151] BCM2708FB: register framebuffer (0)
[ 5.079648] kgdb: Registered I/O driver kgdboc.
[ 5.096212] brd: module loaded
[ 5.105581] loop: module loaded
[ 5.109808] vcos: [1]: vchiq_init_state: slot_zero = 0xffd80000, is_master = 0
[ 5.117571] vcos: [1]: vchiq_init_state: called
[ 5.123067] vcos: [1]: vchiq: initialised - version 2 (min 2), device 253.0
[ 5.131219] usbcore: registered new interface driver smsc95xx
[ 5.137286] cdc_ncm: 04-Aug-2011
[ 5.140751] usbcore: registered new interface driver cdc_ncm
[ 5.146637] dwc_otg: version 2.90b 6-MAY-2010 (platform bus)
[ 5.152822] Core Release: 2.80a
[ 5.156206] Setting default values for core params
[ 5.166358] Finished setting default values for core params
[ 5.177449] cc840008 -> 1
[ 5.385500] Using Buffer DMA mode
[ 5.394015] Periodic Transfer Interrupt Enhancement - disabled
[ 5.405333] Multiprocessor Interrupt Enhancement - disabled
[ 5.416264] Dedicated Tx FIFOs mode
[ 5.425172] dwc_otg bcm2708_usb: DWC OTG Controller
[ 5.435512] dwc_otg bcm2708_usb: new USB bus registered, assigned bus number 1
[ 5.448140] dwc_otg bcm2708_usb: irq 75, io mem 0x00000000
[ 5.458958] Init: Port Power? op_state=1
[ 5.468141] Init: Power Port (0)
[ 5.476638] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[ 5.488724] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 5.501220] usb usb1: Product: DWC OTG Controller
[ 5.511199] usb usb1: Manufacturer: Linux 3.1.9+ dwc_otg_hcd
[ 5.522215] usb usb1: SerialNumber: bcm2708_usb
[ 5.533162] hub 1-0:1.0: USB hub found
[ 5.542297] hub 1-0:1.0: 1 port detected
[ 5.552349] Module dwc_common_port init
[ 5.552762] usbcore: registered new interface driver uas
[ 5.563363] Initializing USB Mass Storage driver...
[ 5.573796] usbcore: registered new interface driver usb-storage
[ 5.585174] USB Mass Storage support registered.
[ 5.595298] usbcore: registered new interface driver libusual
[ 5.607001] mousedev: PS/2 mouse device common for all mice
[ 5.617970] cpuidle: using governor ladder
[ 5.627306] cpuidle: using governor menu
[ 5.636660] sdhci: Secure Digital Host Controller Interface driver
[ 5.648310] sdhci: Copyright(c) Pierre Ossman
[ 5.658206] bcm_power_open() -> 1
[ 5.667174] Registered led device: mmc0::
[ 5.667681] mmc0: SDHCI controller on BCM2708_Arasan [platform] using platform's DMA
[ 5.680905] mmc0: BCM2708 SDHC host at 0x20300000 DMA 2 IRQ 77
[ 5.692111] sdhci-pltfm: SDHCI platform and OF driver helper
[ 5.704444] Registered led device: led0
[ 5.704914] usbcore: registered new interface driver usbhid
[ 5.715818] usbhid: USB HID core driver
[ 5.733916] TCP cubic registered
[ 5.742421] Initializing XFRM netlink socket
[ 5.761096] NET: Registered protocol family 17
[ 5.785603] Registering the dns_resolver key type
[ 5.805658] VFP support v0.3: implementor 41 architecture 1 part 20 variant b rev 5
[ 5.837848] Waiting for root device /dev/mmcblk0p2...
[ 5.861615] mmc0: new SDHC card at address e624
[ 5.881600] mmcblk0: mmc0:e624 SD16G 14.8 GiB
[ 5.897128] mmcblk0: p1 p2 p3
[ 5.995587] usb 1-1: new high speed USB device number 2 using dwc_otg
[ 6.216350] usb 1-1: New USB device found, idVendor=0424, idProduct=9512
[ 6.229998] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 6.243770] hub 1-1:1.0: USB hub found
[ 6.254757] hub 1-1:1.0: 3 ports detected
[ 6.535862] usb 1-1.1: new high speed USB device number 3 using dwc_otg
[ 6.646349] usb 1-1.1: New USB device found, idVendor=0424, idProduct=ec00
[ 6.661904] usb 1-1.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 6.678582] smsc95xx v1.0.4
[ 6.752064] smsc95xx 1-1.1:1.0: eth0: register 'smsc95xx' at usb-bcm2708_usb-1.1, smsc95xx USB 2.0 Ethernet, b8:27:eb:a2:45:75
[ 6.865865] usb 1-1.2: new high speed USB device number 4 using dwc_otg
[ 6.976523] usb 1-1.2: New USB device found, idVendor=1a40, idProduct=0201
[ 6.992416] usb 1-1.2: New USB device strings: Mfr=0, Product=1, SerialNumber=0
[ 7.005351] usb 1-1.2: Product: USB 2.0 Hub [MTT]
[ 7.017124] hub 1-1.2:1.0: USB hub found
[ 7.027246] hub 1-1.2:1.0: 7 ports detected
[ 7.317370] usb 1-1.2.4: new low speed USB device number 5 using dwc_otg
[ 7.451196] usb 1-1.2.4: config 1 interface 0 altsetting 0 has 1 endpoint descriptor, different from the interface descriptor's value: 0
[ 7.476887] usb 1-1.2.4: New USB device found, idVendor=0c45, idProduct=7408
[ 7.489874] usb 1-1.2.4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 7.507393] usb 1-1.2.4: Product: USB Device
[ 7.517787] usb 1-1.2.4: Manufacturer: SONiX
[ 7.532011] usbhid 1-1.2.4:1.0: couldn't find an input interrupt endpoint
[ 7.554855] input: SONiX USB Device as /devices/platform/bcm2708_usb/usb1/1-1/1-1.2/1-1.2.4/1-1.2.4:1.1/input/input0
[ 7.571964] generic-usb 0003:0C45:7408.0001: input: USB HID v1.00 Mouse [SONiX USB Device] on usb-bcm2708_usb-1.2.4/input1
[ 7.596281] input: SONiX USB Device as /devices/platform/bcm2708_usb/usb1/1-1/1-1.2/1-1.2.4/1-1.2.4:1.2/input/input1
[ 7.613301] generic-usb 0003:0C45:7408.0002: input: USB HID v1.00 Keyboard [SONiX USB Device] on usb-bcm2708_usb-1.2.4/input2
[ 7.715727] usb 1-1.2.7: new high speed USB device number 6 using dwc_otg
[ 7.830078] usb 1-1.2.7: New USB device found, idVendor=1a40, idProduct=0101
[ 7.846192] usb 1-1.2.7: New USB device strings: Mfr=0, Product=1, SerialNumber=0
[ 7.862734] usb 1-1.2.7: Product: USB 2.0 Hub [MTT]
[ 7.880283] hub 1-1.2.7:1.0: USB hub found
[ 7.893501] hub 1-1.2.7:1.0: 4 ports detected
[ 8.068878] EXT4-fs (mmcblk0p2): recovery complete
[ 8.083653] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null)
[ 8.098277] VFS: Mounted root (ext4 filesystem) on device 179:2.
[ 8.112194] Freeing init memory: 196K
[ 13.561254] EXT4-fs (mmcblk0p2): re-mounted. Opts: (null)
[ 16.467806] fuse init (API version 7.17)
[ 17.846392] smsc95xx 1-1.1:1.0: eth0: link up, 100Mbps, full-duplex, lpa 0x41E1
[ 21.132681] NET: Registered protocol family 10
[ 21.471792] sshd (736): /proc/736/oom_adj is deprecated, please use /proc/736/oom_score_adj instead.
[ 31.975531] eth0: no IPv6 routers present
[ 83.505779] usb 1-1.2.1: new high speed USB device number 7 using dwc_otg
[ 83.625690] usb 1-1.2.1: New USB device found, idVendor=0ac8, idProduct=3450
[ 83.625726] usb 1-1.2.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 83.625747] usb 1-1.2.1: Product: Vimicro USB Camera (Altair)
[ 83.625777] usb 1-1.2.1: Manufacturer: Vimicro
[ 83.777860] Linux video capture interface: v2.00
[ 83.801681] uvcvideo: Found UVC 1.00 device Vimicro USB Camera (Altair) (0ac8:3450)
[ 83.807125] input: Vimicro USB Camera (Altair) as /devices/platform/bcm2708_usb/usb1/1-1/1-1.2/1-1.2.1/1-1.2.1:1.0/input/input2
[ 83.811701] usbcore: registered new interface driver uvcvideo
[ 83.811736] USB Video Class driver (1.1.1)
[ 491.455549] uvcvideo: Failed to query (SET_CUR) UVC control 3 on unit 2: -110 (exp. 2).
[ 492.513113] INFO:: periodic_channel_available: Total channels: 8, Periodic: 7, Non-periodic: 1
[ 492.513131]
[ 492.513154] INFO:: schedule_periodic: No host channel available for periodic transfer.
[ 492.513167]
[ 492.513206] ERROR::dwc_otg_hcd_urb_enqueue:487: DWC OTG HCD URB Enqueue failed adding QTD. Error status -4008
[ 492.513219]
[ 492.513244] uvcvideo: Failed to submit URB 0 (-4008).


Anyone know what's going on? Both my webcams that appear on the list of UVC compatible cameras both give the same fault.
Posts: 13
Joined: Thu May 31, 2012 10:12 am
by ashbash » Fri Jun 15, 2012 10:55 am
dmesg | tail helps ;-)

But are your cameras running off the Pi's power or ext hub?
Posts: 50
Joined: Fri Jun 01, 2012 9:20 am
by pld7 » Fri Jun 15, 2012 11:06 am
ashbash wrote:dmesg | tail helps ;-)

But are your cameras running off the Pi's power or ext hub?


Just to clarify at the moment I only have one camera plugged in at a time.

Also, I get the same error messages whether it's in my powered hub or the RPi itself.

EDIT: Yeah, sorry about the long dmesg output, I wasn't sure what bits might be important.
Posts: 13
Joined: Thu May 31, 2012 10:12 am
by ashbash » Fri Jun 15, 2012 11:18 am
:)
rpi-updated ?
Posts: 50
Joined: Fri Jun 01, 2012 9:20 am
by pld7 » Fri Jun 15, 2012 12:34 pm
ashbash wrote::)
rpi-updated ?


Yeah my system's all up to date.
Posts: 13
Joined: Thu May 31, 2012 10:12 am
by ashbash » Fri Jun 15, 2012 1:03 pm
Great, can u verify the cams somehow? Motion, cheese .... lets eliminate the hw<->os.
Posts: 50
Joined: Fri Jun 01, 2012 9:20 am
by pld7 » Fri Jun 15, 2012 1:29 pm
ashbash wrote:Great, can u verify the cams somehow? Motion, cheese .... lets eliminate the hw<->os.


I have a bunch of cameras (Some UVC supported, some not). The two ones that are UVC supported don't work on Cheese on my RPi (When started, Cheese displays the loading animation then gives a blank screen or crashes). However, the cameras do work very well when I run Cheese on my Ubuntu laptop so I don't think it's a hardware problem. The cameras were advertised as 'Driverless' and I've read elsewhere that some cameras don't output raw video but instead output video already in a format (Such as MPEG). I think this can then confuse UVCcapture because it uses Video4Linux2 when it doesn't have to. I'm not really sure about this, is there a way of finding out what a webcam is outputting?

One of my cameras that isn't on the UVC compatible list (It's actually an IR camera) does work on Cheese on my RPi but it has a terrible frame rate and gives different errors when I try to use UVCcapture. (From memory I think the error says something along the lines of 'V4L failed to init')
Posts: 13
Joined: Thu May 31, 2012 10:12 am
by ashbash » Sat Jun 16, 2012 9:09 am
Looks to me like you have answered your own question really, it sounds like you have identified an "issue" between the drivers for your devices and/or s/w and the kernel ..
Posts: 50
Joined: Fri Jun 01, 2012 9:20 am
by pld7 » Sat Jun 16, 2012 12:54 pm
Well, it's good to know I'm getting better at troubleshooting my RPi. However, there must be a way around this. I know you can use ffmpeg directly to capture a one-frame video then use ffmpeg to convert that video to a still but seeing as I don't know what format my webcams are outputting I don't know what format to tell ffmpeg to expect.
Posts: 13
Joined: Thu May 31, 2012 10:12 am
by rleyden » Sat Jun 16, 2012 8:18 pm
Could someone provide details of how they compiled uvccapture? When I tried (on Arch) i get an error that videodev.h is not found. Videodev.h came up in another thead,
http://www.raspberrypi.org/phpBB3/viewtopic.php?f=28&t=5671&p=75785&hilit=videodev.h#p75785
saying
Confirms that the driver was developed for video4linux version 1.
Version 2 uses videodev2.h

BTW, I'm fond of using uvccapture because it was the most reliable way to capture images on my Chumby, an analogous resource limited linux system.

Rich
User avatar
Posts: 54
Joined: Thu Jun 14, 2012 2:17 am
by rleyden » Sun Jun 17, 2012 7:58 pm
rleyden wrote:Could someone provide details of how they compiled uvccapture?

Answering my own question.
I switched from Arch to Raspbian v3 and uvccapture is available through apt-get. Also, there is a patch to uvccapture-.05-1 source that I missed.

So far, I haven't had much better luck with Raspbian and a couple of generic UVC webcams. Running uvccapture in the verbose mode gives an error along the lines of "V4L2 format incompatible/file not found". However, previous experience taught me that the error messages are often misleading. Sometimes it will work perfectly with a different set of options specified.
User avatar
Posts: 54
Joined: Thu Jun 14, 2012 2:17 am
by pld7 » Mon Jun 18, 2012 10:19 am
rleyden wrote:
rleyden wrote:Could someone provide details of how they compiled uvccapture?

Answering my own question.
I switched from Arch to Raspbian v3 and uvccapture is available through apt-get. Also, there is a patch to uvccapture-.05-1 source that I missed.

So far, I haven't had much better luck with Raspbian and a couple of generic UVC webcams. Running uvccapture in the verbose mode gives an error along the lines of "V4L2 format incompatible/file not found". However, previous experience taught me that the error messages are often misleading. Sometimes it will work perfectly with a different set of options specified.


I sometimes got the above error because cameras sometimes get listed in /dev/ as /dev/video1 instead of /dev/video0 (Especially if you're detaching and attaching different cameras rapidly). This is readily fixed by unplugging the camera and allowing some time to elapse before plugging it back in. Alternatively you can tell UVCcapture which camera to use.

It might also be worth considering which directory you're trying to execute UVCcapture from. I think I was sometimes trying to run it in the wrong places and this lead to avoidable error messages.

EDIT: PS I also found passing -m to UVCcapture often made it work when it wasn't before. As I understand it this option makes UVCcapture encode the image differently (YUYV instead of RGB).
Posts: 13
Joined: Thu May 31, 2012 10:12 am
by rleyden » Tue Jun 19, 2012 6:11 am
pld7 wrote:I sometimes got the above error because cameras sometimes get listed in /dev/ as /dev/video1 instead of /dev/video0 (Especially if you're detaching and attaching different cameras rapidly). This is readily fixed by unplugging the camera and allowing some time to elapse before plugging it back in. Alternatively
.

Good tip. This was part of the problem which was compounded by one of the webcams not actually being UVC compliant. I used Ubuntu to determine which cameras work with various linux programs.
My favorite webcam, identified by lsusb as "Silicon Motion SM371 ", ID 090c:b371, works with every webcam program under Ubuntu including uvccapture. However, under raspbian v3, I couldn't get it to work with uvccapture. But it worked great with fswebcam, very snappy performance from the command line. Cheese also worked with this cam, but sluggishly, from the graphical desktop.

My current plan is to use the RPi as a webcam server. I may default to just doing frame capture and file transfer to another system to host the web page. I loaded zoneminder and apache2 on the RPIi and I noticed there was something like only 25k free memory left.

Rich
User avatar
Posts: 54
Joined: Thu Jun 14, 2012 2:17 am
by FelesMala » Tue Jun 19, 2012 10:31 am
I too am trying to get webcams working on the raspberry Pi!

I've only tried the initial debian squeeze image (updated), and have tried uvccapture and cheese using an old creative webcam instant and a relatively recent microsoft lifecame vx-3000.

Both of which I've tried plugged directly into the pi or via 3 different hubs, one unpowered and two powered. (not both cameras at the same time)

I get the same result in cheese on both cameras (approx 1 frame every 15-30 seconds for a minute or 3 before the camera light turns off and no more frames are returned). And the same result for both in uvccapture (v4l2 could not init) format unsupported, although it's unclear what formats are supported.

I'm going to watch this thread avidly from now on, because having spent about a week getting drivers, reinstalling, rebuilding, buying hardware (paid more now for hubs, PSUs and cameras than for the pi by a large margin), I'm still not at the point where I can save video/stills, and not even at the point where I can put my considerable python skills into practice :)

I really hope you get it working :)
Posts: 3
Joined: Sat Jun 16, 2012 7:59 pm
by Trevor.Cushen » Tue Jun 19, 2012 11:36 am
Hello,
Not sure if you are still stuck, but I also was stuck using uvccapture for one webcam but another worked fine. What fixed it for me was adding -m flag.

Uvccapture -m -oPicture.jpg

Hope this helps
Posts: 4
Joined: Wed Jun 13, 2012 1:10 pm
by pld7 » Tue Jun 19, 2012 2:35 pm
FelesMala wrote:I too am trying to get webcams working on the raspberry Pi!

I've only tried the initial debian squeeze image (updated), and have tried uvccapture and cheese using an old creative webcam instant and a relatively recent microsoft lifecame vx-3000.


I've got the furthest with Squeeze here's a couple of points.

1) have you checked whether your webcams are supported by UVC? If not use 'lsusb' to get their Device ID and check it here.

http://www.ideasonboard.org/uvc/

2) Have you passed the -v command to UVCcapture? If you could run 'uvccapture -v -m' and post the results here it might help someone help you. (Make sure your webcam is listed as /dev/video0 as I mentioned above before you run it)

3) What does 'dmesg' give you when UVCcapture fails? Don't make the mistake I did and post it all 'dmesg | tail' should suffice.
Posts: 13
Joined: Thu May 31, 2012 10:12 am
by rleyden » Wed Jun 20, 2012 3:31 am
rleyden wrote:However, under raspbian v3, I couldn't get it to work with uvccapture.

Uvccapture now works (-m option). I unwittingly had installed it with the wrong source.list for Raspbian (see post "apt-get update error") Removing and re-installing with the correct source.list did the trick.
User avatar
Posts: 54
Joined: Thu Jun 14, 2012 2:17 am