SEO

I inherited an SCO 5.x UNIX machine.

It has a NIC card, but is not listed in the hardware config.

Model is D5013-60001. That model is not listed in types to install.

When connected to Network, the card shows green lights, but I'm not sure
what that means. Maybe that the card is working hardware wise, but has not
been installed?

Any ideas, or would it be best to just buy a new card and put it into
machine.

If someone can help, I can furnish any additional information.

Thanks.

don wrote:
> I inherited an SCO 5.x UNIX machine.
>
> It has a NIC card, but is not listed in the hardware config.
>
> Model is D5013-60001. That model is not listed in types to install.
>
> When connected to Network, the card shows green lights, but I'm not sure
> what that means. Maybe that the card is working hardware wise, but has not
> been installed?
>
> Any ideas, or would it be best to just buy a new card and put it into
> machine.

Yep, hasn't been installed - you may be able to download a SCO driver
from HP. You'll need to install the driver into 'the set of drivers
available to install' ie put it on the hard drive in a place where sco
knows about it, then run netconfig to install the driver for the NIC,
relink, reboot.

If the NIC doesn't get auto-detected you probably have installed a
driver for a NIC you don't have. Try another driver.

After a while this silly dance get tiresome, and browsing the Hardware
Compatibility List and a trip to the store starts to look good. Others
will chime in with their favorite NICs for SCO.

On Mon, 12 Apr 2004 22:40:18 -0000, don <donw.ns@ns.mweco.com> wrote:

>I inherited an SCO 5.x UNIX machine.
>
>It has a NIC card, but is not listed in the hardware config.
>
>Model is D5013-60001. That model is not listed in types to install.
>
>When connected to Network, the card shows green lights, but I'm not sure
>what that means. Maybe that the card is working hardware wise, but has not
>been installed?
>
>Any ideas, or would it be best to just buy a new card and put it into
>machine.
>
>If someone can help, I can furnish any additional information.
>
>Thanks.

Well, first thing I would check is the exact version of SCO. Start
with
# uname -X

(this will give you the release version, among other things), and then


# grep IQM_PROD_DESC /var/adm/ISL/iqm_file

which will tell us whether you are running Host or Enterprise. If
it's Host, you will have no networking capabilities. If Enterprise,
run
# netconfig

and see what shows up.

The D5013 is, AFAIK, an Intel-based HP/Compaq 10/100 PCI card. With
the correct drivers, netconfig should automagically 'see' it.


Scott McMillan

Scott McMillan <smcm@usa.net> wrote in
news:1dpn7050sjm24rqvf2j2tcppg6d5bnm7h4@4ax.com:

> Well, first thing I would check is the exact version of SCO. Start
> with
> # uname -X
>
> (this will give you the release version, among other things), and then
>
>
> # grep IQM_PROD_DESC /var/adm/ISL/iqm_file
>
> which will tell us whether you are running Host or Enterprise. If
> it's Host, you will have no networking capabilities. If Enterprise,
> run
> # netconfig
>
> and see what shows up.
>
> The D5013 is, AFAIK, an Intel-based HP/Compaq 10/100 PCI card. With
> the correct drivers, netconfig should automagically 'see' it.
>
>
> Scott McMillan

uname -X reveals 3.2v5.05

grep reveals Enterprise

netconfig list a big group of devices, none of which have any numbers
corresponding to any of the numbers found on the board.

I did a search on HP website for D5013A-60001, a number I found on the
board and it told me it was a OEM version of Intel Pro 100B which is one of
the devices listed by netconfig.

I will try installing it tonight or tomorrow morning when no users on
system. I assume it will want me to relink the kernal.

Any other caveats you might have for me?

Thanks for the responses.


--
<IMG SRC=http://www.strousesoftware.com/sss1.jpg>
My Signature

Fabio Giannotti typed (on Tue, Apr 13, 2004 at 04:04:40PM +0000):
|
|
| So, before running netconfig, do:
|
| hw -r pci |more
|
| and look for something that says "etherner controller" or something like
| that. It will list a bunch of info for the card. The first three items
| should be what you need.

Simpler to type, but the same result:

hw -mr pci

--
JP

On Tue, 13 Apr 2004 15:10:48 -0000, Don <donns@yahoo.com> wrote:

>Scott McMillan <smcm@usa.net> wrote in
>news:1dpn7050sjm24rqvf2j2tcppg6d5bnm7h4@4ax.com :
>
<snip>
>
>uname -X reveals 3.2v5.05
>
>grep reveals Enterprise
>

Good. How about patches?
# customquery Listpatches | head -1

I would recommend at the very least
rs505a
oss497c
oss600a

All of which (and more) can be found here:
http://support.sco.com/rn_cgi/instal...hp?p_li=&p_sp=

>netconfig list a big group of devices, none of which have any numbers
>corresponding to any of the numbers found on the board.
>
>I did a search on HP website for D5013A-60001, a number I found on the
>board and it told me it was a OEM version of Intel Pro 100B which is one of
>the devices listed by netconfig.

Yep, that's what I recall. Should be as simple as selecting the Intel
Pro100 in netconfig.

>
>I will try installing it tonight or tomorrow morning when no users on
>system. I assume it will want me to relink the kernal.

Your assumption is correct. Make sure you have a couple of good
backups!!

>
>Any other caveats you might have for me?

You may want the latest 5.0.5 drivers for the Pro100B:
ftp://stage.caldera.com/pub/drivers/...etwork/pro100b

>
>Thanks for the responses.

Best of luck


Scott McMillan

Scott McMillan typed (on Tue, Apr 13, 2004 at 12:32:19PM -0400):
| On Tue, 13 Apr 2004 15:10:48 -0000, Don <donns@yahoo.com> wrote:
|
| >Scott McMillan <smcm@usa.net> wrote in
| >news:1dpn7050sjm24rqvf2j2tcppg6d5bnm7h4@4ax.com :
| >
| <snip>
| >
| >uname -X reveals 3.2v5.05
| >
| >grep reveals Enterprise
| >
|
| Good. How about patches?
| # customquery Listpatches | head -1
|
| I would recommend at the very least
| rs505a
| oss497c
| oss600a
|
| All of which (and more) can be found here:
| http://support.sco.com/rn_cgi/instal...hp?p_li=&p_sp=
|
| >netconfig list a big group of devices, none of which have any numbers
| >corresponding to any of the numbers found on the board.
| >
| >I did a search on HP website for D5013A-60001, a number I found on the
| >board and it told me it was a OEM version of Intel Pro 100B which is one of
| >the devices listed by netconfig.
|
| Yep, that's what I recall. Should be as simple as selecting the Intel
| Pro100 in netconfig.
|
| >
| >I will try installing it tonight or tomorrow morning when no users on
| >system. I assume it will want me to relink the kernal.
|
| Your assumption is correct. Make sure you have a couple of good
| backups!!
|
| >
| >Any other caveats you might have for me?
|
| You may want the latest 5.0.5 drivers for the Pro100B:
| ftp://stage.caldera.com/pub/drivers/...etwork/pro100b
|

Obsolete URL, Scott, you do a disservice by pointing to it. All that's
there is the trps driver for 5.0.6; nothing from 21st century.

You really want to get them from ftp.sco.com, except as another thread
just pointed out, stuff just went missing from there.


--
JP

On 13 Apr 2004 12:43:05 -0400, Jean-Pierre Radley <jpr@jpr.com> wrote:

>Scott McMillan typed (on Tue, Apr 13, 2004 at 12:32:19PM -0400):
<snipped>
>| You may want the latest 5.0.5 drivers for the Pro100B:
>| ftp://stage.caldera.com/pub/drivers/...etwork/pro100b
>|
>
>Obsolete URL, Scott, you do a disservice by pointing to it. All that's
>there is the trps driver for 5.0.6; nothing from 21st century.

Really? I see all kinds of stuff, aside from the trps driver. I had
looked at the April 2000 date/time stamp on the eeE VOL file and
believed that to be about right (for 5.0.5).

>
>You really want to get them from ftp.sco.com, except as another thread
>just pointed out, stuff just went missing from there.

That's the first place I looked, and was surprised to find nothing
there (at about the same time Bob Bailin was posting "Where is
ftp.sco.com/pub/openserver ?")

My apologies for pointing to the older drivers.


Scott McMillan

Don <donns@yahoo.com> wrote:

>netconfig list a big group of devices, none of which have any numbers
>corresponding to any of the numbers found on the board.

It shouldn't be listing anything but the single card that is there.

You have an unsupported card or the wrong driver loaded. If you
haven'tb checked SCO's ftp site for updated drivers, do so.


--
tony@pcunix.com Unix/Linux/Mac OS X resources: http://aplawrence.com
Get paid for writing about tech: http://aplawrence.com/publish.html

tony@pcunix.com typed (on Tue, Apr 13, 2004 at 10:28:01PM +0000):
| Don <donns@yahoo.com> wrote:
|
| >netconfig list a big group of devices, none of which have any numbers
| >corresponding to any of the numbers found on the board.
|
| It shouldn't be listing anything but the single card that is there.

Tony, you certainly have noticed that if netconfig doesn't autodetect
the card, the user does have the option to see OSR's list of available
drivers and pick amongst them.


--
JP