public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Thomas Dodd <ted@cypress.com>
To: Mark C <gen-lists@blueyonder.co.uk>
Cc: linux-usb-users <linux-usb-users@lists.sourceforge.net>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [Linux-usb-users] Re: Problems accessing USB Mass Storage
Date: Tue, 17 Sep 2002 16:40:34 -0500	[thread overview]
Message-ID: <3D87A152.50800@cypress.com> (raw)
In-Reply-To: 1032297193.1276.23.camel@stimpy.angelnet.internal



Mark C wrote:
> [root@stimpy mark]# dd if=/dev/sda of=tmp/tmp.img skip=50 \
> bs=1k                                                                                                         dd: reading `/dev/sda': Input/output error

That's correct.

> Then the output of dmesg:
> 
> SCSI device (ioctl) reports ILLEGAL REQUEST.
> SCSI device sda: 16384 512-byte hdwr sectors (8 MB)
> sda: test WP failed, assume Write Enabled
>  sda: I/O error: dev 08:00, sector 0
>  I/O error: dev 08:00, sector 0
>  unable to read partition table
>  I/O error: dev 08:00, sector 96

That's what I expected. I didn't help.


Sector 96 is a little odd.  50 1K blocks
should be sector 99. (counting starts at zero)

I wonder why 96 is accessed...

This is really starting to look like it's
*NOT* really a Mass Storage Class device,
just claiming to be. (black list time?)

I noticed the windows driver setup several
other interfaces, like audio and VfW (video).

Best sugestion for now is buy 1) a memory card,
2) a card reader that works there are several.

It probably doesn't use the internal memory if a card
is loaded, but you'd have to read the manul/test to
find out. 8M isn't much room for pics at 1280x1024
any way :)


	-Thomas


  reply	other threads:[~2002-09-17 21:36 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-17 18:15 Problems accessing USB Mass Storage Jonathan Corbet
2002-09-17 18:22 ` Randy.Dunlap
2002-09-17 19:46   ` Mark C
2002-09-17 20:12     ` jbradford
2002-09-17 21:21     ` Jonathan Corbet
2002-09-17 19:50   ` Thomas Dodd
2002-09-17 19:58     ` Matthew Dharm
2002-09-17 20:13       ` Thomas Dodd
2002-09-17 21:13         ` [Linux-usb-users] " Mark C
2002-09-17 21:40           ` Thomas Dodd [this message]
2002-09-17 21:51             ` Mark C
2002-09-17 21:58           ` Rogier Wolff
2002-09-17 22:17             ` Thomas Dodd
2002-09-17 22:23               ` Randy.Dunlap
2002-09-18  9:28         ` Andries Brouwer
2002-09-18  9:22 ` Andries Brouwer
  -- strict thread matches above, loose matches on Subject: below --
2002-09-17 22:04 Thomas Dodd
2002-09-17 22:12 ` [Linux-usb-users] " Randy.Dunlap
2002-09-17 22:51 Mark C
2002-09-17 23:09 ` [Linux-usb-users] " Randy.Dunlap
     [not found] <Pine.LNX.4.33L2.0209171627330.14033-100000@dragon.pdx.osdl.net>
2002-09-17 23:46 ` Mark C

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=3D87A152.50800@cypress.com \
    --to=ted@cypress.com \
    --cc=gen-lists@blueyonder.co.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb-users@lists.sourceforge.net \
    /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