Hi Amelie, On Tuesday 04 November 2008, Amelie Zapf wrote: > Dear Laurent, > > > > This is weird. Upon rmmodding and re-modprobing the driver, the device > > > file /dev/video0 is deleted and not recreated (why, I don't know). > > > > This is indeed weird. Could you check the kernel log (dmesg) when this > > happens to see if the driver prints any error message ? > > Here's the whole shebang: > > schlepptop:/home/amelie # lsmod | grep uvc > uvcvideo 75912 0 > compat_ioctl32 25984 1 uvcvideo > videodev 52096 2 uvcvideo,compat_ioctl32 > v4l1_compat 29444 2 uvcvideo,videodev > usbcore 188248 7 > uvcvideo,snd_usb_audio,snd_usb_lib,usbhid,ehci_hcd,ohci_hcd > schlepptop:/home/amelie # rmmod uvcvideo > schlepptop:/home/amelie # lsmod | grep uvc > schlepptop:/home/amelie # modprobe uvcvideo > schlepptop:/home/amelie # lsmod | grep uvc > uvcvideo 75912 0 > compat_ioctl32 25984 1 uvcvideo > videodev 52096 2 uvcvideo,compat_ioctl32 > v4l1_compat 29444 2 uvcvideo,videodev > usbcore 188248 7 > uvcvideo,snd_usb_audio,snd_usb_lib,usbhid,ehci_hcd,ohci_hcd > schlepptop:/home/amelie # dmesg > [...] > uvcvideo: Found UVC 1.00 device USB 2.0 Camera (174f:5a31) > uvcvideo: Forcing device quirks 0x4 by module parameter for testing > purpose. uvcvideo: Please report required quirks to the linux-uvc-devel > mailing list. [...] > uvcvideo: Failed to query (1) UVC control 1 (unit 0) : -110 (exp. 26). > [...] > uvcvideo: Failed to query (1) UVC control 1 (unit 0) : -110 (exp. 26). > uvcvideo: Failed to query (1) UVC control 1 (unit 0) : -110 (exp. 26). > usbcore: deregistering interface driver uvcvideo > uvcvideo: Found UVC 1.00 device USB 2.0 Camera (174f:5a31) > uvcvideo: Forcing device quirks 0x4 by module parameter for testing > purpose. uvcvideo: Please report required quirks to the linux-uvc-devel > mailing list. uvcvideo: Failed to query (135) UVC control 1 (unit 0) : -110 > (exp. 26). uvcvideo: Failed to query (129) UVC control 1 (unit 0) : -110 > (exp. 26). uvcvideo: Failed to initialize the device (-5). > usbcore: registered new interface driver uvcvideo > USB Video Class driver (SVN r200) > schlepptop:/home/amelie # ls /dev/video* > ls: Zugriff auf /dev/video* nicht möglich: Datei oder Verzeichnis nicht > gefunden > > > What about '-f yuv' ? :-) > > No better, I'm afraid: > > [EMAIL PROTECTED]:~> luvcview -f yuv > luvcview version 0.2.1 > Video driver: x11 > A window manager is available > video /dev/video0 > Unable to set format: 5. > Init v4L2 failed !! exit fatal > > Hope this helps,
No really unfortunately :-( From what you report the camera seems to completely crash. All error messages report a -110 error, which indicates a timeout (-ETIMEDOUT). Timeouts are usually caused by firmware errors, as bad requests should be answered with an error and not ignored by the device. When loaded, the driver queries the video probe control (control 1, unit 0) for it's default value (GET_DEF, 135) or, if this fails, for its current value (GET_CUR, 129). As you can see in the log, no such error is reported the first time the driver is loaded. When an application sets the video format the driver will set (SET_CUR, 1) the video probe control value. The driver reports timeouts, which means that either the first SET_CUR request or the request right before made the device crash. This can be confirmed by the module unloading and reloading, as the device then fails to respond to the initial GET_DEF and GET_CUR. My guess would be that the SET_CUR request makes the device crash. This could be caused by unexpected values (from the device's point of view) in the request data. If you have access to a Windows box, it would be interesting to try the camera there and, if it works properly, capture a USB trace. Best regards, Laurent Pinchart _______________________________________________ Linux-uvc-devel mailing list [email protected] https://lists.berlios.de/mailman/listinfo/linux-uvc-devel
