Re: Looking for drivers (WinXP or Linux) for an IBM 97P6513 (U320)



"Michael Baeuerle" <michael.baeuerle@xxxxxxxx> wrote in message news:4mkem4-nik.ln1@xxxxxxxxxxxxxxxxxxx
Folkert Rienstra wrote:
Michael Baeuerle wrote:
Folkert Rienstra wrote:
Michael Baeuerle wrote:
Folkert Rienstra wrote:
"Petros" wrote:

I purchased an U320 SCSI card that used to be in an IBM AIX machine
(at least this is what I was told.)

Right, so it is not meant to be used with an X86 PC.
It may even hang it up if it has RS6000 code on it.

97P6513 should be a "PCI-X Dual Channel Ultra320 SCSI Adapter" like
this:
http://www.gstinc.com/store/images/01-image/2-SCSI.jpg

IMHO there are good chances that it will run in a PC and that it has no
host code onboard. .

#5712/5710 - PCI-X Dual Channel Ultra320 SCSI - Type 5702
- Announcement Letter: US 103-288 | CDN A03-1383
- Supported: AIX 5.1/5.2 with appropriate updates
- Documentation:
- Fileset: devices.pci.14106602.*
*This adapter has downloadable microcode*
FRU: 97P6513, 97P3359 #5712 no carrier
97P6653, 53P4705 #5710 with carrier

http://www-941.ibm.com/collaboration/wiki/download/attachments/1196/RSinfo.pdf?version=1

That should be no problem, the "microcode" ist very likely the firmware
for the local PowerPC CPU on the card (not driver code for the host).

If.

Yes, if.

I can't see why you would have different code for AIX and Linux
running on the PPC cpu without having supporting code for the HOST
to access, whatever that different code supports on the SCSI adapter.

Where have IBM stated that Linux requires different microcode than AIX?

In that uCode download page, I guess. Well, that is my interpretation of it.

The different files to download may simply contain different flashing
tools for the same microcode.

If you read Desc(ription) the procedure is completely manual, so it's not
that they are different install packages, AFAICT. It's all rather confusing.

I tried to compare them but IBM wants JavaScript, Cookies,
Licence aggreement, Machine type, etc. until I gave up.

That code can't be entirely SCSI bus related.

Ack, this code also provides the API for the host driver - and therefore
a certain version may be required for a certain driver. If the Linux
driver from Brian King is not derived from the AIX driver, there may
be different requirements. But this does not inevitably mean that the
microcode contains code for the host.

Normally IBM machines for AIX have drivers for all
supported boot adapters already in their BIOS

It is very likely that Windows XP won't work. But the "ipr" Linux driver
from IBM may support this adapter on a PC too:
http://www.gelato.unsw.edu.au/lxr/source/drivers/scsi/ipr.c?a=i386

http://www14.software.ibm.com/webapp/set2/firmware/gjsn?mode=7&fc=5710&go.x=12&go.y=8

Still not sure though where x86 features in that.

The Linux driver runs at least on IBM pSeries Hardware:
http://www-941.ibm.com/collaboration/wiki/display/LinuxP/Adapter+and+Device+Support
(#5710/5712 is listed as supported by the ipr driver)

It seems that this is inofficial because IBM list only AIX as
"supported" in the PDF. But the ipr driver itself should be platform
independent. I have found a binary utility packages for it:
http://rpmfind.net/linux/RPM/opensuse/OSS-factory/i586/iprutils-2.2.6-2.i586.html
... it is compiled for x86 - so I assume the driver runs on this platform too.

How about a RAID configuration setup utility to replace the usual BIOS setup utility?

Here is the man page of the iprconfig utility that is contained in
iprutils:
http://www.sourcentral.org/man/SUSE102/8+iprconfig

To prove that the ipr driver can be build for Linux/x86 I have compiled
it on my machine:
----------------------------------------------------------------------
[root@WStation2:/usr/src/linux]# uname -mo
i686 GNU/Linux
[root@WStation2:/usr/src/linux]# make menuconfig
...
[root@WStation2:/usr/src/linux]# make modules
CHK include/linux/version.h
SPLIT include/linux/autoconf.h -> include/config/*
CC [M] drivers/scsi/ipr.o
Building modules, stage 2.
MODPOST
CC drivers/scsi/ipr.mod.o
LD [M] drivers/scsi/ipr.ko
[root@WStation2:/usr/src/linux]# make modules_install
...
[root@WStation2:/usr/src/linux]# modprobe ipr
[root@WStation2:/usr/src/linux]# dmesg | tail -n1
ipr: IBM Power RAID SCSI Device Driver version: 2.1.2 (February 8, 2006)
----------------------------------------------------------------------

It can be build, loaded and started without complaining or crashing.
This does not prove that it will _work_ on x86 but at least that it is
written platform independent and not for PPC only.


Micha
.



Relevant Pages

  • Re: Looking for drivers (WinXP or Linux) for an IBM 97P6513 (U320)
    ... I purchased an U320 SCSI card that used to be in an IBM AIX machine ... running on the PPC cpu without having supporting code for the HOST ... Where have IBM stated that Linux requires different microcode than AIX? ... this code also provides the API for the host driver - and therefore ...
    (comp.periphs.scsi)
  • Re: Looking for drivers (WinXP or Linux) for an IBM 97P6513 (U320)
    ... I purchased an U320 SCSI card that used to be in an IBM AIX machine ... for the local PowerPC CPU on the card (not driver code for the host). ...
    (comp.periphs.scsi)
  • Re: Win2k3 R2 - Storage Reporting on File Svr Cluster (SCSI-Attach
    ... The 7.12 driver set from the link you gave me is actually the ones I used. ... I questioned the IBM hardware support staff I contacted on this ... Cluster Manager, I have an IPSHA Disk D: resource which is attached to the ...
    (microsoft.public.windows.server.clustering)
  • Recommendations for a serial port card you can actually BUY?
    ... The Rocketport 550 looked promising, as its just a bunch of 16550s on the ... Comtrol EOL'd the entire 550 line several months ago. ... to work under the pucdriver are actually in production either - I've been ... and it is in no way "obsolete" or something I intend to stop supporting. ...
    (freebsd-stable)
  • RE: Fast IR NDIS Miniport Driver for Windows CE
    ... receive functions and may be with the total supported Irda speeds which i was ... supporting to the OID_IRDA query. ... I have developed a Fast IR driver for ARM platform. ... of connection establishment includes baud rate negotiation. ...
    (microsoft.public.windowsce.embedded)