Thomas Hepper ([EMAIL PROTECTED]):
> OK, so lets try to figure out where it is.
Thanks for the steps, the results are getting closer.
Some notes:
> 3. Try chg-scsi -scanbus (i'm not sure that it works :-)
This doesn't work on my chg-scsi (2.4.2p2).
> 4. From the output of the cat /proc/scsi/scsi you can get the number of the
> changer device, start counting at 0, example
> Host: scsi0 Channel: 00 Id: 01 Lun: 00
> Vendor: EXABYTEE Model: EXB-85058SQANNR1 Rev: 07T0
> Type: Sequential-Access ANSI SCSI revision: 02
> Host: scsi0 Channel: 00 Id: 02 Lun: 00
> Vendor: EXABYTE Model: EXB-210 Rev: 3.11
> Type: Medium Changer ANSI SCSI revision: 02
> Host: scsi1 Channel: 00 Id: 00 Lun: 00
> Vendor: IBM Model: DDRS-34560 Rev: S97B
> Type: Direct-Access ANSI SCSI revision: 02
> Host: scsi1 Channel: 00 Id: 01 Lun: 00
> Vendor: IBM OEM Model: 0662S12 Rev: 3 30
> Type: Direct-Access ANSI SCSI revision: 02
> In the above the library ist at /dev/sg1
Ok, my changer is at /dev/sg0 (and tape at /dev/sg1). You'd think that
the device numbering would follow chains, ids, etc. but I guess not.
> 6. After this try an amtape daily reset
Returned
amtape: changer is reset, slot chg-scsi: is loaded.
So it looks like this might work. How does this approach compare to
Paul's chg-userland fix?
--
Jeremy Wadsack
Wadsack-Allen Digital Group
