SCSI Drivers
Norman Street
going through the readme files on the HP Navigator CD and they refer to
using either the alad or alad325 driver. My question is, what is the
difference between the two, and which one should I use? Any help will be
appreciated.
Norm
Abid Khan
alad325 since you are installing OSR5.0.5
Sent via Deja.com http://www.deja.com/
Share what you know. Learn what you don't.
Abid Khan
"Norman Street" <NSt...@worldnet.att.net> wrote:
> I am going to be installing SCO OS 5.0.5 on a HP E60 NetServer. I have
been
> going through the readme files on the HP Navigator CD and they refer
to
> using either the alad or alad325 driver. My question is, what is the
> difference between the two, and which one should I use? Any help will
be
> appreciated.
>
> Norm
>
>
Scott Taylor
board or PCI.
Norman Street wrote:
>
> I am going to be installing SCO OS 5.0.5 on a HP E60 NetServer. I have been
> going through the readme files on the HP Navigator CD and they refer to
> using either the alad or alad325 driver. My question is, what is the
> difference between the two, and which one should I use? Any help will be
> appreciated.
>
> Norm
--
Scott Taylor gsta...@junction.net
IT Manager
MAAX Westco Inc. http://www.maax.com
Norman Street
controller for the E60 NetServer. I called HP support about this but they
didn't know what the alad325 was, even though it was their documentation
that mentioned it.
Scott Taylor wrote in message <37D81000...@junction.net>...
Norman Street
automatically detect the proper host adapter and load the appropriate
driver?
Abid Khan wrote in message <7r94gl$v2n$1...@nnrp1.deja.com>...
>In article <7r8v1v$7la$1...@bgtnsc02.worldnet.att.net>,
> "Norman Street" <NSt...@worldnet.att.net> wrote:
>> I am going to be installing SCO OS 5.0.5 on a HP E60 NetServer. I have
>been
>> going through the readme files on the HP Navigator CD and they refer
>to
>> using either the alad or alad325 driver. My question is, what is the
>> difference between the two, and which one should I use? Any help will
>be
>> appreciated.
>>
>> Norm
>>
>>
Scott Taylor
I had a fair amount of grief with that chip set (AIC-7890) on an Asus
board. But that was when it first came out.
Try, at the boot: prompt, enter:
defbootstr ahslink=alad325 Sdsk=alad325(0,0,0,0)
or sometimes just plain link=alad325
You will need the BTDL from HP for that board.
check your documentation again, link may ask you for a number then.
ST
Norman Street
driver is built into the SCO product. Does this mean that it is on the
installation media or do I have to download the driver from SCO? It also
states that I would have to use link instead of ahslink for anything after
5.0.2.
Scott Taylor wrote in message <37D8204A...@junction.net>...
Scott Taylor
Norman Street wrote:
>
> Thanks for the reply. From the documentation I have read, it states that the
> driver is built into the SCO product. Does this mean that it is on the
> installation media or do I have to download the driver from SCO? It also
> states that I would have to use link instead of ahslink for anything after
Yes, the drivers alad and alad325 are both on the 5.0.5 release. If the
documents say the drivers are built in then:
boot: link
link will ask you what you want to link, enter alad325 and follow the
instructions on the screen.
If you don't already have one, there is a btld on your OSR5.0.5 CD.
look in /images/boot/readme.htm to find out how to create a BTLD
diskette in UNIX or MS-DOS
ST
John Gray
> I am going to be installing SCO OS 5.0.5 on a HP E60 NetServer. I have been
> going through the readme files on the HP Navigator CD and they refer to
> using either the alad or alad325 driver. My question is, what is the
> difference between the two, and which one should I use? Any help will be
> appreciated.
>
> Norm
Hi Norm;
Just use the stock kernel off the floppy or the bootable CD. You don't need
to use a BTLD
for 5.05.
-john
Norman Street
following:
The following drivers are present on both the installation diskette and on
the BTLD disk for customer convenience:
Adaptec 154x - ad
Adaptec 294x 394x 494x (785X 7860 7870 7880 7895 Chip) - alad
Adaptec 2940U2W 3950U2 (Ultra-II SCSI 7890, 7897 Chip) - blad
Advanced Micro Devices PCscsi - amd
Symbios Logic (formerly NCR MPD) 53c8xx Host Adapters - slha
ATAPI (Extended IDE) - wd
This leads me to believe that I don't need to link to the alad325 driver. Do
you have any thoughts on this. BTY, I received a call back from HP and they
said that they "think" that I need to use the alad325 driver for OS5.0.5 on
the E60. But, with the information listed above from the readme file, do you
feel that I should just go with whatever the installation media detects?
I'm sorry if I seem to be asking the same question, but I have just been
appointed the resident unix expert and this will be my first customer
installation. Our previous unix expert jumped ship and I am trying to come
up to speed on this.
Norm
Scott Taylor wrote in message <37D83839...@junction.net>...
Scott Taylor
Norman Street wrote:
>
Have you tried anything yet? It won't hurt to try, just waste a little
time. I don't see alad325 in that list. The default is alad anything
else you have to tell boot.
gl
gra...@peachy.org
> I am going to be installing SCO OS 5.0.5 on a HP E60 NetServer. I have been
> going through the readme files on the HP Navigator CD and they refer to
> using either the alad or alad325 driver. My question is, what is the
> difference between the two, and which one should I use? Any help will be
> appreciated.
alad is the Adaptec 2940 driver for SCO 3.2r4.2. alad325 is the Adaptec
2940 driver for SCO 3.2r5.0.x
5.0.5 has both drivers built into the install.
If you don't have the driver disk just let the install use the default. If
you do have a driver disk, link the new driver during the install using
defbootstr ahslink=alad325 Sdsk=alad325(0,0,0,0).
graham.
--
Graham Broadbridge Home <gra...@peachy.org>
Marsfield NSW Australia Work <gra...@insnet.com.au>
Australia AmprNet <vk2...@gw.vk2yui.ampr.org>
<vk2...@amsat.org>
Jean-Pierre Radley
| I am going to be installing SCO OS 5.0.5 on a HP E60 NetServer. I have been
| going through the readme files on the HP Navigator CD and they refer to
| using either the alad or alad325 driver. My question is, what is the
| difference between the two, and which one should I use? Any help will be
| appreciated.
There is no point durng the installation of OSR 5.0.5 where you need to
answer that question; you don't need to use any Adaptec-supplied BTLD
diskette, OSR 5.0.5 already knows how to handle a 2940 card quite well,
thank you.
But, to elucidate:
On 3.2v4.x, or on OSR 5.0.x, the 2940 driver is called alad.
But that code name, alad, does not comprise the same bunch'o'bytes.
IOW, on both 3.2v4 machines and 3.2v5 machines, there's a directory
called /etc/conf/pack.d/alad, and in that directory are files called
Driver.o and space.c. They are NOT identical, and certainly not
interchangeable.
When you get drivers from Adaptec's web site, the drivers for both of
those releases are included in the same archive by Adaptec. The files
intended for 3.2v4 are referred to as alad. The files in that archive
intended for 3.2v5 are referred to as alad325. In either case, the
files get installed under directories called 'alad' on a 3.2v5 machine
as they do on a 3.2v4 machine.
Now why Adaptec is incapable of having its installation script run
'uname -X' and deciding which OS is present, and thus selecting the
correct bunch'o'alad bytes, but instead expects the user to pick alad or
alad325, well, I've no idea. Probably the same mental deficiency which
causes them to provide NO removal script if you want to revert to the
driver you had before.
Given that Adaptec likes to offer its UNIX drivers in a DOS *.exe
archive, don't count on getting an intelligent answer if you write to
them. I've tried, and was sorry I did.
Since I'm quite pleased with the performamnce of their hardware and
software, I grit my teeth and overlook their lacunae.
--
Jean-Pierre Radley <j...@jpr.com> XC/XT Custodian Sysop, CompuServe SCOForum
Jean-Pierre Radley
| Thanks for the reply. From the documentation I have read, it states that the
| driver is built into the SCO product. Does this mean that it is on the
| installation media or do I have to download the driver from SCO? It also
| states that I would have to use link instead of ahslink for anything after
| Scott Taylor wrote in message <37D8204A...@junction.net>...
| >Norman,
| >I had a fair amount of grief with that chip set (AIC-7890) on an Asus
| >board. But that was when it first came out.
| >Try, at the boot: prompt, enter:
| >defbootstr ahslink=alad325 Sdsk=alad325(0,0,0,0)
| >or sometimes just plain link=alad325
| >You will need the BTDL from HP for that board.
| >check your documentation again, link may ask you for a number then.
| >
Scott is wrong.
You do not need any BLTD diskette at all, you do not need to use
the link command, certainly not the ahslink command.
The driver is on the 5.0.5 installation media.
Tom Parsons
| Thanks for the reply. From the documentation I have read, it states that the
| driver is built into the SCO product. Does this mean that it is on the
| installation media or do I have to download the driver from SCO? It also
| states that I would have to use link instead of ahslink for anything after
| 5.0.2.
Alad drivers are part of the OpenServer 5.0.5 distribution and I have
never had a problem with them. Having said that, others have implied
they had problems with certain hardware, most notably the HP machines.
Try the distribution drivers. If they don't work, they use the BTLD
and the proper syntax is link, not ahslink.
| Scott Taylor wrote in message <37D8204A...@junction.net>...
| >Norman,
| >I had a fair amount of grief with that chip set (AIC-7890) on an Asus
| >board. But that was when it first came out.
| >Try, at the boot: prompt, enter:
| >defbootstr ahslink=alad325 Sdsk=alad325(0,0,0,0)
| >or sometimes just plain link=alad325
| >You will need the BTDL from HP for that board.
| >check your documentation again, link may ask you for a number then.
--
==========================================================================
Tom Parsons t...@tegan.com Sysop, SCOForum-CompuServe
==========================================================================
Jean-Pierre Radley
|
|
| Norman Street wrote:
| >
| > Thanks for the reply. From the documentation I have read, it states that the
| > driver is built into the SCO product. Does this mean that it is on the
| > installation media or do I have to download the driver from SCO? It also
| > states that I would have to use link instead of ahslink for anything after
|
| documents say the drivers are built in then:
Please, Scott, you are making things up!
cat /etc/default/scsihas.
There is NO SUCH THING as alad325 as a file name, driver, reference, or
anything else, anywhere on the OSR 5 media, or on an OSR 5 filesystem.
Scott Taylor
So that's where alad325 comes from. Thanks for clearing that up.
ST
> --
> Jean-Pierre Radley <j...@jpr.com> XC/XT Custodian Sysop, CompuServe SCOForum
--
Scott Taylor
Jean-Pierre Radley wrote:
>
> Scott Taylor opined (on Thu, Sep 09, 1999 at 03:44:09PM -0700):
> |
> |
> | Norman Street wrote:
> | >
>
> Please, Scott, you are making things up!
;->
That's what he said his documentation says. I thought it sounded kinda
funny to. Of course, I guess I could have checked first. :o(
>
> cat /etc/default/scsihas.
>
> There is NO SUCH THING as alad325 as a file name, driver, reference, or
> anything else, anywhere on the OSR 5 media, or on an OSR 5 filesystem.
I totally agree with you JP, but if the documentation says to use their
driver and they give it a strange name... He should at least try to
install, if he gets errors or the aha controller isn't found then try to
link another driver.
One time, I installed OSR5.0.4 onto an ASUS board with an on-board AIC
controller and it sucked bad. Nothing would work but:
defbootstr ahslink=alad Sdsk=alad(0,0,0,0)
and use the BTDL diskette that I made from a downloaded driver. The
thing booted, got to the install portion and the thing crapped out at
the dskinit part. So I went back to PCI aha controllers and a different
board and everything went fine. I guess that's fixed now with 5.0.5.
However, I just installed 5.0.5 and ahslink did work for changing the
defbbotstr to mdac and link even asked for the BTLD disk, and it works
fine. I believe you can still use ahslink to replace or update the alad
drive the same way during an installation, no? Although link is much
more simplified.
That AIC controller was a good lesson, I will never try to cheap out on
mother boards again, and I always check chwp for the right parts before
I buy/build a new server.
:o)
Thanks for pointing out the alad325, I thought it sounded kinda hoaky
too.
ST
Norman Street
on a Vectra I use as server and had no problems. I think my first mistake in
this mess was to read the SCO installation notes that came in the HP
Navigator CD-ROM. In the readme file it indicates that alad325 must be used.
As it turns out, that just refers to alad driver version 3.25. According to
the HP tech I worked with for three hours this morning, the alad version
currently included with the OS5 installation media is version 5.22 so the
alad325 is a non-issue. The problem now is that the Adaptec controller can
see the 9.1GB hard drive from a bios level, but the drive isn't being seen
by unix or dos. HP is sending out a tech on Monday to fix the problem. I
personally don't care if the tech comes or not as long as the parts arrive.
I have a feeling that the installation will go smoothly once the system is
behaving. I will let you know if I am still having problems.
Norm
Jean-Pierre Radley wrote in message
<1999090921...@jpradley.jpr.com>...
ds
chipsets. Try it first.
Do apply the recommended supplements for 505.
* Sent from RemarQ http://www.remarq.com The Internet's Discussion Network *
The fastest and easiest way to search and participate in Usenet - Free!
do...@nospamdellit.com.au
I have installed OS 5.0.5 on about 10 HP boxes recently and it has
been an absolute breeze. I installed two E60 boxes last week - took
about an hour each in total for basic OS. I have learnt that with HP
Servers you just expect SCO Unix to go straight on (I did not use to
be a HP fan but I am now). If there are any odd parts to the
installation, it will be well covered in Docs.
For E60 (or any other HP Server), I boot HP Navigator CD, follow
instructions to create three SCO driver disks, boot SCO Unix from CD,
install SCO, after reboot run "custom" and install network driver from
3rd HP floppy disk. After reboot everything is working. I don't
bother with what type of network card it is. The Adaptec is just an
Ultra-Wide not a U2W so is used "alad" when installing the tape.
Extremely straight forward install - no external drivers.
Doug
Norman Street
I agree that the installation should be straight forward. But, after reading
the readme file included with the E60, I have come to the conclusion that HP
isn't very familiar with the SCO install process. HP seems to agree with me
to some extent. The tech I worked with said that he took the readme file up
the chain of command and every person that looked at it was confused. They
promised that the SCO readme is going to be re-written ASAP. Anyway, I am in
a wait and see mode this morning waiting for the HP tech to come out and
swap the hard drive. With any luck, the tech will actually show up and fix
the system so I can install unix today.
Norm
do...@NOSPAMdellit.com.au wrote in message
<37dc8e3a....@news.arach.net.au>...
Norman Street
working with HP on the phone for half the day, they sent out a tech with a
mainboard and a hard drive. The problem is that he wasn't able to fix or
figure out the problem. I sent it back to the vendor and received a new E60
the next day. The installation has gone just fine on the new machine. Thanks
for the quick responses.
Norm
Norman Street wrote in message <7rj6ug$ahs$1...@bgtnsc03.worldnet.att.net>...