*BSD News Article 47999


Return to BSD News archive

Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!simtel!news1.oakland.edu!jobone!newsxfer.itd.umich.edu!sol.ctr.columbia.edu!math.ohio-state.edu!howland.reston.ans.net!gatech!news.mathworks.com!uunet!in1.uu.net!mr.net!news.mr.net!healthpartners.com!btv
From: btv@ldl.HealthPartners.COM (Bryan T. Vold)
Newsgroups: comp.unix.bsd.freebsd.misc
Subject: Help getting 3C503 up w/ 2.0.5
Date: 27 Jul 1995 17:33:28 GMT
Organization: HealthPartners
Lines: 20
Message-ID: <3v8il8$hgl@daffy.healthpartners.com>
NNTP-Posting-Host: ldl.healthpartners.com

I just got FreeBSD 2.0.5, and got the minimal release (had to load via floppy).
I have been trying to get the 3C503 up.  It gets recognized by the kernel, and
I have it jumpered to the correct settings (per HARDWARE file).  I did get
NetBSD up a while back, and I had a hard time with that until I found the link0 
option.  Under FreeBSD, the link0 option doesn't seem to do anything.  When I
do a:
	netstat -rn

I get a bunch of references in the gateway field to "link#1".  I assume this
is where the problem is.  The FreeBSD.FAQ seems to be in error when it says
something about using the altphys or -altphys to change which port is used.
I haven't tried different hardware settings (yet).  Should I need to?  The 
settings under NetBSD are completely different (irq 2, 280, d0000) as
opposed to (irq 5, 280, d8000).  Any hints or suggestions appreciated.  I
really want to try FreeBSD.  BTW, it boots under Linux fine.  

-Bryan
-- 
btv@ldl.healthpartners.com               "The relentless pursuit of perfection"
Linux -- The Choice of a GNU Generation  "Make it so, Number One."