*BSD News Article 10615


Return to BSD News archive

Received: by minnie.vk1xwt.ampr.org with NNTP
	id AA380 ; Sun, 31 Jan 93 14:05:26 EST
Newsgroups: comp.unix.bsd
Path: sserve!manuel.anu.edu.au!munnari.oz.au!spool.mu.edu!uwm.edu!cs.utexas.edu!hellgate.utah.edu!fcom.cc.utah.edu!cs.weber.edu!terry
From: terry@cs.weber.edu (A Wizard of Earth C)
Subject: Re: 386BSD Installation
Message-ID: <1993Jan31.224750.19475@fcom.cc.utah.edu>
Sender: news@fcom.cc.utah.edu
Organization: Weber State University  (Ogden, UT)
References: <1993Jan31.090002.2601@organpipe.uug.arizona.edu>
Date: Sun, 31 Jan 93 22:47:50 GMT
Lines: 54

In article <1993Jan31.090002.2601@organpipe.uug.arizona.edu> ece_0051@bigdog.engr.arizona.edu (Anand Kuratti) writes:
>I have been trying to get 386BSD to boot on an AT&T WGS 6386/E Model S
>with limited success.  The system is configured as follows:
>
>1. WD7000 SCSI controller
>
>   a. IRQ: 15
>   b. DMA channel: 6
>   c. I/O address: 0x350
>   d. BIOS ROM address: 0xCE000
>   e. connected to:
>
>      3.5 1.44 MB floppy drive
>      HP 600 MB SCSI hard drive (SCSI ID 0)
>      120 MB Wangtek tape drive (SCSI ID 3)

[ ... ]

>At this point, the floppy drive drive light goes off and the system hangs
>(rebootable by CTL-ALT-DEL).  I have tried the new patch-kist dist.fs, but
>wd0 is not recognized and the system still hangs at the same point.

This is what happens if the controller is fund by the wd driver but isn't
a "wd" controller.  the distinction between a wd controller and a "wd"
controller being that a "wd" controller is one recognized by more than the
probe routine in wd.c, and a wd controller is one manufactured by Western
Digital.

The WD7000 is not supported.  The fact that it comes up in the inventory
is precisely what has kept me from releasing a driver for the thing under
Julian's SCSI system.  Basically, the thing *shouldn't* be recognized by
the wd driver's probe -- I can fix it, but it means IDE drives aren't
recognized either.

This is probably why AT&T provides SVR4.0 SCSI and ESDI bootables on two
sets of disks rather than just a single set of disks: they couldn't fix
it either.

You will have to pick a different controller or wait for someone to solve
the problem; it has me stumped for now, and I'm frantically trying to do
five million things before a March deadline.


					Terry Lambert
					terry@icarus.weber.edu
					terry_lambert@novell.com
---
Any opinions in this posting are my own and not those of my present
or previous employers.
-- 
-------------------------------------------------------------------------------
                                        "I have an 8 user poetic license" - me
 Get the 386bsd FAQ from agate.berkeley.edu:/pub/386BSD/386bsd-0.1/unofficial
-------------------------------------------------------------------------------