All of lore.kernel.org
 help / color / mirror / Atom feed
From: Phil <phillor@telstra.com>
To: linux-hams@vger.kernel.org
Subject: Re: /dev/dsp busy
Date: Mon, 1 Jun 2009 14:50:38 +1000	[thread overview]
Message-ID: <200906011450.38388.phillor@telstra.com> (raw)
In-Reply-To: <4A234B0C.6010608@radagast.org>

On Monday 01 June 2009 13:29:16 Dave Platt wrote:
<cut>
>
> It's possible that something is using the ALSA sound
> resource path (which is the baseline audio implementation
> in modern Linux kernels - the old OSS sound drivers are
> deprecated, and /dev/dsp is usually implemented as an ALSA
> compatibility driver).
>
> Try "lsof | grep dev/snd" to see what (if anything) is using
> the ALSA sound pseudodevices.
>

Thanks for your prompt reply Dave.

The problem was Pulse Audio, as I suspected. It wasn't enough to just  
disable pulse audio in the sound settings, I had to kill the resulting PID.

Now another problem has surfaced; there is a ticking sound in the 
background of the transmitted sound. Again, this is a problem that I 
had previously encountered and the cure was to buy a different sound 
card. However, this option is not viable in the case of a laptop.

I don't know what effect this ticking sound will have on my transmitted  
signal (I've recently returned to Amateur Radio after a lengthy break 
and need to construct a suitable lead) but I'm sure that I can do without 
it.

Again, can anyone offer any suggestions?

-- 
Regards,
Phil

  reply	other threads:[~2009-06-01  4:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-01  0:59 /dev/dsp busy Phil
2009-06-01  3:29 ` Dave Platt
2009-06-01  4:50   ` Phil [this message]
2009-06-01  5:38     ` Dave Platt
2009-06-02  2:43       ` Phil

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=200906011450.38388.phillor@telstra.com \
    --to=phillor@telstra.com \
    --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.