Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 8 Sep 1999 18:33:46 -0400
From:      Ben Williams <williamsl@home.com>
To:        FreeBSD questions <freebsd-questions@freebsd.org>
Subject:   Re[3]: finding a modem
Message-ID:  <14773.990908@home.com>
In-Reply-To: <1673.990908@home.com>
References:  <1673.990908@home.com>

next in thread | previous in thread | raw e-mail | index | archive | help
   I  know  it's bad form to reply to your own messages but I had some
email from Wayne Self which reminded me that I didn't tell you exactly
what I am dealing with.
   I   have   a   P2/200/64mb/2gb   running a recent version of STABLE
(3.2 I think) with only video and ethernet cards and both serial ports
turned  on in the BIOS. The kernel recognizes both PORTS (sio0 & sio1)
when  it  boots  but  I  still have the situation described here. Also
possibly of note is the fact that I am still running kernel.GENERIC on
this box as I haven't had time to recompile it yet. Surely running the
generic kernel wouldn't cause it to not talk to a serial device?

/snips for clarity/

    Ok I dug out the cu man page and followed your directions which was
the  same  as my original plan to talk to each port but now I have run
up  on  something  stranger.  Whenever  I cu -l/dev/cuaa0 [-s115200 or
-s1200]  (this  meaning  with no speed option or with either 115200 or
1200  speed  option)  I get "Connected." but that's all I ever receive
from  the  port.  I issue several AT commands (ATZ ATE0 AT ATZ ATE1 AT
ATZ ~.) ((all followed by a <CR> of course)) and I get nothing. Next I
do  the  same  thing  with  cuaa1 and I never get "Connected." so I am
assuming  my  modem  is  on  cuaa0  since  it  connects  but  I cannot
successfully  send  commands  to it. The modem is a USR 28.8 Sportster
and if I recall my AT commands ATE1 enables local echo from the modem,
but even there I have myself covered by having an ATE0 as well.

--
 Ben  <mailto:received@email.com>

BW> On or about Wednesday, September 08, 1999, sometime around 3:01:29 PM, you said:
WS>> On Wed, Sep 08, 1999 at 02:46:07PM -0400, Ben Williams wrote:
>>>    I help to remotely administer a FreeBSD server that recently got an
>>> external modem addition but I don't know which port they plugged it in
>>> to. What utility can I use to 'talk' to the port (I would talk to each
>>> until I got a response) or what other method do I have of finding this
>>> new modem?
>>> 
>>> TIA
>>> --
>>>  Ben   <mailto:received@email.com>

WS>> cu will talk to the port.

WS>>  man cu

WS>> to attach to a modem on COM1:

WS>>  cu -l /dev/cuaa0

 
WS>>  - wayne




BW> To Unsubscribe: send mail to majordomo@FreeBSD.org
BW> with "unsubscribe freebsd-questions" in the body of the message




To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?14773.990908>