From owner-freebsd-questions Wed Dec 10 08:18:47 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id IAA24397 for questions-outgoing; Wed, 10 Dec 1997 08:18:47 -0800 (PST) (envelope-from owner-freebsd-questions) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id IAA24385; Wed, 10 Dec 1997 08:18:35 -0800 (PST) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id LAA00857; Wed, 10 Dec 1997 11:18:19 -0500 (EST) (envelope-from toor) From: "John S. Dyson" Message-Id: <199712101618.LAA00857@dyson.iquest.net> Subject: Re: Can't get FreeBSD 2.2.5 to recognize controller card In-Reply-To: <199712101029.CAA06916@lsbsdi1.lightspeed.net> from Lightning Firestormer at "Dec 10, 97 02:29:05 am" To: lightningfire@lightspeed.net (Lightning Firestormer) Date: Wed, 10 Dec 1997 11:18:18 -0500 (EST) Cc: dyson@FreeBSD.ORG, questions@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-questions@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Lightning Firestormer said: > > Subject: Re: Can't get FreeBSD 2.2.5 to recognize controller card > > To: lightningfire@lightspeed.net (Lightning Firestormer) > > Date: Wed, 10 Dec 1997 05:20:40 -0500 (EST) > > Cc: questions@FreeBSD.ORG > > From: "John S. Dyson" > > Reply-to: dyson@FreeBSD.ORG > > > Lightning Firestormer said: > > > Greetings. > > > > > > I downloaded FreeBSD 2.2.5 the other day, and when I went to attempt > > > to install it I found that it won't detect my PCI-based controller > > > card. The unit is a Promise Technologies Ultra33 (the card has been > > > on the market since May). Is there anything I can do to get FreeBSD > > > to recognize it? > > > > > FreeBSD-current works with it. > > What's the word on how long until the support that FreeBSD-current > has for the card becomes part of FreeBSD-stable? I've enough > trouble with configuration on this heavily-customized system, and I > try to avoid the bleeding edge like the plaque (this system is messy > enough to troubleshoot as-is). > Unfortunately, it will likely be when -current becomes -stable. :-(. The problem has to do with the size of the changes, and hopefully, -stable is feature frozen. Every time we try to do something massive in -stable, we break things terribly. This is NOT meant as arrogance or anything, but the problems abound when we try to do things like that. Our regression testing isn't adequate, and so we tend to like to keep -stable "golden." One bad thing, there are times that we do make the mistake of adding something "necessary" and that is usually a heap of trouble. -- John dyson@freebsd.org jdyson@nc.com