From owner-freebsd-isp Fri Feb 12 19:57:54 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA22123 for freebsd-isp-outgoing; Fri, 12 Feb 1999 19:57:54 -0800 (PST) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from Radford.i-Plus.net (radford.i-plus.net [209.100.20.24]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA22118 for ; Fri, 12 Feb 1999 19:57:51 -0800 (PST) (envelope-from rewt@i-Plus.net) Received: from Radford.i-Plus.net (rewt@www.i-plus.net [209.100.20.4]) by Radford.i-Plus.net (8.8.8/8.8.5) with SMTP id WAA11645; Fri, 12 Feb 1999 22:57:04 -0500 (EST) Date: Fri, 12 Feb 1999 22:57:04 -0500 (EST) From: Troy Settle To: Dan Busarow cc: "Francis Percival C. Favoreal" , freebsd-isp@FreeBSD.ORG Subject: Re: PCI NE2000 problem In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, 12 Feb 1999, Dan Busarow wrote: > On Sat, 13 Feb 1999, Francis Percival C. Favoreal wrote: > > de0 rev 33 int a irq 10 on pci0:13:0 > > de0: 21041 [10Mb/s] pass 2.1 > > de0: address 00:80:c8:59:e1:dc > > vga0 rev 16 int a irq 11 on pci0:15:0 > > ed0 rev 0 int a irq 9 on pci0:16:0 > > PCI NE2000 should be detected at ed1, ed0 is ISA This depends entirely on the kernel configuration. I had a box with 2 of these, and they are ed0 and ed1. Both worked perfectly. > > > The kernel is compiled with ed0 config as, > > > > device ed? at pci0 port 0xff80 net irq 12 iomem 0xd800 vector edintr > > Wrong. You don't want that. Number 4 below is the one you want. > > > > I also tried the ff. ed0 configs then compiling the kernel for each: > > > > (1) device ed? at pci0 > > (2) device ed? at pci? > > (2) device ed? at pnp0 > > (3) device ed? at pnp? > > (4) device ed0 at isa? port 0x300 net irq 3 iomem 0xd8000 vector edintr > > (5) device ed0 at isa? disable port 0x300 net irq 3 iomem 0xd8000 vector > > edintr Try this: device ed0 no options, no nothing. This will get everything you need for this card to work. I did have the same problem as the original poster, reseating the card did the trick... I guess it just wasn't comfortable the first time. If still no luck, try booting the generic kernel. It has the appropriate drivers as well. The card will show up as either ed1 or 2. And, as a final, last resort, try swapping out the card for another. Could have a bad card on your hands. laters, -- Troy Settle Network Administrator, iPlus Internet Services http://www.i-Plus.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message