*BSD News Article 8443


Return to BSD News archive

Path: sserve!manuel.anu.edu.au!munnari.oz.au!news.hawaii.edu!ames!olivea!uunet!zaphod.mps.ohio-state.edu!moe.ksu.ksu.edu!usenet-feed.cc.umr.edu!mcs213i.cs.umr.edu!yting
From: yting@mcs213i.cs.umr.edu (Yu-Han Ting)
Newsgroups: comp.unix.bsd
Subject: Re: [386BSD] Troublesome SCSI problems with VL-BUS machine
Message-ID: <1992Dec1.185127.4785@umr.edu>
Date: 1 Dec 92 18:51:27 GMT
Sender: cnews@umr.edu (UMR Usenet News Post)
Organization: University of Missouri - Rolla
Lines: 42
Nntp-Posting-Host: mcs213i.cs.umr.edu

Ooooooops!

   It seems that I have screwed up my previous post.  Sorry about that.  Here
comes the original question:

===============

Hi, everyone

   I apologize if this problem has been asked before.  I got my new machine
half a month ago.  It's based on Micronics' VL-BUS motherboard with an i486
DX2/66 CPU.  The hard drive equipped is an Fujitsu SCSI one with Adaptec
1542b controller.  When I tried to boot 386BSD from floppy, the floppy just
kept spinning for nearly 3 minutes.  I've read the unofficial FAQ from
agate.berkeley.edu and it said the boot process will take only about 1.5
minutes.  Since that there were not any message displayed on the screen and
the floppy had running for an unreasonable time, finally I decided to reset
the machine with no clue for diagnostics.

   Somethings unusual to my hardware configuration are listed below:

   1) The hard drive is of 512Mb (1429 cylinders).

   2) The partition reserved for 386BSD is on the last 200Mb of the hard disk.

   3) The ROM BIOS is of Phoenix ROM BIOS plus version 0.10 GB22-2 LB.

   4) The Adaptec controller (BIOS version 3.10, 1988) is put in a 32-bit VL-
      BUS slot.

   5) There are two IDE drive setup entries in the CMOS.  Both of them are
      set to be disabled.  It seems that it's required to do so.  Otherewise,
      the SCSI controller couldn't take over the hard drive.

   Since that I can't get my SCO Unix to be installed either (the setup pro-
gram can not find the hard drive information), I'm considering to replace the
SCSI drive with an IDE one if the problem can not be solved.  Anyway, that
will be the last thing I will do :(  If anyone has any similar experience,
please let me know.  Any suggestion is greatly appreciated.   

Yu-Han Ting
yting@cs.umr.edu