Exabyte 8200 on a DECstation 3100 ?
Steve Dyer
dyer at spdcc.COM
Wed Jan 17 06:53:30 AEST 1990
I found that during my upgrade from Ultrix 3.0 to Ultrix 3.1,
my kernel had a lot of xxxx_data.o files which did not get rebuilt
from their new xxxx_data.c files. Thus, I was building a
composite Ultrix kernel with some 3.0 binaries and some 3.1 binaries.
At the very least make sure that scsi_data.o is built from scsi_data.c.
The Ultrix 3.1 scsi driver relies on the presence of a 3.1 scsi_data.c
entry for the Exabyte--it will misbehave if you are building a kernel
with an older 3.0 scsi_data.o.
If the Exabyte is recognized as a "TZ88" upon boot up, then you've
got the wrong file from 3.0 linked into your kernel. It should be
recognized as a "TZxx". Since cleaning this up, the Exabyte has
been working fine. The dip switches on the drive should include
"no disconnect on odd byte boundaries".
--
Steve Dyer
dyer at ursa-major.spdcc.com aka {ima,harvard,rayssd,linus,m2c}!spdcc!dyer
dyer at arktouros.mit.edu, dyer at hstbme.mit.edu
More information about the Comp.unix.ultrix
mailing list