*BSD News Article 23097


Return to BSD News archive

Newsgroups: comp.os.386bsd.bugs
Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!agate!howland.reston.ans.net!xlink.net!subnet.sub.net!flatlin!flyer!robkaos!robsch
From: robsch@robkaos.GUN.de (Robert Schien)
Subject: Re: FreeBSD 1.0 EPSILON won't boot
References: <dgontz.54.00154821@po-box.esu.edu>
Organization: Private System, Essen, Germany
Date: Tue, 26 Oct 1993 22:21:20 GMT
X-Newsreader: TIN [version 1.2 PL2]
Message-ID: <1993Oct26.222120.2547@robkaos.GUN.de>
Lines: 41

Douglas Gontz (dgontz@po-box.esu.edu) wrote:
........
:      The first problem I have getting the system to boot once I add an entry 
: in the /etc/fstab file to pick up a partition on the second hard drive.  As 
: soom as I try to boot with this fstab, the machine crashes with several lines 
: telling me that I have stray interrupt 7's.   After several of these lines the 
: system reports that is has received too many of them and is ignoring them.  At 
: that point the drive LED comes on solid and the boot stops.  This all happens 
: at the pioint where the boot is running fsck.  At random times I am able to 
: get past this problem and actually get a running machine - to a point.  For 
: the majority of the time IO get nailed with a crash.

I had very similiar problems. When trying to boot FreeBSD-EPS the systems
hangs at random times when inserting the file-system floppy. Sometimes
booting was successfull, sometimes not. I solved the problem by using
a different IDE drive. With my Kalok 100 MB drive, installation was not
possible. Now I have a Seagate ST3390 and all works fine. But the random
hangings during installation is wierd. It seems that FreeBSD is more picky
about the hardware than the old 386bsd-0.1.

:      The second problem I am having is trying to figure out why inetd does not 
: start telnetd.  The files in /etc all look correct.  I am able to use the 
: system to telnet and ftp to other machines.  But other machines are not able 
: to telnet into this machine.  Using ps waux I can see that telnetd has not 
: started.  I checked inetd.conf and it looks good.

Again, I have similiar effects, but for me it's ftp which makes problems.
I can't ftp to my own machine from another system, although telnet, talk 
and finger work! I can ftp from my system to another. I checked inetd.cf
and it seems properly configured. I just don't know why ftpd will not
be started by inetd. Maybe, this has to do with the fact, that my only
(temporary) internet connections are via SLIP.
:      I would like any suggestions at all on correcting either problem.  If you 
: can help would you please write me directly as I don't often have a chance to 
: check the network news.

:      Thank-you for taking the time to read this.

: === Douglas   dgontz@po-box.esu.edu

Robert