[Pkg-alsa-devel] Bug#614113: alsa-base: alsa accepts cards names in /usr/share/alsa/alsa.conf but wants only numbers in /etc/alsa.conf

[Elimar Riesebieter]

* sergey [110220 14:03 +0300]:
> 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;

Yes

> 2) go to /etc/modprobe.d, look for sound.conf, not found it, be
> surprised;

The file doesn't exist by default. It must be created by root

> 3) create sound.conf in hope that it will works;

Yes

> 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;

It is the correct modul, Please post the output of
$lsmod | grep snd


> 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

Absolutely correct

> 6) think about apply changes without reboot.
> Will command "/etc/init.d/alsa restart" apply changes or not?
> Reboot system to take guarantied result.

Try 
# /usr/bin/alsa force-reload


> 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:

You can name that file as you want. What's needed is the extension
'.conf'. i.e. alsa-$HOST.conf


> 1) How to determine what modules corresponds to real sound cards,
> not for various software things?

$ modinfo snd_<whatever you see>

> 2) When we know modules - how to get descriptions of corresponding
> sound devices?

In your case:
$ modinfo snd_intel8x0

Elimar

-- 
  Excellent day for drinking heavily. 
  Spike the office water cooler;-)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-alsa-devel/attachments/20110220/8f143159/attachment-0001.pgp>