From owner-freebsd-stable Tue Jan 22 6:49:35 2002 Delivered-To: freebsd-stable@freebsd.org Received: from sage-american.com (sage-american.com [216.122.141.44]) by hub.freebsd.org (Postfix) with ESMTP id 7918837B400; Tue, 22 Jan 2002 06:49:31 -0800 (PST) Received: from SAGEONE (adsl-64-219-20-214.dsl.crchtx.swbell.net [64.219.20.214]) by sage-american.com (8.9.3/8.9.3) with SMTP id IAA01608; Tue, 22 Jan 2002 08:49:14 -0600 (CST) Message-Id: <3.0.5.32.20020122084912.01831ca0@mail.sage-american.com> X-Sender: jacks@mail.sage-american.com X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.5 (32) Date: Tue, 22 Jan 2002 08:49:12 -0600 To: scotty@klement.dstorm.net, Dmitry Valdov From: jacks@sage-american.com Subject: Re: ATA driver feature request Cc: Bill Moran , , In-Reply-To: <20020121235548.D40648-100000@grungy.dstorm.net> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG 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, scotty@klement.dstorm.net 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: 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 [39535/16/63] at ata0-master UDMA66 >ad1: 76319MB [155061/16/63] at ata0-slave UDMA66 >ata1-master: DMA limited to UDMA33, non-ATA66 compliant cable >ad2: 76319MB [155061/16/63] at ata1-master UDMA33 >ad3: 2503MB [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 majordomo@FreeBSD.org >with "unsubscribe freebsd-stable" in the body of the message > > Best regards, Jack L. Stone, Server Admin =================================================== Sage-American http://www.sage-american.com jacks@sage-american.com "My center is giving way, my right is in retreat; ....situation excellent! ....I shall attack!" =================================================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message