Date: Sun, 26 May 1996 22:30:57 -0500 (EST) From: John Fieber <jfieber@indiana.edu> To: current@freebsd.org Subject: Archive Viper not correctly identified. Message-ID: <Pine.NEB.3.93.960526222322.735C-100000@Fieber-John.campusview.indiana.edu>
next in thread | raw e-mail | index | archive | help
[I posted this to scsi a while ago, no responese. Does anybody
read it?]
I recently jumped from 2.1R to 2.2-960501-SNAP. Now, my Archive
Viper is apparently not being identified properly as a
"known rogue". At boot I get this:
(aha0:2:0): "ARCHIVE VIPER 150 21247 -005" type 1 removable SCSI 1
st0(aha0:2:0): Sequential-Access density code 0x0, drive empty
But rather than defaulting to the appropriate QIC-150 and QIC-120
densities as identified in the scsiconf code, it defaults to
those densities identified in the "unknown" tape device. I have
to manually set the density for it to work. Any scsi code gurus
care to speculate on this. It looks to me like it should match
the entry in scsiconf.c:
{
T_SEQUENTIAL, T_SEQUENTIAL, T_REMOV, "ARCHIVE", "VIPER 150", "*",
"st", SC_ONE_LU, ST_Q_NEEDS_PAGE_0, mode_archive150
},
-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.960526222322.735C-100000>