Return to BSD News archive
Xref: sserve comp.os.386bsd.bugs:632 comp.os.386bsd.questions:2118 Newsgroups: comp.os.386bsd.bugs,comp.os.386bsd.questions Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!elroy.jpl.nasa.gov!decwrl!netcomsv!netcom.com!duncan From: duncan@netcom.com (Donald K. Duncan) Subject: Re: System Died Message-ID: <duncanC6BHxJ.Gr9@netcom.com> Summary: check bios setup Organization: NETCOM On-line Communication Services (408 241-9760 guest) References: <1993Apr30.115617.25778@mcs.kent.edu> Date: Fri, 30 Apr 1993 22:17:42 GMT Lines: 18 In article <1993Apr30.115617.25778@mcs.kent.edu>, gspiegel@mcs.kent.edu (Greg "TwoTone" Spiegelberg) writes: > Just the other day our 386bsd server died. > It wouldnt' allow any telnet or ftp sessions and unfortunately, the last kernel > I built for it wouldn't allow anyone to use the console keyboard either. > So basically, I have to boot off floppy for the time being, right? > Wrong. It won't recognize a floppy. I've made up new boot floppies and used > the original ones from when I first downloaded everything. > Here's what it does: I'll turn the computer off and put a boot floppy in. > It'll start up like it's doing just fine but once it looks like > it's reading drive A: it switches over to the hard drive and boots > from it and I'm back where I started. Check your bios setup. Some bios have a bootable drive selection capability and it may be that the floppy isn't in the list. Just a possibility... -- duncan@zycad.com (Donald Duncan - WB6QMS)