[8033] in linux-scsi channel archive
Re: Adding SCSI Iomega ZIP drive to existing Linux system...
daemon@ATHENA.MIT.EDU (Jeff Sutherland)
Mon Feb 7 08:55:49 2000
Message-ID: <389ECD63.8960F1AB@accelent.com>
Date: Mon, 07 Feb 2000 08:49:23 -0500
From: Jeff Sutherland <jSutherland@accelent.com>
MIME-Version: 1.0
To: Kurt Garloff <garloff@suse.de>
Cc: "'linux-scsi@vger.rutgers.edu'" <linux-scsi@vger.rutgers.edu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Kurt Garloff wrote:
> On Fri, Feb 04, 2000 at 11:55:52AM -0500, Jeff Sutherland wrote:
> > The bios automatically (via plug-and-pray) assigns id #4 to the fixed disk
> > normally. Because the ZIP drive can only be assigned to 5 or 6, I tried 6
>
> I'd suggest to disable SCAM completely. It only causes trouble.
> If you have to live with it, I'd suggest to use the alias feature of scsidev
> (http://www.garloff.de/kurt/linux/scsidev/) to get a unique view of your
> disks independent of the IDs being used.
I hacked the hardware and got things working. The drive that came with this
system (IBM DCAS-3033xxx something) was jumpered for ID6. I simply changed the
jumpers to ID0, which forced Linux to detect it first always. Somewhere I
recall reading that Linux always wanted its boot device to be on either ID0 or
ID1, but I guess as long as it was the only disk device in the system it didn't
really matter (until now). The Iomega ZIP drive is perfectly happy at sdb4. I
wonder why the ZIP drive's disk appears at partition 4, not partition 1?
Thanks for that link to scsidev, Kurt. I will download that and play around
with it.
Regards,
//Jeff
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.rutgers.edu
