Re: ALSA not loading at system boot

[Vinicius Massuchetto <viniciusandre@gmail.com>]

Hi Florian,

Florian Kulzer escreveu:
> [ I am putting the discussion back on the list. ]

Sorry by that. :)

> Forwarded message from Vinicius Massuchetto:
> > Florian Kulzer escreveu:
> > > On Tue, Nov 04, 2008 at 12:30:28 -0200, Vinicius Massuchetto wrote:
> > > > Hi Everyone,
> > > >
> > > > I've been trying to get help on ALSA mailing lists, Debian IRC 
> > > > channels  and forums with no success.
> > > >
> > > > Every time I boot my Debian Sid box I don't have sound until running  
> > > > 'alsaconf'.
> > > >
> > > > Well, here we go, again:
> > > > I've just rebooted my system.
> > > >
> > > > # vinicius@vinicius:~$ lsmod | grep snd
> > > > # snd_hda_intel         434776  0
> > > > # snd_pcm                81672  1 snd_hda_intel
> > > > # snd_seq                54304  0
> > > > # snd_timer              25744  2 snd_pcm,snd_seq
> > > > # snd_seq_device         11668  1 snd_seq
> > > > # snd                    63688  5   
> > > > snd_hda_intel,snd_pcm,snd_seq,snd_timer,snd_seq_device
> > > > # soundcore              12064  1 snd
> > > > # snd_page_alloc         13072  2 snd_hda_intel,snd_pcm
> > > > #
> > > >
> > > > My driver is the snd_hda_intel for this soundcard here:
> > > >
> > > > # vinicius@vinicius:~$ lspci | grep -i audio
> > > > # 00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD 
> > > > Audio  Controller (rev 02)
> > > >
> > > > It's loaded, but no sound.
> > > Which application do you use to test that?
> > Rhythmbox and Totem. I tried speaker-test once with the same results in  
> > this thread.
>
> OK, so we know that the problem is not limited to desktop applications;
> it seems to be a general issue with ALSA.
>
> > All these applications behave as they were playing something, but no  
> > sound comes off. Everything seems to be a volume problem, but all the  
> > channels are always unmutted.
>
> You can do this:
>
> amixer > before.txt
>
> before you run alsaconf and afterwards you run
>
> amixer > after.txt
>
> and compare the mixer settings with
>
> diff -u before.txt after.txt
>
> to make sure that the difference is not due to some semi-obscure control
> that you overlooked.

There's no difference between these two outputs.

> > > > Then trying to start ALSA:
> > > >
> > > > # vinicius@vinicius:~$ sudo /etc/init.d/alsa-utils start
> > > > # Setting up ALSA...done.
> > > >
> > > > No sound yet. Checking alsamixer channels.
> > > > All unmutted and at max. No sound.
> > > >
> > > > Trying alsaconf:
> > > >
> > > > # vinicius@vinicius:~$ sudo alsaconf
> > > > # Unloading ALSA sound driver modules: snd-hda-intel snd-pcm snd-seq  
> > > > snd-timer snd-seq-device snd-page-alloc.
> > > > # Building card database...
> > > > # Loading driver...
> > > > # Setting default volumes...
> > > > # Now ALSA is ready to use.
> > > > # For adjustment of volumes, use your favorite mixer.
> > > > # Have a lot of fun!
> > > >
> > > > SOUND!
>
> [...]
>
> > > Run "lsof $(find /dev/ -group audio)" to see if there are any
> > > applications or sound daemons blocking the sound devices.
> > This command returns nothing just after system boot.
> > Only after alsaconf I can hear the 'speaker-test' sound.
>
> Please post the output of the following commands (before you run
> alsaconf):
>
> cat /dev/sndstat

vinicius@vinicius:~$ cat /dev/sndstat
Sound Driver:3.8.1a-980706 (ALSA v1.0.16 emulation code)
Kernel: Linux vinicius 2.6.26-1-amd64 #1 SMP Sat Oct 18 15:27:18 UTC 
2008 x86_64
Config options: 0
Installed drivers:
Type 10: ALSA emulation
Card config:
HDA Intel at 0xfebfc000 irq 21
Audio devices: NOT ENABLED IN CONFIG
Synth devices: NOT ENABLED IN CONFIG
Midi devices: NOT ENABLED IN CONFIG
Timers:
7: system timer
Mixers: NOT ENABLED IN CONFIG

There's a lot of "NOT ENABLED IN CONFIG" in this output. I guess this 
might mean something.

> cat /proc/asound/cards

vinicius@vinicius:~$ cat /proc/asound/cards
 0 [Intel          ]: HDA-Intel - HDA Intel
                      HDA Intel at 0xfebfc000 irq 21

> grep ^Codec /proc/asound/card?/codec*

vinicius@vinicius:~$ grep ^Codec /proc/asound/card?/codec*
/proc/asound/card0/codec#0:Codec: SigmaTel STAC9228
/proc/asound/card0/codec#1:Codec: Conexant ID 2c06

> grep '.*' /sys/module/snd_hda_intel/parameters/*

vinicius@vinicius:~$ grep '.*' /sys/module/snd_hda_intel/parameters/*
/sys/module/snd_hda_intel/parameters/enable:Y,Y,Y,Y,Y,Y,Y,Y
/sys/module/snd_hda_intel/parameters/enable_msi:0
/sys/module/snd_hda_intel/parameters/id:<NULL>,<NULL>,<NULL>,<NULL>,<NULL>,<NULL>,<NULL>,<NULL>
/sys/module/snd_hda_intel/parameters/index:0,-1,-1,-1,-1,-1,-1,-1
/sys/module/snd_hda_intel/parameters/model:3stack,<NULL>,<NULL>,<NULL>,<NULL>,<NULL>,<NULL>,<NULL>
/sys/module/snd_hda_intel/parameters/position_fix:0,0,0,0,0,0,0,0
/sys/module/snd_hda_intel/parameters/power_save:0
/sys/module/snd_hda_intel/parameters/power_save_controller:Y
/sys/module/snd_hda_intel/parameters/probe_mask:-1,-1,-1,-1,-1,-1,-1,-1
/sys/module/snd_hda_intel/parameters/single_cmd:N

> It would furthermore be interesting to know if the output of the last
> one (the module parameters) changes after you run alsaconf.

There's no difference between both outputs as well.

Hope we can figure out somehting.
Thanks again!
Vinicius