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
