From: William Park <parkw@better.net>
To: Brian Dushaw <dushaw@munk.apl.washington.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: VIA vt82c686b and UDMA(100)
Date: Thu, 22 Mar 2001 01:05:07 -0500 [thread overview]
Message-ID: <20010322010507.A3170@better.net> (raw)
In-Reply-To: <Pine.LNX.4.30.0103212029540.3646-100000@munk.apl.washington.edu>
In-Reply-To: <Pine.LNX.4.30.0103212029540.3646-100000@munk.apl.washington.edu>; from dushaw@munk.apl.washington.edu on Wed, Mar 21, 2001 at 08:40:21PM -0800
On Wed, Mar 21, 2001 at 08:40:21PM -0800, Brian Dushaw wrote:
> Dear Linux Kernel Wisemen,
> I have been following the discussion of the VIA vt82c686b chipset
> and the troubles people have had in getting UDMA(100) to work. This
> is to report that I have now tried the 2.4.2-ac20 kernel and the
> 2.2.18 kernel with Andre's patch (dated March 20) and neither of
> them get the disk speed up to where it ought to be. hdparm -t reports
> back 11 MB/s or so for either kernel.
> VIA82CXXX enabled, and I also tried the ide0=ata66 flag, in desparation.
> At boot up both kernels report the disk as UDMA(100) - everything
> seems to be peachy keen, but for the sluggish disk performance.
>
> Merely a report from the front lines,
Try 'hdparm -d1 -t', and see what you get.
:wq --William Park, Open Geometry Consulting, Linux/Python, 8 CPUs.
next prev parent reply other threads:[~2001-03-22 6:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-22 4:40 VIA vt82c686b and UDMA(100) Brian Dushaw
2001-03-22 6:05 ` William Park [this message]
2001-03-22 10:23 ` Brian Dushaw
2001-03-22 10:25 ` Brian Dushaw
2001-03-22 13:29 ` Nils Philippsen
2001-03-22 12:30 ` Brian Dushaw
-- strict thread matches above, loose matches on Subject: below --
2001-03-23 14:22 David Balazic
2001-03-24 1:31 ` Brian Dushaw
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=20010322010507.A3170@better.net \
--to=parkw@better.net \
--cc=dushaw@munk.apl.washington.edu \
--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.