Puppy Linux Discussion Forum Forum Index Puppy Linux Discussion Forum
Puppy HOME page : puppylinux.com
"THE" alternative forum : puppylinux.info
 
 FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

The time now is Thu 19 Oct 2017, 09:11
All times are UTC - 4
 Forum index » Advanced Topics » Hardware
Anyone know how to install an IBM LTO 3 Ultrium tape drive?
Moderators: Flash, Ian, JohnMurga
Post new topic   Reply to topic View previous topic :: View next topic
Page 2 of 4 [47 Posts]   Goto page: Previous 1, 2, 3, 4 Next
Author Message
PappyPuppy

Joined: 30 Sep 2016
Posts: 220

PostPosted: Sat 27 May 2017, 09:21    Post subject: And it's NOT 0 or 7 or 15
Subject description: Should I NOT use the defaults
 

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?
Back to top
View user's profile Send private message 
PappyPuppy

Joined: 30 Sep 2016
Posts: 220

PostPosted: Sat 27 May 2017, 09:27    Post subject: I'm trying to specialize to the -TD3 device id I see on boot
Subject description: I'm trying to get information for my specific drive
 

http://www-01.ibm.com/support/docview.wss?uid=swg21193425
Back to top
View user's profile Send private message 
PappyPuppy

Joined: 30 Sep 2016
Posts: 220

PostPosted: Sat 27 May 2017, 09:34    Post subject: Their Fix Central says to start by typing your product name
Subject description: Every name I type it says it's not the product
 

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
Back to top
View user's profile Send private message 
PappyPuppy

Joined: 30 Sep 2016
Posts: 220

PostPosted: Sat 27 May 2017, 10:35    Post subject: I'm justchecking some stuff
Subject description: Here are the device info for the Adaptec
 

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
Back to top
View user's profile Send private message 
PappyPuppy

Joined: 30 Sep 2016
Posts: 220

PostPosted: Sat 27 May 2017, 10:41    Post subject: I have NOT yet tried SCSI Select's 2nd option
Subject description: SCSI Disk Utilities.
 

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.
Back to top
View user's profile Send private message 
PappyPuppy

Joined: 30 Sep 2016
Posts: 220

PostPosted: Sat 27 May 2017, 10:45    Post subject: I think I need to reboot
Subject description: And get rid of the BIOS being the default boot
 

How can the BIOS on the Adaptec SCSI Controller be disabled?
Answer ID 2353 | Published 05/21/2001 06:06 PM | Updated 08/12/2010 08:58 AM
The Adaptec SCSI Controller becomes the priority boot card when installed.

How can the BIOS on the Adaptec SCSI Controller be disabled so it won't attempt to boot over the existing boot controller or onboard chipset?


This information applies to the following Operating System(s):
- This information is not Operating System specific
The SCSI Controller BIOS can be disabled within the SCSI BIOS, via the SCSISelect feature on the SCSI controller.

During the system boot process, you will see the Adaptec BIOS and a prompt to press Ctrl-A to go inside SCSISelect.

Once inside the SCSISelect utility:

Choose the SCSI controller you want to disable the BIOS on and press enter.

Choose Configure / View SCSI Controller Settings and press enter.

Choose Advanced Configuration inside Additional Options area below.

Select SCSI Controller Int 13 Support. This option controls the state of the BIOS at POST time. The following settings are available:

Enabled - Supports INT 13 for booting from a SCSI hard disk drive connected to the SCSI card. If you use this option, the following options are available:
- Extended INT 13 Translation for DOS Drives > 1 GB
- Support Removable Disks Under INT 13 as Fixed Disks
- BIOS Support for Bootable CD-ROM

Disabled:NOT Scan - select this option if all the devices on the SCSI bus are controlled by software drivers and do not need the BIOS, and you do not want the BIOS to scan the SCSI bus. SCSISelect remains available if needed.

Disabled:Scan Bus - select this option if all the devices on the SCSI bus are controlled by software drivers and you need the BIOS to scan the SCSI bus. Allows devices to spin up according to the setting of the Send Start Unit Command. SCSISelect remains available if needed.

Note: Once you have changed the BIOS settings, press "Esc" twice and it will prompt you to save the changes. Press "Esc" again to exit and then restart the system.
Was this answer helpful?
Back to top
View user's profile Send private message 
PappyPuppy

Joined: 30 Sep 2016
Posts: 220

PostPosted: Sat 27 May 2017, 10:55    Post subject: I've changed the Adaptec under Advanced on boot
Subject description: To disable but scan the bus and I disabled the BIOS bootup screen
 

from running SCSISelect each time. I hope this streamlines things a little at least.

When I ran the Drive Configurator it gave me the message "Not a disk drive" which is correct and it gives me the ID 0 for the IBM ULTRIUM-TD3 and 7 for the Adaptec card.

Firmware of the Tape drive is 6B20

So at least I'm learning.

The computer is booting now without the SCSISelect screen for the first time.
Back to top
View user's profile Send private message 
PappyPuppy

Joined: 30 Sep 2016
Posts: 220

PostPosted: Sat 27 May 2017, 10:58    Post subject: Suppose I wanted to reenable the SCSISelect and using card
Subject description: as boot device. I wonder how I would do that
 

Just curious how I would reenable that stuff.

I'm not planning to need that anytime soon. Perhaps I can just run SCSISelect from the command line somehow.??

The computer is rebooted but still no tape drive.

So no kernel drivers are loading.
Back to top
View user's profile Send private message 
PappyPuppy

Joined: 30 Sep 2016
Posts: 220

PostPosted: Sat 27 May 2017, 11:34    Post subject: I may need the source code for the -TD3 drives
Subject description: I saw IBM's documentation for the Fix it
 

I wonder if I can get that source code and recompile?

I have sent a message to someone who had the same problem as me and asked him for the names of the drivers.
Back to top
View user's profile Send private message 
PappyPuppy

Joined: 30 Sep 2016
Posts: 220

PostPosted: Sat 27 May 2017, 12:52    Post subject: I've rebooted into Windows XP
Subject description: I've decided to take time off from the Linux approach
 

My computer can be booted into Windows XP. I'll work with that for a while while I await any feedback from those who've read my posts and messages - maybe there is a tape tool or driver source that I can compile for Fatdog.

So I will start now to get this to run on Windows. But in the end, I need it to run on Linux.
Back to top
View user's profile Send private message 
PappyPuppy

Joined: 30 Sep 2016
Posts: 220

PostPosted: Sat 27 May 2017, 13:07    Post subject: I am trying to find the IBM manuals from a long list
Subject description: I believe I need the -13 manual although I'm not sure
 

IBM says that they obsolete their manuals - not sure what that means.

I am still looking for a manual so I can install in windows now while I wait for help with Fatdog Linux.

IBM Ultrium Device Drivers Installation and User’s Guide, GC32-0430-13

I need the above manual. I cannot find it.
Back to top
View user's profile Send private message 
PappyPuppy

Joined: 30 Sep 2016
Posts: 220

PostPosted: Sat 27 May 2017, 13:17    Post subject: Under device manager, I see a yellow question mark
Subject description: IBM ULTRIUM-TD3 SCSI Sequential Device
 

So I wonder if I can update the drivers for this and get it to recognize it?

It says that this device is working properly.

I have no program to use in windows yet. So that's another job. I wonder if it is really working properly. Why doesn't it list it as a tape drive? Apparently it doesn't know that it's a tape drive but it says it's working properly. I guess I need to check for drivers. If it really has a driver? It says Driver Provider: Unknown, I don't think it's really working.
Back to top
View user's profile Send private message 
PappyPuppy

Joined: 30 Sep 2016
Posts: 220

PostPosted: Sat 27 May 2017, 15:30    Post subject: I can't get it to work on Windows XP either
Subject description: I'm back to hoping I can get it to work on Fatdog
 

But I will be busy for the day, so I'm not on this for a bit. I'm not making any progress. I wonder though, did another company develop stuff that will work on IBM's tape system. Like firmware/software, or even hardware. Am I looking in the wrong place for drivers for the IBM tape drive.
Back to top
View user's profile Send private message 
PappyPuppy

Joined: 30 Sep 2016
Posts: 220

PostPosted: Sun 28 May 2017, 07:58    Post subject: Implementing IBM Tape in Linux and Windows
Subject description: This document should guide me - it was written in 2005
 

I hope that this document was written soon enough for the release of my tape drive. My tape drive was manufactured in 2007 although I think that model was available as early as late 2005 or 2006. These are details that may be important. This (October 2005) is the Fourth edition of the above manual, started in 2002. I am trying to point my helper(s) in the direction I'm going as I was hoping to finish this by Friday and it's now Sunday. Such is life.

Windows XP came out in late 2001 I believe? A little later than Windows 2000 but before Windows 2003. The reason I mention this is just that the overall hardware/software platforms they supported can sometimes come into play. I will make a call tomorrow to a "helper" I spoke with once already and see what "platform(s)" he uses. This might help also.

But page 183 of that manual describes what to do for Linux. I will start reading that now.

There is an issue of which manual to read or should I just read what I can find, so I will at least take a look at that and see if I can follow it and get it to work.

Thanks for any help. And this is my only thread for this forum. The others are locked so please if you have some smarts or whatever, post it here, thanks. Very Happy
Back to top
View user's profile Send private message 
PappyPuppy

Joined: 30 Sep 2016
Posts: 220

PostPosted: Sun 28 May 2017, 08:18    Post subject: Narrowing down which set of documents are for my reader
Subject description: There seem to be two Ultrium series of readers
 

SLES12, SLES11, RHEL7, RHEL6, Archives
Update: The above refer to Enterprise Linux Server, and Redhat, so I would guess I'll be in Archives or possibly one of the other. I don't know yet.

I am trying to see which set of Fixit Central archives to go through. In the previous post I mention page 183. On page 184, they suggest reading over some documents - if I navigate to IBM's ftp site, and drill down to storage/devdrvr/Doc, the Doc has been replaced with a link to an http site FixIt Central. I'm going through that now.

So two mysteries:
1) Which document is for my reader?
2) Why is my Ultrium reader, a 23R4762 never, ever mentioned anywhere but the IBM 3580 series ARE mentioned. This is what I'm trying to figure out - where is my reader mentioned - that would help.
Back to top
View user's profile Send private message 
Display posts from previous:   Sort by:   
Page 2 of 4 [47 Posts]   Goto page: Previous 1, 2, 3, 4 Next
Post new topic   Reply to topic View previous topic :: View next topic
 Forum index » Advanced Topics » Hardware
Jump to:  

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You can download files in this forum


Powered by phpBB © 2001, 2005 phpBB Group
[ Time: 0.0740s ][ Queries: 11 (0.0097s) ][ GZIP on ]