I'm not sure if it is the same bug. I'm still experiencing with the latest
updates in Intrepid. By the way, this fix works for me as well. I can't help
with a script, though.

On Wed, Mar 4, 2009 at 7:09 AM, hyperair <email address hidden> wrote:

> *** This bug is a duplicate of bug 202089 ***
>    https://bugs.launchpad.net/bugs/202089
>
> On Wed, 2009-03-04 at 14:41 +0000, Liuskur wrote:
> > *** This bug is a duplicate of bug 202089 ***
> >     https://bugs.launchpad.net/bugs/202089
> >
> > I am experiencing the same problems and I have a notebook with Intel
> HDA883 sound.
> > I have fresh installed ubuntu 8.04 LTS.
> > I tested my system for hours and finally found a solution that works for
> me without totally rebooting.
> > sudo alsa force-reload
> > pulseaudio -D
> >
> > these are the only lines necessary for me, anyone with the same problem
> may also try:
> > sudo /etc/init.d/alsa-utils stop
> > sudo alsa force-reload
> > sudo /etc/init.d/alsa-utils start
> > pulseaudio -k
> > pulseaudio -D
> >
> > WHAT ABOUT MAKING IT TO A SCRIPT!!
> > There is one problem for me, why i cant just write it to a file and let
> ubuntu load it every time it resumes.
> > The problem is:
> > when alsa force-reload is executed the volume control crashes and it asks
> you to not to reload or to reload.
> > this must be answered before pulseaudio -D is typed in.
> > So if it all is in script, then the script runs all those
> commands(including pulseaudio -D) in row and the volume control prompt is
> left on your desktop.
> >
> > So for a script it is necessary to close the volume-control before alsa
> > force-reload and then start the volume control again.
> >
> > I DO NOT KNOW THE NEEDED COMMANDS FOR THAT please help!
> >
> This bug is fixed in Intrepid. See Bug #202089 and please do not post on
> duplicate bugs.
> --
> Chow Loong Jin
>
> --
> No sound after suspend to RAM
> https://bugs.launchpad.net/bugs/222428
> You received this bug notification because you are a direct subscriber
> of the bug (via bug 202089).
>
> Status in “pulseaudio” source package in Ubuntu: Confirmed
>
> Bug description:
> Problem description: when recovering from suspend to RAM there is no sound.
> Sound is working fine the rest of the time, closing the session does not
> restore sound but a reboot does.
>
> 1) Ubuntu version: Hardy Heron upgraded from Gutsy, default configuration;
> output of uname -r: 2.6.24-16-generic
>
> 2) Output of aplay -l
> **** Liste des PLAYBACK périphériques ****
> carte  0: VT82xx [HDA VIA VT82xx], périphérique 0 : ALC883 Analog [ALC883
> Analog]
>  Sous-périphériques: 1/1
>  Sous-périphérique: #0: subdevice #0
> carte  0: VT82xx [HDA VIA VT82xx], périphérique 1 : ALC883 Digital [ALC883
> Digital]
>  Sous-périphériques: 1/1
>  Sous-périphérique: #0: subdevice #0
>
> 3) lspci -v
>  04:01.0 Audio device: VIA Technologies, Inc. VIA High Definition Audio
> Controller (rev 10)
>        Subsystem: Europop AG Unknown device e028
>        Flags: bus master, fast devsel, latency 0, IRQ 23
>        Memory at dfafc000 (64-bit, non-prefetchable) [size=16K]
>        Capabilities: <access denied>
>
> 4) sudo modprobe snd-via82xx
> Display nothing but still no sound
>
> 5) cat /proc/asound/cards
>  0 [VT82xx         ]: HDA-Intel - HDA VIA VT82xx
>                      HDA VIA VT82xx at 0xdfafc000 irq 23
>
> 6) Restarting ALSA (sudo /etc/init.d/alsa-utils start ) doesn't change the
> issue
>
> 7) Stopping (pulseaudio -k) and relaunch pulseaudio (pulseaudio -D) doesn't
> help either
>
> 8) uname -a
> Linux  2.6.24-16-generic #1 SMP  i686 GNU/Linux
>
> 9) dpkg -s linux-ubuntu-modules-$(uname -r)
> Package: linux-ubuntu-modules-2.6.24-16-generic
> Status: install ok installed
> Priority: optional
> Section: base
> Installed-Size: 15420
> Maintainer: Ubuntu Kernel Team <email address hidden>
> Architecture: i386
> Source: linux-ubuntu-modules-2.6.24
> Version: 2.6.24-16.23
> Provides: ndiswrapper-modules-1.9
> Depends: linux-image-2.6.24-16-generic
> Pre-Depends: dpkg (>= 1.10.24)
>
> I don't know what I can test in addition of this., I tried to follow
> troubleshooting procedure.
> If more information is needed please don't hesitate to contact me.
>
> Thanks for your help,
> Yann
>