Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!news.mel.connect.com.au!munnari.OZ.AU!news.ecn.uoknor.edu!feed1.news.erols.com!howland.erols.net!rill.news.pipex.net!pipex!tank.news.pipex.net!pipex!news.utell.co.uk!usenet
From: brian@shift.utell.net (Brian Somers)
Newsgroups: comp.unix.bsd.freebsd.misc
Subject: Re: Everex 386 and boot problems
Date: 10 Jun 1997 15:15:00 GMT
Organization: Awfulhak Ltd.
Lines: 45
Message-ID: <5njr1k$c02@ui-gate.utell.co.uk>
References: <339cccde.89899180@news.mindspring.com>
Reply-To: brian@awfulhak.org, brian@utell.co.uk
NNTP-Posting-Host: shift.utell.net
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Newsreader: knews 0.9.8
Xref: euryale.cc.adfa.oz.au comp.unix.bsd.freebsd.misc:42695
In article <339cccde.89899180@news.mindspring.com>,
anindya@bastard.net (AC) writes:
> Hi Folks,
>
> I recently acquired a 386 box, manufactured by Everex (a
> little
> more detail: this box was a high-end 386 for its time: math
> co-processor,
> onboard IDE controller, 12 Megs of RAM.) In any case, I have ambitions
> to install FreeBSD on it and turn it into a router. However, every
> boot.flp image I try hangs after probing for all the device drivers
> (after zp0, i think). I have tried using the -c option at the
> boot prompt and removed all the conflicts, but it still hangs.
> I even removed 4 megs of RAM in case it was having problems dealing
> wit an odd amount like 12. No good. I have tried boot.flp images
> from the 2.1.0, 2.1.7, and 2.2.1 releases, and all have the same
> affect. I'm also convinced nothing in the CMOS could be affecting
> this. I would hate to install Linux on the box; I already have
> one of those boxes ;) Anybody have any suggestions, or any experience
> installing FreeBSD onto an Everex box? (I didn't mention the
> really cool feature: it has an LED display on the front panel
> which tells you what sectors on the disk it is accessing : that
> was worth what I paid for it alone )
>
> Any suggestions or wild theories are welcome.
You could try disabling *everything* that isn't vital
after the -c prompt.
> Thanks,
> --Anindya
>
>|------------------------------------|
>| Anindya Chakraberti |
>| Business Services Network Engineer |
>| Mindspring Enterprises Inc. |
>| Atlanta, GA |
>| anindya@mindspring.net |
>|------------------------------------|
>
--
Brian <brian@awfulhak.org> <brian@freebsd.org>
<http://www.awfulhak.org>
Don't _EVER_ lose your sense of humour !