FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Debian > Debian User

 
 
LinkBack Thread Tools
 
Old 11-04-2008, 01:30 PM
Vinicius Massuchetto
 
Default ALSA not loading at system boot

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_de vice

# 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. 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!

Can someone help me? I don't want to keep running alsaconf every tim I
turn on my computer.


Thanks in advance.
Vinicius


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
 
Old 11-04-2008, 05:10 PM
Florian Kulzer
 
Default ALSA not loading at system boot

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_de vice
> # 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?

> 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!
>
> Can someone help me? I don't want to keep running alsaconf every tim I
> turn on my computer.

Boot the PC and run "speaker-test -t sine". Do you get sound, is there
an error message?

Try "modprobe snd_pcm_oss".

Run "lsof $(find /dev/ -group audio)" to see if there are any
applications or sound daemons blocking the sound devices.

--
Regards, | http://users.icfo.es/Florian.Kulzer
Florian |


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
 
Old 11-05-2008, 05:13 PM
Florian Kulzer
 
Default ALSA not loading at system boot

[ 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_de vice
>>> # 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.

--
Regards, | http://users.icfo.es/Florian.Kulzer
Florian |


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
 
Old 11-05-2008, 07:14 PM
"Anton Piatek"
 
Default 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_de vice
>>>> # 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.


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
 
Old 11-05-2008, 09:42 PM
Vinicius Massuchetto
 
Default ALSA not loading at system boot

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_de vice

# 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>,<N ULL>,<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


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
 
Old 11-05-2008, 09:45 PM
Vinicius Massuchetto
 
Default ALSA not loading at system boot

Hi Anton,

> Anton Piatek escreveu:

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


Well. Something popped out here:

vinicius@vinicius:~$ diff -u lsmod_before lsmod_after
--- lsmod_before 2008-11-05 20:34:58.000000000 -0200
+++ lsmod_after 2008-11-05 20:41:45.000000000 -0200
@@ -1,4 +1,12 @@
Module Size Used by
+snd_hda_intel 434776 3
+snd_pcm 81672 2 snd_hda_intel
+snd_seq 54304 0
+snd_timer 25744 3 snd_pcm,snd_seq
+snd_seq_device 11668 1 snd_seq
+snd 63688 9
snd_hda_intel,snd_pcm,snd_seq,snd_timer,snd_seq_de vice

+soundcore 12064 1 snd
+snd_page_alloc 13072 2 snd_hda_intel,snd_pcm
nvidia 8105072 36
ppdev 11656 0
parport_pc 31016 0
@@ -24,7 +32,6 @@
i2c_core 27936 2 nvidia,i2c_i801
serio_raw 9860 0
pcspkr 7040 0
-snd_hda_intel 434776 0
led_class 8968 1 iwl3945
iTCO_wdt 15696 0
compat_ioctl32 12288 1 uvcvideo
@@ -33,18 +40,11 @@
cfg80211 30224 2 iwl3945,mac80211
video 24084 10
output 7808 1 video
-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
ac 9352 0
wmi 11712 0
battery 16904 0
button 11680 0
-snd 63688 5
snd_hda_intel,snd_pcm,snd_seq,snd_timer,snd_seq_de vice

-soundcore 12064 1 snd
intel_agp 31728 0
-snd_page_alloc 13072 2 snd_hda_intel,snd_pcm
evdev 14208 11
dcdbas 11952 0
reiserfs 211072 2

It seems something was definitively loaded after running alsaconf.

Thanks for helping!
Vinicius


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
 
Old 11-06-2008, 01:44 AM
Lachlan
 
Default ALSA not loading at system boot

2008/11/6 Vinicius Massuchetto <viniciusandre@gmail.com>:
> Hi Anton,
>
>> Anton Piatek escreveu:
>>
>> do "lsmod>before" then run "alsaconf" and then run "lsmod>after". Now
>> do "diff before after" and post the results

i had exactly the same problem.

when you run alsaconf get the names of all the soundcards it loads
when you select your card. blacklist the ones you don't use in
/etc/modprobe.d/blacklist

i kept having the ati hdmi and another card that i'm not even sure was
connected to my system blocking my actual sound card from being
detected at all.

the only way i could get my sound to stay without blacklisting the extra cards.

>>
>> 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...
>
> Well. Something popped out here:
>
> vinicius@vinicius:~$ diff -u lsmod_before lsmod_after
> --- lsmod_before 2008-11-05 20:34:58.000000000 -0200
> +++ lsmod_after 2008-11-05 20:41:45.000000000 -0200
> @@ -1,4 +1,12 @@
> Module Size Used by
> +snd_hda_intel 434776 3
> +snd_pcm 81672 2 snd_hda_intel
> +snd_seq 54304 0
> +snd_timer 25744 3 snd_pcm,snd_seq
> +snd_seq_device 11668 1 snd_seq
> +snd 63688 9
> snd_hda_intel,snd_pcm,snd_seq,snd_timer,snd_seq_de vice
> +soundcore 12064 1 snd
> +snd_page_alloc 13072 2 snd_hda_intel,snd_pcm
> nvidia 8105072 36
> ppdev 11656 0
> parport_pc 31016 0
> @@ -24,7 +32,6 @@
> i2c_core 27936 2 nvidia,i2c_i801
> serio_raw 9860 0
> pcspkr 7040 0
> -snd_hda_intel 434776 0
> led_class 8968 1 iwl3945
> iTCO_wdt 15696 0
> compat_ioctl32 12288 1 uvcvideo
> @@ -33,18 +40,11 @@
> cfg80211 30224 2 iwl3945,mac80211
> video 24084 10
> output 7808 1 video
> -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
> ac 9352 0
> wmi 11712 0
> battery 16904 0
> button 11680 0
> -snd 63688 5
> snd_hda_intel,snd_pcm,snd_seq,snd_timer,snd_seq_de vice
> -soundcore 12064 1 snd
> intel_agp 31728 0
> -snd_page_alloc 13072 2 snd_hda_intel,snd_pcm
> evdev 14208 11
> dcdbas 11952 0
> reiserfs 211072 2
>
> It seems something was definitively loaded after running alsaconf.
>
> Thanks for helping!
> Vinicius
>
>
> --
> To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org with a subject
> of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
>
>


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
 
Old 11-06-2008, 03:43 PM
Vinicius Massuchetto
 
Default ALSA not loading at system boot

Hi Lachlan,

Lachlan escreveu:

2008/11/6 Vinicius Massuchetto <viniciusandre@gmail.com>:

Hi Anton,


Anton Piatek escreveu:

do "lsmod>before" then run "alsaconf" and then run "lsmod>after". Now
do "diff before after" and post the results


i had exactly the same problem.

when you run alsaconf get the names of all the soundcards it loads
when you select your card. blacklist the ones you don't use in
/etc/modprobe.d/blacklist

i kept having the ati hdmi and another card that i'm not even sure was
connected to my system blocking my actual sound card from being
detected at all.

the only way i could get my sound to stay without blacklisting the extra cards.


That makes sense, because 'alsaconf' asks me to choose between my HDA
Intel card, and another 'legacy' one. Then according to my '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...

# Then I have the following prompt:
# hda-intel Intel Corporation 82801H (ICH8 Fa...
# legacy Probe legacy ISA (non-PnP) chips...

Loading driver...
Setting default volumes...
================================================== =============================
Now ALSA is ready to use.
For adjustment of volumes, use your favorite mixer.

Have a lot of fun!

What would be the lines I shall add to /etc/modprobe.d/blacklist ?

Thanks!
Vinicius


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
 
Old 11-06-2008, 05:52 PM
Florian Kulzer
 
Default ALSA not loading at system boot

On Wed, Nov 05, 2008 at 20:42:19 -0200, Vinicius Massuchetto wrote:
>> Forwarded message from Vinicius Massuchetto:
>>> Florian Kulzer escreveu:
>>>> On Tue, Nov 04, 2008 at 12:30:28 -0200, Vinicius Massuchetto wrote:

[...]

>>>>> 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_de vice
>>>>> # 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)

[ snip: The mixer settings are absolutely identical before and after
running alsaconf. ]

[...]

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

This is certainly related to the problem. I have never seen "NOT ENABLED
IN CONFIG" for the audio devices. I think this means that the hardware
is not detected properly. (My guess would be that this message is
different after you run alsaconf, at least for audio.)

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

It does not seem that the problem is due to multiple recognized cards
and changes in their order.

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

Hmm, one card with two codecs; I cannot find any information about the
Conexant one in ALSA-Configuration.txt. If I google "SigmaTel STAC9228
Conexant ID 2c06" then I find some discussions about problems on
(ed)ubuntu forums, which were resolved by installing a newer version of
alsa. (They mention kernel 2.6.24; with a fully up-to-date Sid you
should have kernel 2.6.26.)

>> 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>,<N ULL>,<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.

So the difference is not due to a change of module parameters ("model"
is often good candidate, but it remains the same in your case). I am
beginning to suspect that there is a bug that requires the modules to be
loaded later than they normally are in the boot process. (One of the
main things that alsaconf does is unload the sound modules and load them
again.) When I look at the diff output of lsmod that you posted in
another mail, I see that the same modules were loaded again, but some of
the "Used by" numbers changed. I propose that you try this (as root)
after boot:

modprobe -r snd_hda_intel snd_pcm_oss snd_seq
modprobe snd_hda_intel
modprobe snd_pcm_oss

to see if merely unloading and reloading the modules is enough to get
your sound working. (If it works then I would simply put this sequence
of commands into /etc/rc.local and hope that this workaround will be
obsoleted by some future alsa upgrade.)

--
Regards, | http://users.icfo.es/Florian.Kulzer
Florian |


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
 
Old 11-06-2008, 05:54 PM
Nigel Henry
 
Default ALSA not loading at system boot

On Wednesday 05 November 2008 23:42, Vinicius Massuchetto wrote:
>
> > 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
>

> Hope we can figure out somehting.
> Thanks again!
> Vinicius

Hi Vinicius.

It's very odd that you have 2 different codecs showing above. This could well
be causing a conflict, and is why you have no sound after bootup.

Could you post the complete output of lspci -v . I ask, because I have seen
before, a graphics card, which has a sound component, which is an hda intel
based one, but using a different codec.

After running alsaconf, and getting your soundcard up and running, would you
open alsamixer, and report back which chipset it is showing being used. It's
going to be either the STAC9228, or the Conexant one, not both.

If this is the case, I'm not too sure how to resolve the problem.

Perhaps a couple of lines in /etc/rc.local, as below.

modprobe -r snd-hda-intel
modprobe snd-hda-intel

Just some thoughts.

Nigel.



--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
 

Thread Tools




All times are GMT. The time now is 04:45 AM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org