From: Frank Roberts - SOTL <sotl155360@earthlink.net>
To: Linux Newbie <linux-newbie@vger.kernel.org>
Subject: Re: Modem Identification
Date: Sun, 15 Dec 2002 09:01:21 -0500 [thread overview]
Message-ID: <200212150901.21290.sotl155360@earthlink.net> (raw)
In-Reply-To: <5.1.0.14.1.20021214171540.020e0cb0@celine>
Thanks Ray
Actually your response is very close to my intent.
What I am trying to do is identify which port I have a modem which may or may
not be a win modem connected to.
It was purchased as a full modem but I sincerely question that it is.
As far as using minicom that is another slight problem there in that for some
reason I do not have minicom functioning correctly or something resulting in
that being the next major issue to be resolved since I need minicom for
another major reason.
Isn't there a command that allows one to "ping" a modem from the command line
and which returns the modem identification annd type? I seem to recall that
there is but I can not recall it but again this may be falty network memory.
Thanks
Frank
On Saturday 14 December 2002 20:19, Ray Olszewski wrote:
> At 08:14 PM 12/14/02 -0500, Frank Roberts - SOTL wrote:
> >Hi All
> >
> >Question:
> > >From the command line how does one determine which port a modem is on?
>
> It depends on exactly what you mean. I'm guessing that you intend to refer
> to a situation where you have 2 or more serial ports in a computer, and a
> modem conencted to one of them, but the ports are unlabeled so you dont
> know which one the modem is attached to. In that case, I would use a
> terminal app (such as minicom) to connect to each port, and see which port
> (actuall, its associated /dev/ttyS* entry) gets responses from the modem to
> typical AT commands.
>
> There are many more things you *might* mean, though. So if I've guessed
> wrong (and someone else does not guess right), please post a followup that
> asks the question in a different, more specific form.
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
next prev parent reply other threads:[~2002-12-15 14:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-15 1:14 Modem Identification Frank Roberts - SOTL
2002-12-15 1:19 ` Ray Olszewski
2002-12-15 14:01 ` Frank Roberts - SOTL [this message]
2002-12-15 15:34 ` Chuck Gelm
2002-12-15 19:55 ` Modem Identification - Thanks Frank Roberts - SOTL
2002-12-15 20:29 ` dashielljt
2002-12-15 23:21 ` Frank Roberts - SOTL
2002-12-16 21:47 ` whitnl73
2002-12-15 15:23 ` Modem Identification Hal MacArgle
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200212150901.21290.sotl155360@earthlink.net \
--to=sotl155360@earthlink.net \
--cc=linux-newbie@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.