boot sequence and alsa
Hi all,
I am having a problem with alsa modules during boot. The problem is
the following: after boot sound card does not work, when I do
/etc/init.d/alsa force-reload it works OK. I checked that after boot
all the required modules are loaded (via lsmod), so it not the
problem of loading the right modules. In order to make that card
working I had to add manually a parameter for the sound card module
(I use snd-hda-intel), and I added it into /etc/modprobe.d/sound. I
guess the problem is that at boot the modules are started without
that parameter.
So I decided to track down the problem and see how exactly the alsa
modules are started at boot. Now, here is a mess (at least for me).
There is no any one document that describes how the modules are
configured and started. For example, I have /etc/modutils/*,
/etc/modules.conf and /etc/modprobe.d/* (it is all installed
automatically by Etch in testing). How this all works? man
modules.conf tells me that I shouldn't edit it since it is generated
by update-modules, man update-modules tells me that it is
deprectated. So what files are really used /etc/modules.conf or
/etc/modprobe.d/*? If i edit /etc/modprobe.d/sound, how do I make
sure that this file is read during boot?
Now, let's assume this mess somehow works and let's find who calls
modprobe for snd-hda-intel. The main file that loads alsa dirver is
/etc/init.d/alsa. I don't have symlink to this script from /etc/rcS
nor from /etc/rc2.d. OK, probably the modprobe is called directly by
a hardware detector, I have "discovery" installed automatically. I
unload all sound modules and run "/etc/init.d/discover start" and I
find that it does *not* load any sound modules. I also checked that
file /etc/modules does not contain any sound modules either. Now I am
stuck. Which other sript can load the sound modules? How it might be
that a module parameter in /etc/modprobe.d/sound is not taken into
account during boot?
I would be greatful for any hint on the last question, in particular.
Denis
Reply to: