17 Jan
2004
17 Jan
'04
6:25 a.m.
modprobe.conf and modules.conf have the same sound related entries.
Where is snddevices found? I can't install alsa-driver when alsa is
built in and even if I exclude alsa from the kernel I still can't
install it. I'm just going to try a straight 2.6.1 kernel (no patches).
I got sound with the 2.6 by doing this but had dreadful jack
performance. Here goes...
/dev/snd/pcmC0D0p failed:
This file exists and I gave it full permissions. But no luck for me.
Gian Paolo Mureddu wrote:
Tommi Sakari Uimonen wrote:
Also, did you set the modules to load in modprobe.conf, used by 2.6.x
(instead of modules.conf which is used by 2.4.x) to load modules
(copy-paste the settings). Definitly it is also advisable to run
snddevices (if this is your first time using ALSA).
rebooted
and install alsa-lib-1.0.1 and alsa-utils-1.0.1 as well but I
get these errors
root@upstairs glenn # aplay /usr/kde/3.2/share/sounds/pop.wav
ALSA lib pcm_hw.c:1055:(snd_pcm_hw_open) open /dev/snd/pcmC0D0p failed:
No such file or directory
aplay: main:502: audio open error: No such file or directory
I'm not totally sure, but if devfs is not in the kernel, you should also
run snddevices script from alsa-driver.
It will create the /dev entries needed for alsa.
Tommi Uimonen