[nas] No love (could not create audio connection block info when starting)

[Jon Trulson]

On Tue, 14 Sep 2004, Paul England wrote:

> Yeah, this is a bad problem.
> I'm running on RH8, and ARTS does not start when the system comes up.
> nasd runs (on the default port), and my QT app connects to it okay.
> There's a function that should either return okay when sound is available
> through nasd, or an error, when not available.  It never returns the error,
> and the program plays the sound.  However.... no sound. :(

 	One of the issues I ran into with ALSA sometime ago is that when 
it starts, it mutes all the outputs.  I assume you did check for that? 
Also, what happens if you just cat a .wav file to /dev/dsp ?

>
> Yeah, I checked the speakers and all that jazz as well.
>
> The following are the only errors I see in the syslog, but even that 
> shouldn't
> mean that sound is unavailable...  most other machines on my network have
> this error, but play sound.
>
> Sep 14 07:47:44 mynode modprobe: modprobe: Can't locate module sound-slot-1
> Sep 14 07:47:44 mynode modprobe: modprobe: Can't locate module 
> sound-service-1-0
> Sep 14 07:47:44 mynode modprobe: modprobe: Can't locate module sound-slot-1
> Sep 14 07:47:44 mynode modprobe: modprobe: Can't locate module 
> sound-service-1-0
>

 	I see these too (on Mandrake 7.1), no idea what those really mean, 
but everything does still work...  I always used to use OSS, but I wanted 
to try out midi, and the apps I wanted to use required the ALSA MIDI 
interface, so I installed it, enabling the OSS emulation.  I haven't had 
any problems with it.  I'm using an SB 128 PCI.



> Any insight is appreciated.
> Regards
> Paul
>
>> Thanks for the reply Jon.
>> I dug around a bit, and I think I've fixed it (won't know until the 
>> morning)
>> 
>> I had to shutdown the machine in a rather nasty way today.  I think this 
>> was
>> the root of the problem.  I looked in /tmp/.sockets, and saw that audio0 
>> through
>> audio5000+ was taken (probably what happened when I ran my perl script
>> to find an open port) :(.
>> 
>> Anyways, I deleted all of these and restarted.  I'm thinking I've got the 
>> problem
>> fixed.  nasd starts, and my Qt app thinks that NASD is available, so that's 
>> definitely
>> better than before.
>> 
>> I'll come back wining in the morning if it doesn't though.
>> 
>> Regards
>> Paul
>> 
>>> On Mon, 13 Sep 2004, Paul England wrote:
>>> 
>>>> I get the following error
>>>> 
>>>> Fatal server error:
>>>> could not create audio connection block info
>>>> 
>>>> when running:
>>>> nasd :x -aa &
>>>> 
>>>> where x = 1 thru 65000 or so (I wrote a script to try them all).
>>>> This is strange, as I know not all network ports are in use.
>>>> Any help is appreciated
>>>> 
>>> 
>>>     What version of nas are you running?  If you are using a newer version 
>>> (1.6d or better) try running nas with '-v -d 99' and see if you get better 
>>> information (maybe in your syslog file).
>>> 
>>>     This error usually means that it could not access the audio hardware 
>>> for some reason...
>>> 
>> 
>

-- 
Jon Trulson    mailto:jon at radscan.com
ID: 1A9A2B09, FP: C23F328A721264E7 B6188192EC733962
PGP keys at http://radscan.com/~jon/PGPKeys.txt
#include <std/disclaimer.h>
"I am Nomad." -Nomad