ad4: DMA limited to UDMA33, non-ATA66 cable or device
ad6: DMA limited to UDMA33, non-ATA66 cable or device
This is because the cblid bit in the disks indicate that the disk doesn't
see the right cable (or rather the right signals it tests for).
Since I dont have a dmesg from the system I
It seems Len Conrad wrote:
ad4: DMA limited to UDMA33, non-ATA66 cable or device
ad6: DMA limited to UDMA33, non-ATA66 cable or device
This is because the cblid bit in the disks indicate that the disk doesn't
see the right cable (or rather the right signals it tests for).
Since I
ad4: DMA limited to UDMA33, non-ATA66 cable or device
ad6: DMA limited to UDMA33, non-ATA66 cable or device
ar0: 39083MB ATA SPAN array [4982/255/63] status: READY subdisks:
0 READY ad4: 39083MB Maxtor 6Y040L0 [79408/16/63] at ata2-master
UDMA33 ar1: 39083MB ATA SPAN array [4982/255/63]
On Thursday 27 February 2003 10:31, someone, possibly Len Conrad, typed:
The ata driver is quite strict on standards implementation. It could be
that the promise cables may not comply as strictly with the standard as
it would prefer. Try getting 80-conductor cables from a third party.
On Thursday 27 February 2003 10:43, someone, possibly Willie Viljoen, typed:
On Thursday 27 February 2003 10:31, someone, possibly Len Conrad, typed:
The ata driver is quite strict on standards implementation. It could
be that the promise cables may not comply as strictly with the
There are two things you might want to look at. First it trying to set the
modes manually after boot. This is not recommended, and I would not do it
unless on a read only file system, if setting the higher mode fails, or
fails partially, you might be in for a world of trouble. To do this, you
can
It seems Len Conrad wrote:
There are two things you might want to look at. First it trying to set the
modes manually after boot. This is not recommended, and I would not do it
unless on a read only file system, if setting the higher mode fails, or
fails partially, you might be in for a world
On Thursday 27 February 2003 11:08, someone, possibly Soeren Schmidt, typed:
I've already thought of that and the guy on site says the Promise
cables are 18 inches.
Which is just about right...
-Søren
Strange, I was told 30cm emphatically by our local techie, but Søren did
write the
It seems Willie Viljoen wrote:
On Thursday 27 February 2003 11:08, someone, possibly Soeren Schmidt, typed:
I've already thought of that and the guy on site says the Promise
cables are 18 inches.
Which is just about right...
-Søren
Strange, I was told 30cm emphatically by our
On Thursday 27 February 2003 11:30, someone, possibly Soeren Schmidt, typed:
Strange, I was told 30cm emphatically by our local techie, but Søren
did write the driver, so he's probably more correct than my techie. My
mistake
:)
Well, point him at the ATA specs :)
It seems he was
mx# dmesg
Copyright (c) 1992-2002 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights reserved.
FreeBSD 4.7-RELEASE #0: Wed Oct 9 15:08:34 GMT 2002
[EMAIL
On Thursday 27 February 2003 1:01, someone, possibly Len Conrad, typed:
FreeBSD 4.7R
Promise TX2000 with two ATA133 drives as ata masters using the ATA133 IDE
cables that came with the TX2000.
dmesg shows:
ad4: DMA limited to UDMA33, non-ATA66 cable or device
ad6: DMA limited to UDMA33,
(snip)
Subject: can't get to ATA133
FreeBSD 4.7R
Promise TX2000 with two ATA133 drives as ata masters using the ATA133 IDE
cables that came with the TX2000.
dmesg shows:
ad4: DMA limited to UDMA33, non-ATA66 cable or device
ad6: DMA limited to UDMA33, non-ATA66 cable or device
ar0:
Seems that you are running 40 conductor IDE cables.
no, the tx2000 is running the tx2000 ata133 cables.
the tx2000 on-board setup util is reporting mode U6, ata133
it seems that the hardware is actually running ata133 but FreeBSD is seeing
it a udma33.
mx# atacontrol mode 2
Master = UDMA33
14 matches
Mail list logo
