From owner-freebsd-stable Mon Aug 21 17:23:19 2000 Delivered-To: freebsd-stable@freebsd.org Received: from freeway.dcfinc.com (cx74889-a.phnx3.az.home.com [24.1.193.157]) by hub.freebsd.org (Postfix) with ESMTP id 04DB137B424 for ; Mon, 21 Aug 2000 17:23:17 -0700 (PDT) Received: (from chad@localhost) by freeway.dcfinc.com (8.8.8/8.8.8) id RAA25598; Mon, 21 Aug 2000 17:23:09 -0700 (MST) (envelope-from chad) From: "Chad R. Larson" Message-Id: <200008220023.RAA25598@freeway.dcfinc.com> Subject: Re: ATA66 cable being ignored? In-Reply-To: <39A1C549.5557E62E@glue.umd.edu> from Brandon Fosdick at "Aug 21, 0 08:11:53 pm" To: bfoz@glue.umd.edu (Brandon Fosdick) Date: Mon, 21 Aug 2000 17:23:09 -0700 (MST) Cc: richw@webcom.com, freebsd-stable@FreeBSD.ORG Reply-To: chad@DCFinc.com Organization: DCF, Inc. X-O/S: FreeBSD 2.2.8-STABLE X-Unexpected: The Spanish Inquisition X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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. -crl -- Chad R. Larson (CRL15) 602-953-1392 Brother, can you paradigm? chad@dcfinc.com chad@larsons.org larson1@home.net DCF, Inc. - 14623 North 49th Place, Scottsdale, Arizona 85254-2207 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message