From owner-freebsd-questions Tue Jan 20 21:53:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA15095 for questions-outgoing; Tue, 20 Jan 1998 21:53:17 -0800 (PST) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from ns1.castlenet.com (ns1.castlenet.com [209.63.23.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA15072 for ; Tue, 20 Jan 1998 21:53:02 -0800 (PST) (envelope-from efinley@castlenet.com) Received: from ip65.castlenet.com (sfiction@ip65.castlenet.com [209.63.23.65]) by ns1.castlenet.com (8.8.5/8.8.5) with SMTP id XAA18242; Tue, 20 Jan 1998 23:00:03 GMT From: efinley@castlenet.com (Elliot Finley) To: kris@airnet.net Cc: freebsd-questions@FreeBSD.ORG Subject: Re: detecting a PCI NE2000 compatible card Date: Wed, 21 Jan 1998 05:57:20 GMT Organization: Hiawatha Coal Company Reply-To: efinley@castlenet.com Message-ID: <34c78df0.47091617@castlenet.com> References: <34c5315c.23388061@castlenet.com> <34C588E2.6364DEC3@ninbsdbox.dyn.ml.org> In-Reply-To: <34C588E2.6364DEC3@ninbsdbox.dyn.ml.org> X-Mailer: Forte Agent 1.5/32.451 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id VAA15084 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk On Tue, 20 Jan 1998 23:34:26 -0600, you wrote: I pulled out the RealTek 8129, and put in my RealTek 8029 and it works... Maybe a new probe is in order? >Elliot Finley wrote: >> >> Hello, >> I have a PCI NE2000 compatible NIC installed in my 2.2-stable >> box, but it doesn't seem to detect it. I have 'device ed0' in the >> kernel config file, but I don't end up with a ed0 device when I boot. >> >> Also, what is 'lp0'? >> >> dmesg | grep lp0 says 'lp0: TCP/IP capable interface'.... this isn't >> the loopback device is it? isn't the loopback device lo0? > >I probably should be doing this but... lp0 is the TCP/IP over parallel >port interface. I believe it was designed to facilitate FBSD >installation over the parallel port, which is *much* faster than 115K >serial link. Don't worry about it. Most people don't mess with it. >Unless they need it. As for the PCI NE2000, I have found that not >putting in the 'controller pci' line will kill the probe for a PCI NIC. >Don't forget your ed0 line too. Without that, no ethernet! I have found >that if you compile in the ed0 and ed1 with the disable in the line, >like this: > >device ed0 at isa? disable port 0x280 net irq 5 iomem 0xd8000 vector >edintr >device ed1 at isa? disable port 0x300 net irq 5 iomem 0xd8000 vector >edintr > >That when you switch to kernel.GENERIC for some unsightly system >failure/operator error [the latter more prevalent here], your rc.conf is >ready and you don't have to reconfig. In Other Words, you have ethernet >without having to kernel -s and edit rc.conf. Great time saver. Note: no >ed2 line is required. It usually finds it: > >ed2 rev 0 int a irq 9 on pci0:17 >ed2: address 00:40:05:4d:11:af, type NE2000 (16 bit) > >Best of luck. Oops, almost forgot. If the PCI card is PnP, and your BIOS >supports PnP, go and add an interrupt line to the PnP config if you >aren't running all PnP [that's the default]. That's how I tied the NIC >to IRQ 2/9 instead of 3. Don't know about you, but I need those sios. -- Elliot Finley (efinley@castlenet.com) President Hiawatha Coal Company