From: "IT3 Stuart Blake Tener, USN" <teners@bh90210.net>
To: linux-hams@vger.kernel.org
Cc: Bob Nielsen <nielsen@oz.net>
Subject: Re: BayPac BP-1 Modem and Linux
Date: Fri, 20 Jul 2007 22:11:39 -0700 [thread overview]
Message-ID: <C2C6E39B.EC4F%teners@bh90210.net> (raw)
In-Reply-To: <A6FEE2F8-48F7-4994-8B3D-447C0DD66221@oz.net>
Bob:
Indeed the more I learn about Ubuntu 7.04, the more I am impressed with
its capabilities.
I intend to attempt its installation on a Sun e450 later this month!
V/R,
Stuart, N3GWG
On 7/20/07 7:48 PM, "Bob Nielsen" <nielsen@oz.net> wrote:
>
> On Jul 20, 2007, at 6:37 PM, Doug wrote:
>
>> Is there anyway to connect a BayPac BP-1 modem to a linux system. I
>> seem to find drivers
>> for only the epp and usb variety. I need a modem to check my port
>> configiration via the
>> "LISTEN" command and I have run out unless I shut down the cluster
>> and the bbs.
>> Fbb is not loaded onto the system just yet. This is a new system
>> (Mepis 6.5) and nothing
>> else is loaded on to it yet except the ax25 stuff. The BP-1 is a
>> serial device.
>
> My Ubuntu 7.04 stock kernel includes the baycom_ser_hdx.ko module.
> If this one isn't included with Mepis, you need to recompile the
> kernel and make sure the configuration file includes:
>
> CONFIG_BAYCOM_SER_HDX=m (or y)
>
> Bob, N7XY
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-hams" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
Very Respectfully,
IT3 Stuart Blake Tener, USN
Beverly Hills, California
Amateur Radio Call Sign: N3GWG (Extra)
email: teners@bh90210.net
phone: +(1) 310.358.0202 (Beverly Hills, CA)
phone: +(1) 215.338.6005 (Philadelphia, PA)
phone: +(1) 702.988.3989 (Las Vegas, NV)
E-Fax: +(1) 915.773.0935 (Telecopier)
Military emails (checked monthly until remote NMCI access is secured)
NIPRNET: stuart.tener@navy.mil / tenerstu@nro.mil
SIPRNET: NONE
TS/SCI: tenerstu@nro.ic.gov (GWAN)
Confidentiality Notice: This e-mail message, including any attachments, is
for the sole use of the intended recipient(s) and may contain confidential
and/or privileged information. Any unauthorized review, use, disclosure or
distribution is prohibited. If you are not the intended recipient, please
contact the sender by reply e-mail and destroy all copies of the original
message.
next prev parent reply other threads:[~2007-07-21 5:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-21 1:37 BayPac BP-1 Modem and Linux Doug
2007-07-21 2:34 ` Lance Cotton
2007-07-21 2:48 ` Bob Nielsen
2007-07-21 5:11 ` IT3 Stuart Blake Tener, USN [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-07-21 16:06 Doug
2007-07-21 16:09 Doug
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=C2C6E39B.EC4F%teners@bh90210.net \
--to=teners@bh90210.net \
--cc=linux-hams@vger.kernel.org \
--cc=nielsen@oz.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox