Date: Mon, 21 Aug 2000 16:58:56 -0700 From: David Burton <odyseus2000@earthlink.net> To: Rich Wales <richw@webcom.com>, freebsd-stable@freebsd.org Subject: Re: ATA66 cable being ignored? Message-ID: <20000821165856.A79469@slick.earthlink.net> In-Reply-To: <200008211670886.richw@wyattearp.stanford.edu>; from richw@webcom.com on Mon, Aug 21, 2000 at 10:03:28AM -0700 References: <200008211670886.richw@wyattearp.stanford.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
Did the cable ever work with UDMA66? As far as possibilities with the cable, it could be that when it was manufactured that one of the lines didnt get cleanly cut, I forget which one it is but it allows it to sense the cable is for UDMA 66/100. You should be able to see where a machine has stamped a small cut in one of the wires. Or if the cable is 24 inches you could trying using a 18 inch cable, if possible. I believe 24 inches is the supposed max length, so using the shortest cable possible could make a difference. On Mon, Aug 21, 2000 at 10:03:28AM -0700, Rich Wales wrote: > My new Dell OptiPlex GX300 (running 4.1-RELEASE) came with an 80-wire > ATA cable. I added a second drive and am using this cable for both > drives. However, the kernel fails to recognize the cable and is limit- > ing DMA speed accordingly. Any ideas? > > See below for the relevant portion of the "boot -v" output. I note the > "cblid=0" value -- leading me to wonder if the problem might possibly > be with the integrated ATA controller on the motherboard not sensing or > reporting the cable properly. This is an 800-MHz Pentium III system, > though, so I find it a bit hard to believe that it isn't UDMA66-capable. > > BTW, in the line which claims I have a non-ATA66 compliant cable, I > believe the preferred spelling is "limited", with just one T (not two). > > Rich Wales richw@webcom.com http://www.webcom.com/richw/ > > ======================================================================== > > . . . > atapci0: <Intel ICH ATA66 controller> port 0xffa0-0xffaf at device 31.1 on pci0 > ata0: iobase=0x01f0 altiobase=0x03f6 bmaddr=0xffa0 > ata0: mask=03 status0=50 status1=50 > ata0: mask=03 status0=50 status1=50 > ata0: devices = 0x3 > ata0: at 0x1f0 irq 14 on atapci0 > . . . > ata0-master: DMA limitted to UDMA33, non-ATA66 compliant cable > ata0-master: success setting up UDMA2 mode on ICH chip > ad0: <IBM-DTLA-307015/TX2DA50C> ATA-5 disk at ata0 as master > ad0: 14324MB (29336832 sectors), 29104 cyls, 16 heads, 63 S/T, 512 B/S > ad0: 16 secs/int, 1 depth queue, UDMA33 > ad0: piomode=4 dmamode=2 udmamode=4 cblid=0 > Creating DISK ad0 > Creating DISK wd0 > ata0-slave: success setting up UDMA2 mode on ICH chip > ad1: <Maxtor 91008D7/WAS82739> ATA-4 disk at ata0 as slave > ad1: 9617MB (19696320 sectors), 19540 cyls, 16 heads, 63 S/T, 512 B/S > ad1: 16 secs/int, 1 depth queue, UDMA33 > ad1: piomode=4 dmamode=2 udmamode=2 cblid=0 > Creating DISK ad1 > Creating DISK wd1 > > ======================================================================== > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > 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?20000821165856.A79469>