Andy Green wrote:
Brian Mury wrote:
> On Thu, 2006-05-11 at 20:55 -0600, Karl Larsen wrote:
>> Here is what happened. I got gmfsk to compile and load and it
>> came up working just fine except for the same dam error message whan
>> you try to go to transmit:
>>
>> sound_open_for _write: opensnd: /dev/dsp Device or resource busy.
>>
>> I was never able to clear this error message so of course it doesn't
>> work.
>
> This is not a gmfsk problem. This simply means that some other program
> has the soundcard locked, and gmfsk is unable to access it. You need to
> find out what program is using the soundcard. For example, I have to
> shut down Skype before I can run gmfsk.
As root:
lsof -n | grep dsp
The first field is the process name.
-Andy
Thanks Andy. I used it and it found nothing. I started gmfsk in
receive and it found it fine.
[root@k5di ~]# lsof -n | grep dsp
gmfsk 2495 karl 16r CHR 14,3 4041
/dev/dsp
It is true there is nothing on /dev/dsp except gmfsk.
Karl