Hello, I’m trying to setup a terminal server on an old PC. Here is my environment:
pc/8e isa rs422, epca-1.56-1 compiled, installed and running, redhat 7.1 kernel 2.4.2-2.
All of the correct devices are in /dev/dg/epca/
to include: digiCtl, epcadl -> digiCtl, tprD000-7 and ttyD000 - 7.
I have a cisco router connected to p1 and a loopback conected to p2. Minicom says there “online” but I can’t get any data echoed back from either.
setserial /dev/dg/epca/ttyD000 autoconfig [or any other operation with it] always returns:
Cannot get serial info: Invalid argument
I’m experiencing the exact same issue on RedHat 7.1, Kernel 2.4.20-28.7, and using epca-1.56-1 on a 16-port XEM. Did you ever figure it out? Strange thing on this end is, we had a working system. One of the guys in our hardware department did something, no confessions yet, and it’s no longer working. I set the system up several years ago so my memory is rusty. Rechecked config, driver’s loading fine - no errors, etc. Ditty command works but setserial gives same error you got.
Verify that the devices are useable with command "ditty -a /dev/ttyD000. You should get a bunch of i/o output, rather than an error message saying “device temporarily unavailable”. If you get the output, check to see if -clocal is set. If it is, try setting clocal and test your application again. If you get the error message, there’s a problem loading your driver and that would be a good time to call Technical Support.
Just to be sure, is the Cisco port RS-422 protocol also? An RS-422 serial adapter will not be able to communicate with an RS-232 port, just want to be sure there is no mixing of communication protocols.
One possibility that comes to mind about what might have been done is cabling. The EBI cable between an Xem Host Adapter card and the Ports/EM concentrator is an extension of your computer bus, and therefore “hot”. If this cable were moved/removed without powering down the server first it could have damaged card, concentrator, and/or server itself.
Other things to check with the server powered down would be to make sure the card is seated properly, all cables are secure, etc. With power on you can check /proc/pci or /proc/interrupts to see if Linux sees the card, i.e. is the server BIOS allocating resources to it.
If none of these things resolve the problem, best thing to do next would be to call Technical Support and open a ticket.