Re: ALSA not loading at system boot
2008/11/5 Florian Kulzer <florian.kulzer+debian@icfo.es>:
> [ I am putting the discussion back on the list. ]
>
> 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.
>
>>>> 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
>
> cat /proc/asound/cards
>
> grep ^Codec /proc/asound/card?/codec*
>
> grep '.*' /sys/module/snd_hda_intel/parameters/*
>
> It would furthermore be interesting to know if the output of the last
> one (the module parameters) changes after you run alsaconf.
do "lsmod>before" then run "alsaconf" and then run "lsmod>after". Now
do "diff before after" and post the results
I found I had snd_pcsp module loading badly which was causing problems
for sound - the reason it was loading badly was because
/etc/modprobe.conf had been created and wasn't loading
/etc/modprobe.d/*
I solved my problem by moving /etc/modprobe.conf out of the way...
Anton
--
Anton Piatek
email: anton@piatek.co.uk
blog/photos: http://www.strangeparty.com
pgp: [0xB307BAEF] (http://www.strangeparty.com/anton.asc)
fingerprint: 116A 5F01 1E5F 1ADE 78C6 EDB3 B9B6 E622 B307 BAEF
No trees were destroyed in the sending of this message, however, a
significant number of electrons were terribly inconvenienced.
Reply to: