From: Mike Markowski <mm@UDel.Edu>
To: linux-hams@vger.kernel.org
Subject: Re: soundmodem and fedora c3
Date: Tue, 08 Mar 2005 12:44:34 -0500 [thread overview]
Message-ID: <422DE482.6030800@udel.edu> (raw)
In-Reply-To: <BAY104-F33C8680A7BC732DF8330068B500@phx.gbl>
Just as a sanity check, did you remember to run soundmodemconfig so that
it creates interface sm0? And similarly, remember to actually run
soundmodem before starting xastir. :-) I know you probably did, but
just making sure all bases are covered! After running soundmodem, make
sure an "ifconfig" shows that sm0 is up before starting xastir.
Mike AB3AP
Ron- VE3DTT wrote on 03/08/05 12:35 ET:
> Thanks to all who responded to my query.
>
> I am aware that 'soundmodem' is usermode software but I tried loading
> the modules anyway, out of desperation.
>
> 'make menuconfig' suggests that ax.25 is hard coded in my kernel.
>
> I have this sample of an 'axport' file which addresses 'sm0':
>
> "sm0 KA1FSB-8 1200 255 2 145.630 Mhz "Wellesley, MA" 1200
> bps soundmodem"
>
> but it doesn't help. I've tried many variations on sample
> configurations with negative results.
>
> 'xastir' will allow me to bring up a 'kiss' device on any port I choose
> but none communicate with soundmodem. The xastir manual tells me to use
> ax25.
>
> 'Listen' informs me that my ax25 ports aren't active.
>
> --
> "Windows: Microsoft's tax on computer illiterates." -- WE7U
>
> I, reluctantly, must include myself among the computer illiterate and
> when I discovered that 'soundmodem' is available for windows I
> downloaded 'soundmodem', 'flexnet32' and 'paxon' and was decoding
> packets within 15 minutes start to finish. In view of the time it takes
> to get anything up and running with Linux, I'm inclined to counter that,
> perhaps,
>
> Linux is Life's tax on those of us who don't have one.
>
> It has to be it's own reward. I'll keep trying things until something
> works.
>
> Thanks again,
> Ron
> 73 VE3DTT
>
>
> -
> 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
next prev parent reply other threads:[~2005-03-08 17:44 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-08 17:35 soundmodem and fedora c3 Ron- VE3DTT
2005-03-08 17:42 ` Curt, WE7U
2005-03-08 17:44 ` Mike Markowski [this message]
2005-03-08 18:20 ` Jeff Camp
2005-03-08 20:07 ` Richard Adams
2005-03-08 20:13 ` Luc Langehegermann
2005-03-08 20:35 ` Curt, WE7U
2005-03-08 21:25 ` Jeff Camp
2005-03-09 6:35 ` Richard Adams
2005-03-08 18:55 ` oz6bl
-- strict thread matches above, loose matches on Subject: below --
2005-03-09 14:41 Ron, VE3DTT
2005-03-09 16:25 ` Jeff Camp
2005-03-10 6:43 ` Richard Adams
2005-03-07 15:22 ronald schultz
2005-03-07 17:03 ` Curt, WE7U
2005-03-07 18:23 ` Tomi Manninen
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=422DE482.6030800@udel.edu \
--to=mm@udel.edu \
--cc=linux-hams@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox