Technical article 109368

Why doesn't SCO OpenServer 5.0.4 or 5.0.5 detect my network card?

OpenServer 5.0.4OpenServer 5.0.5

Written · Last revised

Problem

When /etc/netconfig is run, my network card is not detected. The following shows how /etc/netconfig detects which cards it has in the system. The pathnames are specific to a 5.0.4 system; for OpenServer 5.0.5 systems, replace "5.0.4d" with "5.0.5a":

1. /etc/netconfig calls:
/opt/K/SCO/lli/5.0.4d/ncfg/ncfgBE
which calls:
/opt/K/SCO/lli/5.0.4d/bin/ndscript
which calls:
/opt/K/SCO/lli/5.0.4d/bin/pcislot

2. The pcislot program outputs the subsystem vendor and device IDs, if they exist (non-zero); otherwise it outputs the vendor and device IDs.

3. Next, the system compares these IDs with the ones it knows
   about.  The /opt/K/SCO/lli/5.0.4d/bin/ndscript searches
   through the /var/opt/K/SCO/lli/5.0.4d/ID/*/AOF/* directory
   recursively.
It tries to match the subsystem vendor and device IDs found by the
pcislot program with the IDs in the ID subsection of the ADAPTER
section of the "card"/AOF/"card" files, which have an entry
"BUS=PCI".  For example, stbg/AOF/stbg-pci or pnt/AOF/pnt-pci.

When a match is found that card is displayed as a choice in the netconfig window.

As an example, the following describes a machine that does
detect its network card.  pcislot gives the following:
Bus Device Function ID(v-4,d-4,r-2) BaseIO
 0 0 0 8086123702
 0 7 0 5333881154
 0 11 0 1014002201
 0 19 0 8086700001
 0 19 1 8086701000 4020
 0 19 2 8086702001 4000
 1 3 0 1014002e03  3100
 1 4 0 9004807800  3000
 1 5 0 1022200025  3200 <-----AMD Vendor(1022),
                              Device 2000(PCI-Net)
This shows the network card as:
Bus=1
Device=5
Function=0
AMD=1022
Device=2000
Rev=25
I/O=3200

Then ndscript searches the /var/opt/K/SCO/lli/5.0.4d/ID directory structure for any references to 10222000 in the ID subsection of the Adapter section of the "card"/AOF/"card" files, which have an entry "BUS=PCI".

In this case, it finds there are two entries; one is the "IBM PCI Ethernet" in the stbg/AOF/stbg-pci file and the second is the "AMD PCNet-PCI Adapter" in the pnt/AOF/pnt-pci file.

The output from an "hw" command shows the following for the card:

Index: 8
    DeviceNum:     5
    Function:      0
    Bus:           1
    VendorId:      0x1022      Advanced Micro Devices
    DeviceId:      0x2000      PCNet-PCI
    RevId:         0x25
    Command:       0x0107      Memory Enabled, I/O Enabled
    Status:        0x0280
    ClassCode:     0x020000    Ethernet controller
    CacheLineSize: 0           No limiting
    LatencyTimer:  0x90
    HeaderType:    0x00        Single-function, Standard encoding
    SelfTest:      0x00        Not BIST capable
    BaseAddr[0]:   0x00003201  I/O 0x3200
    BaseAddr[1]:   0x50003000  Memory 0x50003000, 32 bit space
    BaseAddr[2]:   0x00000000
    BaseAddr[3]:   0x00000000
    BaseAddr[4]:   0x00000000
    BaseAddr[5]:   0x00000000
    CardbusCISPtr: 0x00000000
    SubsysVendorID:0x0000
    SubsystemID:   0x0000
    ROMbaseAddress:0x00000000  Expan ROM   0x00000000, Disabled
    InterruptLine: 0x0b        IRQ-11
    InterruptPin:  0x01        INTA
    Min_Gnt:       0x12
    Max_Lat:       0xff
pcislot checks the SubsysVendorID and SubsystemID, which are zero,
and then outputs the VendorId and DeviceId, which gives 1022 and
2000 respectively.  This indicates an AMD vendor ID and a PCNet-PCI
device ID.

As another example, here is a machine that does not detect its network card.

The hw output for the network card gives:

DeviceNum:      14
Function:       0
Bus:            0
VendorId:       0x1022      Advanced Micro Devices
DeviceId:       0x2000      PCNet-PCI
RevId:          0x25
Command:        0x0147      Memory Enabled, I/O Enabled
Status:         0x0280
ClassCode:      0x020000    Ethernet controller
CacheLineSize:  0           No limiting
LatencyTimer:   0x30
HeaderType:     0x00        Single-function, Standard encoding
SelfTest:       0x00        Not BIST capable
BaseAddr[0]:    0x00002181  I/O 0x2180
BaseAddr[1]:    0xfebfdc00  Memory 0xfebfdc00, 32 bit space
BaseAddr[2]:    0x00000000
BaseAddr[3]:    0x00000000
BaseAddr[4]:    0x00000000
BaseAddr[5]:    0x00000000
CardbusCISPtr:  0x00000000
SubsysVendorID: 0x1014      IBM
SubsystemID:    0x2000
ROMbaseAddress: 0x00000000  Expan ROM   0x00000000, Disabled
InterruptLine:  0x0f        IRQ-15
InterruptPin:   0x01        INTA
Min_Gnt:        0x18
Max_Lat:        0x18

pcislot checks the SubsysVendorID and SubsystemID, which are 1014 and 2000 respectively, whereas the VendorId and DeviceId are 1022 and 2000 respectively.

So, the VendorID indicates an AMD device and the SubsysVendorID indicates an IBM device.

The output from pcislot is:
Bus Device Function ID(v-4,d-4,r-2) BaseIO
0 0 0  8086719202
0 3 0  1014002e04 2000
0 4 0  1014002207
0 14 0 1014200025 2180 <---IBM Vendor, Device 2000,
                           Unknown in the AOF
0 15 0 5333890116
0 19 0 8086711002
0 19 1 8086711101 ffa0
0 19 2 8086711201 ff00
0 19 3 8086711302
Bus=0
Device=14
Function=0
Vendor=IBM
Device=2000
Rev=25
I/O=2180

Next, the ndscript searches the /var/opt/K/SCO/lli/5.0.4d/ID directory structure for any references to 10142000 in the ID subsection of the Adapter section of the "card"/AOF/"card" files, which have an entry "BUS=PCI".

In this case, it does NOT find any entries which is why none are displayed.

NOTE: The entries in the AOF files are case dependent.

Solution

You need to configure the card manually using the parameters as given by the "pcislot" program.

So, for example, the AMD PCNet card would be selected and the Bus, Device and Function would be set to 0, 14, and 0 respectively.

For autodetection to work, ask your hardware system and/or network card suppliers to work through their channels with SCO to get their network cards/chips approved.

From the Xinuos technical article database, record 109368. Reproduced with permission. The original is at www.sco.com/ta/109368, which is reachable but blocked from search engines. Xinuos marks this article against a retired product line. That refers to the product’s lifecycle, not to whether the advice still works — plenty of it still applies to running systems.

Next step

Need this fixed rather than explained?

Tell us the release, what the system runs and what it is doing. We will reply by email with what we would do next.

  • You deal with the people who do the work
  • No obligation, and no upgrade required before we will help
  • We tell you plainly if something is not worth doing

Send an enquiry

We reply by email. If a server is down, say so in the first line. You can also write to help@scoexpert.com.