Release Notes PN 40002072_B SCSIScsi Terminal Server(TM) Module Driver 1.30 IRIX versions 6.4 & 6.5 Software Driver P/N 40002072_B Source Code P/N 81000136_B Release Notes P/N 93000358_B June 20, 2000 INTRODUCTION Software driver for using SCSI Terminal Server(TM) serial and parallel port units with IRIX 6.4 and 6.5. SUPPORTED PRODUCTS This is the list of units the driver will work with. Some of these units may be legacy units. X1800, X/SM-5008, SM-5016, SP-1003, ST-1002, ST-1008/X, ST-1016G, ST-1032, ST-1400, ST-1400X, ST-1600, ST-1610, ST-1620,ST-1622, ST1800*, ST-1800X+, ST-2000/X, SX4032. This driver does NOT support Etherlite units. Contact SGI concerning Etherlite units. ENHANCEMENTS None. BUG FIXES This version of the driver eliminates problems caused by the SCSI read_buffer command not working on certain models of SGI computers. This version of the driver determines the number of ports each unit supports based on a table lookup of all known Digi (and formerly Central Data) SCSI units made. KNOWN LIMITATIONS The IRIX 6.5 wd93 SCSI driver for the Indy and Challenge S (IP22) platforms does not renegotiate correctly with SCSI devices after a check condition. If sync has been negotiated, and after the STS device resets itself, the SCSI driver does not renegotiate. Thus, the wd93 is talking in sync mode, and the STS is attempting to communicate in async mode, and the end result is an endlessly resetting SCSI bus. The workaround is to edit the file /var/sysgen/master.d/wd93, read the comments about the variable wd93_syncenable, and turn off sync negotiation for the target IDs that the STS units are at. There is nothing which can be done by Digi software to correct this problem. Not all IRIX 6.4 applications seem to understand the concept of split baud rates correctly. Apps such as getty set only the ospeed parameter, leaving the ispeed parameter at 9600. Since this isn't the desired behavior of getty, the STS device driver, likewise, does not support split baud rates. 0xFF expansion (on receipt of breaks or parity errors) is currently not enabled if the PARMRK input flag is set. Digi's proprietary "baud extensions" -- as described in man cdstty(1) -- are not supported. Use the IRIX stty utility to set all baud rates. WHAT IS CONTAINED IN THIS RELEASE This package consists of these subsystems: sts.sw.base Base software required to use STS products. sts.man.manpages On-line manual pages for STS. sts.man.more Additional documentation for STS products. sts.man.relnotes These release notes. DOCUMENTATION Consult these man pages for further information on using STS devices: sts(7) cdmknods(1) cdflush(1) cdscanbus(1) cdstty(1) cdupdate(1) Additional documentation on setup and use can be found on your system at /usr/local/STS/docs/. If you have Internet access, information on setup and use can be found at Digi's home at the World Wide Web at http://www.digi.com/ Follow the links to IRIX technical support. Links to recommended products, tips on serial programming, PPP configuration and wiring diagrams are also provided. Serial programming information can be found by reading the man page for termios(3t). Other man pages of interest may be serial(7), uugetty(1m), getty(1m), and ppp(1m). TO INSTALL THIS DRIVER ******************************************************************** ******************* IMPORTANT IRIX 6.4 NOTE ************************ You MUST have these SGI patches, or their successors, installed BEFORE installing the STS driver: 2837, 2871, and 2344. The driver installation will FAIL if those patches (or their successors) are not installed. This is for IRIX 6.4 only. ******************************************************************** ******************************************************************** **** Important note for Indy, Challenge S, and Indigo^2 users ****** To ensure that the serial ports are in a known state at system boot, the STS driver always resets STS devices at system initialization time which results in a SCSI check condition. The IRIX 6.5 wd93 SCSI driver, however, does not correctly renegotiate SCSI modes when a check condition occurs, resulting in mismatched SCSI parameters and a dead SCSI SCSI bus. This problem affects the Indy, Challenge S, and Indigo^2. The workaround is to edit the file /var/sysgen/master.d/wd93 and modify the wd93_syncenable variable. Read the comment associated with that variable, and disable the bits associated with the STS device to disable synchronous SCSI mode for scsiTerminal Server's target ID. ******************************************************************** The driver package which has a .sis extension must be made executable with chmod and then executed to unpack the contents. After any necessary patches have been installed, run the ./Install script from the install directory (e.g. /usr/sts). If you see error messages about undefined structures in IRIX 6.4, you have a patch missing -- ensure all required patches are loaded. The Install script will also ensure the STS "daemon" driver has been removed. The "daemon" driver and the kernel driver cannot coexist on the same system! (The "daemon driver" is a previous release of the STS driver for IRIX 6.4 and is fundamentally incompatible with the current software). The Install script will also check for the existence of any IRIX 5.3, 6.2, or 6.3 STS drivers which may be on the system as a result of an upgrade to IRIX 6.5 from an older version of IRIX. HISTORY R1.20 This package is the first combined IRIX 6.4/6.5 release -- support for both IRIX 6.4 and 6.5 is included in this package. The install procedure now includes the ability to select a "base directory" other than /usr/local/STS/. The Install procedure has been modified to detect the presence of older STS drivers which might be on the machine as a result of an upgrade to IRIX 6.5 from IRIX 6.3, 6.2, or 6.3. The previous release of the IRIX 6.5 driver was confused if an older STS driver was installed on the machine. The current Install will detect the driver and warn the user to first remove the older software before proceeding. The STS driver uses a special class of SCSI commands to get information about the STS hardware it is communicating with. These 10-byte commands do not appear to be fully supported under IRIX 6.5 on the O2 (IP32), which resulted in incorrect tty counts at best, and panics or hangs at worst. This problem has been worked around my more stringent sanity checks, and repeatedly issuing the SCSI READ BUFFER command until the returned data appears correct. -end of release notes.