Date: Mon, 21 Aug 2000 23:50:17 -0400 From: Garance A Drosihn <drosih@rpi.edu> To: chad@DCFinc.com, bfoz@glue.umd.edu (Brandon Fosdick) Cc: richw@webcom.com, freebsd-stable@FreeBSD.ORG Subject: Re: ATA66 cable being ignored? Message-ID: <v04210105b5c7a606ab0d@[128.113.24.47]> In-Reply-To: <200008220023.RAA25598@freeway.dcfinc.com> References: <200008220023.RAA25598@freeway.dcfinc.com>
next in thread | previous in thread | raw e-mail | index | archive | help
At 5:23 PM -0700 8/21/00, Chad R. Larson wrote: >As I recall, Brandon Fosdick wrote: > > Are both drives ATA66? I built a new computer with a K7V > > (integrated ATA66 controller) and when I plugged my old > > ATA33 drive into the same cable (for copying stuff) I > > started getting the same messages. When I took the old > > drive off ATA66 started working again. I guess it can > > only go as fast as the slowest drive on the cable. > >That's documented to be the case. > >In fact, I've also seen it recommended that ATA66 drives >should be on an interface by themselves. In my situation, I have two drives, both of which claim to be ATA66 capable. I have two separate controllers (not just interfaces, but entire controllers). One of the drives was a maxtor, and I have seen claims in other mail that maxtor didn't quite get their ATA66 drives working right. (note: I do not know that for a fact, I'm just saying I've read it). In any case, I could not get the machine to boot up if both drives were on the ATA66 controller, so (as luck would have it) I moved that Maxtor to the ATA33 controller, which is on the motherboard. The harddrive on the ATA66 controller is a 20-gig Seagate drive. The promise controller itself does seem to recognize it as an ATA66 device at bootup, but freebsd claims the cable can't handle it and drops back to ATA33. I'm about 95% sure I *do* have an ATA-66 cable in there, but given the way my machine is setup it would take at least an hour to find out for sure. It's also possible that I have some flags wrong or missing in my kernel config. My machine works well enough that I haven't been motivated to track this down, but if someone else is motivated and they come up with a quick fix then I'd give it a shot... :-) --- Garance Alistair Drosehn = gad@eclipse.acs.rpi.edu Senior Systems Programmer or drosih@rpi.edu Rensselaer Polytechnic Institute To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?v04210105b5c7a606ab0d>