From: Tomas Szepe <szepe@pinerecords.com>
To: Dennis Grant <trog@wincom.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Identifying/activating faster ATAxx modes (WAS kernel config tale of woe)
Date: Tue, 26 Nov 2002 04:49:00 +0100 [thread overview]
Message-ID: <20021126034900.GB29196@louise.pinerecords.com> (raw)
In-Reply-To: <3de2eee3.16fd.0@wincom.net>
> /dev/hda:
>
> Model=Maxtor 6E030L0, FwRev=NAR61590, SerialNo=E106SZLE
> Config={ Fixed }
> RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=57
> BuffType=DualPortCache, BuffSize=2048kB, MaxMultSect=16, MultSect=16
> CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=60058656
> IORDY=on/off, tPIO={min:120,w/IORDY:120}, tDMA={min:120,rec:120}
> PIO modes: pio0 pio1 pio2 pio3 pio4
> DMA modes: mdma0 mdma1 mdma2
> UDMA modes: udma0 udma1 udma2 udma3 udma4 udma5 *udma6
> AdvancedPM=yes: disabled (255) WriteCache=enabled
> Drive conforms to: (null): 1 2 3 4 5 6 7
>
> Output from hdparm -tT
>
> /dev/hda:
> Timing buffer-cache reads: 128 MB in 0.44 seconds =290.91 MB/sec
> Timing buffered disk reads: 64 MB in 8.11 seconds = 7.89 MB/sec
This is weird. Your disk seems to be set up for udma6 (UATA133),
which should provide for transfer rates of at least 40MiB/s.
Could you try a recent -ac kernel? It comes with a significantly
more modern IDE driver that fixes lots of issues with newer chipsets.
ftp://ftp.kernel.org/pub/linux/kernel/people/alan/linux-2.4/2.4.20/patch-2.4.20-rc2-ac3.gz
(apply on top of patch-2.4.20-rc2 found in /pub/linux/kernel/v2.4/testing/)
--
Tomas Szepe <szepe@pinerecords.com>
next prev parent reply other threads:[~2002-11-26 3:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-26 3:31 Dennis Grant
2002-11-26 3:49 ` Tomas Szepe [this message]
2002-11-26 12:13 ` Adrian Bunk
2002-11-26 12:15 ` Tomas Szepe
2002-11-26 12:48 ` Adrian Bunk
2002-11-26 13:05 ` Tomas Szepe
2002-11-26 12:44 ` Adrian Bunk
2002-11-26 12:53 ` Adrian Bunk
2002-11-26 10:53 Christian Guggenberger
2002-11-26 13:36 Dennis Grant
2002-11-26 13:42 Dennis Grant
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=20021126034900.GB29196@louise.pinerecords.com \
--to=szepe@pinerecords.com \
--cc=linux-kernel@vger.kernel.org \
--cc=trog@wincom.net \
/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®