Technical article 105819

mkdev serial hangs looking for a second serial port.

OpenServer 5.0.0OpenServer 5.0.2OpenServer 5.0.4OpenServer 5.0.5

Written · Last revised

Problem

I am experiencing one (or both) of the following problems:

1. I am trying to add COM2 via Scoadmin/Hardware. I have checked the cmos to see that it is enabled prior to entering Scoadmin. The procedure appears to go fine. I choose to relink and a screen returns saying that COM2 has been added successfully, and to press <Enter> to continue. I press <Enter> but the system is hung. I am forced to hit the reset button. Upon bootup it would appear that COM2 has been added successfully.

2. I use mkdev serial in a character screen, and it hangs after displaying the information for COM1. It seems to be searching endlessly for something.

NOTES:    This problem is fixed in SCO OpenServer Release 5.0.6.

Solution

For SCO OpenServer 5.0.5 (and earlier):

If you're experiencing what is described in #1, the workaround is to use "scoadmin serial" from a character screen.

If you're experiencing what is described in #2, follow this script to troubleshoot it.

This problem could be caused by a number of things. Read through the following possibilities, and apply each corresponding test to determine the source of this behavior on your system:

1. Shut down, then restart the system; enter the CMOS and check the COM port entries. Are they both enabled? Write down the address and IRQ values for each com port as they are displayed in the CMOS.

2. Bring the system up, and type "hwconfig -hc". Does hwconfig
report possible conflicts?  Do you see output that looks like this:

serial 0x3f8-0x3ff 4 - unit=0 type=Standard nports=1 fifo=no serial 0x2f8-0x2ff 3 - unit=1 type=Standard nports=1 fifo=no

The lines above reflect the default configuration values for com1
and com2 expected by the kernel. Do the address and IRQ values in
this output match the values from the CMOS? If not, update the CMOS
values to match those displayed from hwconfig. Do you see any other
drivers listed with vectors 3 or 4? If so, this could cause mkdev
serial to hang. The device(s) using IRQ 3 and 4 will need to be
removed and  reconfigured to use different interrupt vectors if you
wish to configure and use com1 and com2. If you do not want to
configure com2, and wish to use IRQ 3 for a device other than com2,
follow TA106439, "Removing the second serial port COM2 from the
SCO XENIX kernel" to free up IRQ 3 by removing com2 entries from
the link kit.

3. If you are using the scoadmin GUI (or serial manager) and are experiencing a hang before the link, try using "mkdev serial" from a character screen to determine if the GUI interface is the problem.

4. To find out where the script is hanging, edit the file /usr/lib/mkdev/serial. Add the line "set -x" to the beginning of the script, save, and run mkdev serial. You may want to redirect output to a file so you can easily look through it. The "set -x" line will cause each script command to be echo'd to stdout as it is executed.

5. Does your system have an internal modem? If so, remove the internal modem card, reboot, and try "mkdev serial" again.

6. If the above suggestions do not solve your issue, contact your SCO Software Support Supplier.

See also

TA106439, "Removing the second serial port COM2 from the SCO kernel."

TA105768, "After OS install my system hangs when trying to add COM2 via SCOADMIN/HARDWARE."

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