Return to BSD News archive
Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!bunyip.cc.uq.oz.au!munnari.oz.au!spool.mu.edu!howland.reston.ans.net!Germany.EU.net!wizard.pn.com!bhhome.bh.org!bill From: bill@bhhome.bh.org (Bill Heiser) Newsgroups: comp.os.386bsd.misc Subject: modems and FreeBSD 2.0A Date: 21 Nov 1994 11:37:57 GMT Organization: Bill Heiser's Organization Lines: 23 Message-ID: <3aq0ql$m9q@wizard.pn.com> NNTP-Posting-Host: bhhome.bh.org X-Newsreader: TIN [version 1.2 PL2] I have found that to use a modem on a FreeBSD 2.0A system, one must configure the modem to force CD high all the time. This makes it a hassle (and a little tricky) to swap modems between FreeBSD-2.0A and other systems. Is there any particular reason that CD must be high for FreeBSD 2.0A to talk to the modem? Is this a bug, or is it this way by design? It would be nice if FreeBSD 2.0A (like 1.1.5.1R) dealt with modems in a more "standard" way. Part of what makes it tricky to switch modems back and forth between CD-high and "normal" mode (for use on multiple systems) is the fact that when using 'cu' to talk to the modem on the FreeBSD system, entering the modem command to switch to "normal" mode causes 'cu' to die with a "signal 1 - user defined signal". This means that to switch modems between systems, one must actually have a third system, or a dumb terminal, nearby... otherwise there's no way to make either of the systems talk to the modem to change mdoes! Thanks in advance, Bill -- Bill Heiser: bill@bh.org http://www.bh.org/ PGP public key available upon request.