From: Hamish Moffatt <hamish@cloud.net.au>
To: Linux Hams <linux-hams@vger.kernel.org>
Subject: Re: PTT with soundmodem
Date: Mon, 2 Feb 2004 09:09:20 +1100 [thread overview]
Message-ID: <20040201220920.GA18771@cloud.net.au> (raw)
In-Reply-To: <20040201215530.GA572@strauss.udel.edu>
On Sun, Feb 01, 2004 at 04:55:30PM -0500, Mike Markowski wrote:
> I'm thiiis close to having my packet set up working in kernel 2.4.24
> (currently unpatched). I'm using the user space soundmodem to create
> interface ax0 -- so I assume I don't need to do a kissattach. When I
> use soundmodemconfig to test the setup, I can successfully use the
> PTT gui button to get my rig to transmit (and also have no problem
> with PTT when using Tomi's great gMFSK!). However, while i can
> receive APRS packets while running xastir, when it tries to transmit,
> soundmodem complains after the xastir info:
>
> Tx: fm AB3AP-0 to APX121-0 via RELAY-0,WIDE-0 UI^ pid=F0
> =/:B7_;?z&y ab3ap@arrl.net, Avondale PA (XASTIR-Linux)
>
> sm[15891]: ioctl: SNDCTL_DSP_SYNC: Device or resource busy (16)
>
> I see the LED on my PTT interface briefly light, but not long
> enough to activate the rig itself before the error above is
> printed.
Do you have any other programs at all accessing the sound card? Things
like the sound server for KDE or GNOME?
Is AX.25 working properly in 2.4.24? I was under the impression that it
was never reliable in 2.4, and fixes are going straight to 2.6. I'm
still running 2.2 on my packet machine.
Hamish
--
Hamish Moffatt VK3SB <hamish@debian.org> <hamish@cloud.net.au>
next prev parent reply other threads:[~2004-02-01 22:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-01 21:55 PTT with soundmodem Mike Markowski
2004-02-01 22:09 ` Hamish Moffatt [this message]
2004-02-02 6:09 ` Mike Fenske
2004-02-02 12:19 ` Tomi Manninen
2004-02-06 1:05 ` PTT with soundmodem - solved! Mike Markowski
2004-02-02 15:38 ` PTT with soundmodem Mike Markowski
2004-02-06 21:48 ` 2.6.[012] register_netdev kernel bug Leo Bistmans
2004-02-06 22:52 ` Jeroen Vreeken
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=20040201220920.GA18771@cloud.net.au \
--to=hamish@cloud.net.au \
--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 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.