That seems to indicate that the daemon is running:
root 5678 0.0 0.0 3088 1444 ? Ss Mar06 0:00
/usr/bin/esd -terminate -nobeeps -as 1 -spawnfd 14
pcs 21426 0.0 0.0 2876 792 pts/0 R+ 08:09 0:00 grep esd
but starting manually produced some interesting output:
[EMAIL PROTECTED]:~$ esd &
[1] 21600
[EMAIL PROTECTED]:~$ ALSA lib confmisc.c:672:(snd_func_card_driver) cannot find
card '0'
ALSA lib conf.c:3493:(_snd_config_evaluate) function snd_func_card_driver
returned error: No such device
ALSA lib confmisc.c:392:(snd_func_concat) error evaluating strings
ALSA lib conf.c:3493:(_snd_config_evaluate) function snd_func_concat
returned error: No such device
ALSA lib confmisc.c:1072:(snd_func_refer) error evaluating name
ALSA lib conf.c:3493:(_snd_config_evaluate) function snd_func_refer returned
error: No such device
ALSA lib conf.c:3962:(snd_config_expand) Evaluate error: No such device
ALSA lib pcm.c:2102:(snd_pcm_open_noupdate) Unknown PCM default
Is there a way to tell ALSA (or whoever) what to do about card '0' ?
TIA
Hi,
On Tue, 06 Mar 2007, Michael Steigerwald wrote:
> snd_hda_intel 18964 0
> snd_hda_codec 157616 1 snd_hda_intel
> snd_pcm 89864 3 snd_hda_intel,snd_hda_codec,snd_pcm_oss
> snd 55268 6
> snd_hda_intel,snd_hda_codec,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_timer
> snd_page_alloc 10632 2 snd_hda_intel,snd_pcm
>
> I don't know how to interpret it. Does the '0' in the first line
indicate
> it's not loaded?
Its presence in the list means it is loaded, but the 0 usually means
something along the lines of "not in use by any process". I wouldn't
worry
overly about that.
> From the BIOS, it appears that the internal modem is enabled. Restarting
> ALSA did not seem to help.
I wasn't clear what this would do, just that it was suggested in that
article.
> I learned a lot from the tutorials, but the only other tangible
suggestion I
> found seemed to paraphrase to 'compile snd_hda_intel' into the kernel.
Is
> that my next best attempt?
There shouldn't be any need to do this -- the module is already there.
What do you get if you type the following commands:
ps aux |grep esd
esd &
The first searches the running processes for esound, the sound daemon, to
see if it is running. The second starts the sound daemon, it would be
interesting to know what happens when you try to start it.
Gavin
--
edubuntu-users mailing list
[email protected]
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/edubuntu-users
