Summary: 8505XL Kernel mods SUN/OS

From: Mike Rhyner x6-2354 (rhyner@comm.mot.com)
Date: Mon Jun 12 1995 - 13:23:52 CDT


Here is the info I received from Exabyte for modifying the
kernel for SUN/OS. Other helpful hints are included.

Thank you to all who replied,

------------------------------------------------------------------------------------------------------
> EXABYTE INTEGRATION NOTES
> SUN4C & SUN4M PLATFORMS
> SUNOS 4.X
> 12/14/94 9:32 AM
> This document has been produced in an effort to provide basic kernel patch information for integrating
> Exabyte tape drives onto a Sun workstation running SunOS 4.x. An effort has been made to assure that this
> information is as accurate as possible. Use this information at your own risk. Exabyte Corporation reserves
the right to change this document at anytime. This document is not intended to be a step by step guide but
rather a general source of information intended for experienced system administrators. If you don't feel
comfortable with making these changes, it is recommended that you turn to an experienced UNIX wizard or, refer
to your system documentation.
>
> In general, most systems running SunOS 4.X should have default support for the EXB-8200 and the
> EXB-8500. Most other Exabyte products will require a modification to the kernel in order to be recognized by
the OS. The file to modify is the st_conf.c file located in: /usr/kvm/sys/scsi/targets. It is recommended that
you look at the entries for the EXB-8200 and the EXB-8500 to serve as a guide. The entry for the EXB-8500
should look something like:
>
> /* Exabyte 8mm 5GB cartridge */
> {
> "Exabyte EXB-8500 8mm Helical Scan", 16, "EXABYTE EXB-8500",
> ST_TYPE_EXB8500, 1024,
> (ST_VARIABLE | ST_BSF | ST_BSR | ST_LONG_ERASE),
> 5000, 5000,
> { 0x14, 0x15, 0x8C, 0x8C }, <= Density code parameters note: see last page for
> { 0, 0, 0, 0 } explanation.
> },
>
> The following pages will contain the required entry for the non-supported Exabyte drives. After you have
edited the st_conf.c with the appropriate entry, it will then be necessary to make a new kernel for the
changes to take effect. WARNING!!! It is absolutely essential that you have a good working knowledge of how to
remake your kernel. Information on how to remake your kernel is beyond the scope of this document and Exabyte
technical support in general. If you are unsure, don't proceed without help or d
> umentation.
>
> Comments / questions:
> Craig Barnes
> Technical Support Engineer
> Exabyte Corporation
> voice: 800-445-7736 ext. 7846
> fax: 303-447-7890
> email: support@exabyte.com
>
> The following are examples of the entries in the st_conf.c file you need to make depending on which Exabyte
drive you have:
>
> EXB-8500C:
>
> /* Exabyte 8mm w/compression (Full-high) */
> {
> "Exabyte EXB-8500C 8mm Helical Scan", 16, "EXABYTE EXB8500C",
> ST_TYPE_EXB8500, 1024,
> (ST_VARIABLE | ST_BSF | ST_BSR | ST_LONG_ERASE | ST_KNOWS_EOD),
> 5000, 5000,
> { 0x14, 0x15, 0x90, 0x8C },
> { 0, 0, 0, 0 }
> },
>
> EXB-8505 and EXB-8505XL:
>
> /* Exabyte 8mm w/compression (Half-high) */
> {
> "Exabyte EXB-8505 8mm Helical Scan", 16, "EXABYTE EXB-8505",
> ST_TYPE_EXB8500, 1024,
> (ST_VARIABLE | ST_BSF | ST_BSR | ST_LONG_ERASE | ST_KNOWS_EOD),
> 5000, 5000,
> { 0x14, 0x15, 0x90, 0x8C },
> { 0, 0, 0, 0 }
> },
>
> EXB-8205 and EXB-8205XL:
>
> /* Exabyte 8mm w/compression (Half-high) */
> {
> "Exabyte EXB-8205 8mm Helical Scan", 16, "EXABYTE EXB-8205",
> ST_TYPE_EXABYTE, 1024,
> (ST_VARIABLE | ST_BSF | ST_BSR | ST_LONG_ERASE | ST_KNOWS_EOD),
> 5000, 5000,
> { 0x14, 0x90, 0x0C, 0x0C },
> { 0, 0, 0, 0 }
> },
>
>
>
>
>
> EXB-4200:
>
> /* Exabyte 4mm DAT cartridge */
> {
> "Exabyte EXB-4200 4mm Helical Scan", 16, "EXABYTE EXB-4200",
> ST_TYPE_DEFAULT, 512,
> (ST_VARIABLE | ST_BSF | ST_BSR | ST_LONG_ERASE | ST_KNOWS_EOD),
> 5000, 5000,
> { 0x00, 0x0C, 0x0C, 0x0C },
> { 0, 0, 0, 0 }
> },
>
> EXB-4200C:
>
> /* Exabyte 4mm DAT w/compression cartridge */
> {
> "Exabyte EXB-4200C 4mm Helical Scan", 17, "EXABYTE EXB-4200C",
> ST_TYPE_DEFAULT, 512,
> (ST_VARIABLE | ST_BSF | ST_BSR | ST_LONG_ERASE | ST_KNOWS_EOD),
> 5000, 5000,
> { 0x63, 0x43, 0x0C, 0x0C },
> { 0, 0, 0, 0 }
> },
>
> EXB-2501:
> *Note: In order to boot from an EXB-2501 or EXB-2501C, it will be necessary to jumper pins 5 & 6 of the
drive option jumpers (refer to installation and operation manual).
>
> /* Exabyte 1Gb cartridge tape */
> {
> "Exabyte 2501", 16, "EXABYTE EXB-2501",
> ST_TYPE_DEFAULT, 512,
> (ST_QIC | ST_BSF | ST_BSR | ST_FIXED | ST_LONG_ERASE | ST_KNOWS_EOD),
> 400, 400,
> { 0x00, 0x00, 0x00, 0x00 },
> { 0, 0, 0, 0 }
> },
>
>
>
>
>
>
> EXB-2501C:
> *Note: The only method to change from compression to non-compression is to jumper pins 1 & 2 of the drive
option jumpers (refer to installation and operation manual).
>
> /* Exabyte 2 Gb cartridge tape */
> {
> "Exabyte 2501C", 16, "EXABYTE EXB-2501",
> ST_TYPE_DEFAULT, 512,
> (ST_QIC | ST_BSF | ST_BSR | ST_FIXED | ST_LONG_ERASE | ST_KNOWS_EOD),
> 400, 400,
> { 0x00, 0x0C, 0x0C, 0x0C },
> { 0, 0, 0, 0 }
> },
>
> General Information:
> A common question asked by many callers is how to get the Exabyte drive to write in other densities for
compatibility reasons. The tape driver in SunOS defines multiple devices for each Exabyte drive found on the
system. If you look in the /dev directory, you will see devices such as; nrst0, nrst8, nrst16, etc. The
density the drive will write in depends on which device you select in your command (tar, dump, etc.). Another
item to note is that the SunOS expects the Exabyte tape drive to be at SCSI address
> or 5. The following table gives an example of a system with two 8505 tape drives, one at SCSI ID 4 and the
other at SCSI ID 5:
>
> Device Range Density Code Parameter Device to specify Density Drive
will write in
> 0-7 1st (0x14) nrst0 (Drive at ID 4) 8200 format
> nrst1 (Drive at ID 5)
>
> 8-15 2nd (0x15) nrst8 (Drive at ID 4) 8500 format
> nrst9 (Drive at ID 5)
>
> 16-23 3rd (0x90) nrst16 (Drive at ID 4) 8200 compressed
format
> nrst17 (Drive at ID 5)
>
> 24-31 4th (0x8C) nrst24 (Drive at ID 4) 8500 compressed format
> nrst25 (Drive at ID 5)
>
>
> Another common question pertains to parameters to use in the dump command. So far, the examples below seem
to work well:
>
> EXB-8200, 8205, 4200, 4200C: dump 1unbdsf 126 54000 6000 /dev/nrstx filename
>
> EXB-8500, 8500C, 8505: dump 1unbdsf 126 54000 13000 /dev/nrstx filename
>
>
>
>
>
>



This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:10:26 CDT