Date: Mon, 27 May 1996 15:23:38 +0930 (CST) From: Michael Smith <msmith@atrad.adelaide.edu.au> To: jfieber@indiana.edu (John Fieber) Cc: current@freebsd.ORG Subject: Re: Archive Viper not correctly identified. Message-ID: <199605270553.PAA25819@genesis.atrad.adelaide.edu.au> In-Reply-To: <Pine.NEB.3.93.960526222322.735C-100000@Fieber-John.campusview.indiana.edu> from "John Fieber" at May 26, 96 10:30:57 pm
next in thread | previous in thread | raw e-mail | index | archive | help
John Fieber stands accused of saying: > > [I posted this to scsi a while ago, no responese. Does anybody > read it?] Yup, don't recall your post though. > 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 I have one of these on a machine running this SNAP. > 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 Weird; I haven't had any problems with mine, it's running A-OK reading 120's and writing 150 and 250's. I don't get the 'known rogue' message though, so it's possible I'm just not tickling the problem. > -john -- ]] Mike Smith, Software Engineer msmith@atrad.adelaide.edu.au [[ ]] Genesis Software genesis@atrad.adelaide.edu.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control (ph/fax) +61-8-267-3039 [[ ]] Collector of old Unix hardware. "Where are your PEZ?" The Tick [[
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199605270553.PAA25819>