FinePix s5000 camera detection problems (gphoto2)

vexer · 02-17-2004, 01:18 PM

I connect my FinePix s5000 to my usb drive and try to get gtkam and gphoto2 to auto detect my camera and it doesn't find it.

www.gphoto2.com documentation tells me I need usb mass storage. Done. I have that. I compiled the lib with --with-drivers=all. USB works. But I believe the problem is maybe that scsi4 is emulating the mass storage for some reason. Below you will find the output of USBview and of dmesg (reason why I think scsi is doing foul play)

------------------DMESG--------------------

Code:

hub 3-0:1.0: new USB device on port 2, assigned address 9
scsi6 : SCSI emulation for USB Mass Storage devices
  Vendor: FUJIFILM  Model: USB-DRIVEUNIT     Rev: 1.00
  Type:   Direct-Access                      ANSI SCSI revision: 02
WARNING: USB Mass Storage data integrity not assured
USB Mass Storage device found at 9

----------------USBview------------------------------

Code:

USB Mass Storage
Serial Number: Y-558^^^^^031027XFPX0009024438
Speed: 12Mb/s (full)
USB Version:  2.00
Device Class: 00(>ifc )
Device Subclass: 00
Device Protocol: 00
Maximum Default Endpoint Size: 64
Number of Configurations: 1
Vendor Id: 04cb
Product Id: 0130
Revision Number:  1.00

Config Number: 1
	Number of Interfaces: 1
	Attributes: c0
	MaxPower Needed:  50mA

	Interface Number: 0
		Name: usb-storage
		Alternate Number: 0
		Class: 08(stor.) 
		Sub Class: 6
		Protocol: 50
		Number of Endpoints: 2

			Endpoint Address: 81
			Direction: in
			Attribute: 2
			Type: Bulk
			Max Packet Size: 64
			Interval: 0ms

			Endpoint Address: 02
			Direction: out
			Attribute: 2
			Type: Bulk
			Max Packet Size: 64
			Interval: 0ms

vexer · 02-17-2004, 02:07 PM

I've even (just now) removed scsi emulation (which I found built into my kernel) and I still get the same dmesg message as above. (Keep in mind the the scsi dev files changes, scsi0, scsi1, scsi2...)

vexer · 02-18-2004, 01:07 PM

amair · 02-19-2004, 07:22 AM

Quote:

Originally posted by vexer
I've even (just now) removed scsi emulation (which I found built into my kernel) and I still get the same dmesg message as above. (Keep in mind the the scsi dev files changes, scsi0, scsi1, scsi2...)

Hi,

AFAIK you need scsidisk support. You'll have to access your mass-storage device using e.g. /dev/sda if there's no other scsi disk available in you PC. With my mass-storage device I can access (mount) its "partition" with /dev/sda1.

Regards,
Andreas