From owner-freebsd-stable Tue Aug 22 9:28: 4 2000 Delivered-To: freebsd-stable@freebsd.org Received: from wyattearp.stanford.edu (wyattearp.Stanford.EDU [171.66.63.23]) by hub.freebsd.org (Postfix) with ESMTP id 4F80937B43E for ; Tue, 22 Aug 2000 09:28:00 -0700 (PDT) Received: (from richw@localhost) by wyattearp.stanford.edu (8.9.3/8.9.3) id JAA06732; Tue, 22 Aug 2000 09:27:00 -0700 (PDT) (envelope-from richw) Date: Tue, 22 Aug 2000 09:27:00 -0700 (PDT) From: Rich Wales X-Sender: richw@wyattearp.stanford.edu To: freebsd-stable@freebsd.org Subject: Re: ATA66 cable being ignored? Message-ID: <200008221604690.richw@wyattearp.stanford.edu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Steve Coles wrote: > "ad1: ATA-4 disk at ata0 as slave" > Are you sure the Maxtor is UDMA-66? Isn't "ATA-4" UDMA-33? Very good point. In fact, this Maxtor disk is at least a year old -- truly ancient by modern standards :-} -- so I'm pretty sure it's not UDMA66. As I recall, the interface cable that originally came in the box with this particular drive was an older, 40-wire cable. So, until such time as I can rearrange my hardware -- either by upgrad- ing the old Maxtor to a newer drive, or else by freeing up a spot for the older drive on the secondary ATA controller -- I guess I'll just have to endure slower disk throughput. I suppose I'll somehow manage to survive. :-} This brings up another question, though. Is there any way to redo the kernel's device probe output so it doesn't try to blame the cable in cases like this? For example, if an ATA controller has two devices, and one is ATA-5 (or better?) but the other is not, then ata-dma.c could say something like "can't do UDMA66 with fast/slow device mix". Rich Wales richw@webcom.com http://www.webcom.com/richw/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message