*BSD News Article 69357


Return to BSD News archive

Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!news.mel.connect.com.au!munnari.OZ.AU!news.hawaii.edu!ames!enews.sgi.com!news.mathworks.com!uunet!in1.uu.net!news1.erols.com!newsmaster@erols.com
From: Ken Bigelow <kbigelow@www.play-hookey.com>
Newsgroups: comp.unix.bsd.freebsd.misc
Subject: Re: learning freebsd...
Date: Fri, 24 May 1996 23:46:46 -0700
Organization: Erols Internet Services
Lines: 40
Message-ID: <31A6ACD6.696F@www.play-hookey.com>
References: <31A4F111.3AD@ahoynet.com>
NNTP-Posting-Host: kenjb05.play-hookey.com
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Mailer: Mozilla 2.02 (Win16; I)

kevin graham wrote:
> 
> I'm still entirely green with freebsd, having come from the realm of
> windows nt/95... in any case, i have a successful installation and have
> been trying for several days now to rebuild the kernel..
> 
> the system is an intel486/66 with 12mb ram and a single ide disk
> (325mb)... along with a 1.44 floppy, 3c5x9 ethernet adapter, 2 serial/1
> parallel, and a vga card that's it.. it will eventually be used as a web
> server..
> 
> however, it seems whenever i try to compile the kernel (following
> instructions in the 'intro to freebsd'), while runing make in
> /usr/src/sys/compile/mykernel, it crashes on errors at seemingly random
> spots (the same source set run twice in a row may very well crash at two
> different spots)... i even tried compiling
> /usr/src/sys/i386/conf/GENERIC and had error... any ideas?


Try disabling your external cache and then recompile. It sounds silly, I 
know, but I have had huge amounts of grief installing, compiling, and 
just running FreeBSD with 20 ns cache chips (which is what I had on 
hand). RAM checkers pass the cache, DOS and Windows don't complain, but 
FreeBSD may be enough more efficient that the cache gets lost. (Or, the 
fact that FBSD keeps a lot of stuff in RAM may have something to do with 
it.) Either way, I could run with faster cache or no cache, but not with 
slower cache.
> 
> on another note, i also have had no luck getting the ethernet card
> clicking... its setup at 300h/irq10 both phyically and in the os, with
> (a presumable) ip address of 192.168.0.1 ... no luck at all on pinging
> into or out of the thing.... once again... could someone spin me towards
> the right corner?
> I'd need more info on what you're trying to access it with; the whole 
network can affect this. For example, is your ethernet cable properly 
terminated at both ends?

I hope this helps!

Ken