public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Prashant Viswanathan <vprashant@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Compactflash (Sandisk 512) hangs on access
Date: Thu, 3 Feb 2005 00:23:53 -0800	[thread overview]
Message-ID: <2ec2c15a05020300235355d997@mail.gmail.com> (raw)
In-Reply-To: <2ec2c15a050128221279a11585@mail.gmail.com>

On Fri, 28 Jan 2005 22:12:04 -0800, Prashant Viswanathan
<vprashant@gmail.com> wrote:
> > > I have been trying unsuccessfully over the last 2 weeks to get
> > > compactflash working on my Linux system based on mini-ITX (Via CL
> > > motherboard, pentium compatible).
> > >
> > > I use a CF->IDE adapter to access it just like a IDE hard disk. My
> > > compactflash is Sandisk SDCFH-512. Linux can detect it. I can even
> > > mount it and do a fdisk on it. However, the moment I try to do
> > > anything substantial like copy multiple files or copy 1000 blocks
> > > using dd, I lose access to it. Linux loses access to it totally. I
> > > can't even do a fdisk on it. I get an error like "Unable to open
> > > /dev/hdc".
> 
> On Thu, 27 Jan 2005 22:07:35 +0100, Willy Tarreau <willy@w.ods.org> wrote:
> > Have you checked that the power connector really provides 5V to the
> > IDE-CF adapter ? I had the exact same behaviour 5 years ago with a power
> > wire cut. Signal lines were powerful enough to bring power to the cheap
> > flash (16 MB), I could even read it, most times. The kernel almost always
> > booted from it, and when it turned to mount the ext2 fs R/W, it hanged. I
> > finally partially destroyed it this way, and it got several defects which
> > could not be cleaned with a simple write or format.
> >
> > Other than that, I have lots of CF cards on IDE adapters (some on motherboard,
> > some hand-made, some bought to serious makers), and never ran into such
> > problems since.
> >
> > Willy
> 
> The power connector is fine.
> 
> I also disabled DMA (some suggestion on this newsgroup to a similar
> error) and now I can't turn it back on.
> 
> <snip>
> everest root # hdparm -d1 /dev/hdc
> 
> /dev/hdc:
> setting using_dma to 1 (on)
> 


Finally figured out the problem (or at least worked around it).
Everything seems to work perfectly after I switched to an older 40
conductor IDE cable!  Before that I was using the newer 80 conductor
IDE cable. I sitll dont understand why the newer ( and apparently
better) cables are problematic. Higher speeds causing race conditions perhaps?

      reply	other threads:[~2005-02-03  8:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-27 18:35 Compactflash (Sandisk 512) hangs on access Prashant Viswanathan
2005-01-27 21:07 ` Willy Tarreau
2005-01-29  6:12   ` Prashant Viswanathan
2005-02-03  8:23     ` Prashant Viswanathan [this message]

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=2ec2c15a05020300235355d997@mail.gmail.com \
    --to=vprashant@gmail.com \
    --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