From: "David St.Clair" <dstclair@cs.wcu.edu>
To: linux-kernel@vger.kernel.org
Subject: Re: UDMA(66) drive coming up as UDMA(33)?
Date: Mon, 09 Apr 2001 23:41:59 -0400 [thread overview]
Message-ID: <986874119.4770.0.camel@bugeyes.wcu.edu> (raw)
In-Reply-To: <008401c0c167$73f14d80$8d19b018@c779218a>
In-Reply-To: <986664971.1224.4.camel@bugeyes.wcu.edu> <008401c0c167$73f14d80$8d19b018@c779218a>
Well, I'm positive what I have is an 80pin cable. I may try a diffrent
one. I guess I could benchmark the drive in windows and see how it
compares to linux. (Both are on the same drive). The HPT366 chip is
integrated on the BE6 motherboard.
The manual says PIO 4 mode should get about 16.6 Mb/s, UDMA 2 33 Mb/s,
and UDMA 4 66 Mb/s. Does anyone know what the correct numbers I should
be seeing in linux? (/w hdparm -t)
Again, my hardware is:
Quantum Fireball KA 13.6 7200 rpm HD
Abit BE6 /w integrated HPT366 chip
Kernel 2.4.3
Thanks,
David St.Clair
On 09 Apr 2001 19:39:23 -0700, Nicholas Knight wrote:
> ----- Original Message -----
> From: "David St.Clair" <dstclair@cs.wcu.edu>
> To: <linux-kernel@vger.kernel.org>
> Sent: Saturday, April 07, 2001 10:36 AM
> Subject: UDMA(66) drive coming up as UDMA(33)?
>
>
> > I'm trying to get my hard drive to use UDMA/66. I'm thinking the cable
> > is not being detected. When the HPT366 bios is set to UDMA 4; using
> > hdparm -t, I get a transfer rate of 19.51 MB/s. When the HPT366 bios is
> > set to PIO 4 the transfer rate is the same. Is this normal for a UDMA/66
> > drive? What makes me think something is wrong is that the log says
>
> The speed is dependant on the drive, and has absilutely nothing to do with
> the UDMA mode, beyond that the controller and cable need to be able to
> support at least the speed the drive is recieving/outputting data in order
> for the drive to operate at full speed, 19.51MB/sec sounds right for a good
> 7200RPM HDD
>
> >
> > "ide2: BM-DMA at 0xbc00-0xbc07, BIOS settings: hde:pio" <-- PIO?
>
> hmm this is a little odd but I don't know the ins and outs of the HPT366
> controller
>
> >
> > and
> >
> > "hde: 27067824 sectors (13859 MB) w/371KiB Cache, CHS=26853/16/63,
> > UDMA(33)" <--- UDMA(33)? shouldn't it be UDMA(66)?
> >
>
> this certainly sounds like it's not detecting the cable properly... have you
> tried replacing it with a new cable that you KNOW supports ATA/66?
>
>
> > HPT366: onboard version of chipset, pin1=1 pin2=2
>
> is the HPT366 controller in an add-in card or built into the motherboard? it
> looks like it's builtin from this line
>
> the bottom line here is that the cable probably isn't being detected
> properly for some reason, I doubt if it's a kernel problem, the cable is
> probably "bad", try picking up a new ATA/66+ cable and putting it in there
> this shouldn't actually cause you problems unless you're often transferring
> more than 33MB/sec though, which isn't likely on a desktop system, ATA/66
> and ATA/100 are *generaly* overkill for most desktop systems, even for many
> powerusers
next prev parent reply other threads:[~2001-04-10 3:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-07 17:36 David St.Clair
2001-04-08 17:44 ` Wilfried Weissmann
2001-04-10 2:25 ` Nicholas Knight
2001-04-10 2:39 ` Nicholas Knight
2001-04-10 3:41 ` David St.Clair [this message]
2001-04-10 15:46 ` Reverend EvvL X
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=986874119.4770.0.camel@bugeyes.wcu.edu \
--to=dstclair@cs.wcu.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 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®