home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.unix.pc-clone.32bit
- Path: sparky!uunet!virtech!cpcahil
- From: cpcahil@vti.com (Conor P. Cahill)
- Subject: Re: scsi tape problems on isc 3.0
- Message-ID: <C0qrxp.6H9@vti.com>
- Organization: Virtual Technologies Inc.
- References: <1993Jan11.013407.2303@dogtag.uucp>
- Distribution: na
- Date: Tue, 12 Jan 1993 12:56:11 GMT
- Lines: 32
-
- rwj@dogtag.uucp (Rob Janes) writes:
-
- >I've been kind of banging my head against the wall here- I can't figure
- >out how to get this archive viper tape drive recognized by the kernel.
- >A scsi probe reveals scsi 1 and 2 are hard disks, and scsi 4 is the
- >archive viper. The light on the viper comes on, so it looks like the
- >hardware is working to some extent.
-
- Why are you not using the HPDD configuration to configure the tape drive.
- I have installed something like 10 different tape drives using the
- HPDD configuration without a problem.
-
- to do this just go into the HPDD configuration, boot controller
- config, set the parameters (yes, you need to remember them and
- set them), select basic device config, change the entries for target
- 1 and 2 to DISK and the entry for target 4 to TAPE. Then you are
- done. Just rebuild, install, reboot and the tape device is created.
-
-
- >3 rebuilt the kernel, rebooted, there was no /dev/tape, so I made
- > one, major 41, minor (scsi id 4*16+8) 72. Guess the node.d/tape wasn't
- > set up.
-
- The HPDD will configure a device with the name /dev/rmt{ctrlr}t{target},
- so assuming you put the tape on your first controller, the node would be
- named /dev/rmt0t4.
-
- --
- *** SENTINEL(tm) The ultimate Debugging Environment - email for more info ***
-
- Conor P. Cahill (703)430-9247 cpcahil@virtech.vti.com
- Virtual Technologies, Inc. 46030 Manekin Plaza Dulles, VA 20166
-