2.4.18 Fuji 1300 usb-storage problem

2.4.18 Fuji 1300 usb-storage problem

[John August]

I'm trying to access the memory on a Fuji Fine Pix 1300. It works fine
on a 2.4.2-2 kernel, with the output to dmesg :

hub.c: USB new device connect on bus1/2, assigned device number 4
scsi0 : SCSI emulation for USB Mass Storage devices
Vendor: FUJIFILM  Model: USB-DRIVEUNIT     Rev: 1.00
Type:   Direct-Access                      ANSI SCSI revision: 02
Attached scsi removable disk sda at scsi0, channel 0, id 0, lun 0
SCSI device sda: 128000 512-byte hdwr sectors (66 MB)
sda: Write Protect is off
sda: sda1
WARNING: USB Mass Storage data integrity not assured
USB Mass Storage device found at 4

With the 2.4.18 kernel, I get :
hub.c: USB new device connect on bus1/2, assigned device number 3
scsi0 : SCSI emulation for USB Mass Storage devices
Vendor: Fujifilm  Model: FinePix 1400Zoom  Rev: 1000
Type:   Direct-Access                      ANSI SCSI revision: 02
Attached scsi removable disk sda at scsi0, channel 0, id 0, lun 0
SCSI device sda: 128000 512-byte hdwr sectors (66 MB)
sda: Write Protect is off

And this is as far as it gets. I think I've once seen "unable to access
partition table". 

Note that it does not get as far as identifying the partition table,
and the Model is indicated as FinePix 1400Zoom, when its in fact a 1300,
and previously it was "USB-DRIVEUNIT" as the model.

As far as I can tell, all the needed modules are loaded and the problem
is not with kernel configuration. In any case, you would think accessing
the partition table is independent of filesystems and stuff.

Is this a dinky die bug ? Any thoughts for workarounds ?

I'm not on the list, please cc replies to me.

Thanks,

-- 
John August

Re: 2.4.18 Fuji 1300 usb-storage problem

[Nathan Straz]

On Thu, Jul 25, 2002 at 10:29:55AM +1000, John August wrote:
> Note that it does not get as far as identifying the partition table,
> and the Model is indicated as FinePix 1400Zoom, when its in fact a 1300,
> and previously it was "USB-DRIVEUNIT" as the model.

Maybe the 1300 doesn't have as broken a USB implementation as the 1400
does.  In linux/drivers/usb/storage/unusual_devs.h there is an entry for
the 1400.

UNUSUAL_DEV(  0x04cb, 0x0100, 0x0000, 0x2210,
                "Fujifilm",
                "FinePix 1400Zoom",
                US_SC_8070, US_PR_CBI, NULL, US_FL_FIX_INQUIRY),

The third and fourth numbers are the range of product identifiers to
consider unusual.  0x0000 - 0x2210 is probably a little broad.  Try
changing that to 0x2210 - 0x2210 and see if your 1300 works again.

-- 
Nate Straz                                              nstraz@sgi.com
sgi, inc                                           http://www.sgi.com/
Linux Test Project                                  http://ltp.sf.net/

Re: 2.4.18 Fuji 1300 usb-storage problem

[John August]

On Thu, Jul 25, 2002 at 11:25:21AM -0500, Nathan Straz wrote:
> On Thu, Jul 25, 2002 at 10:29:55AM +1000, John August wrote:
> > Note that it does not get as far as identifying the partition table,
> > and the Model is indicated as FinePix 1400Zoom, when its in fact a 1300,
> > and previously it was "USB-DRIVEUNIT" as the model.
> 
> Maybe the 1300 doesn't have as broken a USB implementation as the 1400
> does.  In linux/drivers/usb/storage/unusual_devs.h there is an entry for
> the 1400.

Thanks Nathan,

I've changed things as suggested ...

Now, it does not even have the lines 

SCSI device sda: 128000 512-byte hdwr sectors (66 MB)
sda: Write Protect is off

Let alone viewing the partitions.

You have :

hub.c: USB new device connect on bus1/2, assigned device number 3
scsi0 : SCSI emulation for USB Mass Storage devices
Vendor: FUJIFILM  Model: USB-DRIVEUNIT     Rev: 1.00
Type:   Direct-Access                      ANSI SCSI revision: 02
Attached scsi removable disk sda at scsi0, channel 0, id 0, lun 0

As the total output.

It appears the original "USB-DRIVEUNIT" code in 2.4.2-2 was OK, or there's
some external problem in indentifying the sda device characteristics.

-- 
John August

Re: 2.4.18 Fuji 1300 usb-storage problem

[Nathan Straz]

On Fri, Jul 26, 2002 at 04:59:43PM +1000, John August wrote:
> On Thu, Jul 25, 2002 at 11:25:21AM -0500, Nathan Straz wrote:
> > On Thu, Jul 25, 2002 at 10:29:55AM +1000, John August wrote:
> > > Note that it does not get as far as identifying the partition table,
> > > and the Model is indicated as FinePix 1400Zoom, when its in fact a 1300,
> > > and previously it was "USB-DRIVEUNIT" as the model.
> > 
> > Maybe the 1300 doesn't have as broken a USB implementation as the 1400
> > does.  In linux/drivers/usb/storage/unusual_devs.h there is an entry for
> > the 1400.
> 
> You have :
> 
> hub.c: USB new device connect on bus1/2, assigned device number 3
> scsi0 : SCSI emulation for USB Mass Storage devices
> Vendor: FUJIFILM  Model: USB-DRIVEUNIT     Rev: 1.00
> Type:   Direct-Access                      ANSI SCSI revision: 02
> Attached scsi removable disk sda at scsi0, channel 0, id 0, lun 0
> 
> As the total output.
> 
> It appears the original "USB-DRIVEUNIT" code in 2.4.2-2 was OK, or there's
> some external problem in indentifying the sda device characteristics.

Hmm, are you sure you have SCSI disk support loaded (sd_mod)?

Since that didn't fix it, I'd suggest taking this to the linux-usb-devel
list.  You'll probably want to turn on the usb-storage debugging output
to get some more detail.  I think they would appreciate seeing all of
the kernel messages that result from plugging in the camera.  

Good luck, 
-- 
Nate Straz                                              nstraz@sgi.com
sgi, inc                                           http://www.sgi.com/
Linux Test Project                                  http://ltp.sf.net/