On Thu, Jan 11, 2001 at 12:05:14PM -0600, duane voth wrote:
> Chris wrote:
>
> > Thanks for all the advice. So far no luck. Specifically;
> >
> > turning off the sound-at-startup option in DrakConf had no effect after
> > rebooting. That is, sound was not started, but mpg123 still gave the same
> > "device busy" error. (which makes me wonder - if sound still works without
> > the sound service starting at boot time, what is the point of starting it
> > at boot?)
>
> There is some on-demand loading of modules but I wouldn't trust it.
> Also some daemon (I forget which) likes to unload modules that havn't
> been used for a long time. If they don't get reloaded quick enough
> when mpg123 plays, I could see it possibly being a race condition.
>
> What is that daemon that attempts to clean up "unused" kernel modules?
>
> > ls /pro/*/fd | egrep 'dsp|fd:' showed no processes using /dev/dsp
>
> Make sure you have a 'c' in that ls: ls /proc/*/fd | egrep 'dsp|fd:'
> or use:
>
> lsof /dev/dsp
>
> which is much easier.
>
> duane
>
>
Sorry, that was a typo - I did have the c in proc and got lots of info, just
nothing about /dev/dsp
Likewise, lsof /dev/dsp showed nothing - literally, no results at all.
I am beginning to think this must be an mpg123 problem. Is there a way to
tell it to use a different sound device? What it the difference between
/dev/dsp and /dev/snd?
(Just did ls -l /dev/snd and the results were:
lrwxrwxrwx 1 root root 18 Jan 3 19:39 /dev/snd -> ../proc/asound/dev/
but with the last two in white letters with flashing red background, which I
believe means that they don't exist, or at least the proc/asound/dev
doesn't). Could this have any relevence to the mpg123 problem? Or does it
simply not exist because nothing is currently using it?)
--
Chris Spackman
[EMAIL PROTECTED]
I have recently switched to mutt. If there are any problems with this mail,
I would appreciate it if you could let me know at either the above address
or at [EMAIL PROTECTED]
