Contents:
The information in this Section is designed
to help you identify the cause of error situations and to correct them
quickly.
All Stallion Technologies' products are supplied
with comprehensive Diagnostic software which also pin-points problems.
See the DOS Diagnostics section for
instructions on how to use the Diagnostic software.
If you encounter a problem or error during installation,
these points should assist you in makping the system operational.
Booting Problems
System does not boot
and console remains blank
Step 1.
Check system power supply by listening for fan and disk motor or observing
indicator lights.
Step 2.
Does system boot without an EasyIO or EasyConnection board? If yes,
system works without an EasyIO or EasyConnection board:
- Check that the board is not shorting on
an adjacent card.
- Visually check board for burnt-out components
Step 3.
If no, system does not boot without EasyIO or EasyConnection board
the problem is in System Hardware.
* Refer to system manuals for troubleshooting procedure.
* Check nothing was disturbed when EasyIO or EasyConnection board
was plugged in.
System begins to boot
but stops before operating system starts to load
Step 1.
Check there is no diskette in diskette drive.
Step 2.
Is the disk controller card OK?
- Check controller card is seated properly.
- Check cables haven't been dislodged.
- Check controller isn't shorting with other boards.
Step 3.
For upgrade or new installations, can you boot from an old kernel
(eg. unix.old)? If yes, contact your dealer for support.
System boots, begins
to load, but stops in the Unix configuration banner. (SCO Unix/XENIX
only)
Step 1.
Check at what point in the boot banner it stops and refer to the system
manual.
Step 2.
Does the system boot if the EasyIO or EasyConnection board is
removed?
Step 3.
If so, is there a message similar to:
"EasyIO Not Found: nr=1 type=21 io=000003A0 irq=0'?
or:
"EasyIO Not Found: nr=1 type=21 io=000003A0 irq=0'?
Step 4.
If you can boot off a pre-EasyIO or pre-EasyConnection kernel, the
board configuration is probably in conflict with another peripheral.
New or upgrade installation
- board boots to Unix, but banner reports message similar to:
(A) "EasyIO Not Found:
nr=1 type=21 io=00000204 mem=000D0000 irq=0'
(B) "EC 8/64 Not Found:
nr=1 type=21 io=00000204 mem=000D0000 irq=0'
Possible Causes:
Step 1.
Check that switches are set correctly to match software installation.
Step 2.
Conflict of I/O address or with another device's configuration.
System has been operating
for some time, when system boots, banner reports message similar to:
(A) "EasyIO Not Found:
nr=1 type=21 io=00000204 mem=000D0000 irq=0'
(B) "EC 8/64 Not Found:
nr=1 type=21 io=00000204 mem=000D0000 irq=0'
Step 1.
Isolate software causes: Check on other changes made to the system.
Check if new kernels have been built. Try booting an older kernel.
Step 2.
If no software causes are found: Board may be damaged or dislodged.
Try re-seating the board or call your Support Center.
Problems adding extra
boards
Step 1.
Treat the problem as for a problem with a single board.
Step 2.
Check that each board functions separately in the system.
Step 3.
Check if the power supply has the capacity to run a number of boards.
Other peripherals stop
functioning or function incorrectly after board installation
Most likely the EasyIO or EasyConnection board
configuration uses some settings already used by another installed device
(ie. a configuration conflict).
Step 1.
Check that the switches are correct.
Step 2.
Does the peripheral still work on a pre-EasyIO or pre-EasyConnection
board installation kernel?
Step 3.
Check that other controllers have not been physically disturbed.
Step 4.
Check that all cables are intact.
Step 5.
Remove the board. Do the other peripherals work?
Step 6.
Try configuring the board to use a different interrupt.
Step 7.
Try configuring the board to use a different I/O address.
Terminal Problems
System boots correctly
but there are no login messages on the terminals
Step 1.
Check the port is configured and enabled in the software driver.
If the green activity indicator on EasyConnection
modules is on continuously, there may be a hardwre interrupt conflict
with another installed device. Try a different interrupt.
Step 2.
Check the port and terminal communication parameters are the same:
- Baud Rate.
- Bits/Character.
- Parity (Odd, Even, None).
- Stop Bits (1 or 2).
- Handshaking (Software, Hardware, Both, None) .
- Verify the terminal is OK on a known working port.
Step 3.
On new installations check adapter cables (or panels for EasyConnection
users) are fully plugged into the board.
Step 4.
Check the cable is connected as per required wiring diagram.
Step 5.
Check that CTS is enabled for the port.
Step 6.
Do a single port loopback on the port to check for open circuits in
the cable and to confirm the port is working.
Step 7.
Use an indicator lamp box to check data is being transmitted on the
Tx pin, and received on the Rx at the other end. Do this at both adapter
cable and terminal ends.
Step 8.
Alternatively, use the easyadm single port monitoring function
to check the state of port signals.
Step 9.
Check the port is not flow controlled. Type ^Q.
Step 10.
If the port fails the loopback test, move the terminal to an
unused working port.
If the port has been working for some time and
then fails, and single port loopback fails with the loopback plug plugged
at the adapter cable, the board may be faulty. Call your Support
Center.
Characters output to
terminals are corrupted/missing
Step 1.
Check that both the port and the terminal are set up with the same
communications parameters:
- Baud Rate.
- Bits/Character.
- Parity (Odd, Even, None).
- Stop Bits (1 or 2).
- Handshaking (Software, Hardware, Both, None).
Step 2.
Does the corruption happen with some applications and files and not
others? If so, the problem is most likely to be with flow control.
Step 3.
Is the port set up for software flow control?
Step 4.
If so, list a large file (eg. /etc/termcap), and type ^S. The
output should stop. ^Q should restart the output.
Step 5.
If using software flow control, use easyadm port monitoring
screens to check Xoff and Xon characters are being sent to the
port.
Step 6.
If you are using hw handshaking, is the cabling correct?
Step 7.
Swap the cable with a known working cable.
Step 8.
If using hardware flow control, use the easyadm port monitoring
screens to check the state of the CTS pin on the single port monitoring
screen.
Step 9.
Try enabling AutoCTS. This will require a hardware handshake cable.
Keyboard Input does not
function
Step 1.
Check that port and terminal communication parameters agree.
Step 2.
Monitor the received characters using easyadm to see if characters
are being received by the board.
Step 3.
If using software flow control, check the port is not flow controlled.
Type ^Q on the terminal.
Step 4.
Check if the problem always occurs or only when running a certain
application.
Step 5.
Type cat < /dev/ttybbppx
on the console, where /dev/ttybbppx is the offending port device.
Try to type some characters on the offending port. Characters
should appear on the console.
Step 6.
Check cabling. Swap the cable with a known working port.
Step 7.
Try using easyadm's Single Port Monitor Admin menu option "Flush'
to flush the port.
Step 8.
If flushing the port does not work, try using easyadm to reset the
port.
Output to a terminal
has stopped when it should not have
Step 1.
If using software flow control, type ^Q on the terminal to check if
the port is flow controlled.
Step 2.
Use easyadm to see if output is blocked by flow control.
Step 3.
Type echo 1234567890
> /dev/ttybbppx, where /dev/ttybbppx is the offending
port. Use easyadm to check that the transmit character queue
increases.
Step 4.
Use easyadm to flush the port. If this does not work, try
using easyadm to reset the port.
Screen painting applications
cause the layout on the screen to be corrupted
Step 1.
Check terminal flow control is set up to match software configuration.
Step 2.
Check TERM variable agrees with terminal type.
Step 3.
Check that the terminal is set up for the correct number of lines
(normally 24 or 25).
Step 4.
Check the terminal's terminfo or /etc/termcap entries for correctness.
Step 5.
Check if the application runs on the standard serial port.
Some keys on a terminal
do not function correctly for a particular application
Step 1.
This is almost certainly a terminal type problem.
Step 2.
Check the TERM variable is correct.
Step 3.
Check that the terminfo or /etc/termcap entry is correct for this
terminal.
Step 4.
Does the application require the terminal to be in 'scan-code mode'?
- If not, ensure the application cannot put the terminal into scan-code
mode.
Step 5.
Is the terminal in scan-code mode?
Step 6.
Does the application reprogram the keyboard?
Flow control problems
for some applications only
Step 1.
Run the application on the standard serial port.
Step 2.
Try using hardware flow control only.
Step 3.
Try enabling AutoCTS. This will require a hardware handshake
cable.
Some keys cause terminal
to hang
- Some applications switch the terminal into
PC/TERM mode. In this mode different keys may generate hotkey sequences.
- Is the terminal in scan-code (PC/TERM) mode?
- If so, set the terminal back to native mode,
enter the hotkey to get back to the PC/TERM mode session, set the
terminal back to PC/TERM.
- It is not recommended to use sessions on
terminals running PC/TERM mode applications.
Printer Problems
No printers are working
Check line printer scheduler is working:
- Type lpstat -t and
look for a "scheduler is running' message. If not, use the system
administration shell to enable the lp scheduler.
Individual Printers not
working
Step 1.
If individual printers are not working, use the system administration
shell to check printers are:
(a) Enabled.
(b) Accepting requests.
Step 2.
Check the cable is working correctly by swapping it with a known
working cable if necessary.
Step 3.
Check the communications parameters of the port while printing:
-
At the console type:
stty
-a < /dev/ttybbpp
where /dev/ttybbpp is the device for
the printer port.
Step 4.
Check the printer communications parameters.
Step 5.
Try printing something to the port by typing:
echo
0123456789 > /dev/ttybbpp
Printers enabled, accepting
requests, but no output
Step 1.
Check the port and terminal communication parameters are the same:
- Baud Rate.
- Bits/Character.
- Parity (Odd, Even, None).
- Stop Bits (1 or 2).
- Flow Control (Software, Hardware, Both, None).
Step 2.
Send a large job to the printer. Monitor its progress with
easyadm's single port display screen. When the port is open,
type (from another terminal or console screen): stty
-a < /dev/ttybbpp where /dev/ttybbpp is the device
of the printer port device.
Step 3.
Check these are as expected. If not, check:
- Interface script for stty commands.
- System administration shell for port configuration parameters.
Step 4.
Follow the procedure for fixing terminal problems (described earlier
in this Section).
Note: If
you suspect the port is flow controlled, use easyadm's
single port monitor screen Admin option to flush the port.
Characters output to
printer are corrupted or missing
Step 1.
Check the port and printer communication parameters are the same:
- Baud Rate
- Bits/Character
- Parity (Odd, Even, None)
- Stop Bits (1 or 2)
- Flow Control (Software, Hardware, Both, None)
Step 2.
Send a large job to the printer. Monitor its progress with
easyadm's single port display screen. When the port is open,
type (from another terminal or console screen): stty
-a < /dev/ttybbpp where /dev/ttybbpp is the device
name of the printer port. Check these are as expected.
If not, check:
- Interface script for stty commands.
- System adm shell for port configuration parameters.
Step 3.
Does corruption happen with some files and not others? If so,
the problem is most likely to be with flow control.
Step 4.
If using Software Flow Control: Connect a terminal to the port,
and print a large file (eg. /etc/termcap), and type ^S.
The output should stop. ^Q
should restart the output.
Step 5.
Use easyadm's single port monitoring screen to check Xoff and
Xon characters are being sent to the port.
Step 6.
If using Hardware Flow Control:
- Check the cable against the hardware flow
control cable wiring diagrams.
EasyConnection
| EasyIO (Select
the product to view the appropriate cabling diagrams)
- Check the CTS line is being de-asserted
when printer flow controls.
- If possible, swap cable with a known working
cable.
Printer output stopped
when it should not have
- Use single port monitor screens to check
port not flow controlled.
- Try flushing port from Admin option Single
port monitor screen.
- Check cables have not worked loose.
Printers connected to
a port do not line feed and carriage return properly
Step 1.
This is most likely a problem with the stty setting used by the interface
script.
Step 2.
Try a different interface script.
Step 3.
Check the stty settings of the port while it is printing.
Step 4.
Check the onlcr and ocrnl values are set as expected.
Step 5.
Check the printer switches against the printer manual.
Attached Printer
Problems (Unix only)
No output to attached
printer but terminal is OK
Step 1.
Check the terminal auxiliary port parameters match the printer's:
- Baud Rate.
- Bits/Character.
- Parity (Odd, Even, None).
- Stop Bits (1 or 2).
- Flow Control (Software, Hardware, Both, None).
Step 2.
Check printer is connected to terminal auxiliary serial port, not
the parallel auxiliary port.
Step 3.
Check the terminal setup uses the serial port for the auxiliary device.
Step 4.
Consult your terminal manual. Check the cable matches
the wiring diagram for the attached printer cable.
Step 5.
Check Escape Sequence for Auxiliary Port.
Attached Printer prints
corrupted characters
Step 1.
Check setup of auxiliary port agrees with printer setup.
Step 2.
Run easyadm and set the Characters Per Second printed
(CPS) parameter to be less than the printer's slowest printing rate.
Attached Printer Output
always displayed on terminal
Step 1.
Is the Escape Sequence to Select Transparent Print mode correct?
Step 2.
The ESCAPE_WAIT parameter may be set too low.
Terminal Output Appears
on Printer.
The Escape Sequence to disable Transparent Print mode is not correct,
or it has not been specified in the Escape Sequences to switch between
sessions.
No output to terminal
with Attached Printer while printer is operating.
Run easyadm and set the Characters Per Second printed (CPS)
parameter to be less than the printer's slowest printing rate.
Attached Printers connected
to a terminal do not line feed and carriage return properly
Step 1.
This is most likely a problem with the stty setting used by the printer
interface script.
Step 2.
Try a different interface script.
Step 3.
Check the stty settings of the port while the attached printer is
printing.
Step 4.
Check the onlcr and ocrnl values are set as it should be.
Step 5.
Check the printer switches against the printer manual.
Output to terminal is
bursty when printer is operating
Run easyadm and modify the Quantum Parameter
for the Attached Printer and Sessions devices.
Multiple
Session (MSS) Problems (Unix only)
Terminal on a port configured
for Multiple Sessions does not switch between sessions correctly
Step 1.
Check Escape Sequences are correct.
Step 2.
Check Escape Sequences Received with Terminal in Monitor mode.
Step 3.
Check Hotkey is correct.
Step 4.
If unusual characters are left on the screen, increase ESCAPE_WAIT
parameter value.
Terminal on a port configured
for multiple sessions loses screen data switching between sessions
Step 1.
Does the terminal have sufficient memory for the number of sessions
supported?
Step 2.
Check if the terminal has a special mode to allow more memory
for sessions. If you have a Wyse 60 terminal, select ECON-80
mode.
Modem Problems
Modem Overruns
Some modems are unable to respond quickly enough at high speed to a
drop in the RTS handshaking line. This usually results in data overruns
(visible in the easyadm
port monitor screens). This release of the driver allows the RTS threshold
to be adjusted on a per port basis via the bccstty utility. To reduce
the threshold from the default of 8 down to say, 6 on port tty1a00,
try:
bccstty
rxthold 6 -d /dev/tty1a00
To turn this off:
bccstty
-rxthold -d /dev/tty1a00
To display the bccstty current settings:
bccstty
-d /dev/tty1a00
Note that the bccstty utility is in the /usr/lib/easyio/bin
directory while the bccstty documentation is in /usr/lib/easyio/man
directory.
Modem does not go off
hook to dial out
Step 1.
Check the cable against a modem cable wiring diagram.
Step 2.
Check port communications parameters agree with modem.
Step 3.
Check status of modem indicator lights, especially DTR, TXD and RXD.
Step 4.
Check using a terminal connected to the modem.
- You may need to use cable with no CTS, DCD or RTS.
- Verify the communications parameters.
Step 5.
Check CTS line not pulled low by incorrect modem register settings.
Modem does not answer
- DTR may need to be high for modems to go
off hook.
- Check Cable is correct, especially DTR.
- Check the cable against a modem cable wiring
diagram.
- Check modem configured to autoanswer (ie.
Hayes modem s0 not = 0).
Modem Answers but no
data to port
Step 1.
Check cable, especially DCD.
Step 2.
Check modem registers aren't set to hold DCD always high.
- Set modem register so that DCD follows the
carrier.
Step 3.
Check communication parameters when modem answers.
Step 4.
When modems connect, they often change their communications parameters
to match the connection speed. These may disagree with the port.
- Connect a terminal to the modem - you
may need a cable with no CTS, DCD or RTS connection. Dial into the
modem from elsewhere to check for this.
If this is the problem, either:
- If possible, lock the modem interface
speed to that of the port. This is the preferred
solution.
- Set up a cycling getty on the port.
When you log in, press <Break> until the baud rate
is correct. The required baud rate must be in the /etc/gettydefs
entry for the port.
Modem does not hang up
at end of call
Step 1.
Check HUPCL flag is set in the gettydefs entry for port.
Step 2.
Check modem registers aren't set to hold DCD always high. If so:
- Set register so that DCD follows carrier.
Step 3.
Check modem registers are set for a drop in DTR to terminate the connection.
Characters are lost or
corrupted
Step 1.
Check that the modem flow control is equal to the port flow control
setting.
Step 2.
Check cable is correct.
Step 3.
If Hardware Flow Control is used, check that the RTS and CTS lines
are connected.
Step 4.
Check for a bad line by dialling up locally.
Step 5.
Check that the modem baud rate is equal to the port baud rate.
Step 6.
If cycling getty is used, then check required baud rate is supported
by
/etc/gettydefs entry.
Step 7.
If cycling getty is not used, make sure modem registers are set to
lock interface speed to the port baud rate.
Modem hangs up when it
shouldn't
Step 1.
Check as for Modem problem for a noisy line.
Step 2.
Check if DTR or DCD indicators on modem go off momentarily before
hangup. If line is noisy, you may be able to set your modem
to ignore short carrier losses.
Step 3.
Is the problem with the application?
Step 4.
Does the problem show only with some applications?
Step 5.
Does the problem also happen if you use the modem on a standard
serial port as well?
General Errors
Particular ports no longer
operate
Step 1.
Move terminal/cable to another port.
Step 2.
Run diagnostic loopback test on offending port.
Step 3.
If fault is suspected, contact your Support Center.
Spurious r & w letters
with MS-Word on Wyse 60's
Step 1. Word puts Wyse 60 terminals
into PC-term (i.e. scan-code) mode, and sets the port to use codes
\x145 and \x147 for Xon and Xoff respectively. (These are set
according to the XN=\145 and XF=\147 entries in /usr/lib/word/termscan.)
Step 2.
If your terminal XPC HNDSHK setting is off, it will still send ^S
and ^Q characters, when it handshakes. These are the scan codes for
r and w respectively.
To fix this problem, turn XPC
HNDSHK on in the terminal setup screen.
