*BSD News Article 22786


Return to BSD News archive

Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!agate!msuinfo!netnews.upenn.edu!jake.esu.edu!po-box.esu.edu!dgontz
From: dgontz@po-box.esu.edu (Douglas Gontz)
Newsgroups: comp.os.386bsd.bugs
Subject: FreeBSD 1.0 EPSILON won't boot
Keywords: IRQ7 EPSILON Strayint
Message-ID: <dgontz.54.00154821@po-box.esu.edu>
Date: 25 Oct 93 01:16:45 GMT
Organization: East Stroudsburg University
Lines: 35
NNTP-Posting-Host: cc003.esu.edu
X-Newsreader: Trumpet for Windows [Version 1.0 Rev A]


     I just installed freeBSD 1.0 EPSILON I was able to ftp from 
freebsd.cdrom.com.  I am having several problems getting the system to 
function as anything other than a single user system.  I am especially having 
trouble getting the system to function with the second hard drive.

     The system configuration is a 386sx33 with 16 meg of ram and two Seagate 
3144 IDE hard disks.  The controller card is a multifunction type that handles 
the serial ports, parallel port and a game port.  Both disks are completely 
partitioned for BSD.  The NIC is an SMC 8013 Elite configured properly for BSD 
to recognize it.

     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.

     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.

     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