From owner-freebsd-current Tue Mar 14 8:33:39 2000 Delivered-To: freebsd-current@freebsd.org Received: from chmls06.mediaone.net (chmls06.mediaone.net [24.128.1.71]) by hub.freebsd.org (Postfix) with ESMTP id 7942F37B750 for ; Tue, 14 Mar 2000 08:33:36 -0800 (PST) (envelope-from bloom@acm.org) Received: from acm.org (reyim.ne.mediaone.net [24.218.251.241]) by chmls06.mediaone.net (8.8.7/8.8.7) with ESMTP id LAA07143; Tue, 14 Mar 2000 11:33:09 -0500 (EST) Message-ID: <38CE69C3.FAD64C50@acm.org> Date: Tue, 14 Mar 2000 11:33:07 -0500 From: Jim Bloom X-Mailer: Mozilla 4.72 [en]C-MOENE (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Soren Schmidt Cc: Thomas Veldhouse , freebsd-current@FreeBSD.ORG Subject: Re: CMD640 and ATA drivers References: <200003141553.QAA83093@freebsd.dk> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG And I have three machines which I was trying to use for testing -current and my firewall. These machines all have either a CMD640 or an RZ100 controller on the motherboard. (They seemed to be popular with the early Pentium machines.) The controllers seem reliable enough to use for extended periods as test machines. If it gets trashed because of a controller bug, I can simply reinstall and only lose the install time. I upgraded my firewall to an old Adaptec SCSI controller, but I don't care about data integrity on the other machines. Unfortunately, none of them are usable at the moment because of various bugs (panics on boot, not probing the hard drive, etc.). Jim Bloom bloom@acm.org Soren Schmidt wrote: > > It worked until the latest newbus changes, I'm looking at it, but havn't > found anything obvious yet. > But seriously you want to get another ATA interface, the CMD640 is > _broken_ and no software can help that, you are playing russian > roulette with your data. Get a promise, abit or siig controller > and use that instead... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message