Return to cy.4 CVS log

Up to [CSRG BSD Unix] / 43BSDTahoe / man / man4 / tahoe

Annotation of 43BSDTahoe/man/man4/tahoe/cy.4, revision 1.1

1.1     ! root        1: .\" Copyright (c) 1986 Regents of the University of California.
        !             2: .\" All rights reserved.  The Berkeley software License Agreement
        !             3: .\" specifies the terms and conditions for redistribution.
        !             4: .\"
        !             5: .\"    @(#)cy.4        6.3 (Berkeley) 7/8/88
        !             6: .\"
        !             7: .TH CY 4 "July 8, 1988"
        !             8: .UC 7
        !             9: .SH NAME
        !            10: cy \- Cipher/tapemaster magtape interface
        !            11: .SH SYNOPSIS
        !            12: .B "controller cy0 at vba? csr 0xffff4000 vector cyintr"
        !            13: .br
        !            14: .B "device yc0 at cy0 drive 0"
        !            15: .SH DESCRIPTION
        !            16: The Cipher F880, M990/Tapemaster combination provides a standard tape drive
        !            17: interface as described in
        !            18: .IR mt (4).
        !            19: The Cipher F880 tape drive operates at 1600 or 3200 bpi \-
        !            20: controlled by a switch on the drive. 
        !            21: The Cipher M990 operates at 1600, 3200 or 6250 bpi \-
        !            22: controlled by switches on the front of the drive.
        !            23: .PP
        !            24: The Tapemaster controller board is actually a Multibus controller
        !            25: accessed through a Halversa Multibus to VERSAbus converter card.
        !            26: .SH "SEE ALSO"
        !            27: mt(1), tar(1), mtio(4)
        !            28: .SH DIAGNOSTICS
        !            29: \fBcy%d: %dkb buffer\fP.  The formatter was found to have a
        !            30: %d kilobyte buffer during autoconfiguration.
        !            31: .PP
        !            32: \fBcy%d: timeout or err during init, status=%b\fP.  The controller
        !            33: timed out or an error occurred on a nop command during autoconfiguration;
        !            34: the controller may be hung.
        !            35: .PP
        !            36: \fBcy%d: configuration failure, status=%b\fP.  The controller
        !            37: timed out or an error occurred on a configure command during
        !            38: autoconfiguration; the controller may be hung.
        !            39: .PP
        !            40: \fByc%d: no write ring\fR.  An attempt was made to write on the tape drive
        !            41: when no write ring was present; this message is written on the terminal of
        !            42: the user who tried to access the tape.
        !            43: .PP
        !            44: \fByc%d: not online\fR.  An attempt was made to access the tape while it
        !            45: was offline; this message is written on the terminal of the user
        !            46: who tried to access the tape.
        !            47: .PP
        !            48: \fBcy%d: i/o size too large\fP.  A read or a write request exceeded the
        !            49: maximum transfer size for the controller \- 32 kilobytes; this message
        !            50: is written on the terminal of the user who made the read or write request.
        !            51: .PP
        !            52: \fByc%d: hard error bn%d status=%b\fR.   A tape error occurred
        !            53: at block \fIbn\fR; the cy error register is
        !            54: printed in hexadecimal with the bits symbolically decoded.  Any error is
        !            55: fatal on non-raw tape; when possible the driver will have retried
        !            56: the operation which failed several times before reporting the error.
        !            57: For known errors, the trailing %s is one of the following:
        !            58: .RS
        !            59: \fBtimeout\fP, \fBtimeout1\fP, \fBtimeout2\fP, \fBtimeout3\fP, \fBtimeout4\fP. 
        !            60: Time out errors; this may be due to trying to read a blank tape
        !            61: or the controller failing to interrupt or the drive dropping off-line.
        !            62: .PP
        !            63: \fBnon-existent memory\fP.  A controller transfer to memory timed out.
        !            64: .PP
        !            65: \fBblank tape\fP.  The controller detected a blank tape when
        !            66: data was expected.
        !            67: .PP
        !            68: \fBmicro-diagnostic\fP, \fBmissing diagnostic jumper\fP. 
        !            69: An error occurred in the micro-diagnostics or
        !            70: the diagnostic mode jumper was not installed while attempting to execute
        !            71: a diagnostics command.
        !            72: .PP
        !            73: \fBeot/bot detected\fP.  The controller unexpectedly encountered
        !            74: end-of-tape or beginning-of-tape during an operation.
        !            75: .PP
        !            76: \fBretry unsuccessful\fP.  
        !            77: An error occurred which could not be recovered by repeated retries.
        !            78: .PP
        !            79: \fBfifo over/under-flow\fP.
        !            80: The controller was unable to transfer data to the drive fast enough.
        !            81: This usually occurs because a transfer was performed without using the
        !            82: controller's internal buffer.
        !            83: .PP
        !            84: \fBdrive to controller parity error\fP.
        !            85: A parity error was detected by the controller in data transferred
        !            86: between the drive and the controller's internal buffer.
        !            87: .PP
        !            88: \fBprom checksum\fP.
        !            89: The controller thinks its PROM is corrupted.
        !            90: .PP
        !            91: \fBtime out tape strobe (record length error)\fP.
        !            92: The controller timed out while looking for an inter-record gap.
        !            93: This usually occurs because the records on the tape are larger than
        !            94: expected (or can be handled).
        !            95: .PP
        !            96: \fBtape not ready\fP.
        !            97: The drive does not respond; usually the power has been turned off
        !            98: or a cable has come off.
        !            99: .PP
        !           100: \fBwrite protected\fP.
        !           101: A write ring was present in the tape when a write was attempted.
        !           102: .PP
        !           103: \fBinvalid link pointer\fP.
        !           104: An invalid pointer was encountered in a tape parameter block.
        !           105: .PP
        !           106: \fBunexpected file mark\fP.
        !           107: A tape file mark was encountered while trying to read or space.
        !           108: .PP
        !           109: \fBinvalid byte count\fP.
        !           110: An invalid byte count parameter was encountered in a tape parameter
        !           111: block.
        !           112: .PP
        !           113: \fBunidentified hardware error\fP, \fBstreaming terminated\fP.
        !           114: These should not happen.
        !           115: .RE
        !           116: .PP
        !           117: \fByc%d: lost interrupt\fP.
        !           118: The controller failed to respond with an interrupt signifying completion
        !           119: of the current command.  The system will attempt to abort the
        !           120: outstanding command and reset the controller.
        !           121: .PP
        !           122: \fBcy%d: reset failed\fP.
        !           123: The system was unable to reset the controller.  This is normally preceded
        !           124: by another message from the driver.
        !           125: .SH BUGS
        !           126: The controller supports only 20-bit addresses.  The only way the
        !           127: system can insure the controller will be able to address data
        !           128: to be transferred
        !           129: is to copy it into an intermediate buffer allocated in the first megabyte
        !           130: of system memory.

This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.