Return to BSD News archive
Path: sserve!manuel.anu.edu.au!munnari.oz.au!spool.mu.edu!sol.ctr.columbia.edu!destroyer!cs.ubc.ca!unixg.ubc.ca!sitka.triumf.ca!felawka
From: felawka@sitka.triumf.ca (Larry Felawka)
Newsgroups: comp.unix.bsd
Subject: Problems with 386bsd and 3COM 503 ethernet interface
Date: 14 Oct 1992 01:56:12 GMT
Organization: TRIUMF, Vancouver BC
Lines: 29
Distribution: world
Message-ID: <1bfunsINN3ek@iskut.ucs.ubc.ca>
NNTP-Posting-Host: sitka.triumf.ca
Keywords: 386bsd 3COM ethernet
Help! Is there anyone out there who has got the 3COM 503 ethernet interface
running with 386bsd? I have had success with 386bsd and the Western Digital
ethernet interface (it works great). When I rebuild the kernel with only the
3COM 503 i/f support, the system crashes after about 30 seconds after I do
ifconfig ec0 inet nn.nn.nn.nn aui
with the 3COM 503 i/f. The "aui" parameter is recognized by the patched version
of "ifconfig" and is necessary to get the system working with external thicknet
ethernet transceivers (alas, for only for 30 seconds in my case). I believe
that the driver is suspect, although possibly it works for the on-board thinnet
transceiver. The system crashes with the messages
vm_fault(fe103000,fe623000,3,0) -> 1
type c, code fe070002
trap type 12 code = fe070002 eip = fe0007f7 cs = 8 eflags = 10696 cr2
panic: trap fe6230ed cpl 525a
Many thanks,
Larry Felawka
TRIUMF
Vancouver, BC
--
Larry Felawka