public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: jbradford@dial.pipex.com
To: gen-lists@blueyonder.co.uk (Mark C)
Cc: linux-kernel@vger.kernel.org
Subject: Re: Problems accessing USB Mass Storage
Date: Tue, 17 Sep 2002 21:12:14 +0100 (BST)	[thread overview]
Message-ID: <200209172012.g8HKCFrG004537@darkstar.example.net> (raw)
In-Reply-To: <1032291993.1276.12.camel@stimpy.angelnet.internal> from "Mark C" at Sep 17, 2002 08:46:31 PM

> > This is a bit like what we (JE, David Brownell, and I) saw at
> > the USB plugfest in 1999.  We had a camera device that we
> > couldn't mount as a filesystem, but we could dd it.
> > When we did that and studied the dd-ed file, we could see a
> > FAT filesystem beginning after the first <N> blocks (but more than
> > 25 sectors IIRC -- more like after 50-100 KB, or maybe even more).
> 
> Sorry to sound a bit bewildered, but would be the next best thing for me
> to do on this?, 
> I have also been advised by Jonathan Corbet 
> to use dd to copy your card to disk with an offset of 25

Have you tried reading from a different card?  The common opinion seems to be that the actual data starts some way in to the card, and as you get an input/output error when you try to access the card from the begining, it could be that there is a genuine media error, that is not showing up when you use drivers from another OS, that do not attempt to read those first few blocks, because they 'know' where the filesystem begins.

Just an idea, anyway.

John.

  reply	other threads:[~2002-09-17 19:59 UTC|newest]

Thread overview: 29+ 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 [this message]
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
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 11:25 Mark C
2002-09-17 15:18 ` Greg KH
2002-09-17 17:37   ` Thomas Dodd
2002-09-17 17:46     ` Greg KH
2002-09-17 18:06       ` Richard B. Johnson
2002-09-17 20:09       ` Thomas Dodd
2002-09-17 21:01         ` Mark C
2002-09-17 21:43       ` Rogier Wolff
2002-09-17 22:04         ` Thomas Dodd
2002-09-17 22:21           ` Patrick Mansfield
2002-09-17 22:51             ` Mark C
     [not found]             ` <mailman.1032306001.9987.linux-kernel2news@redhat.com>
2002-09-18  1:37               ` Pete Zaitcev
2002-09-18  6:01           ` Rogier Wolff

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=200209172012.g8HKCFrG004537@darkstar.example.net \
    --to=jbradford@dial.pipex.com \
    --cc=gen-lists@blueyonder.co.uk \
    --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