F Card Problems



This appendix explains how to troubleshoot problems with your Serial Parallel Controller card. If your system is displaying messages, see Appendix G for an explanation of the messages. You can use these messages to determine which of the following five problems is most likely affecting your card. Follow the instructions for correcting the appropriate problem. Problems are organized according to when you are most likely to experience them during installation.

System Initialization Problems

If the system cannot recognize that your Serial Parallel Controller card has been installed into your system, you will see a message on your console similar to the following example:

The problem might be a faulty card or corrupted device driver. To determine which is the cause of the problem:

    1. Remove your Serial Parallel Controller card and install it again in the same SBus slot.

    After powering your system on, observe the boot messages. If you see the preceding message again, your card is most likely faulty and must be replaced. Otherwise proceed to the next step.

    2. Install your device driver again.

    The device driver might have become corrupted. If the software is not corrupted, installing the device driver again will initialize your card correctly.

Serial Port Problems

If your Serial Parallel Controller card initializes correctly, but peripherals or modems connected to the patch panel do not operate correctly or SunOS displays device error messages, you most likely have serial port problems. You can use the spiftest program installed with your device driver to determine which port(s) is responsible for the problem.

To use the spiftest program:

    1. Quit processes on the particular card you wish to test.

    Processes using the serial and parallel ports might interfere with the spiftest program.

    2. If a specific serial port is responsible for the problem, disconnect the serial cable of the peripheral or modem from the port.

    Install a 25-pin loopback connector on the port you wish to test.

    3. Type cd /usr/diag/sundiag and press the Return key.
    4. Type spiftest D=/dev/ttyz# T=8 and press the Return key.

    For # type the number of the peripheral or modem you wish to test. This command runs a data loopback to the port to test the path from your card to the 25-pin serial port connector on your patch panel.

    If the test is successful, the problem is most likely a faulty peripheral, modem, or serial cable. Otherwise, the problem might be a faulty patch panel, 96-pin cable, or card. To determine whether the problem is a faulty patch panel or cable, follow the instructions for troubleshooting patch panel and cable problems later in this appendix.

Parallel Port Problems

If the printer connected to the parallel port does not print, perform the following instructions.

    1. Quit processes using the parallel port.

    Processes using the parallel port might interfere with the diagnostic programs that test the parallel port for correct operation.

    2. If your parallel printer has a test print diagnostic, run the test to determine whether the basic electronics and print mechanism of your printer are working correctly.
    3. Make sure the parallel cable is connected properly to the printer and to the parallel port on your patch panel.

    Disconnect the cable and inspect the connector contacts at both ends. They must be clean and free from obstructions.

    4. If you have another parallel cable, connect one end to the printer and the other end to the parallel port on your patch panel.
    5. Test the printer again using the new cable.

    To test the new cable:

      a. Type cd /usr/diag/sundiag and press the Return key.
      b. Type spiftest D=/dev/stclp# T=2 and press the Return key.

      For #, type the number of the Serial Parallel Controller card you wish to test. For example, if the printer is connected to the first or second card, use D=/dev/stclp0 or D=/dev/stclp1, respectively.

      If the test is successful, your printer prints the ASCII character set.

    6. If the printer prints under the control of the spiftest print program, but does not print under the control of SunOS or an application program, the most likely cause is a software or setup problem.
    7. If the printer does not appear to receive data from your system, test the parallel port on your Serial Parallel Controller card for correct operation.

    To test the parallel port on your card:

      a. Disconnect the 96-pin cable from the rear panel connection of your card.
      b. Connect the 96-pin loopback connector to the rear panel connection of your card.
      c. Type cd /usr/diag/sundiag and press the Return key.
      d. Type spiftest D=sb# T=4 and press the Return key.

      For #, type the number of the Serial Parallel Controller card you wish to test. For example, if the printer is connected to the first or second card, use D=sb1 or D=sb2, respectively.

      This command runs a data loopback test of the parallel port on the card, and reports any errors.

    8. If the card passes the loopback test, but your printer does not print under the control of the spiftest print program, the most likely cause is a faulty 96-pin cable, patch panel, or both.

Serial Parallel Controller Card Problems

If you suspect that the problem concerns any or all of the ports on your card, determine whether the problem is the electronics or the connector on your card.

To determine whether the electronics on your card is the problem:

    1. Disconnect the 96-pin cable from the rear panel connection of your card.
    2. Type cd /usr/diag/sundiag and press the Return key.
    3. Type spiftest D=sb# T=1 and press the Return key.

    For #, type the number of the Serial Parallel Controller card you wish to test. For example, if the problem is with the first or second card, use D=sb1 or D=sb2, respectively.

    This command runs an internal test of the electronics on your card. If the test reports any errors, your card is faulty and you must replace it. If the test is successful, test the connector on your card.

To determine whether the connector on your card is the problem:

    1. Connect the 96-pin loopback connector to the rear panel connection of your card.
    2. Type cd /usr/diag/sundiag and press the Return key.
    3. Type spiftest D=sb# T=4 and press the Return key.

    For #, type the number of the Serial Parallel Controller card you wish to test. For example, if the problem is with the first or second card, use D=sb1 or D=sb2, respectively.

    This command runs a data loopback test on all ports on your card. If the test reports any errors, the most likely cause is faulty components on your card (data drivers or receivers). You must replace your card.

Patch Panel and Cable Problems

If you suspect that the problem concerns the 96-pin cable or patch panel, determine whether the problem is the cable or patch panel.

To determine which is the problem:

    1. Quit processes using the ports.

    Processes using the ports might interfere with the diagnostic programs that test the ports for correct operation.

    2. Disconnect the terminal or printer cable from your patch panel.
    3. If all ports cannot communicate with terminals or printers, determine whether your card is the problem.

    See "Serial Parallel Controller Card Problems" earlier in this appendix.

    4. If the card passes both tests in that section, the problem might be a faulty 96-pin cable or patch panel.
    5. Replace the 96-pin cable.
    6. If the problem continues, replace the patch panel.