Troubleshooting guide:

Checking installation

If problems are encountered after installation the following steps may be useful in diagnosing the problem.

Check card is installed

Assuming that mechanical installation is OK you can check whether the

system has detected the card by running the “lspci” command.

# lspci -vt

-[00]-+-00.0 Intel Corporation 440FX – 82441FX PMC [Natoma]
+-07.0 Intel Corporation 82371SB PIIX3 ISA [Natoma/Triton II]
+-07.1 Intel Corporation 82371SB PIIX3 IDE [Natoma/Triton II]
+-08.0 Matrox Graphics, Inc. MGA 2064W [Millennium]
+-09.0 Unknown device 1619:0400
+-0a.0 Adaptec AHA-294x / AIC-7871
\-0b.0 Intel Corporation 82557 [Ethernet Pro 100]

In this typical example the FarSync T2P card is the fifth device.

+-09.0 Unknown device 1619:0400

More recent versions of Linux may have an lspci command that is aware of the FarSite cards in which case you will see a textual description of the card rather than the “Unknown device” entry. A more extensive listing is available with “lspci -v”. The typical entry for the above card being:

00:09.0 Communication controller: Unknown device 1619:0400 (rev 02)
Subsystem: Unknown device 1619:71f0
Flags: medium devsel, IRQ 10
Memory at e0a07000 (32-bit, non-prefetchable)
I/O ports at 9100
Memory at e0800000 (32-bit, non-prefetchable)
Memory at e0a04000 (32-bit, non-prefetchable)
I/O ports at 9200

Check device driver is being run

Watch the startup sequence carefully. When the FarSync device driver is first loaded a line like this will appear:

FarSync X.25 driver 1.00

This messages can also be viewed after startup by using to command:

$ dmesg | more

If the card is installed as indicated by the “lspci” command yet the device driver message is not apparent the most likely cause is that the driver module is not being loaded correctly.

Check module installation

If the device driver was built as a module then you can check whether it has been loaded by using the “lsmod” command.

# lsmod

Module Size Used by

pcnet32 10456 1
fsx25 9556 1

This shows the fsx25 module has been loaded. (The pcnet32 entry is for an unrelated Ethernet driver.) If the fsx25 module has not been loaded run the command

# /etc/rc.d/init.d/fsx25 start

and check the error messages. This command is normally run automatically at system startup.

Check card detections and download OK

You can check the status of the cards detected by looking at the contents of the control file /proc/fsx25

# cat /proc/fsx25

1 cards installed
fsx0: FarSync T2P irq=10 mem=0xE0800000,0x9100,0xE0A04000 NCB access OK
NCB users 0

NCB access OK indicates that the firmware is running and ready to process Network Command Blocks.