UDMA(66) drive coming up as UDMA(33)?

UDMA(66) drive coming up as UDMA(33)?

[David St.Clair]

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

"ide2: BM-DMA at 0xbc00-0xbc07, BIOS settings: hde:pio" <-- PIO? 

and

"hde: 27067824 sectors (13859 MB) w/371KiB Cache, CHS=26853/16/63,
UDMA(33)" <--- UDMA(33)? shouldn't it be UDMA(66)?

Any ideas what might be wrong? Possible bug?


Hardware:
Abit BE6 Motherboard with HPT366 controller
Quantum Fireball KA 13.6 UDMA/66 HD
80 pin connector
Linux Partition is on /dev/hde2

Software:
Redhat 7.0
Kernel 2.4.3 (non-modified)

Use multi-mode by default = Y
CMD640 chipset bugfix/support = Y
RZ1000 chipset bugfix/support = Y
Generic PCI IDE chipset support = Y
Shareing PCI IDE interrupts support = Y
Generic PCI bus-master DMA support = Y
Use PCI DMA by default when available = Y
HPT366 chipset support = Y
Intel PIIXn chipsets support = Y
PIIXn Tuning support = Y
IGNORE word93 Validation BITS = Y



My Log:

Uniform Multi-Platform E-IDE driver Revision: 6.31
ide: Assuming 33MHz system bus speed for PIO modes; override with
idebus=xx
automount[415]: starting automounter version 3.1.6, path = /misc,
maptype = file, mapname = /etc/auto.misc
PIIX4: IDE controller on PCI bus 00 dev 39
PIIX4: chipset revision 1
PIIX4: not 100%% native mode: will probe irqs later
    ide0: BM-DMA at 0xf000-0xf007, BIOS settings: hda:pio, hdb:pio
    ide1: BM-DMA at 0xf008-0xf00f, BIOS settings: hdc:DMA, hdd:pio
HPT366: onboard version of chipset, pin1=1 pin2=2
HPT366: IDE controller on PCI bus 00 dev 98
PCI: Found IRQ 11 for device 00:13.0
PCI: The same IRQ used for device 00:0b.0
PCI: The same IRQ used for device 00:13.1
HPT366: chipset revision 1
HPT366: not 100%% native mode: will probe irqs later
    ide2: BM-DMA at 0xbc00-0xbc07, BIOS settings: hde:pio, hdf:pio
HPT366: IDE controller on PCI bus 00 dev 99
PCI: Found IRQ 11 for device 00:13.1
PCI: The same IRQ used for device 00:0b.0
PCI: The same IRQ used for device 00:13.0
HPT366: chipset revision 1
Initializing random number generator:  succeeded
HPT366: not 100%% native mode: will probe irqs later
     ide3: BM-DMA at 0xc800-0xc807, BIOS settings: hdg:pio, hdh:pio
hdc: Pioneer DVD-ROM ATAPIModel DVD-113 0114, ATAPI CD/DVD-ROM drive
hdd: IOMEGA ZIP 100 ATAPI, ATAPI FLOPPY drive
hde: QUANTUM FIREBALLP KA13.6, ATA DISK drive
ide1 at 0x170-0x177,0x376 on irq 15
ide2 at 0xb400-0xb407,0xb802 on irq 11
hde: 27067824 sectors (13859 MB) w/371KiB Cache, CHS=26853/16/63,
UDMA(33)
hdc: ATAPI DVD-ROM drive, 512kB Cache, UDMA(33)
Uniform CD-ROM driver Revision: 3.12
hdd: 98304kB, 96/64/32 CHS, 4096 kBps, 512 sector size, 2941 rpm



Thank you,

David St.Clair
dstclair@cs.wcu.edu

Re: UDMA(66) drive coming up as UDMA(33)?

[Wilfried Weissmann]

"David St.Clair" wrote:
> 
> 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

I think that should be UDMA 5 for 66? As far as I can remember UDMA4 is 33MHz with S.M.A.R.T. which
add some reporting functionality. But I might be wrong...

> 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
> 
> "ide2: BM-DMA at 0xbc00-0xbc07, BIOS settings: hde:pio" <-- PIO?
> 
> and
> 
> "hde: 27067824 sectors (13859 MB) w/371KiB Cache, CHS=26853/16/63,
> UDMA(33)" <--- UDMA(33)? shouldn't it be UDMA(66)?

I got (kernel 2.2.18):

HPT370: IDE controller on PCI bus 00 dev 98
HPT370: chipset revision 3
HPT370: not 100% native mode: will probe irqs later
    ide0: BM-DMA at 0xe800-0xe807, BIOS settings: hda:DMA, hdb:pio
    ide1: BM-DMA at 0xe808-0xe80f, BIOS settings: hdc:DMA, hdd:pio

hda and hdc are my hd's. My mainboard is a Abit KT7-RAID.

> 
> Any ideas what might be wrong? Possible bug?

I would set the UDMA5 for the HDs in the HPT bios.

good luck,
Wilfried

Re: UDMA(66) drive coming up as UDMA(33)?

[Nicholas Knight]

----- Original Message -----
From: "Wilfried Weissmann" <Wilfried.Weissmann@gmx.at>
To: <linux-kernel@vger.kernel.org>
Sent: Sunday, April 08, 2001 10:44 AM
Subject: Re: UDMA(66) drive coming up as UDMA(33)?


> "David St.Clair" wrote:
> >
> > 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
>
> I think that should be UDMA 5 for 66? As far as I can remember UDMA4 is
33MHz with S.M.A.R.T. which
> add some reporting functionality. But I might be wrong...

66 is 4, 100 is 5,

Re: UDMA(66) drive coming up as UDMA(33)?

[Nicholas Knight]

----- 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

Re: UDMA(66) drive coming up as UDMA(33)?

[David St.Clair]

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

Re: UDMA(66) drive coming up as UDMA(33)?

[Reverend EvvL X]

I'm currently running a BP6 with a on board HPT366 and a 7200rpm
drive. From what I've seen with my setup at home that 19.51 MB/s
sounds just about right for a hdparm test. When the manual is
refering to the "UDMA 4 66 Mb/s" their talking about the maximum
burst rate for the ATA bus not the max transfer rate, someone
please correct me if I'm worng.

-Eric Olinger

----- Original Message -----
From: "David St.Clair" <dstclair@cs.wcu.edu>
To: <linux-kernel@vger.kernel.org>
Sent: Monday, April 09, 2001 8:41 PM
Subject: Re: UDMA(66) drive coming up as UDMA(33)?


> 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
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/