From owner-freebsd-isp Mon Nov 25 11:32:52 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA03142 for isp-outgoing; Mon, 25 Nov 1996 11:32:52 -0800 (PST) Received: from brasil.moneng.mei.com (brasil.moneng.mei.com [151.186.109.160]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id LAA03107 for ; Mon, 25 Nov 1996 11:32:45 -0800 (PST) Received: (from jgreco@localhost) by brasil.moneng.mei.com (8.7.Beta.1/8.7.Beta.1) id NAA15349; Mon, 25 Nov 1996 13:31:40 -0600 From: Joe Greco Message-Id: <199611251931.NAA15349@brasil.moneng.mei.com> Subject: Re: Newsserver running NCR815 cards To: mikael@Hugo.pp.se Date: Mon, 25 Nov 1996 13:31:39 -0600 (CST) Cc: isp@freebsd.org In-Reply-To: <199611251845.TAA14581@nic.dataphone.se> from "Mikael Hugo" at Nov 22, 96 10:08:21 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > 6: Spending a couple extra bucks for better drives will fix problem and > > also get you tagged queueing if you usr NCR controllers. Better fix. > > My drives are fast and reliable - They dont work with NCR under FreeBSD. But the question is WHY? > The drives are 3 GB DEC Drives (aka Micropolis OEM), so I would rather buy > AHA2940s than tossing out 12 of these drives :):) Well, sure, but it would be nice to see if there isn't something that could be done to fix the problem. But first it needs to be determined.. If it is buggy drive firmware, that would bother me, and I would suspect I was getting less out of the drives than I might be. In which case, I would be hammering on DEC/Micropolis's door for a firmware fix. If it is a buggy NCR driver, that would also bother me, and probably also the author of the driver. :-) If it is buggy drive firmware that can not get fixed, that is the worst situation, because then you may be stuck with 12 less than optimal drives, but maybe FreeBSD can be made to work (with reduced efficiency) even so. ... JG