Re: Serial ATA support in FreeBSD
It seems Matthew Emmerton wrote: Received no responses the first time, so am trying again. - I am in the process of building a new system and was looking at using the new Seagate Barracuda Serial ATA drives. Does FreeBSD 4.x, or 5.x support SATA? Mark Jacobs If FreeBSD can detect the SATA controller, then I imagine it would support it just fine, since the same command set is used on the software side. Currently the only (known) support SATA controllers are the Highpoint 15x0 series (they are just old PATA chips with PATA - SATA converters). Are you offering to donate a SATA controller / SATA-equipped motherboard to Soren to make this a reality? g That would be nice indeed, I do have Promise's SATA products, but I'm looking for all other SATA controllers and *especially* SATA disks... -Søren To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Serial ATA support in FreeBSD
It seems Mark Jacobs wrote: Currently the only (known) support SATA controllers are the Highpoint 15x0 series (they are just old PATA chips with PATA - SATA converters). Are you offering to donate a SATA controller / SATA-equipped motherboard to Soren to make this a reality? g That would be nice indeed, I do have Promise's SATA products, but I'm looking for all other SATA controllers and *especially* SATA disks... -Søren The motherboard I am looking to get is the Asus NForce2 A7N8X deluxe. The SATA connector supported by the SiliconImage SATALINK chipset Sil31122 That is not supported, and most likely wont be until I get one here in the lab, a PCI card with one would do just fine :) -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)
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 (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)
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
