From owner-freebsd-questions Thu Jan 15 18:42:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA13726 for questions-outgoing; Thu, 15 Jan 1998 18:42:20 -0800 (PST) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from fly.HiWAAY.net (root@fly.HiWAAY.net [208.147.154.56]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA13660 for ; Thu, 15 Jan 1998 18:41:55 -0800 (PST) (envelope-from dkelly@nospam.hiwaay.net) Received: from nospam.hiwaay.net (tnt2-80.HiWAAY.net [208.147.148.80]) by fly.HiWAAY.net (8.8.8/8.8.6) with ESMTP id UAA27369; Thu, 15 Jan 1998 20:41:48 -0600 (CST) Received: from localhost (localhost [127.0.0.1]) by nospam.hiwaay.net (8.8.8/8.8.4) with ESMTP id UAA11731; Thu, 15 Jan 1998 20:24:47 -0600 (CST) Message-Id: <199801160224.UAA11731@nospam.hiwaay.net> X-Mailer: exmh version 2.0.1 12/23/97 To: sysop@inlandnet.com cc: questions@FreeBSD.ORG From: David Kelly Subject: Re: Diamond MM Fireport 20/40 In-reply-to: Message from sysop@inlandnet.com of "Wed, 14 Jan 1998 16:28:41 PST." <1.5.4.16.19980115002841.3ce7afcc@inlandnet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 15 Jan 1998 20:24:47 -0600 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk > Hi - > > The Diamond MM Fireport 20 does not seem to work with FreeBSD. It is based > on the NCR (SymBIOS) 53C875 chip and seems to have the generic BIOS but does > not appear to be recognized by FreeBSD. [...] > If the Diamond MM Fireport boards do not work, it may be noteworthy in the > FAQs or compatible hardware list. My purchase of the Fireport 20 was based > on the idea that it was supported because it uses the 53C875 chip. FYI: I > installed from the Walnut Creek CDROM distribution of FreeBSD 2.2.2. The Fireport 40 uses a slightly different chip ID/revision ('875j) than FreeBSD 2.2.2 knew about. FreeBSD 2.2.5 should work perfectly. There was a patch posted in the list archives that you could use as a quick fix. Looking at /usr/src/sys/pci/ncr.c on my recent 2.2.5 I see: #define NCR_875_ID (0x000f1000ul) #define NCR_875_ID2 (0x008f1000ul) If you simply change your NCR_875_ID to the NCR_875_ID2 value shown, then rebuild your kernel, you'll be in business. I think. Your Mileage May Vary. Perform At Your Own Risk. Etc. -- David Kelly N4HHE, dkelly@nospam.hiwaay.net ===================================================================== The human mind ordinarily operates at only ten percent of its capacity -- the rest is overhead for the operating system.