Technical article 101602

Error from network card: "Cannot automatically determine transceiver" when booting.

OpenServer 5.0.0OpenServer 5.0.2OpenServer 5.0.4OpenServer 5.0.5OpenServer 5.0.6UnixWare 7.0.0UnixWare 7.0.1UnixWare 7.1.0

Written · Last revised

Problem

After initially configuring a network card, or after modifying an
existing card's settings, you need to relink and reboot.  During
this reboot, you may see an error similar to:

WARNING: Etherlink III unit0: ERROR: Cannot automatically determine transceiver

This sometimes occurs along with errors from dlpid about not being able to access the network device.

Cause

The error indicates that either the software or hardware (or
both) are set to automatically try to determine the transceiver
type.  The transceiver is the physical connection to your network
media (cabling).

Solution

Since it is usually easier to modify the software settings, use
netconfig (OpenServer), niccfg (UnixWare 2.x), or netcfg
(UnixWare 7.x) to modify the transceiver type.  When you configure
certain adapters, you need to manually enter information as to
whether the adapter connects to "thick," "thin," or "twisted-pair"
Ethernet cable.  Thick and thin are both coaxial cable.  Thick
cable is approximately 1/2-inch in diameter, and thin is
approximately 1/4-inch in diameter.  Twisted pair resembles
slightly thicker phone cable.

- Thick cable (also known as "10Base5" and "DIX") uses a 15-pin AUI (Attachment Unit Interface) connector to connect your adapter to a transceiver, which in turn connects to the Ethernet cable.

- Thin cable (also known as "10Base2" and "Cheapernet") uses an on-board transceiver and connects to the Ethernet with a BNC connector.

- Twisted-pair cable (also known as "10BaseT") connects to a hub transceiver using an RJ-45 modular plug connector.

Some network cards have an "autodetect" option for media type, but if you are getting errors about the transceiver, you should enter one of the above options.

You will have to relink and reboot after making these changes.

You may also have to reconfigure the NIC at the hardware level. For some cards, you will have a configuration disk that will rewrite the ROM settings on the card. Other cards can be reset through the EISA or PCI setup; finally, some older cards have jumpers or DIP switches to make the change. Reset the card to use a specific media type, relink and reboot.

NOTES:    3COM also has information on their Web site (www.3com.com)
          detailing this problem (article number 01854).  It says you
          need to edit /etc/conf/pack.d/e3[x]/space.c, where '[x]' will
          depend on the network card type. The lines to change follow.

Change the value short e3G_xcvr [4] = {8, 8, 8, 8} to:

... /... /* transceiver type for each board, 0 = 10BASE-T, 1 = 10Mbps AUI, 2 = 100BASE-T4, 3 = 10BASE-2 (coax), 4 = 100BASE-TX, 5 = 100BASE-FX, 6 = MII, 7 = reserved, 8 = automatic selection */ short e3G_xcvr [4] = {0, 0, 0, 0}; ... /...

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