*BSD News Article 21529


Return to BSD News archive

Newsgroups: comp.os.386bsd.bugs
Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!agate!doc.ic.ac.uk!uknet!mcsun!ieunet!ieunet!dec4ie.ieunet.ie!jkh
From: jkh@whisker.lotus.ie (Jordan K. Hubbard)
Subject: Re: More *BSD installation grief.
In-Reply-To: fmayhar@acsc.com's message of 25 Sep 1993 09: 46:22 -0700
Message-ID: <JKH.93Sep26045227@whisker.lotus.ie>
Sender: usenet@ieunet.ie (USENET News System)
Nntp-Posting-Host: whisker.lotus.ie
Organization: Lotus Development Ireland
References: <280eic$eu4@acsc.com> <JKH.93Sep25112639@whisker.lotus.ie>
	<281sku$f39@acsc.com>
Date: Sun, 26 Sep 1993 04:52:27 GMT
Lines: 34

In article <281sku$f39@acsc.com> fmayhar@acsc.com (Frank Mayhar) writes:
   Nope.  Standard IDE through a multifunction card (QuickPath 13-port card
   with two floppy controllers [one disabled], IDE, two parallel [disabled],
   4 serial [16550-emulating ASICs], game port), to a WD2200 Caviar; there's
   also a Quantum 80 MB drive on that controller, which isn't being used by
   *BSD.  The controller is at IRQ 14 as usual.  I also have an Adaptec 1542B
   with a Maxtor LXT340SY and an Archive Viper on it, but which isn't being
   used this early in the boot.

Hmmmm.  Well, all I can say is that the wd support situation is still
a little dicey for all *BSD variants at the moment and sometimes we
encounter a situation where a given drive (more often than the
controller) Just Won't Work.  This is less often the case with SCSI
peripherals, and I find myself wondering if there's any way you can
use that Adaptec of yours as the boot drive/device instead and save
yourself a whole lot of grief?

Sorry I can't be more helpful regarding the IDE, but it's pretty hard
to debug it from here.  If you really wish to use the IDE, and have
access to another FreeBSD machine where you can build kernels, then
send mail to FreeBSD-questions@freefall.cdrom.com outlining your
problem in as much detail as you can, and we'll see about sending you
a couple of experimental variations of the wd drivers to try, in hopes
of at least narrowing down (if not fixing) the problem.

Thanks!

				Jordan

--
(Jordan K. Hubbard)  jkh@violet.berkeley.edu, jkh@al.org, jkh@whisker.lotus.ie

I do not speak for Lotus, nor am I even a Lotus employee.  I am an independent
contractor.