Re: ATA driver feature request

[Chris Dillon]

On Thu, 24 Jan 2002, SXren Schmidt wrote:

  However, the warning message would be slightly reworded like non-ATA66
  compliant cable or second device

 Good point, I'll get something done about this...

Just as a note, it doesn't have to just be the cable or the second
device, it can be either one or both or maybe the controller too. :-)

I don't remember, but I might actually be using an 80-wire cable here
on my box at work (as if it would matter with only an ATA33
controller):

atapci0: Intel PIIX4 ATA33 controller port 0xf000-0xf00f at device
7.1 on pci0
ad0: 19541MB Maxtor 52049U4 [39703/16/63] at ata0-master UDMA33
ata0-slave: DMA limited to UDMA33, non-ATA66 compliant cable
ad1: 6149MB Maxtor 90650U2 [12495/16/63] at ata0-slave UDMA33
acd0: CDROM ATAPI CDROM at ata1-master using PIO4
afd0: 96MB IOMEGA ZIP 100 ATAPI [32/64/96] at ata1-slave using PIO0

ata0-master is actually the device that is capable of ATA66 (actually
ATA100 I think).  I think ata0-slave is only capable of ATA33, but I
could be wrong.

My system at home with an ATA100-capable drive on a PIIX4 controller
doesn't mention anything about a non-compliant cable (though it really
is an 80-wire cable, maybe that's why), but it is also the only thing
on the bus (I use SCSI for everything else):

atapci0: Intel PIIX4 ATA33 controller port 0xffa0-0xffaf at device
7.1 on pci0
ad0: 39083MB Maxtor 5T040H4 [79408/16/63] at ata0-master UDMA33

--
 Chris Dillon - [EMAIL PROTECTED] - [EMAIL PROTECTED]
 FreeBSD: The fastest and most stable server OS on the planet
 - Available for IA32 (Intel x86) and Alpha architectures
 - IA64, PowerPC, UltraSPARC, and ARM architectures under development
 - http://www.freebsd.org



To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-stable in the body of the message

Re: ATA driver feature request

[jacks]

Yes, I always see this same thing if I place an older CD-ROM slave on the
same cable. It drops to UDMA33. If I remove the CD-ROM, then the systme
sees the cable fine as ATA100. If I then put my new CD-ROM on the cable, it
likes that too.

At 12:04 AM 1.22.2002 -0600, [EMAIL PROTECTED] wrote:

On Sun, 20 Jan 2002, Dmitry Valdov wrote:

 On Sun, 20 Jan 2002, Bill Moran wrote:
   FreeBSD limits both
   drives on the bus because there is 'non-ATA66 compliant cable'.
 
  Are you sure you have an 80 conductor cable and that it isn't too long?

 Yes. When I disconnect secondary (non ATA-66/100 compliant) drive from this
 cable, FreeBSD use ATA-100 on primary.


FWIW, I'm seeing the exact same symptom.   I just added to 80gb Western
Digital (IDE) drives to the system.   I used the 80-wire cables that came
with the drives, and I see the following messages:

atapci0: VIA 82C686 ATA66 controller port 0xd000-0xd00f at device 7.1 on
pci0
ata0: at 0x1f0 irq 14 on atapci0
ata1: at 0x170 irq 15 on atapci0
. . .
ad0: 19458MB ST320420A [39535/16/63] at ata0-master UDMA66
ad1: 76319MB WDC WD800BB-40BSA0 [155061/16/63] at ata0-slave UDMA66
ata1-master: DMA limited to UDMA33, non-ATA66 compliant cable
ad2: 76319MB WDC WD800BB-40BSA0 [155061/16/63] at ata1-master UDMA33
ad3: 2503MB FUJITSU MPA3026ATU [5086/16/63] at ata1-slave UDMA33

They are the exact same drives using the exact same cable.  My controller
only supports UDMA66, not 100...   but the reason that the 2nd controller
seems to print out non-ATA66 compiant cable appears to simply be that
ad3 is only ATA33 capable.

Just thought I'd pipe up, since the subject came up :)



To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-stable in the body of the message



Best regards,
Jack L. Stone,
Server Admin

===
Sage-American 
http://www.sage-american.com
[EMAIL PROTECTED]

My center is giving way, my right is in retreat;
situation excellent! I shall attack!
===

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-stable in the body of the message