Return to BSD News archive
Newsgroups: comp.os.386bsd.questions
Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!elroy.jpl.nasa.gov!usc!news.isi.edu!gremlin!nrtc.northrop.com!jpl
From: jpl@nrtc.northrop.com (Jeff P. Lankford)
Subject: [Q] Need help configuring AHA-1542C
Message-ID: <CBCL57.CDu@gremlin.nrtc.northrop.com>
Sender: news@gremlin.nrtc.northrop.com (Usenet News Manager)
Organization: Northrop Research and Technology Center
Date: Fri, 6 Aug 1993 17:12:42 GMT
Lines: 21
I don't know very much about PCs, but i recently
purchased a 486DX based PC so i could run 386BSD. I
have an IDE disk and controller and the Adaptec 1542C
and SCSI disk.
When i boot the Tiny 386BSD install disk (at patch 0.2.4),
just after the driver initializes the transfer speed
(ie, "150nSEC OK, using 200nSEC"), there is a diagnostic
message displayed ("aha_cmd: aha1542 cmd/data port full").
The controller proceeds to probe for devices, and then a
set of 7 messages is printed ("cmd fail\n abort failed in wait\n").
The Tiny BSD finally boots up, but SCSI devices are not accessible.
Now the interesting part is that this behavior occurs when
the controller setup has BIOS Enabled. If BIOS is disabled, then
the driver diagnostics aren't printed, and Tiny BSD boots fine.
The counter problem is that if Adaptec BIOS is disabled, the various
partition and format commands under DOS don't recognize the SCSI disk.
i've read the FAQ and reviewed news articles, and have seen
nothing addressing this problem. Any suggestions?
thansk,
jpl