SUMMARY: Getting an EXABYTE 8200SX to work with Suns

From: Mike Reetz (miker@ncar.ucar.edu)
Date: Thu May 06 1993 - 12:23:01 CDT


Original post:

I just got an Exebyte 8200SX and I'm having trouble getting it
to work with 4.1.3. Seems SunOS doesn't recognize it as an Exebyte
but defaults it to a 1/4 inch tape. If I try a read (or write)
operation I get on the console:

st1: Generic Drive, Vendor=<EXABYTE >
        Unknown type- assuming 0.25 inch cartridge
        Fixed record length (1024 byte blocks) I/O
st1: Error for command 'read', Error Level: 'Fatal'
        Block: 0 File Number: 0
        Sense Key: Media Error

Does anyone know why this is? Does 4.1.3 not know about the 8200SX (BTW,
the SX means it can do fast searches, otherwise it is a regular 8200).

Thanks.

I didn't get any solutions from netters, but finally did from
Exabyte themselves (thanks to Kristine Anthony at Exabyte). I'll
detail the changes necessary.

Changes need to be made to two files then a kernel re-build.

The files are: /sys/sundev/streg.h and /sys/scsi/targets/st_conf.c,
first streg.h:

below the exeisting two definitions (in 4.1.3, possibly only one entry
in pre-4.1.3) for the Exebyte 8500 and Exebyte 8200 add:

/* Exebyte 8mm 2.3GB cartridge GENERIC entry */ \
{ "Exabyte", 7, "EXABYTE", ST_TYPE_EXABYTE, \
        1024, (ST_VARIABLE | ST_BSF | ST_BSR | ST_LONG_ERASE | ST_PHYSREC), \
        8000000, 30, 30, 30, 30, 60, 60, 60, 60, \
        0x00, 0x00, 0x00, 0x00, 0, 0, 0, 0 }, \

This makes the kernel identify the drive as an EXABYTE on just the first
7 characters of the Vendor/Product ID. Add this AFTER other Exabyte
entries you already have.

To st_conf.c make the following additon:

/* Exabyte 8200SX 8mm 2GB cartridge */
{
        "Exabyte EXB-8200SX 8mm Helical Scan", 16, "EXABYTE 8200SX ",
        ST_TYPE_EXABYTE, 1024,
        (ST_VARIABLE | ST_BSF | ST_BSR | ST_LONG_ERASE | ST_AUTODEN_OVERRIDE),
        5000, 5000,
        { 0x00, 0x00, 0x00, 0x00 },
        { 0, 0, 0, 0 }
},

I made this entry below the others for Exabytes, but I think it should
be able to go anywhere.

Then do a "make" in your kernel directory.

Hope this helps some one.

-- 
-------------------------------------------------------------------------------
Mike Reetz                          boulder.colorado.edu!morse!reetz
UNIX(tm) Operations Manager         or reetz@ncar.ucar.edu (<== BEST)
UCAR - University Corporation For Atmospheric Research 



This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:07:48 CDT