9 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
A few of our machines need upgrading and we are looking into a selection of processors at present. There are suggestions on the vendor's websites that the L3 cache was specifically introduced for gamers. Is this true? Does having L1, L2 and/or L3 cache help at all in performance or are the... (0 Replies)
Discussion started by: figaro
0 Replies
2. AIX
I have an IBM pseries 7028-6E1 server with a six drive bay that is currently plugged into the scsi backplane of the motherboard. I am going to install a PCIX Ultra320 scsi raid adapter, and swing the drive bay over to it. I am just wondering how this is going to work. Should I power the server... (1 Reply)
Discussion started by: markper
1 Replies
3. UNIX for Dummies Questions & Answers
Folks;
Is there a command to know if my hardware can run 64-bit or 32-bit?
I'm trying to re-install SUSE 64-bit on one of our server but i'm not sure if this server hardware designed for 32-bit only or for both
Any help? (14 Replies)
Discussion started by: Katkota
14 Replies
4. UNIX for Dummies Questions & Answers
I would like to use my sunblade to firewall the connections to my desktop and laptop, these at the minute are on a wifi router. What is the best solution? (0 Replies)
Discussion started by: Kawakaze
0 Replies
5. AIX
I am looking to buy a 7044 - either a 170 or 270.
From what I can find on web searchs the 170 is NOT upgradable to more that one CPU? Is that correct?
Can I upgrade the planer on a 170 to a 270 to support multiple CPU's?
Does anyone have any other suggestion for AIX hardware? (5 Replies)
Discussion started by: dizman67
5 Replies
6. UNIX for Dummies Questions & Answers
I have an old pc, about 133-200 mhz with very little memory and hard-drive. I want to install a small and fast *nix system with ion or some other simple wm for maximal performance. It's supposed to be used as a desktop. If someone could share their experience with older machines and some... (2 Replies)
Discussion started by: riwa
2 Replies
7. Red Hat
HI
I have problem working with S3 Savage KM 133 Video Card on Redhat Linux 9 Enterprise Edition. It hangs up once probing done on Video Card.So i tried insalling Linux with options as to run the set up on 640*480. As knows case i searched the web forums to get help. Please let me know how can i... (0 Replies)
Discussion started by: prakashpichika
0 Replies
8. HP-UX
I've been asked by my copmpany to scour the web for a computer on which we can run HP-UX 11.i --- Is there a certain architecture type that I need or will any Compaq HP computer be fine for running HP-UX 11.i ??
Thanks!! (3 Replies)
Discussion started by: jalburger
3 Replies
9. UNIX for Dummies Questions & Answers
Does anyone know how to install a second Ethernet adapter on a Sun Sparc 10? (2 Replies)
Discussion started by: jskillet
2 Replies
TMSCP(4) Kernel Interfaces Manual TMSCP(4)
NAME
tmscp - DEC TMSCP magtape interface
SYNOPSIS
/sys/conf/SYSTEM:
NTMSCP 1 # TMSCP controllers
NTMS 1 # TMSCP drives
TMSCP_DEBUG NO # debugging code in in TMSCP drive (EXPENSIVE)
/etc/dtab:
#Name Unit# Addr Vector Br Handler(s) # Comments
tms ? 174500 260 5 tmsintr # tmscp driver
tms ? 164334 0 5 tmsintr # alternate
major device number(s):
raw: 23
block: 12
minor device encoding:
bit: |7 | 6 | 5 | 4 | 3 | 2 | 1 | 0|
-------------------------------
C C X D D N U U
C = Controller # (max of 4 controllers)
D = Density
N = Norewind on close
U = Unit (drive) number (max of 4 drives per controller)
DESCRIPTION
Tape controllers compatible with the DEC Tape Mass Storage Control Protocol (TMSCP) architecture such as the TU81 and the TK50 provide a
standard tape drive interface as described in mtio(4). The controller communicates with the host through a packet oriented protocol. Con-
sult the file <pdp/tmscp.h> for a detailed description of this protocol.
FILES
/dev/MAKEDEV script to create special files
/dev/MAKEDEV.local script to localize special files
The vector specified in /etc/dtab may be given as an explicit value in which case autoconfig(8) will attempt to allocate the specified vec-
tor. The vector may also be (if the system is at revision level 100 or higher) given as 0 - in which case autoconfig(8) will request the
kernel to allocate the next available vector (beginning at 01000 and proceeding downward) which autoconfig(8) will initialize.
Multiple drives on a single controller are supported. Multiple controllers are also supported.
Density selection is specified by bits 3 and 4 in the minor device number. A value of 0 requests the lowest density of a drive and a value
of 3 the highest density. Values of 1 and 2 are essentially equivalent (because because TMSCP only defines values for three densities) and
request the middle density (for tri-density tape drives).
DIAGNOSTICS
tms: !drives. Not enough drives were declared when the kernel was built. The NTMS parameter in the kernel config file needs to be
increased by at least one.
tms%d stepN init failed: sa %x. Step N of the 4 step initialization sequence has failed.
tms%d: random intr. An unexpected interrupt was received. This is indicative of some other device using the same interrupt vector as the
TMSCP controller. The interrupt is ignored.
tms%d Ver %d Mod %d. The version and model number of the controller are displayed when the controller is initialized. This is an informa-
tion message and not an error.
tms%d: state %d. The controller state is not one of the 4 initialization states or the RUN state. This indicates a serious problem in the
driver and possibly the hardware.
tms%d: fatal error %x. The controller detected a ``fatal error'' in the status returned to the host. The contents of the status register
are displayed.
tms%d init fail. The controller failed to initialize. Indicative of a hardware problem.
tms%d,%d flush fail. The cache failed to flush during a close operation. Data loss is possible in this case.
tms%d,%d: sa %x state %d. A fatal error. The controller will be reset in an attempt to resume operation.
tms ioctl. An invalid internal ioctl function call has been made. This is a driver bug.
tms%d,%d inv end. An invalid end (completion) code has been detected. A drive has returned 0 as the opcode originally issued. This is a
hardware problem.
tms%d,%d bad rsp: %x. An unrecognized response has been received. This is a driver bug.
tms%d,%d cache lost The cache on the drive has been lost. Data loss is likely. Usually due to a hardware problem.
The following error is produced when a TMSCP error log datagram is received:
tms%d,%d dgram fmt=%x evt=%x grp=%x flg=%x pos=%D.
Earlier versions of the driver consumed a noticeable amount of kernel D-space decoding and pretty printing more detailed information. This
has been removed in favor of a shorter message. In the future an error log daemon will be written and the datagrams from the MSCP and
TMSCP drivers passed to it for analysis.
SEE ALSO
mt(1), tar(1), tp(1), mtio(4), tm(4), ts(4), ut(4), dmesg(8), dtab(5), autoconfig(8)
BUGS
If any non-data error is encountered on non-raw tape, it refuses to do anything more until closed.
On quad-density tape drives (the Kennedy 9662 for example) the middle density of 3200bpi is not host selectable (it can be manually
selected from the drive's front panel) because TMSCP only defines 800, 1600 and 6250bpi.
3rd Berkeley Distribution December 22, 1995 TMSCP(4)