Well, I got the drive to work finally.  My problem was simply because I
didn't have the SCSI/Tape section enabled in my Kernel.  I'm running
2.0.36 now and it works flawlessly.

Ryan C. Sumner
Director of Technology
LIS Consulting, LLC
[EMAIL PROTECTED] * 512-266-1615

On Tue, 12 Oct 1999, Wayne Horner wrote:

> I have an hp t20i attached to linux mandrake 6.0 kernel 2.2.9.
> The tape drive appears to work. However it wont accept any change in
> blocksize other than 512.
> setblk 0 gives Illegal bits in request field
> setblk 512 works
> setblk 1024 or more gets illegal block size.
> 
> So I looked on the HP website for a scsi programming manual and couldn't find
> one.
> Then I called HP support (not). I explained that I wanted to write a driver
> for linux and wanted to purchase the SCSI interface programming manual.
> After a few minutes on hold he came back and said NO-WAY! Apparently the SCSI
> interface is a top secret, classified, technological advantage for HP and I
> must be some kind of industrial spy.
> 
> So HP is not interested in supporting us. I will return their $500 tape
> drive.
> Beware....
> 
> "Ryan C. Sumner" wrote:
> 
> > Hi,
> >
> > I've installed a HP-T20 into one of my linux machines and it doesn't seem
> > to be working correctly.
> >
> > I can see in the /proc/scsi/scsi the following, which tells me that the
> > drive is loaded:
> >
> > Attached devices:
> > Host: scsi0 Channel: 00 Id: 00 Lun: 00
> >   Vendor: IBM      Model: DDRS-39130D      Rev: DC1B
> >   Type:   Direct-Access                    ANSI SCSI revision: 02
> > Host: scsi0 Channel: 00 Id: 01 Lun: 00
> >   Vendor: IBM      Model: DDRS-39130D      Rev: DC1B
> >   Type:   Direct-Access                    ANSI SCSI revision: 02
> > Host: scsi0 Channel: 00 Id: 04 Lun: 00
> >   Vendor: HP       Model: T20              Rev: 3.01
> >   Type:   Sequential-Access                ANSI SCSI revision: 02
> >
> > And when I create the block devices by running:
> >
> >               mknod -m 660 /dev/st0 c 9 0
> >               mknod -m 660 /dev/st1 c 9 1
> >               mknod -m 660 /dev/nst0 c 9 128
> >               mknod -m 660 /dev/nst1 c 9 129
> >
> > It comes back with no problems.  But, when I run:
> >
> > # mt-f /dev/st0 status
> > mt: /dev/st0: Operation not supported by device
> >
> > Or if I try to tar something to it, I get the same problem.  Keep in mind
> > that this drive was added after the OS was installed, but everything
> > looks good.  Kernel is 2.0.36 running on Debian 2.0.
> >
> > Any help would be greatly appreciated.
> >
> > Ryan C. Sumner
> > Director of Technology
> > LIS Consulting, LLC
> 
> 

Reply via email to