Technical article 101588

Errors relinking kernel after adding second Racal-Interlan ES3210 (EISA) NIC.

OpenServer 5.0.0

Written · Last revised

Problem

One Racal-Interlan ES3210 (EISA) network card is installed and
running fine.  Upon adding a second of the same card, I am
prompted to relink the kernel. Then, I receive errors similar to:

"/var/opt/K/SCO/Unix/5.0.0Cl/etc/conf/pack.d/i3B/space.c", line 68: warning: undeclared initializer name I3B1_CHAN "/var/opt/K/SCO/Unix/5.0.0Cl/etc/conf/pack.d/i3B/space.c", line 68: illegal initialization ERROR: '/var/opt/K/SCO/Unix/5.0.0Cl/etc/conf/pack.d/i3B/space.c' will not compile properly

ld Driver.o fatal: Can't open file
/var/opt/K/SCO/Unix/5.0.0Cl/etc/conf/pack.d/i3B/space.o for input
ERROR: Can not link-edit unix

The relink fails although it appears that the card is correctly configured and installed.

Cause

There is a known error in the driver's space.c file.

There is only one entry for this card in the /etc/conf/cf.d/mdevice
file, and therefore the system thinks only one DMA channel in the
link kit is available for both cards.  However, the driver should
obtain the DMA channel directly from the EISA config information.
Unfortunately, the error in the space.c file prevents this from
occurring.

Solution

Edit the /etc/conf/pack.d/i3B/space.c file manually.
Find the line that refers to "I3B1_CHAN" and change "I3B1_CHAN"
to "0" (the number zero, without quotes).  Then try to relink
again (see below).  If you don't get any errors, shutdown and
reboot the system.

If that relink doesn't work, edit the space.c file and replace "I3B_CHAN" with the exact DMA channel that the new adapter uses. (This information should be available from the EISA config).

The affected line looks like this:
#if (I3B_1 > 100)
    ,(I3B_1 - 100) * 0x1000, I3B_1_VECT, I3B1_CHAN, I3B_1_SCMA, THIK
                                         ^^^^^^^^^
                                 change this to 0 or DMA#

You may also be able to replace the variable with I3B_CHAN.

You will then need to relink and reboot:

cd /etc/conf/cf.d
./link_unix -y
shutdown -g0 -y -i6

Your second NIC should now be recognized.

From the Xinuos technical article database, record 101588. Reproduced with permission. The original is at www.sco.com/ta/101588, 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.