Return to BSD News archive
Newsgroups: comp.unix.bsd.freebsd.misc
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!simtel!news.kei.com!bloom-beacon.mit.edu!spool.mu.edu!howland.reston.ans.net!ix.netcom.com!netcom.com!kientzle
From: kientzle@netcom.com
Subject: ZIP drive, AIC6360, and 2.0R -> ``not configured''??
Message-ID: <kientzleDEq690.6uz@netcom.com>
Organization: NETCOM On-line Communication Services (408 261-4700 guest)
Date: Mon, 11 Sep 1995 05:07:47 GMT
Lines: 32
Sender: kientzle@netcom7.netcom.com
I've heard from people on this group that Iomega ZIP drives work
just fine with FreeBSD, and I was pleased when 2.0R's AIC6360
driver successfully probed my SoundBlaster16/SCSI2 interface.
But, so far I've had no luck getting it to work.
The initial probe sees the ZIP drive, but reports ``unit attention''
(is that an error??)
Once the system is up, attempts to disklabel or mount an
MSDOS-format disk are greeted with ``device not configured''
The drive is receiving commands (the light blinks) when I try
to mount it, but the mount fails.
I do intend to upgrade to 2.0.5R (or 2.1-stable, even) when I have
time (which isn't now!), but was hoping to be able to backup some
critical files to the ZIP drive now. (And for that matter, backup
everything to the ZIP drive before I did the upgrade!)
So, does anyone know what this problem is, or can suggest a quick
hack to get it minimally functioning? Is the problem likely with
a) me? (am I using the wrong mount or disklabel command?)
b) the aic6360 driver (will plugging a newer version of
aic6360.c work?)
c) some other part of the scsi interface software?
d) hardware? (ZIP drive is the only thing on the SCSI
chain, and, yes, it is terminated)
Any help appreciated...
- Tim
kientzle@netcom.com