From: Matthias Andree <matthias.andree@gmx.de>
To: Linux-Kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: IDE DMA/VIA woes on SuSE 2.4.19-167
Date: Sat, 8 Mar 2003 00:23:55 +0100 [thread overview]
Message-ID: <20030307232355.GA9267@merlin.emma.line.org> (raw)
In-Reply-To: <20030305024446.GA13870@merlin.emma.line.org>
On Wed, 05 Mar 2003, Matthias Andree wrote:
> Plextor PX-W4824TA 1.03 as hdc (no hdd)
> VIA KT133
>
> 00:07.1 IDE interface: VIA Technologies, Inc. VT82C586B PIPC Bus Master IDE (rev 10) (prog-if 8a [Master SecP PriP])
> Flags: bus master, medium devsel, latency 32
> I/O ports at ffa0 [size=16]
> Capabilities: [c0] Power Management version 2
>
> When I try to enable DMA (hdparm -d1 or hdparm -d1 -X66), hdparm -tT
> chokes, SuSE k_athlon-2.4.19-167. FreeBSD-5 (with atapicam) is fine and
> uses UDMA33.
Now, seems that PIO manages the default hdparm -tT block size, but DMA
doesn't; but the error messages in the kernel ring buffer aren't
specific.
I let go of hdparm -tT, installed Jörg Schilling's sdd and ran sdd
if=/dev/sr1 -onull -t bs=2048 and lo and behold, it passed and read a
data CD with up to 45x. So the remaining problem is that the ATAPI
drives stick to PIO for data reads.
I tried applying Andrew's ide-akpm on top of SuSE's kernel, to find it
crashes on boot on SuSE's hardware scan.
If that's interesting enough, I can try to dig up the crash messages
(I'll have to use a serial console for that though).
prev parent reply other threads:[~2003-03-07 23:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-05 2:44 Matthias Andree
2003-03-05 5:15 ` Meino Christian Cramer
2003-03-05 5:26 ` [2.4.20]: Question about myst. interrupt thingy Meino Christian Cramer
2003-03-07 23:23 ` Matthias Andree [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=20030307232355.GA9267@merlin.emma.line.org \
--to=matthias.andree@gmx.de \
--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
all inboxes | Powered by JetHome®