From: John August <johna@babel.apana.org.au>
To: linux-kernel@vger.kernel.org
Subject: 2.4.18 Fuji 1300 usb-storage problem
Date: Thu, 25 Jul 2002 10:29:55 +1000 [thread overview]
Message-ID: <20020725102955.A700@babel.apana.org.au> (raw)
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
next reply other threads:[~2002-07-25 0:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-25 0:29 John August [this message]
2002-07-25 16:25 ` Nathan Straz
2002-07-26 6:59 ` John August
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=20020725102955.A700@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®