*BSD News Article 21555


Return to BSD News archive

Newsgroups: comp.os.386bsd.bugs
Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!elroy.jpl.nasa.gov!usc!howland.reston.ans.net!europa.eng.gtefsd.com!uunet!das.wang.com!wang!lar3ry
From: lar3ry gensch <lar3ry@world.std.com>
Subject: Re: More *BSD installation grief.
Reply-To: lar3ry@world.std.com
Organization: Wang Labs, Lowell MA, USA
Date: Mon, 27 Sep 1993 13:26:29 GMT
Message-ID: <CE0LC6.AzI@wang.com>
References: <280eic$eu4@acsc.com>
Sender: lar3ry@wang.com (Larry Gensch)
Lines: 30

fmayhar@acsc.com (Frank Mayhar) writes:

>_This_ time, I can't even get as far as I did with NetBSD.  The kc floppy
>boots and asks for the filesystem floppy, which I provide.  It then proceeds
>to go through its startup sequence.  It finally prints a "ISA strayintr 7"
>message, indicates that it's changing the root filesystem to fd0a, and then
>hangs forever.

I had a similar problem with NetBSD and FreeBSD.  I decided to
disable my ESDI disk (pulled out the power connector), and put in an
Adaptec SCSI adapter (1540A).  I formatted a brand new 330 Mb SCSI
disk and started FreeBSD.  It got to the point you did and hung.

On a hunch, I went back in and powered on the ESDI drive (although I
told the BIOS it wasn't there) and at the same point where it tries to
change the root filesystem to fd0a, I hear the ESDI drive seek a few
times, and then it succeeded.  (Got a message that it couldn't read
the label off "wd0")

However, after spending A WEEK with various configurations of NetBSD
0.9 and FreeBSD 1.0-GAMMA, I have not been able to successfully get
the damn thing to install completely (I now get "sd0a" problems, and
see the drive power down after a boot... ARRRRGGGGGHHH!!!).  My only
fallback position it to try to install Linux (either that or MS-DOS,
which is NOT an option).

-- 
(void) lar3ry();		lar3ry@world.std.com

"Yo Ho, Yo Ho! Another $200 Million for me!" (DIS 'N' DAT - June '93)