1TMSCP(4) Kernel Interfaces Manual TMSCP(4)
2
6 tmscp - DEC TMSCP magtape interface
7
9 /sys/conf/SYSTEM:
10 NTMSCP 1 # TMSCP controllers
12 NTMS 1 # TMSCP drives
13 TMSCP_DEBUG NO # debugging code in in TMSCP drive (EXPENSIVE)
14 /etc/dtab:
16 #Name Unit# Addr Vector Br Handler(s) # Comments
17 tms ? 174500 260 5 tmsintr # tmscp driver
18 tms ? 164334 0 5 tmsintr # alternate
19 major device number(s):
21 raw: 23
23 block: 12
24 minor device encoding:
26 bit: |7 | 6 | 5 | 4 | 3 | 2 | 1 | 0|
28 -------------------------------
29 C C X D D N U U
30 C = Controller # (max of 4 controllers)
32 D = Density
33 N = Norewind on close
34 U = Unit (drive) number (max of 4 drives per controller)
35
37 Tape controllers compatible with the DEC Tape Mass Storage Control Pro‐
38 tocol (TMSCP) architecture such as the TU81 and the TK50 provide a
39 standard tape drive interface as described in mtio(4). The controller
40 communicates with the host through a packet oriented protocol. Consult
41 the file <pdp/tmscp.h> for a detailed description of this protocol.
42
44 /dev/MAKEDEV script to create special files
45 /dev/MAKEDEV.local script to localize special files
46 The vector specified in /etc/dtab may be given as an explicit value in
48 which case autoconfig(8) will attempt to allocate the specified vector.
49 The vector may also be (if the system is at revision level 100 or
50 higher) given as 0 - in which case autoconfig(8) will request the ker‐
51 nel to allocate the next available vector (beginning at 01000 and pro‐
52 ceeding downward) which autoconfig(8) will initialize.
53 Multiple drives on a single controller are supported. Multiple con‐
55 trollers are also supported.
56 Density selection is specified by bits 3 and 4 in the minor device num‐
58 ber. A value of 0 requests the lowest density of a drive and a value
59 of 3 the highest density. Values of 1 and 2 are essentially equivalent
60 (because because TMSCP only defines values for three densities) and
61 request the middle density (for tri-density tape drives).
62
64 tms: !drives. Not enough drives were declared when the kernel was
65 built. The NTMS parameter in the kernel config file needs to be
66 increased by at least one.
67 tms%d stepN init failed: sa %x. Step N of the 4 step initialization
69 sequence has failed.
70 tms%d: random intr. An unexpected interrupt was received. This is
72 indicative of some other device using the same interrupt vector as the
73 TMSCP controller. The interrupt is ignored.
74 tms%d Ver %d Mod %d. The version and model number of the controller
76 are displayed when the controller is initialized. This is an informa‐
77 tion message and not an error.
78 tms%d: state %d. The controller state is not one of the 4 initializa‐
80 tion states or the RUN state. This indicates a serious problem in the
81 driver and possibly the hardware.
82 tms%d: fatal error %x. The controller detected a ``fatal error'' in
84 the status returned to the host. The contents of the status register
85 are displayed.
86 tms%d init fail. The controller failed to initialize. Indicative of a
88 hardware problem.
89 tms%d,%d flush fail. The cache failed to flush during a close opera‐
91 tion. Data loss is possible in this case.
92 tms%d,%d: sa %x state %d. A fatal error. The controller will be reset
94 in an attempt to resume operation.
95 tms ioctl. An invalid internal ioctl function call has been made.
97 This is a driver bug.
98 tms%d,%d inv end. An invalid end (completion) code has been detected.
100 A drive has returned 0 as the opcode originally issued. This is a
101 hardware problem.
102 tms%d,%d bad rsp: %x. An unrecognized response has been received.
104 This is a driver bug.
105 tms%d,%d cache lost The cache on the drive has been lost. Data loss is
107 likely. Usually due to a hardware problem.
108 The following error is produced when a TMSCP error log datagram is
110 received:
111 tms%d,%d dgram fmt=%x evt=%x grp=%x flg=%x pos=%D.
113 Earlier versions of the driver consumed a noticeable amount of kernel
115 D-space decoding and pretty printing more detailed information. This
116 has been removed in favor of a shorter message. In the future an error
117 log daemon will be written and the datagrams from the MSCP and TMSCP
118 drivers passed to it for analysis.
119
121 mt(1), tar(1), tp(1), mtio(4), tm(4), ts(4), ut(4), dmesg(8), dtab(5),
122 autoconfig(8)
123
125 If any non-data error is encountered on non-raw tape, it refuses to do
126 anything more until closed.
127 On quad-density tape drives (the Kennedy 9662 for example) the middle
129 density of 3200bpi is not host selectable (it can be manually selected
130 from the drive's front panel) because TMSCP only defines 800, 1600 and
131 6250bpi.
1323rd Berkeley Distribution December 22, 1995 TMSCP(4)