*BSD News Article 29584


Return to BSD News archive

Xref: sserve comp.periphs.scsi:19551 comp.os.386bsd.questions:9848
Newsgroups: comp.periphs.scsi,comp.os.386bsd.questions
Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!bunyip.cc.uq.oz.au!munnari.oz.au!news.Hawaii.Edu!ames!sgiblab!nbn!news.nbn.com!fen
From: fen@imagine.comedia.com (Fen Labalme)
Subject: Re: Help with Wangtek 6200HS (NetBSD-0.9)
In-Reply-To: rab@hal.cwru.edu's message of 12 Apr 1994 13:27:10 GMT
Message-ID: <FEN.94Apr12144841@imagine.comedia.com>
Sender: news@nbn.com
Organization: Broadcatch Technologies, San Francisco
References: <2oe7je$928@usenet.INS.CWRU.Edu>
Date: Tue, 12 Apr 1994 21:48:41 GMT
Lines: 41

In article <2oe7je$928@usenet.INS.CWRU.Edu> rab@hal.cwru.edu (Roger A.
Bielefeld) writes:

Roger> I've got a Wangtek 6200HS DAT drive from the last group
Roger> purchase on comp.periphs.scsi.  I'm trying to get it working...

For what it's worth, I bought one under perhaps the same group
purchase and it works flawlessly for me on my Mac running OS 7.1
and Retrospect 2.0 backup software.  Good luck!

But I am having trouble getting it recognized by my '486 NetBSD-0.9
system.  (Note:  I have an internal SCSI disk and an external SCSI
CD-ROM that both work just fine off my Adaptec 1542C adapter.)  I have
some ideas, a combination of which might lead to a working system, but
I know little about these internals.  Some guidance would be muchly
appreciated!

1)  the 386BSD FAQ says:
                     ...the original SCSI drivers didn't recognize any 
	devices past the first two (ID 0 and ID 1).  Also, there was a bug 
	in the distribution floppy regarding the devices at ID 6.  The 
	'dev' files for that id need to be remade.  Use MAKEDEV to do that.

I think that 1) this FAQ is out of date (?), and 2) I know I can use a
different ID than 6, but how do I check devices at ID 6 in any case?
And how do I use MAKEDEV to fix 'em?  (I read /dev/MAKEDEV and saw
nothing having to do with SCSI device ID number configurations.)

2)  "/sbin/dump 0uf /dev/nrst0 /tmp" --> "bad sblock magic number"
What does this mean?  Is /dev/nrst0 the correct device to use?  How
can I tell?  (Note:  "ls -l /dev/nrst0" yields the following:
crw-r-----    1 root     wheel     14,   1 Jul 21  1993 /dev/nrst0)

Thanks in advance for any help you can offer.
--
Fen
~~~                        WE ARE EVERYWHERE!     JUST SAY "KNOW"!
Fen Labalme                for EFF info,  email <eff@eff.org>
Broadcatch Technologies    for LPF info,  email <lpf@uunet.uu.net>
<fen@comedia.com>          for CPSR info, email <cpsr@cpsr.org>
PGP Key ID: 1024/0AF8FD    for TLG info,  email <info@tlg.org>