Cyclades PC400 - Manual (Page 28)

Chapter 5 Troubleshooting 28
Cyclades-PC400 Installation Manual
CHAPTER 5 TROUBLESHOOTING
General Tips
What to Do When the PC400 is Not Recognized by the Operating System
• Does the operating system detect the PC400 on boot? A message similar to
Cyclades-PC400 driver <version> <date> built <date>
PC400 #1, RAM at 0xMMMM, IRQn, 64 channels starting from port 0
PC400 #2, RAM at 0xMMMM, IRQn, 64 channels starting from port 64
etc.
should appear on boot. If not,
• Is the board properly installed (physically)? Check the connections inside the computer.
• Does your Linux operating system meet the requirements outlined at the beginning of chapter 3? The
kernel version can be discovered by typing the command uname -r .
• The steps in chapter 4 related to the device files should be reviewed and the configuration files checked.
• Check the configurations modified using “make config” or “make menuconfig” (details supplied in chapter
3). If they are incorrect, execute the commands make dep and then make bzlilo modules
modules_install again to rebuild the kernel. Reboot the computer and see if the boards are detected.
How to Test if the PC400 is Functioning
• The simplest way to test a WAN connection is by pinging. Type ping <IP address of device to be
pinged> . If a response is not received from the remote machine there is probably a problem with the link.
Make sure the remote machine is up by accessing it from another computer before following the directions
below.
What to Do if the PC400 is Detected by the Computer, but Does Not Function as Expected.
• Is the cable properly connected and is the correct cable being used?
• Type the command
ifconfig . Do the devices set up for the board in chapter 4 appear?
• Type the command netstat -rn to see the routing table. Have you defined a default gateway and/or have
a route that includes the remote device you are trying to reach?