🚀 go-pugleaf

I've connected an Intel 14.4 kbps modem to my NeXt and used it
successfully with /dev/cua.  Because this modem supports 'hardware'
flow control I tried using /dev/cufa with some drastic results.

I'm certain that the modem is set up for hardware flow control
because I checked it using /dev/cua.  I'm using Kermit to communicate
with the modem... no matter what options I choose for flow control
or baud rate, the device blocks and no data enters the modem... in
fact, kermit blocks so hard after successfully opening the device,
that if it tries to close the device the process becomes unkillable
with a kill -9.  A root reboot command will fail at this point, the
only way to reboot is through the NMI monitor.  A ttclos error is
displayed when kermit tries to close the device.

I'm fairly certain the cable is just fine... standard 8-25 I believe.
Even if the modem doesn't support RTS/CTS or isn't using it, I can't
imagine the cable just leaving those signals floating... the must be
connected.

Any ideas on why hardware flow control isn't working?

---------------------------------------------------------------------

Please reply by email, and post if it's good.

- Mike