From owner-freebsd-questions Fri Jul 21 13:46:41 2000 Delivered-To: freebsd-questions@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 8FCB837BF1A for ; Fri, 21 Jul 2000 13:46:38 -0700 (PDT) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id e6LKkYg28411; Fri, 21 Jul 2000 13:46:34 -0700 (PDT) Date: Fri, 21 Jul 2000 13:46:34 -0700 From: Alfred Perlstein To: legg@iastate.edu Cc: freebsd-questions@FreeBSD.ORG Subject: Re: your mail Message-ID: <20000721134634.C13979@fw.wintelcom.net> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: ; from legg@iastate.edu on Fri, Jul 21, 2000 at 03:17:41PM -0500 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * legg@iastate.edu [000721 13:18] wrote: > Hello, > > I am trying to install FreeBSD. When I am setting up the hardware > immediately after inserting the mfsroot disk, I see my network card is not > on the list given to me. It is a 3Com 905-TX. > > I searched at 3Com and found that they have drivers for a wide range of > operating systems, Red Hat, Caldera, TurboLinux and SuSe, but not FreeBSD. > > Is the driver that works in those other operating systems able to operate > in FreeBSD and if so, how do I add it to the list of hardware that I > mentioned about earlier? If this driver doesn't work, does this mean that > I am better off using a different Linux/Unix that is compatible with the > driver? Are you sure it's not being detected? If you hit "scroll lock" after all the white messages come up after finishing the first round of hardware config you should be able to use the uparrow to view what FreeBSD probed. -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message