Date: Tue, 21 May 1996 11:26:27 -0500 (EST) From: John Fieber <jfieber@indiana.edu> To: freebsd-scsi@freebsd.org Subject: Archive Viper not correctly identified Message-ID: <Pine.NEB.3.93.960521111933.292B-100000@Fieber-John.campusview.indiana.edu>
next in thread | raw e-mail | index | archive | help
Hi, I just switched from 2.1R to the May 1st snapshot and now my trusty old Archive Viper tape drive is not correctly identified. I poked around it appears as though it *should* be identified, but it comes up with the default densities identified in "mode_unktape": jfieber:/sys/scsi $ mt status Present Mode: Density = 0x00 Blocksize = 512 bytes ---------available modes--------- Mode 0: Density = 0x00 Blocksize variable Mode 1: Density = X3.136-1986 Blocksize = 512 bytes Mode 2: Density = X3.39-1986 Blocksize variable Mode 3: Density = X3.54-1986 Blocksize variable rather than the densities defined in "mode_archive150". Needless to say, it doesn't work unless I manually set the density to QIC-150 with the mt command. The drive reports itself as: (aha0:2:0): "ARCHIVE VIPER 150 21247 -005" type 1 removable SCSI 1 st0(aha0:2:0): Sequential-Access density code 0x0, 512-byte blocks, write-protected Any clue as to why this isn't being identified? -john == jfieber@indiana.edu =========================================== == http://fallout.campusview.indiana.edu/~jfieber ================
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.NEB.3.93.960521111933.292B-100000>