Sound muted, volume 0% after reboot/shutdown

I have the same problem. I upgrade my intrepid distro to jaunty. The volume of ALSA/PCM is mute after any reboot/shutdown.

I have a Core duo 2, 1GB RAM

lspci:
04:01.0 Audio device: VIA Technologies, Inc. VT1708/A [Azalia HDAC] (VIA High Definition Audio Controller) (rev 10)

I solved.

System --> Preferences --> Sound : Assign "PCM" to Level sound of "Alsa Mixer"

Sorry for my english. I'm spanish

Solucionado.

Sistema --> Preferencias --> Sonido: Pestaña dispositivos : Pistas pedeterminadas del mezclador : (Alsa mixer) : Seleccionar "PCM" como pista para manejar con el control del volumen.

Saludos / greetings

2009/5/10, gusvegabol <email address hidden>:
> I solved.
>
> System --> Preferences --> Sound : Assign "PCM" to Level sound of "Alsa
> Mixer"
>
>
> Sorry for my english. I'm spanish
>
> Solucionado.
>
> Sistema --> Preferencias --> Sonido: Pestaña dispositivos : Pistas
> pedeterminadas del mezclador : (Alsa mixer) : Seleccionar "PCM" como
> pista para manejar con el control del volumen.
>
>
> Saludos / greetings
>
> --
> Sound muted, volume 0% after reboot/shutdown
> https://bugs.launchpad.net/bugs/369822
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “pulseaudio” source package in Ubuntu: New
>
> Bug description:
> Binary package hint: pulseaudio
>
> Everytime I boot my PC and log in to gnome, sound is muted and volume is at
> 0%. No matter what status I leave the volume slider at (muted/unmuted, 20%,
> 50%, 100%) it always reappears as muted - 0% upon restart
>
> I'm using jaunty 32-bit final, it is not a clean install but an upgrade over
> an interpid PC that was running just fine.
>
> I have a Core 2 duo processor, 2 GB of ram, and lspci reports:
>
> 00:1b.0 Audio device: Intel Corporation 82801G (ICH7 Family) High Definition
> Audio Controller (rev 01)
>
> doing 'dmesg | grep HDA' only returns
>
> [ 11.081595] HDA Intel 0000:00:1b.0: PCI INT A -> GSI 19 (level, low) ->
> IRQ 19
> [ 11.081651] HDA Intel 0000:00:1b.0: setting latency timer to 64
>
> I'll be glad to help you test/debug the issue, just tell me what info you
> need. Many many thanks in advance
>

--
Enviado desde mi dispositivo móvil

Thanks for the tip, will try that as soon as I get back to my pc.
Gracias por el dato, lo pruebo en un par de horas a ver si funciona.

2009/5/10, gusvegabol <email address hidden>:
> I solved.
>
> System --> Preferences --> Sound : Assign "PCM" to Level sound of "Alsa
> Mixer"
>
>
> Sorry for my english. I'm spanish
>
> Solucionado.
>
> Sistema --> Preferencias --> Sonido: Pestaña dispositivos : Pistas
> pedeterminadas del mezclador : (Alsa mixer) : Seleccionar "PCM" como
> pista para manejar con el control del volumen.
>
>
> Saludos / greetings
>
> --
> Sound muted, volume 0% after reboot/shutdown
> https://bugs.launchpad.net/bugs/369822
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “pulseaudio” source package in Ubuntu: New
>
> Bug description:
> Binary package hint: pulseaudio
>
> Everytime I boot my PC and log in to gnome, sound is muted and volume is at
> 0%. No matter what status I leave the volume slider at (muted/unmuted, 20%,
> 50%, 100%) it always reappears as muted - 0% upon restart
>
> I'm using jaunty 32-bit final, it is not a clean install but an upgrade over
> an interpid PC that was running just fine.
>
> I have a Core 2 duo processor, 2 GB of ram, and lspci reports:
>
> 00:1b.0 Audio device: Intel Corporation 82801G (ICH7 Family) High Definition
> Audio Controller (rev 01)
>
> doing 'dmesg | grep HDA' only returns
>
> [ 11.081595] HDA Intel 0000:00:1b.0: PCI INT A -> GSI 19 (level, low) ->
> IRQ 19
> [ 11.081651] HDA Intel 0000:00:1b.0: setting latency timer to 64
>
> I'll be glad to help you test/debug the issue, just tell me what info you
> need. Many many thanks in advance
>

--
Enviado desde mi dispositivo móvil

I believe I'm encountering the same bug. I'm running jaunty on x64.

When I cold boot my computer and the gdm login screen comes up, I get the ubuntu bongo sound through the speakers. Then I log in to a Gnome session, and during the login process, I hear the speakers making a "chk" sound. After I've finished logging in, the mixer applet shows that the master playback is muted, and the volume is down at 1/31. If I unmute it and raise the volume, I get sound. However, the next time I log in the same thing happens.

The problem seems to be that the mixer applet and gnome volume control have a fixed idea that I want my sound turned off all the time. The way I can tell is by doing the following:

amixer -- set Master playback 100% unmute
amixer contents | head
gnome-volume-control
amixer contents | head

The first line of code unmutes sound, and I can verify that sound actually does work, both by playing sound through the speakers and by using the second line to view the current settings in ALSA's mixer. The third line starts up Gnome Volume Control. As soon as Gnome Volume Control starts up, I hear a "chk" from the speakers, and in the GUI, my master volume is muted again. After I exit Gnome Volume Control, the final line of code verifies that ALSA's mixer knows its volume levels have been modified.

Supporting this interpretation that it's a problem with the mixer applet and gnome volume control, I find the following. I log in to a different window manager (fluxbox) instead of Gnome, and I use amixer to turn on sound. If then reboot and log back in to a fluxbox session, I have sound. However, if I log into a Gnome session (which has the side-effect of launching mixer_applet2), sound becomes muted.

Same bug here. The suggestion of gusvegabol does not solve the problem. As stated by bcrowell, it probably has to do with the mixer applet.

I believe I have exactly the same bug. I'm running Jaunty and my card is -> "| Card: HDA Intel | Chip\codec: Realtek ALC880". But my problem appeared only after I had to remove, purge & reinstall GDM. So it is something to do with gnome panel (99% sure). Anyway it's nothing major, I just made a habit to unmute master volume, first thing after every booting & learn not to expect drums at booting.

A very, very similar bug (bug 449783) has been reported for [Karmic].

This bug was fixed in the package pulseaudio - 1:0.9.22~0.9.21+341-g62bf-0ubuntu1

---------------
pulseaudio (1:0.9.22~0.9.21+341-g62bf-0ubuntu1) lucid; urgency=low

  * New snapshot based on stable-queue git branch (testing requested
    specifically by upstream)
    - LP: #164745, #173212, #201391, #204536, #207796, #210016, #221038,
    - LP: #226342, #230408, #236423, #237443, #250059, #269585, #274304,
    - LP: #274577, #275474, #277532, #277566, #277932, #278025, #280534,
    - LP: #283049, #286816, #287036, #292732, #298011, #298301, #300290,
    - LP: #302038, #311497, #311853, #324062, #339448, #344057, #348979,
    - LP: #350829, #356206, #367379, #367544, #369822, #371897, #374846,
    - LP: #375570, #381801, #399515, #402950, #403786, #408169, #409322,
    - LP: #409723, #410326, #410446, #417695, #417976, #419271, #421072,
    - LP: #422774, #423979, #424655, #425028, #427016, #431072, #432660,
    - LP: #437640, #437996, #442191, #443306, #443389, #446719, #449762,
    - LP: #455417, #461532, #464652, #483191, #497537, #503780
  * debian/patches/:
    + add: 0099-change-configure-git-version-tag.patch: Match released
           upstream 0.9.21 for shlibs and LIBPULSE_VERSION_INFO
    - drop: 0004-set-tsched0.patch (no longer relevant)
            0050-revert-pacmd-poll-argv.patch (no longer relevant)
            0056-dont-bail-on-sound-class-modem.patch (merged)
            0056-ignore-sound-class-modem.patch (merged)
            0058-Backport-4c793.patch (merged)
            0059-Backport-978d3.patch (merged)
            0060-fix-implicit-func-decl-cpu-arm.patch (merged)
            0061-Backport-c5fdb.patch (merged)
            0070-dont-bail-on-sound-class-modem-devs.patch (merged)
    + refresh: 0001-change-resample-and-buffering.patch
               0090-disable-flat-volumes.patch
               0091-dont-load-cork-music-on-phone.patch
               0057-load-module-x11-bell.patch
 -- Daniel T Chen <email address hidden> Thu, 14 Jan 2010 20:33:05 -0500

its not still fixed i have latest updates in xubuntu
on restart shutdown hibernate volume auto mutes.

What is your mixer state at the display manager /before/ logging in? You can switch to a terminal (e.g., tty1), log in, and dump the state via amixer > state.txt

same problem now on maverick (gnome, i386)

each time i start my system, i need to unmute sound (system pref sound), so this setting is reset on every boot (mute)

I had the same problem here after upgrade from Kubuntu Lucid Lynx to Kubuntu Maverick Meerkat. I found out that the problem was in the "~/.kde/share/config/kmixctrlrc" file. I simply deleted this file and everything was back to normality...

gone too on my end, so change it back to Fix released as previously done