11.1 No Sound - Azalia Intel HDA (Asus M3A78-CM M'board)

English Hardware
1

Hello,

After trying many of the suggestions made in other threads about this, as well as trying some of the suggestions in the “SDB:AudioTroubleshooting guide” I’m hoping that somebody will have a solution to this.

There is a bit of sound when gnome starts up and at one point

speaker-test -c2 -l5 -twav

produced output; but nothing else. Also, at the end of this post is /var/log/messages output from ‘rcalsasound restart’

David Murdoch

alsa=info output at
http://www.alsa-project.org/db/?f=123252b8f403ac7f432b9c16d5efd45a8a76c77c

rpm -qa | grep alsa

alsa-oss-32bit-1.0.17.git20080715-2.24
alsa-utils-1.0.19.git20090319-1.2
alsa-driver-unstable-kmp-default-1.0.19.20090324_2.6.27.19_3.2-2.1
alsa-tools-1.0.19.git20090320-1.2
alsa-1.0.19.git20090304-3.1
alsa-plugins-1.0.19.git20090303-1.10
alsa-plugins-pulse-1.0.18-6.13
alsa-oss-1.0.17.git20080715-2.24
alsa-driver-kmp-default-1.0.19.20090404_2.6.27.19_3.2-1.1
alsa-firmware-1.0.19.git20090317-1.1

rpm -qa | grep pulse

libpulse-mainloop-glib0-0.9.12-9.5
pulseaudio-module-bluetooth-0.9.12-9.5
libxine1-pulse-1.1.15-20.8
libpulse0-32bit-0.9.12-9.6
pulseaudio-utils-0.9.12-9.5
libpulse0-0.9.12-9.5
libpulse-browse0-0.9.12-9.5
pulseaudio-0.9.12-9.5
pulseaudio-module-x11-0.9.12-9.5
pulseaudio-esound-compat-0.9.12-9.5
alsa-plugins-pulse-1.0.18-6.13
pulseaudio-module-gconf-0.9.12-9.5
pulseaudio-module-lirc-0.9.12-9.5
libpulsecore4-0.9.12-9.5
pulseaudio-module-zeroconf-0.9.12-9.5

rpm -q libasound2

libasound2-1.0.19.git20090304-3.1

cat /etc/modprobe.d/sound

options snd slots=snd-hda-intel

5Dex.gK2Bvf1HDkE:SBx00 Azalia (Intel HDA)

alias snd-card-0 snd-hda-intel

cat /proc/asound/version

Advanced Linux Sound Architecture Driver Version 1.0.19-git20090324.
Compiled on Mar 24 2009 for kernel 2.6.27.19-3.2-default (SMP).

cat /proc/asound/modules

0 snd_hda_intel

cat /proc/asound/cards

0 [SB ]: HDA-Intel - HDA ATI SB
HDA ATI SB at 0xfbcf4000 irq 16

/var/log/messages output from

rcalsasound restart

Apr 5 07:28:44 linux-oi0v kernel: HDA Intel 0000:00:14.2: PCI INT A disabled
Apr 5 07:28:44 linux-oi0v kernel: HDA Intel 0000:00:14.2: PCI INT A → GSI 16 (level, low) → IRQ 16
Apr 5 07:28:44 linux-oi0v kernel: ALSA /usr/src/packages/BUILD/alsa-driver-unstable/pci/hda/…/…/alsa-kernel/pci/hda/hda_codec.c:3824: autoconfig: line_outs=4 (0x1c/0x19/0x22/0x23/0x0)
Apr 5 07:28:44 linux-oi0v kernel: ALSA /usr/src/packages/BUILD/alsa-driver-unstable/pci/hda/…/…/alsa-kernel/pci/hda/hda_codec.c:3828: speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
Apr 5 07:28:44 linux-oi0v kernel: ALSA /usr/src/packages/BUILD/alsa-driver-unstable/pci/hda/…/…/alsa-kernel/pci/hda/hda_codec.c:3832: hp_outs=1 (0x1d/0x0/0x0/0x0/0x0)
Apr 5 07:28:44 linux-oi0v kernel: ALSA /usr/src/packages/BUILD/alsa-driver-unstable/pci/hda/…/…/alsa-kernel/pci/hda/hda_codec.c:3833: mono: mono_out=0x0
Apr 5 07:28:44 linux-oi0v kernel: ALSA /usr/src/packages/BUILD/alsa-driver-unstable/pci/hda/…/…/alsa-kernel/pci/hda/hda_codec.c:3836: dig-out=0x20/0x0
Apr 5 07:28:44 linux-oi0v kernel: ALSA /usr/src/packages/BUILD/alsa-driver-unstable/pci/hda/…/…/alsa-kernel/pci/hda/hda_codec.c:3844: inputs: mic=0x1a, fmic=0x1e, line=0x1b, fline=0x0, cd=0x1f, aux=0x0
Apr 5 07:28:44 linux-oi0v kernel: ALSA /usr/src/packages/BUILD/alsa-driver-unstable/pci/hda/…/…/alsa-kernel/pci/hda/hda_codec.c:2694: hda_codec: formats == 0 (nid=0x10, val=0xa05e0, ovrd=1, streams=0xa05e0)
Apr 5 07:28:44 linux-oi0v kernel: hda_codec: cannot attach PCM stream 0 for codec #0
Apr 5 07:28:44 linux-oi0v kernel: ALSA /usr/src/packages/BUILD/alsa-driver-unstable/pci/hda/…/…/alsa-kernel/pci/hda/hda_codec.c:2694: hda_codec: formats == 0 (nid=0x12, val=0xa01e0, ovrd=1, streams=0xa01e0)
Apr 5 07:28:44 linux-oi0v kernel: hda_codec: cannot attach PCM stream 1 for codec #0

2

I don’t know about the error messages, but there is a clear problem with the rpms you have installed.

Whether fixing it will help you with an VIA VT1708B 8-Ch codec, I don’t know. I see some mention of the VT1708 on the ALSA web site: Search results - AlsaProject

But you should probably try to fix it. You should not have alsa-driver-unstable-kmp-default installed. So remove it. And then its removal may cause problems with alsa-driver-kmp-default so you probably should re-install alsa-driver-kmp-default. It also is probably a good idea to update alsa-plugins-pulse to a git version to be consistent with your other alsa apps. So after completing that, then reboot and test your sound.

Also, try to be consistent in your mixer settings. For testing sound I recommend you put volume controls at 95% and once basic sound is established, back off to a lower level. Many sound devices do not have a linear range for sound, and one only hears the volume changes at the very high percent levels.

So looking at your mixer:
!!Amixer output
!!-------------

!!-------Mixer controls for card 0 [SB]
Card hw:0 ‘SB’/‘HDA ATI SB at 0xfbcf4000 irq 16’
Mixer name : ‘VIA VT1708B 8-Ch’
Simple mixer control ‘Master Front’,0
Front Left: Playback 21 68%] -3.50dB] [on]
Front Right: Playback 21 68%] -3.50dB] [on]
Simple mixer control ‘PCM’,0
Front Left: Playback 191 75%] -12.80dB]
Front Right: Playback 191 75%] -12.80dB]
Simple mixer control ‘Front’,0
Front Left: Playback 20 74%] -12.25dB] [on]
Front Right: Playback 20 74%] -12.25dB] [on]
Simple mixer control ‘Surround’,0
Front Left: Playback 20 74%] -12.25dB] [on]
Front Right: Playback 20 74%] -12.25dB] [on]
Simple mixer control ‘Center’,0
Mono: Playback 20 74%] -12.25dB] [on]
Simple mixer control ‘LFE’,0
Mono: Playback 0 0%] -47.25dB] [on]
Simple mixer control ‘Side’,0
Front Left: Playback 0 0%] -47.25dB] [on]
Front Right: Playback 0 0%] -47.25dB] [on]
Simple mixer control ‘Line’,0
Front Left: Playback 20 65%] -5.25dB] [on]
Front Right: Playback 20 65%] -5.25dB] [on]
Simple mixer control ‘IEC958’,0
Capabilities: pswitch pswitch-joined
Mono: Playback [off]
Simple mixer control ‘IEC958 Default PCM’,0
Capabilities: pswitch pswitch-joined
Playback channels: Mono
Mono: Playback [on]
Your PC has digital audio IEC958 ON, but then has the mixer control OFF. Why have LFE and mixer side ON at 0% ? Try moving your volume settings up from 75% to 95% (back off once you establish sound).

And make certain you keep trying both speaker-tests from the audio troubleshooting guide as your sound test (as a regular user and with root permissions, both with and without a headset).SDB:AudioTroubleshooting - openSUSE - speaker test

3

alsa-driver-unstable-kmp-default has been removed
alsa-driver-kmp-default has been re-installed

I’ve no idea how to ensure that alsa-plugins-pulse is updated to a git version?

David Murdoch

4

Restart and test your sound.

You never have heard of webpin then ?
Webpin - openSUSE rpm search engine

do a simple search:
Webpin - search results for alsa-plugins-pulse

…or you could go straight to the multimedia repos:
Index of /repositories/multimedia:/audio/openSUSE_11.1

5

Sound is working now after increasing the volume as you suggested but without replacing alsa-plugins-pulse with a git version. Thanks for the ‘git’ tips!

I’ve noticed that many of the sound issues are volume related or conflicting sound settings and I have to admit that - at the moment - I don’t understand what all the settings that are presented mean.

I did re-run alsa-info.sh. Output at
http://www.alsa-project.org/db/?f=cee02f1021f818d8450cc479e6c0745df42ffe50

Your assistance is much appreciated and hopefully this thread will assist others with similar problems.

Best wishes,

David Murdoch

6

Congratulations on sorting this ! Thanks for sharing your solution.

I half expected alsa-plugins-pulse to git was not necessary, … but pulse is still very much an unknown to me.

Me too. Welcome to the club.

Thanks. Its always interesting to see the output when it works.

7

I, too, have a Asus m3a78-em motherboard. And it is silent. Have you had any success with getting sound?

There is a very brief message the pops up and disappears too quickly to get much detail but paraphrasing: “Phonon - HDA SB (ALC 1200) failed). Falling back to HDA HDMI”. (HDMI is considered a fallback?)

alsa 1.0.18.

<small rant>
I thought it was just os/2 and windows that could rarely to get sound to work, at least not without a giant hassle. Now it seems linux also has significant difficulty with sound. What is it about sound that is so d–n difficult?

I don’t even need 2-channel. Monoaural would be find. Sheesh.
</rant>

8

did you try working your way through the openSUSE audio troubleshooting guide?

URL for the guide is here: SDB:AudioTroubleshooting - openSUSE

Unfortunately, Linux also has hiccups.

Non functioning basic sound is also a pet peeve of mine, and to help address that in Linux, I make a point of almost every day doing a search on this forum for “sound”, “speakers”, “audio”, “mic” and then during the course of the day when I can find the time, try to help the users with their basic audio hiccups.

Advanced audio problems I leave for others with more experience/knowledge than I to solve.

So please keep us informed as to your success/failure, and if the guide does not help you, let us know, and we will try give you some specific things to try.

9

oldcpu adjusted his/her AFDB on Friday 21 Aug 2009 07:56 to write:

> So please keep us informed as to your success/failure, and if the guide
> does not help you, let us know, and we will try give you some specific
> things to try.
>
>

I have 2 boards with the azalia sound card working fine here.

All I did was turn the volume and dsp up.

I have both in 7.1, I do however un-install all things pulse except the
libpulse0.

But that should not stop you at least getting the sound working, this should
workout of the box

The HDMI that it is defaulting to after a phonon error is probably the HDMI
on an ATI graphics card.

You need to use YaST and delete all the cards and then re-configure just the
azalia, you should not have to change anything just ok through, oldpc has
stated many many times that the sound test in Yast of 11.1 does not play
anything this is a “feature” so not getting sound there is no indication
that the card is not working.

You need the volume turned pretty high ( 95% ) as some cards do not kick in
till the mixer is cranked up.

The reason that the volume is set low is that when it was set high too many
people complained that it nearly blew their speakers and ears out, so to err
on the safe side it is set at a minimal level, however as I said some cards
do not like a low level.

I think you will find that oldcpu has a page somewhere with all these
details on.

HTH

Mark
Caveat emptor
Nullus in verba
Nil illegitimi carborundum

10

I do not believe that quoted message is relevant.

Rather I believe the message is a known bug and that a number of users have reported this. There are a more than a few threads here, where users have posted solutions that worked for them:

Your lack of sound problems are likely another issue.