From owner-freebsd-questions Thu May 31 11:27:37 2001 Delivered-To: freebsd-questions@freebsd.org Received: from tellurian.net (gate.tellurian.net [216.182.1.1]) by hub.freebsd.org (Postfix) with ESMTP id 1305337B424 for ; Thu, 31 May 2001 11:27:32 -0700 (PDT) (envelope-from walt@betan.com) Received: from walt99 (unverified [216.182.56.86]) by tellurian.net (Rockliffe SMTPRA 4.5.4) with ESMTP id for ; Thu, 31 May 2001 14:17:06 -0400 Message-Id: <4.2.2.20010531141555.00b83bb0@pop3.palace.net> X-Sender: walterbetanc@pop3.palace.net X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 Date: Thu, 31 May 2001 14:16:43 -0400 To: freebsd-questions@freebsd.org From: Walter Betancourt Subject: Re: 2 NIC's not working In-Reply-To: <200105311221.AA2687338@stmail.pace.edu> 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 This may not apply to your problem, I am using a Tyan trinity 400 board with freebsd, had an irq conflict with video 11 and nic 11 after much confusion, discovered nic would work in slot 3 or 4 but created conflict in slot 3, no conflict in slot 4. Tyan web site states, "use slot 3 or 4 for nic..." Walt At 12:21 PM 5/31/01 -0400, you wrote: >James, > > There is no internal network, I just tried two nics with the >same result on both. One is an SMC EZ ISA 1660 and the other is a >NETGEAR FA311 PCI card. As of the time of the install, the hard >drive was clean, there were no files on it. -- Jonathan > >----------------------------------------- >Jonathan M. Slivko >Network Admin., DataSyrge Internet Svces. >Server Co-Admin., AsylumNet IRC Networks > >web: http://webpage.pace.edu/js43064n/ >voice: (212) 696-6774 (24 Hours) >----------------------------------------- > > > >---------- Original Message ---------------------------------- >From: "James Lim" >Date: Fri, 1 Jun 2001 00:17:31 +0800 > > >Hi, > > > > What are your entries in ur /etc/rc.conf? > >and wat would be the device name of the 2 nics? > >and which NIC would be for internal network and > >which would be for DHCP --> cable modem? > > > >Regards, > >James > > > >----- Original Message ----- > >From: "Jonathan Slivko" > >To: > >Sent: Friday, June 01, 2001 12:12 AM > >Subject: 2 NIC's not working > > > > > >> Hello, > >> > >> I just tried to install FreeBSD 4.3-RELEASE > >from FTP on my > >> machine. However, when my machine goes to probe > >for the DHCP > >> server for my cable modem, it doesn't find it. > >In previous > >> releases, and in previous installations of > >4.3-RELEASE, it found > >> the NIC and set it up just fine. Is there any > >reason why this > >> would start occurring now? In Windows, the NIC > >and everything else > >> seems to work fine. So, i'm really puzzled here. > >Any help would be > >> appreciated. Thanks. -- Jonathan M. Slivko > >> > >> ----------------------------------------- > >> Jonathan M. Slivko > >> Network Admin., DataSyrge Internet Svces. > >> Server Co-Admin., AsylumNet IRC Networks > >> > >> web: http://webpage.pace.edu/js43064n/ > >> voice: (212) 696-6774 (24 Hours) > >> ----------------------------------------- > >> > >> > >__________________________________________________ > >_________________ > >> ___ > >> Sent via the Pace University Mail system at > >stmail.pace.edu > >> > >> > >> > >> > >> > >> 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 > > > > >___________________________________________________________________ >___ >Sent via the Pace University Mail system at stmail.pace.edu > > > > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-questions" in the body of the message Walt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message