Anyone know how to install an IBM LTO 3 Ultrium tape drive?

What works, and doesn't, for you. Be specific, and please include Puppy version.
Message
Author
PappyPuppy
Posts: 409
Joined: Sat 01 Oct 2016, 00:27

Anyone know how to install an IBM LTO 3 Ultrium tape drive?

#1 Post by PappyPuppy »

I have the tape drive on an Adaptec SCSI card and I would like to install the drivers for Fatdog 710 Linux.

I've never installed a tape drive before nor any other SCSI device.

I keep reading manuals and I just haven't found one yet. I think I'm getting warm though as I've seen some websites of IBM's.

I'll keep trying, but if anyone knows how to get the drivers and/or install the drivers for my Fatdog please let me know.

It's an 23R4762/95P2012 drive. These were made between about 2006 and 2008. I am looking at the documentation but I'm still clueless. Something detects the thing on boot up. Everything seems ok so far.

PappyPuppy
Posts: 409
Joined: Sat 01 Oct 2016, 00:27

Adaptec Family Manager Set

#2 Post by PappyPuppy »

Perhaps this has the drivers - and i need to install them for the Adaptec card and then later for the IBM drive? I thought Linux would just detect the card and install the drivers.

PappyPuppy
Posts: 409
Joined: Sat 01 Oct 2016, 00:27

I am browsing the Internet to find Linux drivers for the

#3 Post by PappyPuppy »

I believe there are projects where people have attempted this. Perhaps I can just compile their drivers source.

PappyPuppy
Posts: 409
Joined: Sat 01 Oct 2016, 00:27

My Linux kernel should detect the Adaptec SCSI card 39160

#4 Post by PappyPuppy »

I guess somehow I need to get these drivers noticeable? Perhaps when it says Ctrl-A to set up I need to set up the SCSI card with a bunch of parameters.

PappyPuppy
Posts: 409
Joined: Sat 01 Oct 2016, 00:27

I ran the Ctrl A setup on boot twice and I think everything

#5 Post by PappyPuppy »

But I think that's ok.

I'll check for drivers now. Perhaps my Fatdog does not yet have them. I might need to build them so that the kernel picks them uip on boot.

PappyPuppy
Posts: 409
Joined: Sat 01 Oct 2016, 00:27

Adaptec has a link with some source code

#6 Post by PappyPuppy »

But when I try to see the files. they are not there. Strange?

So my next step is to try to build the drivers.

I hope I have the right kernel

https://adaptec.com/en-us/speed/scsi/li ... _6_tgz.php

PappyPuppy
Posts: 409
Joined: Sat 01 Oct 2016, 00:27

I wonder if I should disable the Adaptec SCSI BIOS

#7 Post by PappyPuppy »

Wow, I wish I knew how to set these cards up.

PappyPuppy
Posts: 409
Joined: Sat 01 Oct 2016, 00:27

I guess I have aic7xxx under lib/modules

#8 Post by PappyPuppy »

It lists the Path, Used Memory, Name, Description, Version Magic, Author/Maintainer: Hannes Reinecke <hare@suse.de>
License Dual BSD/GPL

The path is /lib/modules/4.4.35/kernel/drivers/scsi/aic7xxx/aic7xxx.ko

PappyPuppy
Posts: 409
Joined: Sat 01 Oct 2016, 00:27

The output of the lspci command

#9 Post by PappyPuppy »

The output of this command DOES in fact list a controller by Adaptec:

02:00.0 SCSI storage controller: Adaptec AHA-3960D / AIC-7899A U160/m (rev 01)
02:00.1 SCSI storage controller: Adaptec AHA-3960D / AIC-7899A U160/m (rev 01)

So I will now conclude that the Adaptec IS in fact installled.

I need to now search for a tape drive's drivers.

PappyPuppy
Posts: 409
Joined: Sat 01 Oct 2016, 00:27

I might have to just use generic Linux drivers

#10 Post by PappyPuppy »

When I run the dmesg command, I don't see an IBM tape drive - and no /dev/stx devices. I think my only choice of drivers unless I have source code is to use Native Linux. I guess I should find out where these drivers are supposed to be.

Under dev/scsi/dev???_info I do see the IBM tape drive listed. At least one little part of the OS sees a tape drive of some sort. Or perhaps it simply is that it uses that long list of devices and found what it thinks is a match. This is confusing. I guess I thought it simply added that string to that device file - I think this is what happened.

I have not yet installed sq utils on the test machine. They wouldn't work anyway. I need to get the computer to recognize the IBM drive and load some drivers and attach them to the device.

scsijon
Posts: 1596
Joined: Thu 24 May 2007, 03:59
Location: the australian mallee
Contact:

#11 Post by scsijon »

sorry PappyPuppy, just came across this one.

So you can see the adaptic card!

And you can see the Tape drive on the scsi bus!

And it has a bus address as ??? (should be seen if doing a full bios startup routine) and it's not 0 or 7 or 15!

And if you look in /dev there is a suitable block device https://www.cyberciti.biz/faq/tape-driv ... der-linux/ ? You may have to make this with mknod. Also see the last line on the webpage and go there, it's important to understand before you play.

Does your kernel have the internal links to deal with a Tape Drive? Ask the puppy system's maintainer (in the correct thread).

Is there a blank tape in the drive and it's the correct type (very important as a lot look the same but are different). This Just makes it easier to deal with at this stage.

And that's just to start with. It's not hard, just a lot of reading and a bit of setting up for a new user.

I'll keep an eye on the thread in case you need further help. Back when Puppy 3 was very new I had a complete Dialup BBS system running on Tape drives except for a (small by nowadays standard) 5Meg Hard Drive for the system and it's controls and logs.

And I go back to pdp8's and IBM Front End processors that were all connected via scsi, i've even got a 8" Floppy Drive that's SCSI.

Thus is why my 'tag' was given to me in the early '70's.

PappyPuppy
Posts: 409
Joined: Sat 01 Oct 2016, 00:27

Hi SCSIJon, thank you for responding

#12 Post by PappyPuppy »

I am so dead tired from my hardware setup alone as I had to scrounge around box after box to find a power stub extender.

Anyway, I know that there are two ways to "drive" the IBM LTO Ultrium - one is by Linux's own kernel drivers, and the other is by the IBM-specific.

It will take me many hours to check each of the concepts that you just suggested. I'm guessing that the SCSI card is running on ID 7 which is the default, and it sees the IBM drive as you mentioned. What I would love as my next step is to NOT see the Adaptec BIOS program SCSISelect run each time I boot. I've changed and/or just accepted the parameters. It should not keep running each time. Yes, I need to keep reading and studying. And I keep downloading manuals and hope that they are the right vintage - even the wrong vintage will help though as the concepts are similar. It's a lot of reading for me.

I'll post my next step or discovery and keep someone watching. This is tiring work for me as I'm not a Linux guru. But at least I got my Fatdog going on yet another machine. So I now have two fatdog machines and a fatdog laptop. They are all still running but the one I have the IBM tape drive on has a slight hardware problem. But right now it's running ok so I can use it. I can live with that slight problem. It will not interfere with my getting this IBM tape drive to work.

PappyPuppy
Posts: 409
Joined: Sat 01 Oct 2016, 00:27

Here's some information

#13 Post by PappyPuppy »

1) I have not yet put a tape in the drive. I don't want to do that until I have a device. There's no point in putting a tape in - there is no st0 device yet. The device will obviously be called st0 and will appear as an icon once I get some drivers going.

2) I left the jumper on the IBM Ultrium on the left-most position looking from the rear of the drive. I'm confused - I don't actually understand - are there two jumper sets - one for TERMPOWER and one for ID? I am very confused about that.

3) My maintainer is for Fatdog - I would have to ask them. But I should be able to browse and find a driver. I need to know what the names of the drivers are.

PappyPuppy
Posts: 409
Joined: Sat 01 Oct 2016, 00:27

I'm trying to collect some documents

#14 Post by PappyPuppy »

Implementing IBM LTO in Linux and Windows - SG246268.book (pdf file, 2002)
39160_users_reference.pdf
IBM Tape Device Drivers: Installation and User's Guide - this is around 2007, I need around 2005 or 2006 for my drive.
Last edited by PappyPuppy on Sat 27 May 2017, 13:11, edited 1 time in total.

PappyPuppy
Posts: 409
Joined: Sat 01 Oct 2016, 00:27

There is a Fix Central

#15 Post by PappyPuppy »

What is SLES12, RHEL7, Archives, ...????

PappyPuppy
Posts: 409
Joined: Sat 01 Oct 2016, 00:27

And it's NOT 0 or 7 or 15

#16 Post by PappyPuppy »

The ID it finds the IBM LTO Ultrium 3 23R4762/95P2012 drive on IS ID 7.

The Adaptec card is a PCI device. And I would guess that it picks up the IBM drive. I would like to shut the BIOS from running each time. Is it not saving this information ID 7? That's why it runs each boot?


PappyPuppy
Posts: 409
Joined: Sat 01 Oct 2016, 00:27

Their Fix Central says to start by typing your product name

#18 Post by PappyPuppy »

It says that for device names of IBM Ultrium-TD3 that I MUST use the IBM drivers.

Now I have to analyze 3 things!
1) Is my device really IBM Ultrium-TD3. I guess that's a yes.
2) Do I really MUST have those drivers!
3) What is the product name that corresponds to the device that's named IBM Ultrium-TD3.

Why can't I just put in IBM LTO Ultrium 3 23R4762? I can't get the product name to match!

I need to find drivers under this (GNU drivers):
Tape drivers and software, Tape device drivers (Linux 64-bit,x86_64)

I think I'm this:
IBM Ultrium Gen-3 and IBM 400/800GB LTO Gen 3
Drive ID : IBM ULTRIUM-TD3
Firmware : 4C17

I would guess that if they say I need their drivers and the Linux Kernel won't drive it, then I might need source code to recompile, although sometimes drivers will work - like for .deb or something. A lot of unknowns right now.

Under /proc/scsi, I've got a directory aic7xxx, which has 7 and 8, and is what dmesg | grep 'Adaptec' gives the scsi host7 and host 8 params and it lists the ID as 7 iin the files 7 and 8. So the Adaptec is set up. I'm not yet quite sure why there is 25.340029 AND 44.480029

PappyPuppy
Posts: 409
Joined: Sat 01 Oct 2016, 00:27

I'm justchecking some stuff

#19 Post by PappyPuppy »

dmesg | grep 'Adaptec'

[ 25.340029] scsi host7: Adaptec AIC7XXX EISA/VLB/PCI SCSI HBA DRIVER, Rev 7.0
<Adaptec 3960D Ultra160 SCSI adapter>
[ 44.480029] scsi host8: Adaptec AIC7XXX EISA/VLB/PCI SCSI HBA DRIVER, Rev 7.0
<Adaptec 3960D Ultra160 SCSI adapter>


cat /proc/scsi/aic7xxx/7

Adaptec AIC7xxx driver version: 7.0
Adaptec 3960D Ultra160 SCSI adapter
aic7899: Ultra160 Wide Channel A, SCSI Id=7, 32/253 SCBs
Allocated SCBs: 4, SG List Length: 128

Serial EEPROM:
0xc33a 0xc33a 0xc33a 0xc33a 0xc33a 0xc33a 0xc33a 0xc33a
0xc33a 0xc33a 0xc33a 0xc33a 0xc33a 0xc33a 0xc33a 0xc33a
0xb8f4 0x7c5d 0x2807 0x0110 0x0300 0xffff 0xffff 0xffff
0xffff 0xffff 0xffff 0xffff 0xffff 0xffff 0x0250 0x974f

Target 0 Negotiation Settings
User: 160.000MB/s transfers (80.000MHz DT, offset 127, 16bit)
Target 1 Negotiation Settings
User: 160.000MB/s transfers (80.000MHz DT, offset 127, 16bit)
Target 2 Negotiation Settings
User: 160.000MB/s transfers (80.000MHz DT, offset 127, 16bit)
Target 3 Negotiation Settings
User: 160.000MB/s transfers (80.000MHz DT, offset 127, 16bit)
Target 4 Negotiation Settings
User: 160.000MB/s transfers (80.000MHz DT, offset 127, 16bit)
Target 5 Negotiation Settings
User: 160.000MB/s transfers (80.000MHz DT, offset 127, 16bit)
Target 6 Negotiation Settings
User: 160.000MB/s transfers (80.000MHz DT, offset 127, 16bit)
Target 7 Negotiation Settings
User: 160.000MB/s transfers (80.000MHz DT, offset 127, 16bit)
Target 8 Negotiation Settings
User: 160.000MB/s transfers (80.000MHz DT, offset 127, 16bit)
Target 9 Negotiation Settings
User: 160.000MB/s transfers (80.000MHz DT, offset 127, 16bit)
Target 10 Negotiation Settings
User: 160.000MB/s transfers (80.000MHz DT, offset 127, 16bit)
Target 11 Negotiation Settings
User: 160.000MB/s transfers (80.000MHz DT, offset 127, 16bit)
Target 12 Negotiation Settings
User: 160.000MB/s transfers (80.000MHz DT, offset 127, 16bit)
Target 13 Negotiation Settings
User: 160.000MB/s transfers (80.000MHz DT, offset 127, 16bit)
Target 14 Negotiation Settings
User: 160.000MB/s transfers (80.000MHz DT, offset 127, 16bit)
Target 15 Negotiation Settings
User: 160.000MB/s transfers (80.000MHz DT, offset 127, 16bit)


cat /proc/scsi/aic7xxx/8

Adaptec AIC7xxx driver version: 7.0
Adaptec 3960D Ultra160 SCSI adapter
aic7899: Ultra160 Wide Channel B, SCSI Id=7, 32/253 SCBs
Allocated SCBs: 4, SG List Length: 128

Serial EEPROM:
0xc33a 0xc33a 0xc33a 0xc33a 0xc33a 0xc33a 0xc33a 0xc33a
0xc33a 0xc33a 0xc33a 0xc33a 0xc33a 0xc33a 0xc33a 0xc33a
0xb8f4 0x7c5d 0x2807 0x0110 0x0300 0xffff 0xffff 0xffff
0xffff 0xffff 0xffff 0xffff 0xffff 0xffff 0x0250 0x974f

Target 0 Negotiation Settings
User: 160.000MB/s transfers (80.000MHz DT, offset 127, 16bit)
Target 1 Negotiation Settings
User: 160.000MB/s transfers (80.000MHz DT, offset 127, 16bit)
Target 2 Negotiation Settings
User: 160.000MB/s transfers (80.000MHz DT, offset 127, 16bit)
Target 3 Negotiation Settings
User: 160.000MB/s transfers (80.000MHz DT, offset 127, 16bit)
Target 4 Negotiation Settings
User: 160.000MB/s transfers (80.000MHz DT, offset 127, 16bit)
Target 5 Negotiation Settings
User: 160.000MB/s transfers (80.000MHz DT, offset 127, 16bit)
Target 6 Negotiation Settings
User: 160.000MB/s transfers (80.000MHz DT, offset 127, 16bit)
Target 7 Negotiation Settings
User: 160.000MB/s transfers (80.000MHz DT, offset 127, 16bit)
Target 8 Negotiation Settings
User: 160.000MB/s transfers (80.000MHz DT, offset 127, 16bit)
Target 9 Negotiation Settings
User: 160.000MB/s transfers (80.000MHz DT, offset 127, 16bit)
Target 10 Negotiation Settings
User: 160.000MB/s transfers (80.000MHz DT, offset 127, 16bit)
Target 11 Negotiation Settings
User: 160.000MB/s transfers (80.000MHz DT, offset 127, 16bit)
Target 12 Negotiation Settings
User: 160.000MB/s transfers (80.000MHz DT, offset 127, 16bit)
Target 13 Negotiation Settings
User: 160.000MB/s transfers (80.000MHz DT, offset 127, 16bit)
Target 14 Negotiation Settings
User: 160.000MB/s transfers (80.000MHz DT, offset 127, 16bit)
Target 15 Negotiation Settings
User: 160.000MB/s transfers (80.000MHz DT, offset 127, 16bit)

These show that the ID is 7

PappyPuppy
Posts: 409
Joined: Sat 01 Oct 2016, 00:27

I have NOT yet tried SCSI Select's 2nd option

#20 Post by PappyPuppy »

I guess I thought that this was mostly only for Hard-drives, not tape drives, but perhaps I should see if it gives me an ID of the tape drive?

I don't know.

Post Reply