Hello Xavier, The error message from luvcview is :
[ch...@myhost ~]$ luvcview luvcview version 0.2.1 Video driver: x11 A window manager is available video /dev/video0 X Error of failed request: BadAlloc (insufficient resources for operation) Major opcode of failed request: 132 (XVideo) Minor opcode of failed request: 19 () Serial number of failed request: 27 Current serial number in output stream: 28 Well, i didn't tell you all, that a i have now since 1 year Arch Linux. In first time with Arch linux i had kernel 2.6.26 or 27 i don't know which version it was. I am not sure,that my webcam run with skype.In the next time i upgraded the kernel many times and now it's a 2.6.30-5 Kernel.I think it is a kernel problem or other problem. it can have much possibilities. maybe the uvc-driver in the new kernel don't run with my webcam, or v4l don't run too with my webcam. Sorry for my bad englisch :) Best regards Christoph Albert Am Fri, 21 Aug 2009 08:35:39 +0200 schrieb [email protected]: > Send Linux-uvc-devel mailing list submissions to > [email protected] > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.berlios.de/mailman/listinfo/linux-uvc-devel > or, via email, send a message with subject or body 'help' to > [email protected] > > You can reach the person managing the list at > [email protected] > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Linux-uvc-devel digest..." > > > Today's Topics: > > 1. Re: integrated webcam (Xavier Bestel) > 2. Control Pipe Stall (Jacob Fehr) > 3. Re: 093a:2700 camera not work (Paulo Assis) > 4. MSI StarCam 370i Webcam (Dotan Cohen) > 5. Re: MSI StarCam 370i Webcam (Paulo Assis) > 6. Re: MSI StarCam 370i Webcam (Dotan Cohen) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Thu, 20 Aug 2009 14:38:09 +0200 > From: Xavier Bestel <[email protected]> > Subject: Re: [Linux-uvc-devel] integrated webcam > To: Christoph Albert <[email protected]> > Cc: [email protected] > Message-ID: <1250771889.20797.55.ca...@skunk> > Content-Type: text/plain > > Hi, > > On Wed, 2009-08-19 at 22:07 +0000, Christoph Albert wrote: > > My webcam works on vlc ,the mediaplayer,but not in skype( the screen > > is black) ,the video-messenger. luvcview crashes on start. > > Could you send us the messages it prints when it crashes ? > > Thanks, > Xav > > > > > > ------------------------------ > > Message: 2 > Date: Thu, 20 Aug 2009 11:34:19 -0600 > From: Jacob Fehr <[email protected]> > Subject: [Linux-uvc-devel] Control Pipe Stall > To: "'[email protected]'" > <[email protected]> > Message-ID: > <833b0b09c5041d42a9924a3ba6a12b9a024d9ec...@calmail-cms.smarttech.inc> > Content-Type: text/plain; charset="us-ascii" > > I have a UVC camera that will stall the control pipe when I try to access the > extension > unit. At first I thought this was a firmware issue because the kernel docs > say that a > device can't stall its control pipe. I did a little more digging and found > that it > isn't that absolute. The USB spec suggests that control pipe shouldn't but it > can if it > wants to raise a protocol error. I looked at the UVC source code in the > kernel and > found that it doesn't clear the stall when it gets EPIPE. I modified the UVC > driver to > call usb_clear_halt() after it gets EPIPE and this seems to resolve the > issues that I > had with my device. I'm thinking of submitting my fix back to the kernel > maintainers > but thought I'd post here first. Is there anything that I have overlooked? > > Jacob Fehr > SMART Technologies ULC > > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: > https://lists.berlios.de/pipermail/linux-uvc-devel/attachments/20090820/32e2dd17/attachment-0001.html > > > ------------------------------ > > Message: 3 > Date: Thu, 20 Aug 2009 18:35:55 +0100 > From: Paulo Assis <[email protected]> > Subject: Re: [Linux-uvc-devel] 093a:2700 camera not work > To: Laurent Pinchart <[email protected]> > Cc: [email protected] > Message-ID: > <[email protected]> > Content-Type: text/plain; charset=ISO-8859-1 > > Hi, > This seems a recurrent problem. > Make sure that SDL was compiled with all the necessary X headers, if > not then X support will be disabled. > If you are using a binary distribution make sure that your > applications aren't linking against some old (forgotten) SDL library > version. > > use the following command to check library versions: > > ldd luvcview. > > There is a thread on a similar issue here: > http://forums.quickcamteam.net/showthread.php?tid=861 > > best regards, > Paulo > > > > 2009/8/20 Laurent Pinchart <[email protected]>: > > Hi, > > > > On Wednesday 19 August 2009 10:53:00 laiyujun wrote: > >> > >> The name of my camera is "ANC 230". > > > > Thanks. > > > >> I list the device node in /dev: > >> --------------------------------------------------------------------------- > >> someb...@debian:~$ ls /dev/video0 -al > >> crw-rw---- 1 root video 81, 0 08-16 12:02 /dev/video0 > >> --------------------------------------------------------------------------- > >> It seems that video0 locates there. > > > > Unless you have multiple video devices, that's the camera, yes. > > > >> When I try "luvcview", it always return errors: > >> --------------------------------------------------------------------------- > >> someb...@debian:~$ luvcview -d /dev/video0 > >> luvcview 0.2.4 > >> > >> Couldn't initialize SDL: No available video device > >> --------------------------------------------------------------------------- > >> What should I do? > > > > The message is a bit misleading. It doesn't refer to the video input device > > (camera) but to the video output device. luvcview encounters trouble > > initializing the connection with the X server or something similar. I'm > > afraid > > I can't help you there. > > > > -- > > Regards, > > > > Laurent Pinchart > > _______________________________________________ > > Linux-uvc-devel mailing list > > [email protected] > > https://lists.berlios.de/mailman/listinfo/linux-uvc-devel > > > > > ------------------------------ > > Message: 4 > Date: Thu, 20 Aug 2009 23:08:54 +0300 > From: Dotan Cohen <[email protected]> > Subject: [Linux-uvc-devel] MSI StarCam 370i Webcam > To: [email protected] > Message-ID: > <[email protected]> > Content-Type: text/plain; charset=UTF-8 > > I have the MSI StarCam 370i Webcam and I have trying to use it with > Kubuntu Linux 9.04 Jaunty. According to this page, "The StarCam 370i > is compliant with UVC, USB video class": > http://gadgets.softpedia.com/gadgets/Computer-Peripherals/The-MSI-StarCam-370i-3105.html > > According to the Linux UVC driver and tools download page, "Linux > 2.6.26 and newer includes the Linux UVC driver natively" which is nice > as I am on a higher version: > $ uname -r > 2.6.28-15-generic > > However, plugging in the webcam and testing with camorama, cheese, and > luvcview led me to no results: > > jaun...@laptop:~$ luvcview -f yuv > luvcview 0.2.4 > > SDL information: > Video driver: x11 > A window manager is available > Device information: > Device path: /dev/video0 > Stream settings: > ERROR: Requested frame format YUYV is not available and no fallback > format was found. > Init v4L2 failed !! exit fatal > jaun...@laptop:~$ luvcview -f uyvy > luvcview 0.2.4 > > SDL information: > Video driver: x11 > A window manager is available > Device information: > Device path: /dev/video0 > Stream settings: > ERROR: Requested frame format UYVY is not available and no fallback > format was found. > Init v4L2 failed !! exit fatal > jaun...@laptop:~$ luvcview > luvcview 0.2.4 > > SDL information: > Video driver: x11 > A window manager is available > Device information: > Device path: /dev/video0 > Stream settings: > ERROR: Requested frame format MJPG is not available and no fallback > format was found. > Init v4L2 failed !! exit fatal > > > Some more details: > > jaun...@laptop:~$ ls /dev/vi* > /dev/video0 > jaun...@laptop:~$ dmesg | tail > [ 2777.811972] sn9c102: V4L2 driver for SN9C1xx PC Camera Controllers > v1:1.47pre49 > [ 2777.814989] usb 2-1: SN9C105 PC Camera Controller detected (vid:pid > 0x0C45:0x60FC) > [ 2777.842123] usb 2-1: HV7131R image sensor detected > [ 2778.185108] usb 2-1: Initialization succeeded > [ 2778.185220] usb 2-1: V4L2 device registered as /dev/video0 > [ 2778.185225] usb 2-1: Optional device control through 'sysfs' > interface disabled > [ 2778.185283] usbcore: registered new interface driver sn9c102 > [ 2778.216691] usbcore: registered new interface driver snd-usb-audio > [ 2778.218738] usbcore: registered new interface driver sonixj > [ 2778.218745] sonixj: registered > jaun...@laptop:~$ lsusb > Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > Bus 005 Device 002: ID 413c:8126 Dell Computer Corp. Wireless 355 Bluetooth > Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub > Bus 004 Device 004: ID 045e:0040 Microsoft Corp. Wheel Mouse Optical > Bus 004 Device 003: ID 045e:00db Microsoft Corp. Natural Ergonomic > Keyboard 4000 V1.0 > Bus 004 Device 002: ID 05e3:0604 Genesys Logic, Inc. USB 1.1 Hub > Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub > Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub > Bus 002 Device 002: ID 0c45:60fc Microdia PC Camera with Mic (SN9C105) > Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub > jaun...@laptop:~$ > > > > Anything missing? What should I do? Thanks in advance! > _______________________________________________ Linux-uvc-devel mailing list [email protected] https://lists.berlios.de/mailman/listinfo/linux-uvc-devel
