no sound HDA-intel AD1984

Bug #288861 reported by Elias K Gardner
This bug report is a duplicate of:  Bug #288039: pulseaudio upgrade breaks sound. Edit Remove
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
New
Undecided
Unassigned
pulseaudio (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

This is a new problem that occured over the last few days in intrepid today being the 24th oct 08. My sound is usually muted so I cannot narrow it down more. I have no sound whatsoever. Built in speaker is fine I have sound in XP.

I ran an also script I ran an automatic sound information collection scrip found at https://wiki.ubuntu.com/DebuggingSoundProblems the info can be found here http://www.alsa-project.org/db/?f=fec33adab69327b84e10ec8ba472c384db7661fa

Revision history for this message
Elias K Gardner (zorkerz) wrote :
Revision history for this message
Elias K Gardner (zorkerz) wrote :
Revision history for this message
Elias K Gardner (zorkerz) wrote :
Revision history for this message
Elias K Gardner (zorkerz) wrote :

hmm could not figure out how to attach all of these in one post.

Revision history for this message
Elias K Gardner (zorkerz) wrote :

Problem solved due to post #9 on http://ubuntuforums.org/showthread.php?t=942529&highlight=sound

Here is the issue. PCM volume was set to 0 in alsamixer, however, running alsamixer as recommended in the terminal only brings up the the master volume. If you instead run 'alsamixer -Dhw' in a terminal it brings up the master volume plus all the others. Here it is now possible to see that PCM was muted and set it higher.

So the bug here is that PCM volume was inexplicably muted on some intrepid update.

I am also unsure as to why -Dhw is now required when the alsamixer command alone used to suffice.

I can file a new bug about this if it is helpful let me know. For now I will mark the package as alsa if that is wrong please correct me.

Revision history for this message
Erik Reuter (misc71) wrote :

After the recent pulseaudio update, my snd_hda_intel sound also stopped working -- just a low crackling sound.

I tried the alsamixer -Dhw trick, and sure enough, PCM volume was at 0. I turned PCM volume up to max and now my sound plays normally again.

However, I think the PCM volume 0 is just one symptom of the problem. When I shutdown or restart my computer, it always hangs during the "Shutting down ALSA...." process. So, my sound is working now, but there is still a problem related to ALSA and/or pulseaudio.

Revision history for this message
Erik Reuter (misc71) wrote :

Also see these similar bugs:

#288652
#288093
#288039
#286966
#286430
#285965

Revision history for this message
cato (catonano) wrote :

Erik,

thank you SO MUCH ! I've been struggling fr days with this !

I can't believe that was so stupid !

There are LOTS of duplicate bugs, why no one says something ?

My bug was certainly a duplicate of this one and I'm going to signal that.

Thanks again
Bye
Catonano

Revision history for this message
cato (catonano) wrote :

It's confirmed. The simptom is there and I could remove it thanks to the Erik's indication.

Changed in pulseaudio:
status: New → Confirmed
Revision history for this message
Tormod Volden (tormodvolden) wrote :

When listing bugs, please write them like this, so they get linkified: Bug #288652, bug #288093, bug #288039, bug #286966, bug #286430, bug #285965.

Revision history for this message
goto (gotolaunchpad) wrote :

Why is PCM volume set to 0 and is there anything happening to prevent pulseaudio from doing so with an update? Any information needed? Thanks!

Revision history for this message
cato (catonano) wrote : Re: [Bug 288861] Re: no sound HDA-intel AD1984

I'm not sure I understand the question.

   1. I don't know why the PCM volume is set to 0
   2. I guess there must be something that prevents pulseaudio from doing
   so, but I'm not able to help, I was hoping some developer could know better
   than me.
   3. Why do you ask wether any information is needed ? Are you asking to me
   ? I don't need any further information ? Anyone else needs further
   information ?

Also I don't understand clearly who you are: are you a developer and are you
asking for more info ? Or are you a user and trying to help with this bug ?

Thanks
Bye
Cato

2008/11/28 bugmenot <email address hidden>

> Why is PCM volume set to 0 and is there anything happening to prevent
> pulseaudio from doing so with an update? Any information needed? Thanks!
>
> --
> no sound HDA-intel AD1984
> https://bugs.launchpad.net/bugs/288861
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in "pulseaudio" source package in Ubuntu: Confirmed
>
> Bug description:
> This is a new problem that occured over the last few days in intrepid today
> being the 24th oct 08. My sound is usually muted so I cannot narrow it down
> more. I have no sound whatsoever. Built in speaker is fine I have sound in
> XP.
>
> I ran an also script I ran an automatic sound information collection scrip
> found at https://wiki.ubuntu.com/DebuggingSoundProblems the info can be
> found here
> http://www.alsa-project.org/db/?f=fec33adab69327b84e10ec8ba472c384db7661fa
>

--
La difesa più sicura contro il male è l'estremo individualismo,
l'originalità di pensiero, la stravaganza, perfino, se volete,
l'eccentricità… Il male va matto per la solidarietà.

Less than one di Joseph Brodsky

Revision history for this message
goto (gotolaunchpad) wrote :

Sorry for the confusion (I did not want to speak to you directly):
I am a normal user and want to help. I asked in general if anyone needs more information because I want to help.
On my computer PCM was set to 0 after a pulseaudio update, so I just wanted to know if anyone is working on this at the moment, so that this problem gets fixed.

Revision history for this message
goto (gotolaunchpad) wrote :

I think this particular bug has already been reported and is a duplicate of bug 288039, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.

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.