From owner-freebsd-questions Fri Jan 16 06:33:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA17121 for questions-outgoing; Fri, 16 Jan 1998 06:33:28 -0800 (PST) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from k5qwb.lonestar.org (Dal-VD1-125.anet-dfw.com [207.227.175.25]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA17114 for ; Fri, 16 Jan 1998 06:33:17 -0800 (PST) (envelope-from lrk@k5qwb.lonestar.org) Received: (from lrk@localhost) by k5qwb.lonestar.org (8.7.5/8.7.3) id IAA16305 for freebsd-questions@freebsd.org; Fri, 16 Jan 1998 08:33:08 -0600 (CST) Message-Id: <199801161433.IAA16305@k5qwb.lonestar.org> Subject: Re: NE2000 clone ISA card To: freebsd-questions@FreeBSD.ORG Date: Fri, 16 Jan 1998 08:33:06 -0600 (CST) Reply-To: lrkn@anet-dfw.com In-Reply-To: from John Kenagy at "Jan 15, 98 11:49:23 pm" From: lrkn@anet-dfw.com X-Mailer: ELM [version 2.4ME+ PL22 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk I have one like that which is optionally hardwired, set with software, or plug-and-play. The plug-and-play will always set the interrupt to something other than what I set with the software. Then it looks like the lights flash properly but no actual communication is possible. I set it for plug-and-play and it worked. So I swapped it with the non-PnP one that was in the W95 box. I suspect putting the hardware jumpers in (solder only) would fix it as well but haven't tried that yet. > > Also make sure the port address (mine is 0x300) matches what the > card thinks it is. I've had similar things happen when the IRQ is > right and port isn't. > > John > > On Wed, 14 Jan 1998, Doug White wrote: > > > On Wed, 14 Jan 1998, Aaron D. Gifford wrote: > > > > > Not terribly long ago I installed FreeBSD 2.2.2-RELEASE on an old 486 > > > DX2/66 16MB RAM VESA/ISA PC with a small 400 MB HD belonging to a local > > > high school. Everything seemed to work normally, so I took the box back to > > > the school to try it on their ethernet. On boot, the machine correctly > > > detects the NE2000 clone card as device ed1 (never ed0 - weird), printing > > > the hardware ethernet address. The lights on the card show that it is > > > plugged into the hub and happy, and I can even see the traffic light > > > blinking. Then the weirdness comes along. I see a "ed1: device timeout" > > > message as the boot begins starting network services. > > > > Hm. it'll come up ed1 if ed0 is disabled or if the card is PCI (which it > > doesn't sound like). Also, make sure the IRQ you are assigning to the > > card isn't in use by another device and that the cable is in good shape > > (bad cabling and line noise have been known to send ethernet cards into > > tail spins). > -- --------------------------------------------------------------------- | 73, E-mail | lrkn@anet-dfw.com | | Lyn Kennedy webpage | http://webusers.anet-dfw.com/~lrkn/ | | K5QWB pony express = P.O. Box 5133, Ovilla, TX, USA 75154 | ---Livin' on an information dirt road a few miles off the superhighway---