Hello,
I'm experiencing issues with Canon EOS DSLRs (60D, 400D -- both have USB
2.0 connections) when connected to a USB 3.0 port on my notebook. After
connecting it, the camera seems to be recognised by the kernel, but is
sometimes unusable by gphoto2; Nautilus never seems to recognise it on
USB 3.0. In dmesg, immediately after connecting:
[ 72.674463] usb 3-1: new high-speed USB device number 2 using xhci_hcd
[ 72.764255] usb 3-1: New USB device found, idVendor=04a9, idProduct=3215
[ 72.764265] usb 3-1: New USB device strings: Mfr=1, Product=2,
SerialNumber=0
[ 72.764272] usb 3-1: Product: Canon Digital Camera
[ 72.764276] usb 3-1: Manufacturer: Canon Inc.
[ 72.765264] usb 3-1: ep 0x81 - rounding interval to 32768
microframes, ep desc says 0 microframes
[ 72.765275] usb 3-1: ep 0x2 - rounding interval to 32768 microframes,
ep desc says 0 microframes
Sometimes gphoto2 works, but the most consistent way I've found to make
it fail is to run gphoto2 -L shortly after connecting (which might be
successful), and then run it again. If this fails, there's a delay of a
few seconds and it returns
*** Error ***
PTP I/O error
*** Error ***
An error occurred in the io-library ('Unspecified error'): No error
description available
*** Error (-1: 'Unspecified error') ***
and messages like
usbfs: usb 3-1: process 8502 (pool) did not claim interface 0 before use
appear in dmesg. I have logs showing what appears in dmesg after
enabling usbfs_snoop in both the for both USB 2.0 and USB 3.0; and
gphoto2's debugging output. Let me know if these would be helpful and
I'll send them (please let me know the most appropriate destination and
format).
Everything works fine with USB 2.0.
Versions of things:
Distro: Fedora 17
Kernel 3.4
gphoto2 2.4.14
USB Controller: NEC Corporation uPD720200 USB 3.0 Host Controller
(rev 04) (prog-if 30 [XHCI])
Camera: 04a9:3215 Canon EOS 60D, firmware up-to-date
Many thanks,
James.
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
