mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: John August <johna@babel.apana.org.au>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.4.18 Fuji 1300 usb-storage problem
Date: Fri, 26 Jul 2002 16:59:43 +1000	[thread overview]
Message-ID: <20020726165943.B552@babel.apana.org.au> (raw)
In-Reply-To: <20020725162521.GA10675@sgi.com>; from nstraz@sgi.com on Thu, Jul 25, 2002 at 11:25:21AM -0500

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


  reply	other threads:[~2002-07-26  7:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-25  0:29 John August
2002-07-25 16:25 ` Nathan Straz
2002-07-26  6:59   ` John August [this message]
2002-07-26 19:13     ` Nathan Straz

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20020726165943.B552@babel.apana.org.au \
    --to=johna@babel.apana.org.au \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®