I apologize for having put my question in the wrong thread, sorry...

James Fletcher wrote:
> run alsaconf as root in terminal, this will then guide you through sound
> config, and load the module, when you know which module you need, add it
> to the list of modules in the /etc/modules file. also disable your
> onboard sound in BIOS if you're using a sound card (cheap trick but it
> works)

Onboard sound is disabled in BIOS. alsaconf found:
via82xx		VIA Technologies Inc
emu10k1		Creative Labs SB Audigy
When I select Creative Labs alsaconf suggests to load snd-emu10k1 and then
it works. Writing  snd-emu10k1 in/etc/modules however has no effect (after
reboot), Etch still loads VIA.

Or did I misinterpret snd-emu10k1? Does it read "EMUL0KL" or rather
"EMU1K1"?

[ Post a follow-up to this message ]

On Jan 23, 2:09 pm, Hubert Gabler <d...@yahoo.com> wrote:
> I apologize for having put my question in the wrong thread, sorry...
>
> James Fletcher wrote: 
> via82xx         VIA Technologies Inc
> emu10k1         Creative Labs SB Audigy
> When I select Creative Labs alsaconf suggests to load snd-emu10k1 and then
> it works. Writing  snd-emu10k1 in/etc/modules however has no effect (after
> reboot), Etch still loads VIA.
>
> Or did I misinterpret snd-emu10k1? Does it read "EMUL0KL" or rather
> "EMU1K1"?

You could try to put this file this in /etc/modprobe.d (for kernel 2.6
and /etc/modutils for 2.4)
File "alsa-local" (or something like that. Suffix -local to indicat
local additions)
========== cut ===========
# Add Creative Labs SB Audigy as first (default) alsa sound card
alias snd-card-0 snd-emu10k1
option snd-emu10k1 index=0
# Add VIA Tech (or which driver is used for this card) as second alsa
sound card
alias snd-card-1 snd-intel8x0
option snd-intel8x0  index=1
# You could also blacklist a card (or any kernel module) with a line
like this
#blacklist snd_intel8x0
# Look in man page "man modprobe.conf" and in diroctories
# /usr/share/doc/alsa-base/README.Debian.gz
# "Unfortunately, alsaconf can only detect one sound card and is
generally a
#  poorly written program."
# "Another way of discovering what module(s) you need is to install the
"discover"
#  package and to run the following command as root:
#    discover --data-path=linux/module/name --data-version=$(uname -r)
audio"
#
# eof
========== cut ===========
So do "zmore /usr/share/doc/modutils/README.Debian.gz" if you have
modutils installed.
If you   You should instead use package module-init-tools if you use
Linux kernel 2.6 and later

(Mostly from memory.  Please search on net or read documents to verify)

[ Post a follow-up to this message ]

Sorry. I messed things up a bit in the end.
> So do "zmore /usr/share/doc/modutils/README.Debian.gz" if you have
> modutils installed.
> If you   You should instead use package module-init-tools if you use
> Linux kernel 2.6 and later
Package modutils is for kernel 2.4 and module-init-tools is for 2.6

Linux kernels 2.4 uses files in directory /etc/modutils/ to controll
blacklisting kernel moduler, options to kernel modules and which
programs should run when loading and unloading kernel modules.
Linux kernels 2.6 uses directory /etc/modprobe.d/ to do the same.

Remember to read package documents under /usr/share/doc/"modulename"
when you have problems.  In this case, you should read
"/usr/share/doc/alsa-base/README.Debain.gz" and look for information in
"/usr/share/doc/modutils/" and "/usr/share/doc/module-init-tools/".
zmore and zcat is versions of more and cat that can read gzip:ed text
files directly.

Good luck.
/Jxn

[ Post a follow-up to this message ]