Return to BSD News archive
Path: sserve!newshost.anu.edu.au!munnari.oz.au!bunyip.cc.uq.oz.au!harbinger.cc.monash.edu.au!msuinfo!agate!howland.reston.ans.net!gatech!udel!newsserv.cs.sunysb.edu!stark.UUCP!stark!stark!gene
From: stark!gene@newsserv.cs.sunysb.edu (Gene Stark)
Newsgroups: comp.os.386bsd.questions
Subject: Re: FreeBSD and Archive SC499 tape-drive controller/drive
Date: 17 Jan 94 09:19:16
Organization: Gene Stark's home system
Lines: 48
Message-ID: <STARK!GENE.94Jan17091916@stark.uucp>
References: <1994Jan8.225334.13131@news.uit.no>
NNTP-Posting-Host: stark.uucp
In-reply-to: thostr@autotelia.Isv.Uit.NO's message of Sat, 8 Jan 1994 22:53:34 GMT
In article <1994Jan8.225334.13131@news.uit.no> thostr@autotelia.Isv.Uit.NO (Thomas Strandenaes) writes:
I'm trying to use my Archive SC499 QIC02/24 controller with a Archive
60 meg tape drive. I have configured and compiled a kernel with the
QIC-2 support enabled, i.e
device wt0 at isa? port 0x340 bio irq 5 drq 1 vector wtintr
and upon booting the kernel reports:
wt0: <Archive>
So far so good. When I try to use 'mt', 'tar' or any other utility to
talk with the tape-streamer at /dev/rwt* (it's rwt0b for 60 meg drives,
right?) or /dev/nrwt*, I get a syslog message
wt0: Illegal command
I have been using the wt driver with an SC499 controller for a few months.
The line in my config file is as follows:
device wt0 at isa? port 0x100 bio irq 7 drq 1 vector wtintr
I have made devices as follows:
crw-r--r-- 1 root 10, 8 Nov 21 09:26 /dev/qic11
crw-r--r-- 1 root 10, 16 Jan 4 14:16 /dev/qic24
The names are probably not standard, but they help me keep track of what
format the tape is getting written in. There really isn't much in the
way of documentation on what minor device numbers to use; I had to read
the driver code to figure it out. Note that the numbering scheme seems
to have changed in FreeBSD 1.0.2 from one of the earlier versions, so
this may be your problem. The above devices are the rewinding kind,
if you want non-rewinding, have a look at the driver for the extra bit
to set in the minor.
I am sort of happy with the driver. It streams the tape under dump
and restore, as long as there is not much else going on in the system.
I haven't been able to get much streaming with tar. I tried using dd
with large block sizes and caused at least one system crash, so I don't
do that at the moment. The error recovery of the driver is not very
good. If you try to read at the wrong density, you have to execute
a successful rewind or control command before you can then read at
the correct density.
- Gene Stark
--