Date: Wed, 29 Jul 1998 15:50:47 -0700 (PDT) From: Doug White <dwhite@resnet.uoregon.edu> To: "Behal, Satwant" <behsa01@mail.cai.com> Cc: "'Dan Riley'" <daniel@vailsys.com>, "'freebsd-questions@freebsd.org'" <freebsd-questions@FreeBSD.ORG> Subject: RE: problem with network card. Message-ID: <Pine.BSF.4.00.9807291547580.24795-100000@resnet.uoregon.edu> In-Reply-To: <759C8DEC7928D1118B1B00805F85A2F6F407C3@usilmsc1.cai.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 28 Jul 1998, Behal, Satwant wrote: > Can anyone please help me with this ? I'll try, it's pretty badly chopped up. > > > you said: > > > Is this irq available to isa via bios? > > > how do I find that out ? > > > > Forgive my lack of technical terms, but most of the time there is an > > option in the bios related to plug and play. There you can > > enable/disable which irqs are reserved for legacy isa cards and which > > irqs are available to pnp/pci cards. Assuming the Ethernet card is Plug&play (which it is most likey not). Use a diagnostic utility like MSD or Win95's Computer Properties to see what interrupts are in use on your system. Make sure the Ethernet card is using an unique IRQ. In fact, tell FreeBSD to use the one Windows is using. > > > how do I "force tp or bnc"? > > > > Again, if it works in win95 then I doubt this has anything to do with > > it. The card should have most likely come with a setup or configuration > > utility with which you can tell the card exactly what media type is > > being plugged into it rather than letting it auto-select between aui, > > bnc and tp. You can use link flags too; see the ed man page. > > > > > The dmesg has these lines: > > > > > ed0 at 0x300-0x31f irq 10 maddr 0xcc000 msize 16384 on isa > > > > > ed0:address 00:00:c0:67:66:8a type WD8013EPC (16 bit) > > > > > > > > > > > > > Is this irq available to isa via bios? > > > > > > > > > This info matches the WIN95 device drivers info. > > > > > > > > Does it work when you are running win95? > > > > > > > > > > > > > > The entries in /etc/rc.conf are: > > > > > > > > > > network_interfaces "ed0" > > > > > ifconfig_ed0="inet 192.35.xx.xx netmask 255.255.255.0" > > > > > > > > > > Also, de0 seem to be DECDC21040 ethernet adapters. > > > > > > > > > > There is no conflict with any other IRQ as well. > > > > > > > > > > Any idea why kernel would find ed0 not responding ? > > > > > > > > Maybe confused about the media it is connected to, force tp or bnc. A little background on this: Some ed-driven cards (ne2000s particularly) get angry if they aren't detecting carrier on the UTP connector (assuming twisted-pair or 10BaseT is selected). They start spitting the ``ed0: not responding'' error until you plug the network in. Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.00.9807291547580.24795-100000>