Well, I thought this would be the easiest thing in the world: get a SCSI
version of an Iomega 250 ZIP drive, connect it to my computer, and boot up
and run. Windows NT4 didn't mind, found it and recognized it for what it
was without installing any software. Linux croaked. More specifically,
Linux would always want to attemt to mount the Zip drive as /dev/sda after
initializing the adapter card, regardless of the ID (ZIP drive can only do
#5 or #6) of the drive. I have a sneaking suspicion that something is hosed
in the way Linux looks for its boot device. I must tell you that the NT
bootloader always finds the fixed disk no matter what ID it gets assigned,
and that it dutifully launches Lilo and begins the boot process.
Hardware: Adaptec AHA2940UW Scsi card on a 200MHZ P-II
SCSI devices: IBM DCAS 4.1 gig drive with 3 partitions: fat,ext2,linux swap
Connor Travan4 tape drive
CDrom
Trying to connect an Iomega 250Mb ZIP drive
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
first which moved the fixed disk to #3. Setting the ZIP drive to #5 caused
the bios to move the fixed disk to #6. I *THINK* this is the root cause of
the problem, plug and play. I'm going to attempt to force the ID of the
fixed disk to remain at #4 when adding the ZIP drive. Am I on the right
track? If I'm not, someone please set me straight before I start trying to
hack the kernel...
//Jeff
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to [EMAIL PROTECTED]
