No Sound after resume from suspend to RAM

[Frank616]

I have a 'vanilla' Intel-boarded i3 desktop machine that I use for my media PC. It runs Kubuntu fine, and I love it. However, I've had some problems with the power saving settings. Though I had it all turned off so it would run 24/7 on AC power, it would blank out the video after 10 minutes. I got around that by setting it to suspend to RAM after 3 hours. That works fine too. Whole machine shuts down, fans go off. Super.

However, when I touch the power key to bring it back up again afterward, it comes up, but with no sound. I have to log out and in again to restore that.

What do you need to know about this unit, and where might I start to troubleshoot it?

Thanks.

Frank.

[oshunluvr]

Start by listing your sound card and computer models.

Could be an ACPI problem. You could test this by adding "acpi=off" to your kernel line boot options in grub on the next reboot and see if it goes away.

A possible work-around is to add a sound system re-start to the resume script.

[Frank616]

frank@media:~$ lspci00:00.0 Host bridge: Intel Corporation Ivy Bridge DRAM Controller (rev 09)
00:01.0 PCI bridge: Intel Corporation Ivy Bridge PCI Express Root Port (rev 09)
00:02.0 VGA compatible controller: Intel Corporation Ivy Bridge Graphics Controller (rev 09)
00:14.0 USB controller: Intel Corporation Panther Point USB xHCI Host Controller (rev 04)
00:16.0 Communication controller: Intel Corporation Panther Point MEI Controller #1 (rev 04)
00:16.3 Serial controller: Intel Corporation Panther Point KT Controller (rev 04)
00:19.0 Ethernet controller: Intel Corporation 82579LM Gigabit Network Connection (rev 04)
00:1a.0 USB controller: Intel Corporation Panther Point USB Enhanced Host Controller #2 (rev 04)
00:1b.0 Audio device: Intel Corporation Panther Point High Definition Audio Controller (rev 04)
00:1c.0 PCI bridge: Intel Corporation Panther Point PCI Express Root Port 1 (rev c4)
00:1c.6 PCI bridge: Intel Corporation Panther Point PCI Express Root Port 7 (rev c4)
00:1d.0 USB controller: Intel Corporation Panther Point USB Enhanced Host Controller #1 (rev 04)
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev a4)
00:1f.0 ISA bridge: Intel Corporation Panther Point LPC Controller (rev 04)
00:1f.2 SATA controller: Intel Corporation Panther Point 6 port SATA Controller [AHCI mode] (rev 04)
00:1f.3 SMBus: Intel Corporation Panther Point SMBus Controller (rev 04)
01:00.0 VGA compatible controller: NVIDIA Corporation Device 0f00 (rev a1)
01:00.1 Audio device: NVIDIA Corporation GF108 High Definition Audio Controller (rev a1)
03:00.0 Ethernet controller: Intel Corporation 82574L Gigabit Network Connection
04:00.0 Network controller: Ralink corp. RT3060 Wireless 802.11n 1T/1R
04:03.0 FireWire (IEEE 1394): LSI Corporation FW322/323 (rev 70)
frank@media:~$

Could be an ACPI problem. You could test this by adding "acpi=off" to your kernel line boot options in grub on the next reboot and see if it goes away.

I may have to hook up another monitor for that. This one uses only the flat screen TV for a monitor, and that is connected HDMI. HDMI does not kick in until much of the boot process is over, so I run 'blind' for a fair bit, and I can't access the UEFI boot settings on the HDMI connected TV because of this. That shouldn't stop me from changing the kernel boot settings, but it is a complication in troubleshooting this device.

Frank.

[oshunluvr]

You can always just edit /etc/default/grub and add the acpi=off there and run update-grub. You'll have to reverse this obviously to remove it. The advantage to the command line edit via the grub console is changes aren't set beyond the current boot.

[SteveRiley]

Some interesting stuff here: http://askubuntu.com/questions/21083...spend-in-12-10

I'd be interested in whether the suggestion at the bottom -- write a power-resume script that runs alsa force-reload -- works for you. You could try by manually running

/sbin/alsa force-reload

wakes your sound up. If so, then the script is a viable solution to your problem.

[Frank616]

Steve:

Tried it finally, but no success. Output follows:

frank@media:~$ /sbin/alsa/ force-reload
bash: /sbin/alsa/: Not a directory
frank@media:~$ /sbin/alsa force-reload
mkdir: cannot create directory `/var/run/alsa': Permission denied
/sbin/alsa: Warning: Failed to create /var/run/alsa/. 
/sbin/alsa: Warning: Not keeping list of removed modules because /var/run/alsa is absent.
It will not be possible automatically to reload these modules. 
Unloading ALSA sound driver modules:/sbin/alsa: 135: /sbin/alsa: cannot create /var/run/alsa/modules-removed: Directory nonexistent
 snd-hda-codec-hdmi snd-hda-codec-realtek snd-hda-intel snd-hda-codec snd-hwdep snd-pcm snd-seq-midi snd-rawmidi snd-seq-midi-event snd-seq snd-timer snd-seq-device snd-page-alloc.
mkdir: cannot create directory `/var/run/alsa': Permission denied
Loading ALSA sound driver modules: (none to reload).
frank@media:~$ sudo /sbin/alsa force-reload
[sudo] password for root: 
Unloading ALSA sound driver modules: snd-hda-codec-hdmi snd-hda-codec-realtek snd-hda-intel snd-hda-codec snd-hwdep snd-pcm snd-seq-midi snd-rawmidi snd-seq-midi-event snd-seq snd-timer snd-seq-device snd-page-alloc (failed: modules still loaded: snd-hda-codec-hdmi snd-hda-codec-realtek snd-hda-intel snd-hda-codec snd-hwdep snd-pcm snd-timer snd-page-alloc).
Loading ALSA sound driver modules: snd-hda-codec-hdmi snd-hda-codec-realtek snd-hda-intel snd-hda-codec snd-hwdep snd-pcm snd-seq-midi snd-rawmidi snd-seq-midi-event snd-seq snd-timer snd-seq-device snd-page-alloc.
frank@media:~$

Frank.

[Frank616]

Oshunluvr:

You can always just edit /etc/default/grub and add the acpi=off there and run update-grub.

That stops it from going into suspend to RAM altogether, which also keeps the sound server from getting messed up. Good enough for my needs. This is an AC powered machine anyway, and if it runs 24/7, other than the few watts that it uses, that is fine. Not a total solution, but enough to stop the annoyances.

Thanks.

Frank.