Re: can't get to ATA133 (Addendum to previous post)
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 dont know if there are other devices on the cable than the disks, as the most usual culprit here is an ATAPI device that doesn't like UDMA. So, Soeren Mr Promise Schmidt, any ideas? Do you need more info, experiments? Len To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: can't get to ATA133 (Addendum to previous post)
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 dont have a dmesg from the system I dont know if there are other devices on the cable than the disks, as the most usual culprit here is an ATAPI device that doesn't like UDMA. So, Soeren Mr Promise Schmidt, any ideas? Get me the complete dmesg from that system so I have a picture of what you've got there... Do you need more info, experiments? You could try to install a 5-current system there, that should not show this problem. -Søren To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: ATA RAID Suggestions / can't get to ATA133
It seems Len Conrad wrote: False alert! On a hint from Soeren Schmidt, we looked at the Promise ATA cables. The 1U box integrator had reversed the cable, controller-end to disk, and disk-end to controller. With great difficulty, due to the cable routing having the middle ATA connector falling right on a too-small feedthrough hole (could explain why the integrator reversed the cable in the first place. it's a reversible flat cable after all!!), we got the cable connected controller-end to controller, and disk-end to disk and dmesg now shows; ar0: 39083MB ATA SPAN array [4982/255/63] status: READY subdisks: 0 READY ad4: 39083MB Maxtor 6Y040L0 [79408/16/63] at ata2-master UDMA133 ar1: 39083MB ATA SPAN array [4982/255/63] status: READY subdisks: 0 READY ad6: 39083MB Maxtor 6Y040L0 [79408/16/63] at ata3-master UDMA133 Thanks Soeren!! Glad to be of help :) let me know if other problems show up! -Søren To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: can't get to ATA133
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] status: READY subdisks: 0 READY ad6: 39083MB Maxtor 6Y040L0 [79408/16/63] at ata3-master UDMA33 Anybody know why TX sees only 33? 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. Generally speaking, buying your own cables is better than using the ones that came with the controller anyway, as those are usually el-cheapos, even with the most expensive controllers. One unreported point we later verified was in the TX2000 on-board setup util, Show Drive Status shows both drives as mode U6 (is ATA133). Len To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: can't get to ATA133
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. Generally speaking, buying your own cables is better than using the ones that came with the controller anyway, as those are usually el-cheapos, even with the most expensive controllers. One unreported point we later verified was in the TX2000 on-board setup util, Show Drive Status shows both drives as mode U6 (is ATA133). Won't matter to ata(4), if it doesn't like your cables, it will force your drives down to UDMA2 at boot time. It could be that the cables still have abit more noise than the driver is willing to tolerate. A new set of cables won't cost you more than $5 each, try replacing the cables first. The 80-conductor cables that came with my sister's motherboard and with my offboard ATA controller (CMD 649 variant) were both 80-conductor cables by the manufacturors' claims, but ata(4) was not interested. Will -- Willie Viljoen Freelance IT Consultant 214 Paul Kruger Avenue, Universitas Bloemfontein 9321 South Africa +27 51 522 15 60 +27 51 522 44 36 (after hours) +27 82 404 03 27 (mobile) [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: can't get to ATA133 (Addendum to previous post)
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 standard as it would prefer. Try getting 80-conductor cables from a third party. Generally speaking, buying your own cables is better than using the ones that came with the controller anyway, as those are usually el-cheapos, even with the most expensive controllers. One unreported point we later verified was in the TX2000 on-board setup util, Show Drive Status shows both drives as mode U6 (is ATA133). Won't matter to ata(4), if it doesn't like your cables, it will force your drives down to UDMA2 at boot time. It could be that the cables still have abit more noise than the driver is willing to tolerate. A new set of cables won't cost you more than $5 each, try replacing the cables first. The 80-conductor cables that came with my sister's motherboard and with my offboard ATA controller (CMD 649 variant) were both 80-conductor cables by the manufacturors' claims, but ata(4) was not interested. 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 try: atacontrol mode ata4 udma6 --- atacontrol mode ata6 udma6 --- Also, you might want to look at the length of the cables. According to the Ultra-ATA (UDMA) standards, an 80-conductor cable must be no longer than 30cm, or about 12. Cables of longer length begin to build up too much noise, even for the double-conductor design to combat. While Promise's BIOS and their own drivers (as seen on Windows) might tolerate these noise levels, I'm very sure ata(4) will not. Will -- Willie Viljoen Freelance IT Consultant 214 Paul Kruger Avenue, Universitas Bloemfontein 9321 South Africa +27 51 522 15 60 +27 51 522 44 36 (after hours) +27 82 404 03 27 (mobile) [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: can't get to ATA133 (Addendum to previous post)
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 try: atacontrol mode ata4 udma6 --- atacontrol mode ata6 udma6 --- mx# atacontrol mode ata2 udma6 --- Master = UDMA33 Slave = ??? mx# atacontrol mode ata3 udma6 --- Master = UDMA33 Slave = ??? Also, you might want to look at the length of the cables. According to the Ultra-ATA (UDMA) standards, an 80-conductor cable must be no longer than 30cm, or about 12. Cables of longer length begin to build up too much noise, even for the double-conductor design to combat. While Promise's BIOS and their own drivers (as seen on Windows) might tolerate these noise levels, I'm very sure ata(4) will not. I've already thought of that and the guy on site says the Promise cables are 18 inches. Len To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: can't get to ATA133 (Addendum to previous post)
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 of trouble. To do this, you can try: atacontrol mode ata4 udma6 --- atacontrol mode ata6 udma6 --- That wont change anything at all... Also, you might want to look at the length of the cables. According to the Ultra-ATA (UDMA) standards, an 80-conductor cable must be no longer than 30cm, or about 12. Cables of longer length begin to build up too much noise, even for the double-conductor design to combat. While Promise's BIOS and their own drivers (as seen on Windows) might tolerate these noise levels, I'm very sure ata(4) will not. ATA cables for UDMA 2 can be up to 45cm long according to spec. 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 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: can't get to ATA133 (Addendum to previous post)
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 driver, so he's probably more correct than my techie. My mistake :) Søren, what else could be causing this? On bootup, Len's system complains: ad4: DMA limited to UDMA33, non-ATA66 cable or device ad6: DMA limited to UDMA33, non-ATA66 cable or device Yet the controller's BIOS is satisfied with the cables, and they are within the length boundaries as you have correctly pointed out. Any ideas? Will -- Willie Viljoen Freelance IT Consultant 214 Paul Kruger Avenue, Universitas Bloemfontein 9321 South Africa +27 51 522 15 60 +27 51 522 44 36 (after hours) +27 82 404 03 27 (mobile) [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: can't get to ATA133 (Addendum to previous post)
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 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 :) Søren, what else could be causing this? On bootup, Len's system complains: 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 dont know if there are other devices on the cable than the disks, as the most usual culprit here is an ATAPI device that doesn't like UDMA. -Søren To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: can't get to ATA133 (Addendum to previous post)
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 reading some manufacturor's own version of the specs, we just checked the official specs and you are right :) Søren, what else could be causing this? On bootup, Len's system complains: 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 dont know if there are other devices on the cable than the disks, as the most usual culprit here is an ATAPI device that doesn't like UDMA. Len, post dmesg? :) -- Willie Viljoen Freelance IT Consultant 214 Paul Kruger Avenue, Universitas Bloemfontein 9321 South Africa +27 51 522 15 60 +27 51 522 44 36 (after hours) +27 82 404 03 27 (mobile) [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: can't get to ATA133 (Addendum to previous post)
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 PROTECTED]:/usr/obj/usr/src/sys/GENERIC Timecounter i8254 frequency 1193182 Hz CPU: Pentium 4 (1716.95-MHz 686-class CPU) Origin = GenuineIntel Id = 0xf13 Stepping = 3 Features=0x3febfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,b28,AC C real memory = 1065287680 (1040320K bytes) avail memory = 1031696384 (1007516K bytes) Preloaded elf kernel kernel at 0xc050f000. Pentium Pro MTRR support enabled md0: Malloc disk Using $PIR table, 8 entries at 0xc00fded0 npx0: math processor on motherboard npx0: INT 16 interface pcib0: Host to PCI bridge on motherboard pci0: PCI bus on pcib0 pci0: Intel model 2562 VGA-compatible display device at 2.0 irq 5 pcib1: Intel 82801BA/BAM (ICH2) Hub to PCI bridge at device 30.0 on pci0 pci1: PCI bus on pcib1 atapci0: Promise TX2 ATA133 controller port 0xa000-0xa00f,0x9c00-0x9c03,0x9800-0x9807,0x9400-0x9403,0x9000-0x9007 mem 0xed00-0xed00fff f irq 11 at device 0.0 on pci1 ata2: at 0x9000 on atapci0 ata3: at 0x9800 on atapci0 rl0: RealTek 8139 10/100BaseTX port 0xa400-0xa4ff mem 0xed01-0xed0100ff irq 10 at device 4.0 on pci1 rl0: Ethernet address: 00:04:61:44:cf:0a miibus0: MII bus on rl0 rlphy0: RealTek internal media interface on miibus0 rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto isab0: PCI to ISA bridge (vendor=8086 device=24c0) at device 31.0 on pci0 isa0: ISA bus on isab0 atapci1: Intel ICH4 ATA100 controller port 0xf000-0xf00f,0-0x3,0-0x7,0-0x3,0-0x7 irq 0 at device 31.1 on pci0 ata0: at 0x1f0 irq 14 on atapci1 ata1: at 0x170 irq 15 on atapci1 pci0: unknown card (vendor=0x8086, dev=0x24c3) at 31.3 irq 7 pci0: unknown card (vendor=0x8086, dev=0x24c5) at 31.5 irq 7 orm0: Option ROMs at iomem 0xc-0xcafff,0xcc000-0xd57ff on isa0 fdc0: NEC 72065B or clone at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: 1440-KB 3.5 drive on fdc0 drive 0 atkbdc0: Keyboard controller (i8042) at port 0x60,0x64 on isa0 atkbd0: AT Keyboard flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 psm0: PS/2 Mouse irq 12 on atkbdc0 psm0: model IntelliMouse, device ID 3 vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0 sc0: System console at flags 0x100 on isa0 sc0: VGA 16 virtual consoles, flags=0x300 sio0: configured irq 4 not in bitmap of probed irqs 0 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 8250 sio1: configured irq 3 not in bitmap of probed irqs 0 ppc0: parallel port not found. 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] status: READY subdisks: 0 READY ad6: 39083MB Maxtor 6Y040L0 [79408/16/63] at ata3-master UDMA33 acd0: CDROM QSI CD-ROM SCR-242 at ata0-master PIO4 Mounting root from ufs:/dev/ar0s1a ad4: DMA limited to UDMA33, non-ATA66 cable or device ad4: DMA limited to UDMA33, non-ATA66 cable or device ad4: DMA limited to UDMA33, non-ATA66 cable or device ad4: DMA limited to UDMA33, non-ATA66 cable or device ad6: DMA limited to UDMA33, non-ATA66 cable or device To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
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: 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] status: READY subdisks: 0 READY ad6: 39083MB Maxtor 6Y040L0 [79408/16/63] at ata3-master UDMA33 Anybody know why TX sees only 33? Len To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: can't get to ATA133
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, 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] status: READY subdisks: 0 READY ad6: 39083MB Maxtor 6Y040L0 [79408/16/63] at ata3-master UDMA33 Anybody know why TX sees only 33? 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. Generally speaking, buying your own cables is better than using the ones that came with the controller anyway, as those are usually el-cheapos, even with the most expensive controllers. Will -- Willie Viljoen Freelance IT Consultant 214 Paul Kruger Avenue, Universitas Bloemfontein 9321 South Africa +27 51 522 15 60 +27 51 522 44 36 (after hours) +27 82 404 03 27 (mobile) [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
RE: can't get to ATA133
(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: 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] status: READY subdisks: 0 READY ad6: 39083MB Maxtor 6Y040L0 [79408/16/63] at ata3-master UDMA33 Anybody know why TX sees only 33? Seems that you are running 40 conductor IDE cables. In order to get anything higher than UDMA33, you will need to have an 80 conductor cable. These cables run dual conductors to help reduce noise generated on the cable itself. Len To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
RE: can't get to ATA133
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 Slave = ??? mx# atacontrol mode 3 Master = UDMA33 Slave = ??? Len To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
