All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jeffrey W. Baker" <jwbaker@acm.org>
To: "Mudama, Eric" <eric_mudama@maxtor.com>, linux-kernel@vger.kernel.org
Subject: RE: HD DMA disabled in 2.4.21-rc2, works fine in 2.4.20
Date: 19 May 2003 13:04:06 -0700	[thread overview]
Message-ID: <1053374646.10240.5.camel@heat> (raw)
In-Reply-To: <785F348679A4D5119A0C009027DE33C102E0D3AB@mcoexc04.mlm.maxtor.com>

On Mon, 2003-05-19 at 12:56, Mudama, Eric wrote:
> # CONFIG_BLK_DEV_IDEDMA_FORCED is not set
> 
> I think that is the offending line?
> 
> can you enable DMA transfer modes on the drive using hdparm?

Why should force be enabled?  Forced sounds like a last resort.  If you
read this thread you will see that hdparm isn't working.  It returns
EPERM.

I was using Via IDE chipset and, yes, I had configured the kernel for
VIA support.  That's why it worked in 2.4.20.  But it stopped working in
2.4.21-rc.

Meanwhile, I have switched to 2.4.21-rc-ac, and dumped the hardware in
favor of Intel i865, and DMA is working again.

-jwb


  reply	other threads:[~2003-05-19 19:51 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-19 19:56 HD DMA disabled in 2.4.21-rc2, works fine in 2.4.20 Mudama, Eric
2003-05-19 20:04 ` Jeffrey W. Baker [this message]
2003-05-19 19:45   ` Alan Cox
2003-05-19 22:29     ` Tomas Szepe
2003-05-19 23:00       ` Jeffrey W. Baker
2003-05-20  1:25 ` lars hofhansl
  -- strict thread matches above, loose matches on Subject: below --
2003-05-24  2:45 Lars
2003-05-22  7:06 Lars
2003-05-19 23:12 Mudama, Eric
2003-05-17  3:56 Jeffrey Baker
2003-05-18  7:59 ` Tomas Szepe
2003-05-19  3:03   ` Lars
2003-05-15  7:56 Lars

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=1053374646.10240.5.camel@heat \
    --to=jwbaker@acm.org \
    --cc=eric_mudama@maxtor.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.