public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mark Lord <lkml@rtr.ca>
To: Grant Coady <gcoady.lk@gmail.com>
Cc: linux-kernel@vger.kernel.org, alan@lxorguk.ukuu.org.uk
Subject: Re: Query: No IDE DMA for IBM 365X with PIIX chipset?
Date: Sun, 28 May 2006 08:06:52 -0400	[thread overview]
Message-ID: <4479925C.2070909@rtr.ca> (raw)
In-Reply-To: <j9bi729h2u4dcn9da7na3t1d8ckk477d9b@4ax.com>

Grant Coady wrote:
> Hi there,
> 
> Have an old Thinkpad 365X laptop that 'hdparm -i' tells me is 
> running mdma2 but it refuses to set dma mode.  2.6.16.18 also 
> refuses to set dma.
...

No luck with "hdparm -d1 /dev/hda" ??

> ...
> ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
> PIIXa: IDE controller at PCI slot 00:01.0
> PIIXa: chipset revision 2
> PIIXa: not 100% native mode: will probe irqs later
> PIIXa: neither IDE port enabled (BIOS)
> hda: TOSHIBA MK6014MAP, ATA DISK drive
> ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
> hda: attached ide-disk driver.
> hda: host protected area => 1
> hda: 11733120 sectors (6007 MB), CHS=776/240/63
> Partition check:
>  hda: hda1 hda2 hda3 hda4 < hda5 hda6 hda7 hda8 >
...

Mmm.. there's a curious line: "PIIXa: neither IDE port enabled (BIOS)".
Can you enable DMA in the BIOS?  The IDE driver seems to be unwilling
to set up the bus-master DMA (BMDMA) portion of the chip unless
it was already initialized by the BIOS (paranoia, I suppose, or maybe a bug).

Cheers

  reply	other threads:[~2006-05-28 12:06 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-28  5:29 Query: No IDE DMA for IBM 365X with PIIX chipset? Grant Coady
2006-05-28 12:06 ` Mark Lord [this message]
2006-05-28 22:57   ` Grant Coady
2006-06-01 13:50 ` Alan Cox
2006-06-01 15:55   ` Ondrej Zary
2006-06-02  7:17     ` Grant Coady
2006-06-01 17:22   ` Mark Lord
2006-06-01 18:52     ` Alan Cox
2006-06-02 14:57       ` Ondrej Zary

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=4479925C.2070909@rtr.ca \
    --to=lkml@rtr.ca \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=gcoady.lk@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