[Pkg-alsa-devel] Bug#614113: Re
sergey_ifeo at rambler.ru
Sun Feb 20 11:03:33 UTC 2011
On Sat, 19 Feb 2011 21:56:16 +0100
Elimar Riesebieter <riesebie at lxtec.de> wrote:
> >...Standart way is write this settings to
> > /etc/asound.conf AFAIK.
> No, standard is to read /usr/share/doc/alsa-base/README.Debian.gz
> and follow the hints ;-)
I read this file now. As I can understand, user must do this steps to make sound working:
1) login as root;
2) go to /etc/modprobe.d, look for sound.conf, not found it, be surprised;
3) create sound.conf in hope that it will works;
4) run lsmod and try to understood what modules corresponds to him/her sound devices.
It can be untrivial task. For example I have 16 modules with "snd" in its names.
My card that named "ICH5" in /proc/asound/cards has corresponding module with name "snd_intel8x0" (if I am not wrong). There are no any coincidences in "ICH5" and "snd_intel8x0" strings;
5) write to sound.conf something like this:
alias snd-card-0 <module for highest priority card>
options <module for highest priority card> index=0
alias snd-card-1 <module for lower priority card>
options <module for lower priority card> index=1
6) think about apply changes without reboot.
Will command "/etc/init.d/alsa restart" apply changes or not? Reboot system to take
It is easy task to write GUI or TUI that will create /etc/modprobe.d/sound.conf
(or better sound_cards_priority.conf). It can be reported to mainstream as feature request. But some problems exists:
1) How to determine what modules corresponds to real sound cards, not for
various software things?
2) When we know modules - how to get descriptions of corresponding sound devices?
More information about the Pkg-alsa-devel