Date: Tue, 4 Jul 1995 23:09:48 -0400 (EDT) From: jfieber@grendel.csc.smith.edu (John Fieber) To: jmb@kryten.Atinc.COM (Jonathan M. Bresler) Cc: karl@bagpuss.demon.co.uk, spaz@u.washington.edu, FreeBSD-hackers@freefall.cdrom.com Subject: Re: mt grief? Message-ID: <199507050309.XAA15297@grendel.csc.smith.edu> In-Reply-To: <Pine.3.89.9507041921.A28859-0100000@kryten.atinc.com> from "Jonathan M. Bresler" at Jul 4, 95 07:46:32 pm
next in thread | previous in thread | raw e-mail | index | archive | help
Jonathan M. Bresler writes: > > > john, use 'mt -f /dev/rst0 fsf 1' to awaken the mt/kernel code. > > > every time i boot, i get error from the drive till i do this. then 'mt > > > -f /dev/rst0 rewind' and the thing works like a champ ;) > > > > interesting! what kind of drive are you using? > > Archive Viper 150. a known rogue device. see st.c > i have not ktrace'd it. dont know how to map the addresses > provided by ktrace into the proc's data space.....yet. Interesting, I have an Archive Viper 150 and no such jiggery pokery is required to make it work. Maybe this is a controller problem?? I'm afraid I missed the beginning of the discussion. I'm using: aha0: AHA-1542CF-V0.1, enabling mailbox, enabling residuals aha0: reading board settings, dma=5 int=11 (bus speed defaulted) . . . (aha0:2:0): "ARCHIVE VIPER 150 21247 -005" type 1 removable SCSI 1 st0(aha0:2:0): Sequential-Access st0: Archive Viper 150 is a known rogue density code 0x0, drive empty Be sure you have the density set correctly. I had great difficulty with a couple second-hand tapes until I discovered they were QIC 120 rather than the QIC 150 I had assumed. The drive can handle them just fine, once told what they are. :) -john === jfieber@cs.smith.edu ========== Come up and be a kite! --K. Bush ===
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199507050309.XAA15297>