Date: Thu, 23 Oct 1997 16:07:53 -0400 From: Brian McGovern <bmcgover@bmcgover-pc.cisco.com> To: jalves@bsi.com.br Cc: questions@freebsd.org Subject: RE: Cyclom Zo Message-ID: <199710232007.QAA00799@bmcgover-pc.cisco.com>
next in thread | raw e-mail | index | archive | help
Well, since I wrote the driver, I suppose I should take a stab at this... First, I'll need to know what version of the driver you're running. It should tell you on boot. If it doesn't, its way old, and needs to be updated. Mike and November versions were kind of quirky. You should be running QUEBEC. If you're not, pick it up from ftp://spoon.beta.com/pub/cz.tgz. It sounds like it may be a flow control problem. I've seen some terrible strangeness with this due to varying levels of things with FreeBSD working or not working. For instance, if I use kermit to access a port, and set rts/cts flow control, the ioctl() call to turn this on never gets made by kermit. Therefore, no hardware flow control. In order to bypass this problem (because most don't use software flow anymore), hardware flow control is default unless explicitly turned off. Therefore, youre getty settings (and terminal programs) should be set to use HW flow control (unless they explicitly turn it back off). If you are using HW flow, RTS and CTS must be high in their respective directions in order to get data moving. It sounds to me like the control line from the modem is on (cause output works), but the PC isn't supplying this line to the modem, because its not taking input. Again, this default was set late in the game, so if you're using an early driver, it may be in a funky state. Try slapping a breakout box to see (and make sure you're running Quebec). If you still have problems, drop me a line, and I'll try to simulate the problem. -Brian
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199710232007.QAA00799>