Date: Thu, 15 Jan 1998 23:49:23 -0600 (CST) From: John Kenagy <jktheowl@bga.com> To: Doug White <dwhite@resnet.uoregon.edu> Cc: "Aaron D. Gifford" <agifford@infowest.com>, questions@FreeBSD.ORG Subject: Re: NE2000 clone ISA card Message-ID: <Pine.BSF.3.95q.980115234619.8056A-100000@barnowl.roost.net> In-Reply-To: <Pine.BSF.3.96.980114155052.27320F-100000@gdi.uoregon.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi! 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). > > Doug White | University of Oregon > Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant > http://gladstone.uoregon.edu/~dwhite | Computer Science Major > > > >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.95q.980115234619.8056A-100000>