[comp.unix.sysv386] Exabyte drive on Intel V.4 with WD7000

bt@meteor.wisc.edu (Bill Taylor) (01/25/91)

Our news was down so this might be a repeat but doubt it.

I have built a Compuadd 386/25 MHz with a scsi disk hanging off
the WD7000FAST controller. Unix runs(Intel V.4 vs 2.0) as well
as can be expected with 4 Meg. I have a good Exabyte 8200 that
I have placed both at id 2 and at id 5 on the SCSI BUS and upon
booting, It says that it sees an Exabyte(Probably data from
an inquiry) and that since it is not supported, it will not
be configured. Since I wish to develop from X I am not buying more memory
until I either get this to work or uucp(also a problem).

The support number says that since I did not buy  $2000 contract
and I am running have to go through Avnet for support. I assume since
the support manager says they had some Exabyte probelms other than this.
That either another SCSI controller supports it(probably the 1541b adaptec)
or there is some configuration item I am missing. Help via
EMAIL would be wonderful.

The UUCP problem is the infamous DEVICE UNAVAILABLE. I have what worked
well for V.3 and made uucp owner and group. ??????? The other entries
shouls work in Devices, Dialer, and Systems.

Email please

cpcahil@virtech.uucp (Conor P. Cahill) (01/26/91)

In article <1991Jan24.184603.9612@meteor.wisc.edu> bt@meteor.wisc.edu (Bill Taylor) writes:
>I have placed both at id 2 and at id 5 on the SCSI BUS and upon
>booting, It says that it sees an Exabyte(Probably data from
>an inquiry) and that since it is not supported, it will not
>be configured. Since I wish to develop from X I am not buying more memory
>until I either get this to work or uucp(also a problem).

The problem is that AT&T in it's infinite wisdom has placed a hard-coded
table into the kernel of the devices that the system will support.  This
table is located in /etc/conf/pack.d/sd01/space.c.

Each entry in the table has two pieces of information.  The first piece is
the EXACT string returned by the SCSI inquire request.  This will be displayed
by the os when it tells you that it doesn't know about the device.  You must
copy it down exactly including spacing, upper/lower case, punctuation.

The second piece is the number of "LUs supported by the TC".  I don't really
know what this is, but for 99.9% of the SCSI devices out there it will be a
1.  

So to get your tape drive working add a line to the table that says
something like:

	"Exabyte id string....    ", 1, /* Exabyte 8mm tape drive */

> Help via EMAIL would be wonderful.

I posted the response because I felt this would be of general interest.


>The UUCP problem is the infamous DEVICE UNAVAILABLE. I have what worked
>well for V.3 and made uucp owner and group. ??????? The other entries
>shouls work in Devices, Dialer, and Systems.

This isn't enough information to diagnose the problem.

-- 
Conor P. Cahill            (703)430-9247        Virtual Technologies, Inc.
uunet!virtech!cpcahil                           46030 Manekin Plaza, Suite 160
                                                Sterling, VA 22170 

bt@sleaze.meteor.wisc.edu (Bill Taylor) (01/27/91)

In article <1991Jan25.181355.16475@virtech.uucp>, cpcahil@virtech.uucp (Conor P. Cahill) writes:
|> In article <1991Jan24.184603.9612@meteor.wisc.edu> bt@meteor.wisc.edu (Bill Taylor) writes:
|> 
|> The second piece is the number of "LUs supported by the TC".  I don't really
|> know what this is, but for 99.9% of the SCSI devices out there it will be a
|> 1.  
|> 

Most Scsi devices only have one logical device which is attached to the
controller. Some like the Emulex MD/21 will talk to 2 Esdi drives. And
some like the Scientific Micro Systems Omti 7400 will talk to 2 esdi
or st506 drives , 4 floppies, and a streamer tape.

|> So to get your tape drive working add a line to the table that says
|> something like:
|> 
|> 	"Exabyte id string....    ", 1, /* Exabyte 8mm tape drive */

Acutally did fix the problem! The sdo1 directory was for hard drives
and there was one I think called st01 which when I placed the entry
enabled the device /dev/rmt/c0s0

The UUCP entries are set up and if I go "cu sleaze":

	It finds the line, the modem, the dialer, dials the phone
	and even connects correctly. While spiiting lots of debug messages
	to the screen. 

plain "cu" gives me a "CONNECTED" message but I can not control the modem
and dial. uucico never gets the phone dialed.

??