From owner-freebsd-questions@FreeBSD.ORG Tue Mar 22 12:53:02 2005 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A1F1716A4CE for ; Tue, 22 Mar 2005 12:53:02 +0000 (GMT) Received: from stelesys.com (web1.stelesys.com [63.175.100.39]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5CACE43D41 for ; Tue, 22 Mar 2005 12:53:02 +0000 (GMT) (envelope-from jbell@stelesys.com) Received: from [127.0.0.1] (helo=www.stelesys.com) by stelesys.com with esmtpa (Exim 4.44 (FreeBSD)) id 1DDisX-000LAx-Tu for freebsd-questions@freebsd.org; Tue, 22 Mar 2005 07:53:02 -0500 Received: from 209.134.164.137 (SquirrelMail authenticated user jbell@stelesys.com); by www.stelesys.com with HTTP; Tue, 22 Mar 2005 07:53:01 -0500 (EST) Message-ID: <1190.209.134.164.137.1111495981.squirrel@209.134.164.137> In-Reply-To: <1907678552.20050322101315@wanadoo.fr> References: <20050321095647.R83831@makeworld.com> <1907678552.20050322101315@wanadoo.fr> Date: Tue, 22 Mar 2005 07:53:01 -0500 (EST) From: "Jerry Bell" To: freebsd-questions@freebsd.org User-Agent: SquirrelMail/1.4.3a X-Mailer: SquirrelMail/1.4.3a MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal Subject: Re: Anthony's drive issues.Re: ssh password delay X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Mar 2005 12:53:02 -0000 > No, the only way to find the error is to find someone who knows the > FreeBSD code and is competent and willing to discuss the problem, > instead of people who spend their time blowing smoke in order to avoid > admitting that they haven't a ghost of a clue as to what the problem is. You're looking for the reason that your older hardware runs on NT and doesn't run on FreeBSD. Save any real hardware problem, the reason is most certainly pure incompatibility between the hardware and the drivers that are in FreeBSD. When someone goes to write a driver (unless it's provided by the manufacturer, which I don't think is all that common) for a piece of hardware, they have a piece of hardware and some docs on how to interface with it. If the firmware on the board they are using is later than yours, and is incompatible in some slight way that the driver author took advantage of, you see this exact problem. The driver authors ask for people to test the drivers out - but if no one who is willing/ready/able to test is running an older firmware rev, then the testing doesn't extend back to your version and it's not found to be a problem until someone like you comes along and trips over an incompatibility. I've had this very thing happen for several different older raid cards. In every case, I fixed the problem by upgrading the firmware. Alternatively, you can try linux. They tend to support all sorts of crazy hardware versions.