From owner-freebsd-questions Sat Mar 23 14:49: 3 2002 Delivered-To: freebsd-questions@freebsd.org Received: from nycsmtp2out.rdc-nyc.rr.com (nycsmtp2out.rdc-nyc.rr.com [24.29.99.227]) by hub.freebsd.org (Postfix) with ESMTP id C9D7E37B417 for ; Sat, 23 Mar 2002 14:48:58 -0800 (PST) Received: from scott1.nyc.rr.com (24-168-24-239.nyc.rr.com [24.168.24.239]) by nycsmtp2out.rdc-nyc.rr.com (8.12.1/Road Runner SMTP Server 1.0) with ESMTP id g2NMkjlu027696; Sat, 23 Mar 2002 17:46:46 -0500 (EST) Message-Id: <5.1.0.14.0.20020323174744.00bd33d0@pop-server.nyc.rr.com> X-Sender: scottro@pop-server.nyc.rr.com X-Mailer: QUALCOMM Windows Eudora Version 5.1 Date: Sat, 23 Mar 2002 17:48:47 -0500 To: Collins , bsd-questions From: Scott Subject: Re: NIC fails - dc0: couldn't map ports.memory In-Reply-To: <20020321202219.20661709.erichey2@attbi.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG At 20:22 2002/03/21 -0700, Collins wrote: >I had a functional FreeBSD 4.4 system running on my prior computer >(K6/II 300Mz), but now I've switched to a new computer (P3/800Mz) and I >can't get it to work. > > >Eveything about the FreeBSD install works perfectly, except my NIC card. > The card shows up as an ADMtek Commet rev 17. It is on IRQ 11 (shared >with USB). Linux drives the card with the "tulip" module, and it works >perfectly. I've found that my Netgear FA310TX, which also uses Tulip in Linux, shows up as a dc0 in FreeBSD. Possibly recompiling, adding in dc0 support (in Generic, I think it's about the 3rd or 4th one) HTH Scott Robbins >Collins Richey - Denver Area - WWTLRD? >Gentoo_rc6-15 2.4.17 - xfce + sylpheed + mozilla > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-questions" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message