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