From owner-freebsd-questions@FreeBSD.ORG Tue Mar 22 14:59:42 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 2669E16A4CE for ; Tue, 22 Mar 2005 14:59:42 +0000 (GMT) Received: from smtp11.wanadoo.fr (smtp11.wanadoo.fr [193.252.22.31]) by mx1.FreeBSD.org (Postfix) with ESMTP id 70EDD43D1F for ; Tue, 22 Mar 2005 14:59:41 +0000 (GMT) (envelope-from atkielski.anthony@wanadoo.fr) Received: from me-wanadoo.net (unknown [127.0.0.1]) by mwinf1108.wanadoo.fr (SMTP Server) with ESMTP id 9EA891C000A3 for ; Tue, 22 Mar 2005 15:59:40 +0100 (CET) Received: from pix.atkielski.com (ASt-Lambert-111-2-1-3.w81-50.abo.wanadoo.fr [81.50.80.3]) by mwinf1108.wanadoo.fr (SMTP Server) with ESMTP id 74A491C0009E for ; Tue, 22 Mar 2005 15:59:40 +0100 (CET) X-ME-UUID: 20050322145940477.74A491C0009E@mwinf1108.wanadoo.fr Date: Tue, 22 Mar 2005 15:59:40 +0100 From: Anthony Atkielski X-Priority: 3 (Normal) Message-ID: <621018420.20050322155940@wanadoo.fr> To: freebsd-questions@freebsd.org In-Reply-To: <1190.209.134.164.137.1111495981.squirrel@209.134.164.137> References: <20050321095647.R83831@makeworld.com> <1907678552.20050322101315@wanadoo.fr> <1190.209.134.164.137.1111495981.squirrel@209.134.164.137> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: Re: Anthony's drive issues.Re: ssh password delay X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: freebsd-questions@freebsd.org List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Mar 2005 14:59:42 -0000 Jerry Bell writes: > 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. No doubt. > 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. If someone wants me to test a different driver on the machine, I can do that; it's a test machine. I have all the source on the machine and can rebuild stuff. > Alternatively, you can try linux. They tend to support all sorts of crazy > hardware versions. Mandrake Linux wouldn't even install. There's a second problem with this machine: I can't get it to boot from disk. It booted fine under NT, but it won't boot FreeBSD on its own, nor was it willing to boot Mandrake Linux. Strangely, the little boot program that I installed with boot0cfg (I think) does boot up, but when I try to choose the FreeBSD slice to boot into FreeBSD, the machine just stalls. The only way I can boot right now is from diskette. I enter the loader after waiting 10 minutes for the diskette boot to proceed, then I change the current device, unload the kernel, and boot again, and the machine instantly boots from the hard disk and comes up. Now if I could just get the machine to do that on its own ... -- Anthony