1.\" Copyright (c) 1986, 1991, 1993 2.\" The Regents of the University of California. All rights reserved. 3.\" 4.\" %sccs.include.redist.man% 5.\" 6.\" @(#)cy.4 8.1 (Berkeley) 06/05/93 7.\" 8.Dd 9.Dt CY 4 tahoe 10.Os BSD 4.3t 11.Sh NAME 12.Nm cy 13.Nd Cipher/tapemaster magtape interface 14.Sh SYNOPSIS 15.Cd "controller cy0 at vba? csr 0xffff4000 vector cyintr" 16.Cd "device yc0 at cy0 drive 0" 17.Sh DESCRIPTION 18The Cipher 19.Tn F880 , 20.Tn M990 Ns / Tapemaster 21combination provides a standard tape drive 22interface as described in 23.Xr mt 4 . 24The Cipher 25.Tn F880 26tape drive operates at 1600 or 3200 27.Tn BPI \- 28controlled by a switch on the drive. 29The Cipher 30.Tn M990 31operates at 1600, 3200 or 6250 32.Tn BPI \- 33controlled by switches on the front of the drive. 34.Pp 35The Tapemaster controller board is actually a Multibus controller 36accessed through a Halversa Multibus to 37.Tn VERSAbus 38converter card. 39.Sh DIAGNOSTICS 40.Bl -diag 41.It cy%d: %dkb buffer. 42The formatter was found to have a 43.Ql %d 44kilobyte buffer during autoconfiguration. 45.It cy%d: timeout or err during init, status=%b. 46The controller 47timed out or an error occurred on a nop command during autoconfiguration; 48the controller may be hung. 49.It cy%d: configuration failure, status=%b. 50The controller 51timed out or an error occurred on a configure command during 52autoconfiguration; the controller may be hung. 53.It yc%d: no write ring. 54An attempt was made to write on the tape drive 55when no write ring was present; this message is written on the terminal of 56the user who tried to access the tape. 57.It yc%d: not online. 58An attempt was made to access the tape while it 59was offline; this message is written on the terminal of the user 60who tried to access the tape. 61.It cy%d: i/o size too large. 62A read or a write request exceeded the 63maximum transfer size for the controller \- 32 kilobytes; this message 64is written on the terminal of the user who made the read or write request. 65.It yc%d: hard error bn%d status=%b. 66A tape error occurred 67at block 68.Em bn ; 69the cy error register is 70printed in hexadecimal with the bits symbolically decoded. Any error is 71fatal on non-raw tape; when possible the driver will have retried 72the operation which failed several times before reporting the error. 73For known errors, the trailing 74.Ql %s 75is one of the following: 76.Pp 77.Bl -diag -offset indent -compact 78.It timeout, timeout1, timeout2, timeout3, timeout4. 79Time out errors; this may be due to trying to read a blank tape 80or the controller failing to interrupt or the drive dropping off-line. 81.It non-existent memory. 82A controller transfer to memory timed out. 83.It blank tape. 84The controller detected a blank tape when 85data was expected. 86.It micro-diagnostic, missing diagnostic jumper. 87An error occurred in the micro-diagnostics or 88the diagnostic mode jumper was not installed while attempting to execute 89a diagnostics command. 90.It eot/bot detected. 91The controller unexpectedly encountered 92end-of-tape or beginning-of-tape during an operation. 93.It retry unsuccessful. 94An error occurred which could not be recovered by repeated retries. 95.It fifo over/under-flow. 96The controller was unable to transfer data to the drive fast enough. 97This usually occurs because a transfer was performed without using the 98controller's internal buffer. 99.It drive to controller parity error. 100A parity error was detected by the controller in data transferred 101between the drive and the controller's internal buffer. 102.It prom checksum. 103The controller thinks its 104.Tn PROM 105is corrupted. 106.It time out tape strobe (record length error). 107The controller timed out while looking for an inter-record gap. 108This usually occurs because the records on the tape are larger than 109expected (or can be handled). 110.It tape not ready. 111The drive does not respond; usually the power has been turned off 112or a cable has come off. 113.It write protected. 114A write ring was present in the tape when a write was attempted. 115.It invalid link pointer. 116An invalid pointer was encountered in a tape parameter block. 117.It unexpected file mark. 118A tape file mark was encountered while trying to read or space. 119.It invalid byte count. 120An invalid byte count parameter was encountered in a tape parameter 121block. 122.It unidentified hardware error. 123.It streaming terminated. 124These should not happen. 125.El 126.Pp 127.It yc%d: lost interrupt. 128The controller failed to respond with an interrupt signifying completion 129of the current command. The system will attempt to abort the 130outstanding command and reset the controller. 131.Pp 132.It cy%d: reset failed. 133The system was unable to reset the controller. This is normally preceded 134by another message from the driver. 135.El 136.Sh SEE ALSO 137.Xr mt 1 , 138.Xr tar 1 , 139.Xr mtio 4 140.Sh HISTORY 141The 142.Nm 143driver appeared in 144.Bx 4.3 tahoe . 145.Sh BUGS 146The controller supports only 20-bit addresses. The only way the 147system can insure the controller will be able to address data 148to be transferred 149is to copy it into an intermediate buffer allocated in the first megabyte 150of system memory. 151