Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!newshost.dca.gov.au!news.mel.aone.net.au!yarrina.connect.com.au!news.mel.connect.com.au!munnari.OZ.AU!spool.mu.edu!usenet.eel.ufl.edu!newsfeed.internetmci.com!news.ac.net!news.cais.net!news2.cais.com!cais.cais.com!mcgraw From: mcgraw@cais.cais.com (Michael Curry) Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: Oddball ethernet problem and solution (of sorts) Date: 29 Mar 1996 15:55:19 GMT Organization: Capital Area Internet Service info@cais.com 703-448-4470 Lines: 15 Message-ID: <4jh157$6gb@news2.cais.com> References: <rrwood-2903960739190001@bpci.net3.io.org> NNTP-Posting-Host: cais.com X-Newsreader: TIN [version 1.2 PL2] Roy Wood (rrwood@io.org) wrote: : I tried installing an NE2000-compatible ethernet card yesterday, and : encountered some very strange problems. The first clue was that even : though ed0 was recognized by the kernel at boot, it kept timing out. This : suggested that the interrupt was not being detected by FreeBSD (and yes, : it was a unique interrupt, not a conflicting one). Not to ask a silly question, but did you employ the "-c" option at boot, and the "visual" mode process to enter the correct IRQ and port info for the card? Is this an Addtron or Enet16 card? If so, initialization of the EEPROM can sometimes make the BNC/RJ45 recognition problem go away, IF that is what the sympton truly is.