From owner-freebsd-current Sun May 26 20:31:05 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id UAA28027 for current-outgoing; Sun, 26 May 1996 20:31:05 -0700 (PDT) Received: from Fieber-John.campusview.indiana.edu (Fieber-John.campusview.indiana.edu [149.159.1.34]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id UAA28004 for ; Sun, 26 May 1996 20:30:59 -0700 (PDT) Received: from localhost (jfieber@localhost) by Fieber-John.campusview.indiana.edu (8.7.5/8.7.3) with SMTP id WAA02213 for ; Sun, 26 May 1996 22:30:58 -0500 (EST) X-Authentication-Warning: Fieber-John.campusview.indiana.edu: jfieber owned process doing -bs Date: Sun, 26 May 1996 22:30:57 -0500 (EST) From: John Fieber X-Sender: jfieber@Fieber-John.campusview.indiana.edu To: current@freebsd.org Subject: Archive Viper not correctly identified. Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk [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 ================