Thank you very much for the tips, but it looks like the alsa modules still aren't working properly.

Bernard Urban wrote:
For Debian woody and alsa-0.9:
You need packages libasound2, alsa-utils, alsa-base and one the following:
alsa-modules-2.4.xx (xx your kernel release) or alsa-source. The latter
let you compile an alsa-modules-2.4.xx for your specific kernel.
I have libasound2, alsa-utils, alsa-base, and alsa-modules-2.4.19-686 installed (since I'm also using kernel-image-2.4.19-686).

lsmod will show you if snd-xxx modules are present.
They are normally automatically loaded when booting,
'lsmod' doesn't show any sound-related modules loaded after boot, not 'snd' or 'sndcore' or anything else that looks like it deals with audio -- BUT, then I try running 'aplay /usr/share/sounds/pop.wav' and I get the error 'aplay: main:447: audio open error: No such file or directory', and then I run 'lsmod' again and now it lists that modules 'snd' and 'soundcore' are loaded.

I do have the following lines in /etc/alsa/modutils/0.9, which is linked to from /etc/modutils/alsa, and the lines also appear in /etc/modules.conf (because I ran update-modules):

alias char-major-116 snd
alias snd-card-0 snd-card-cs4236
alias char-major-14 soundcore
alias sound-slot-0 snd-card-0
alias sound-service-0-0 snd-mixer-oss
alias sound-service-0-1 snd-seq-oss
alias sound-service-0-3 snd-pcm-oss
alias sound-service-0-8 snd-seq-oss
alias sound-service-0-12 snd-pcm-oss
options snd major=116 cards_limit=1 device_mode=0660 device_gid=29 device_uid=0
options snd-card-cs4236 index=0 id=CARD_0 port=0x530 cport=0x210 mpu_port=0x220 fm_port=0x388 irq=5 mpu_irq=7 dma1=1 dma2=0

What I have is identical to what you said except that I removed 'snd_' from all the options.

(I added my user account to the 'audio' group too, by the way.)

Is it correct that the snd and soundcore modules should only be loading after I try to play a sound, and not at boot?

And what does the 'aplay: main:447: audio open error: No such file or directory' error mean? I searched this mailing list but couldn't find anything conclusive on it.

As recommended in another email I found, I ran '/usr/share/doc/alsa-base/examples/snddevices' to create all the required audio devices, and that ran successfully but had no effect on the problem.

Use alsamixer for unmuting, then aplay (in alsa-utils). If aplay
produces sound, it is ok.
When I run 'alsamixer' I get this error:
alsamixer: function snd_ctl_open failed for default: No such file or directory

Being able to use old OSS only programs with alsa is a matter on itself...
How do I know when a program is trying to use OSS instead of alsa?

Currently, there is no complete automatic installation process for
Debian. Depending on your card, you may try stable or unstable 0.9 drivers.
Are you saying that the 0.9 drivers are unstable? Should I try using 0.5 instead?

Thank you again for any help.



-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
_______________________________________________
Alsa-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/alsa-user

Reply via email to