No sound on installation

Bug #156930 reported by Matthew Craig
16
This bug affects 2 people
Affects Status Importance Assigned to Milestone
alsa-driver (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

On both Feisty and Gutsy, there was no sound on installation. The problem is that the DCA channel in ALSAMIXER was set to zero. The first time I saw this problem in Feisty, it took me a week to figure it out. Most recently I saw it again in a clean Gutsy install, and it took me 8-9 hours to figure it out, because of course I forgot about my previous experience. This may be "working as designed", but it is incredibly frustrating and I decided to file a bug report so others can reference the fix (including myself when this happens to me again.)

A great first step in troubleshooting lack of sound is to open a terminal window and type "alsamixer". The ALSA tools might not know your default card, and result in the following error, "alsamixer: function snd_ctl_open failed for default: No such device", but before you go and try all the troubleshooting guides that recommend reloading modules, try, "alsamixer -c 0" or "alsamixer -c 1".

You should be at a text-GUI (aka: curses) for alsamixer. Scroll through each channel and set them all to 100% with the left, right, and up arrows. Also unmute all channels with the space-bar key. You may need to hit the tab key to get to other interfaces. Check the top-left of the screen to make sure the card you are configuring is the one you expect.

Now that all your channels are maxed, open the GNOME sound configuration tool. (System -> Preferences -> Sound.) You do not need to close the alsamixer or save the settings for them to take effect. Play with the Sound Playback drop down choices and click the Test button. Some may give you errors, and that's okay. Hopefully you will find a setting that works.

Lastly, return to your alsamixer window, which should still be open. While the tone is playing from the sound configuration tool, lower the active channels half way or so, and lower the inactive channels even more. At this time you may want to mute some channels (again with the space bar) or set channels to zero. Do this while the sound is playing so that you know you are not muting your primary sound again.

The Linux sound system can be confusing. There are GNOME sound levels and ALSA sound levels. You have to be sure neither are muted in order to get sound output. It doesn't help that some of the channels are called things like "DAC" (which means Digital Analog Converter, by the way). The problem - the bug - here is that Ubuntu installs with some of these required channels set to zero or set to mute, and dozens of people ask for help on this issue every day. Hope this information finds its way to some of them.

Revision history for this message
Matthew Craig (matthew-t-craig) wrote :

A quick correction: That should be the M key, not the space key, to mute and unmute sound channels.

Revision history for this message
Matthew Craig (matthew-t-craig) wrote :

As an alternative to using alsamixer to check volume levels, one can use the GNOME Volume Control application. However, by default, this application does not show all ALSA channels. Configure all channels in the view, by using Edit->Preferences.

Revision history for this message
Neal McBurnett (nealmcb) wrote :

What sound card did you have this problem with? Do you mean your "DAC" channel was set to 0 (rather than "DCA")?

Thanks for the tip on alsamixer -c 0 - I also needed to specify -c 0, even though the man page labels that as the default. Seems like a bug.

lspci says I'm using
 00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 03)
which alsamixer calls Card: HDA Intel Chip: Generic 1095 ID 1392
And I'm running gutsy.

But sound is working fine for me.

Merging your troubleshooting ideas with relevant ubuntu documentation, e.g. at help.ubuntu.com, would probably reach a lot more people.

Changed in alsa-driver:
status: New → Incomplete
Revision history for this message
Matthew Craig (matthew-t-craig) wrote :

Additional support information from UBOTU:

If you're having problems with sound, first ensure ALSA is selected, by double clicking on the volume control, then File -> Change Device (ALSA Mixer)

If that fails, see ...
https://help.ubuntu.com/community/Sound
https://help.ubuntu.com/community/SoundTroubleshooting
http://alsa.opensrc.org/index.php?page=DmixPlugin

Revision history for this message
Matthew Craig (matthew-t-craig) wrote :

For fixing your Intel HDA sound this page has useful information
https://help.ubuntu.com/community/HdaIntelSoundHowto

Revision history for this message
Matthew Craig (matthew-t-craig) wrote :

Unofficial word from ALSA is that there will be a tool that queries known sound.states to identify whether sound is muted, in the 8.04 Ubuntu release. If so, this addition will be helpful toward fixing this issue.

Revision history for this message
Connor Imes (ckimes) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Can you try with latest Ubuntu release? Thanks in advance.

Revision history for this message
Connor Imes (ckimes) wrote :

Email from OP:

----
Thank you for taking the time to resolve this bug. I am no longer
using Ubuntu, so I am not able to check if this problem still exists.
Feel free to close this bug, if you feel that action is appropriate.

Regards.
----

I will close this bug.

Changed in alsa-driver:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.