I think I have this issue mostly figured out and will write another email to the list soon explaining the problem when time allows. Spoiler: it was mostly operator error.
Thanks everyone for the initial help and ideas. Ryan On Thu, Jan 30, 2014 at 4:50 PM, Ryan Williams <[email protected]> wrote: > Thank you everyone very much for the helpful ideas. Right after I wrote > the first SOS email, I came down sick and have been under the weather since. > > I was able to try a couple of the suggestions. Here is the output for the > dmesg command: > > [rd@rdserv ~]$ dmesg | grep tty > console [tty0] enabled > ttyS0: detected caps 00000700 should be 00000100 > 0000:02:00.0: ttyS0 at I/O 0xe060 (irq = 16) is a 16C950/954 > ttyS1: detected caps 00000700 should be 00000100 > 0000:02:00.0: ttyS1 at I/O 0xe068 (irq = 16) is a 16C950/954 > ttyS2: detected caps 00000700 should be 00000100 > 0000:02:00.0: ttyS2 at I/O 0xe070 (irq = 16) is a 16C950/954 > ttyS3: detected caps 00000700 should be 00000100 > 0000:02:00.0: ttyS3 at I/O 0xe078 (irq = 16) is a 16C950/954 > usb 3-4: pl2303 converter now attached to ttyUSB0 > [rd@rdserv ~]$ > > Typing characters into minicom connected to ttyS0, ttyS1 and ttyUSB0 (I > didn't try S2 or S3) made the activity light on the switcher flash. I > couldn't remember the command for changing the input to a particular > output, but it does seem to be receiving some bits. After I noticed the > light flashing with minicom, I was curious if it would show activity when a > switch event was fired off from RDCatch. It did flash, but the channel did > not change. > > (Fred, you said to set minicom to "full duplex". I couldn't find that > setting. Does it have a different name?) > > I was able to make a loopback serial plug and can hopefully work with it > more tomorrow if I am feeling up to it. > > Thanks again everyone and if anything stands out to you or if you have any > more ideas, please let me know. > > Ryan > > > On Wed, Jan 29, 2014 at 11:30 AM, Cowboy <[email protected]> wrote: > >> On Wednesday 29 January 2014 11:46:54 am drew Roberts wrote: >> > Try leaving Rivendell out of the mix. Can you talk to the device from a >> > program like minicom? >> > >> >> You can even leave minicom out of the mix. >> >> Do the dmesg thing and find the device. >> >> Find the device file. >> Let's say it ends up being /dev/ttyS1 for discussion purposes. >> Check the permissions, group memberships, etc. on the device. >> If they are wrong, then the tests can fail even if you do things right ! >> >> In a terminal window, do >> echo "The Quick Brown Fox Jumped Over The Lazy Dogs Back" > /dev/ttyS1 >> If there is a serial port there, you'll get nothing. >> If there is no serial port there, you'll get an error message. >> >> You should find some useful information in >> /proc/devices >> /proc/interrupts >> /proc/ioports >> /proc/tty/drivers >> /proc/tty/driver/serial >> >> Once you know that the hardware is there, and that the terminal window >> can cat stuff to it, it's a matter of configuring things correctly, but >> at least >> you will know it really is there, and can be accessed. >> >> -- >> Cowboy >> >> http://cowboy.cwf1.com >> >> Please take note: >> >> _______________________________________________ >> Rivendell-dev mailing list >> [email protected] >> http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev >> > >
_______________________________________________ Rivendell-dev mailing list [email protected] http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
