Camera (DSC-P71) in USB mode not mounted as a disk

[alban]

Plugging in a Sony Cybershot DSC-P71 into a USB port; the camera is not recognized as a disk and mounted. The syslog says:-

KERN: devfs: reload driver "emuxki" (3, 3149008) KERN: emuxki: init_hardware() KERN: usb hub 7: port 0: device removed KERN: usb hub 7: port 0 disabled KERN: usb hub 27: port 2: device removed KERN: usb_asix:00.41.983:init_driver::ver.0.8.3 KERN: usb hub 27: port 2: new device connected KERN: usb ehci -1: fullspeed device connected, giving up port ownership KERN: usb hub 7: port 0: new device connected KERN: usb hub 27: port 2: device removed KERN: usb_asix:00.49.910:init_driver::ver.0.8.3 KERN: usb hub 7: port 0: device removed KERN: usb hub 7: KERN: port 0 disabled

Hardware Dell Hybrid 140G. Other USB devices seem to work fine. I can mount the sony memory stick fine using the built in card reader instead.

[stippi]

It's probably due to the camera not implementing the "disk" version of the USB Mass Storage protocol. We don't support the full USB SCSI protocol, but only a sub-protocol of the spec that happens to handle most devices, but unfortunately not all. Changing type to enhancement.

[stippi]

Ah, you could attach the output of "listusb -v" to this ticket while the camera is attached, to confirm my suspicion. It should contain the protocol the camera announces support for.

[mmlr]

It's quite possible that the camera is in PTP mode as well. You can usually switch them between PTP and mass storage mode, in which mass storage would work like an external drive.

[alban]

output from listusb -v with camera connected.

[alban]

I checked the mode; it is in "normal mode" with the other mode being "PTP".

[alban]

output from listusb -v with camera connected.

[alban]

output from listusb -v with camera connected.

[mmlr]

Looks like a vendor specific mass-storage sub-protocol. That kind of sucks of course, as there's not much we can do about it. If it works with a standard transparent SCSI protocol it could be added to a quirks list so it is still detected using the normal mass storage driver. If it actually uses vendor specific stuff then the only option you'll have is to use PTP mode and then use a PTP capable downloader.

[siarzhuk]

Replying to mmlr:

Looks like a vendor specific mass-storage sub-protocol. That kind of sucks of course, as there's not much we can do about it. If it works with a standard transparent SCSI protocol it could be added to a quirks list so it is still detected using the normal mass storage driver.

You are right, old BeOS usb_scsi module has special quirks for this model:

​http://dev.haiku-os.org/browser/haiku/trunk/src/add-ons/kernel/busses/scsi/usb/usb_scsi.devices

17	# Sony DSC series of digital cameras.
21	# Those devices report subclass (command set) as 0xff
22	#   but work with transparent SCSI command set
24	vendor 0x054c {
25	  device 0x0010 {
26	    commandset SCSI
27	    protocol CB
28	  }
29	}

But anyway it is using CBI protocol, that AFAIK is still not supported. :-(