Dell Inspiron 7537 - Sound only works after resuming from suspend

Hello,
So my sound does not work after boot, only once I resume from suspend. So, once I turn on my computer, and I load sound, nothing work (everything is unmuted in Alsa) - then if I suspend my computer and resume - the sound works every time.
I use Alsa and here is my amixer output (before and after suspend is the same) :
eric@archlinux ~> amixer
Simple mixer control 'Master',0
Capabilities: pvolume pswitch pswitch-joined
Playback channels: Front Left - Front Right
Limits: Playback 0 - 65536
Mono:
Front Left: Playback 5358 [8%] [off]
Front Right: Playback 5358 [8%] [off]
Simple mixer control 'Capture',0
Capabilities: cvolume cswitch cswitch-joined
Capture channels: Front Left - Front Right
Limits: Capture 0 - 65536
Front Left: Capture 11003 [17%] [on]
Front Right: Capture 11003 [17%] [on]
What gets rebooted when I do a suspend, but not when I reboot? Does not seem to make sense to me.
Thanks.

Is there any additional information I can include to help figure this out?

Similar Messages

No sound in Flash after resuming from suspend

After I resume from a suspend or sleep there is no sound in Flash and there is no networking.
The only way is to restart my browser to reestablish the sound.
Is there a solution for this problem?
Thanks.

This does not happen with Firefox in Ubuntu, as an example. So something must be wrong somewhere.
I can confirm this happens to me in Arch with Firefox 4.0b7 and Chromium 7.0.517.44. I noticed that after resuming from suspend, not only sound (in Flash) is missing, but Flash is behaving weirdly (YouTube video plays much faster) and CPU usage goes crazy without doing any particular action.
Last edited by Niavlys (2010-12-05 23:34:30)

Touchpad permanently not working after resuming from suspend

I lost touchpad and trackpoint functionality after resuming from suspend on my ThinkPad E530 (3259CTO).
Even after a complete power off (with the battery removed), the touchpad is detected but doesn't send any event, and the trackpoint is not detected.
In Windows, in the UltraNav control panel, the touchpad is marked as enabled and cannot be disabled, the trackpoint is grayed.
In Linux, I can see the difference is kernel traces when the driver is loaded.
Before : psmouse serio1: synaptics: Touchpad model: 1, fw: 8.0, id: 0x1e2b1, caps: 0xd001a3/0x940300/0x120c00
Now : psmouse serio1: synaptics: Touchpad model: 1, fw: 8.0, id: 0x1e2b1, caps: 0xd001a3/0x0/0x0
After looking at https://gerrit.chromium.org/gerrit/#/c/31105/ and Synaptics public documentation, I was able to get more information : the device status register (F01_RMI_Data0) is 0x45, which means the touchpad is in flash programming mode since there is a firmware CRC failure.
It looks like http://code.google.com/p/chromium-os/issues/detail?id=24298, so it's probably not a Lenovo specific problem, but a bug in Synaptics firmware.
Can Lenovo provide the firmware to flash like http://forums.lenovo.com/t5/X-Series-ThinkPad-Laptops/X220-Touchpad-jumpy-response-when-used-with-90... which would hopefully make my touchpad working again ?
The original firmware should work, but an updated one would be better, if it avoids losing the touchpad again later.

I don't know why, but this made me think of the episode of the simpsons when home tries to get over 300 pounds so he can work from home. When he tries to dial the phone he hist all the buttons and gets a recording that says "We're sorry, you're fingers are too fat. To obtain a special dialing wand, please mash the keypad now."
BTW, sorry I can't help... but at least I am entertained easily.

No sound in flash after resume from suspend (linux debian)

Using 10.0.r42, iceweael and linux 2.6.32 kernel.
If I close the lid on my HP laptop which causes it to suspend, and the resume from suspend, other audio playing programs work, but I cant get any sound from iceweasel/flash until I kill all instances of iceweasel and restart the web browser.
Is this a bug that is tied to flash?

What a coincidence, mine is also from scratch.
Good question about how sound is handled. ldd libflashplayer.so doen't give an answer.
So somehow xulrunner can catch the sound.
Libxpcom is linked to libasound. components/libmozgnome.so to libesd in my case.
Maybe you can try fuser /dev/snd/* to identify which process is locking the device.

[SOLVED] Sound (snd_hda_intel) not working after resume from suspend

Using the latest kernel 2.6.30.4, On HP2133, whenever I get back from resume, sound is not working.
Running the following brings back the sound, but that is obviously a hack:
fuser -k /dev/snd/*
rmmod snd_hda_intel
modprobe snd_hda_intel
/etc/rc.d/alsa start
I have on my /etc/modprobe/50-sound.conf:
options snd-hda-intel model=laptop
alias snd-card-0 snd-hda-intel
alias sound-slot-0 snd-hda-intel
Here's the exact hardware specification:
# lspci -nnv|grep Audio
80:01.0 Audio device [0403]: VIA Technologies, Inc. VT1708/A [Azalia HDAC] (VIA High Definition Audio Controller) [1106:3288] (rev 10)
Any idea where to look for this?
Last edited by yhager (2009-08-21 16:54:00)

[SOLVED]
I downgraded to kernel 2.6.29 and the problem is gone.
Note: I also had X VT problems with 2.6.30.4 (xf86OpenConsole: VT_WAITACTIVE failed: Interrupted system call). Those were solved too by downgrading to 2.6.29.

Sound not working after resuming on maverik

Sound stops working after resuming my Mbp. Reseting PRam solves this issue but its tempory. I have to restart my system everytime this issue occurs.
I have one more issue regarding sound, which might be just another bug.
When I plug my headphone, sound doesnt switch to head phone and I cant switch manually too from system preferences. To fix this issue, I have to close the lid and wait for a while for system to sleep and resume system. after resuming, Os starts detecting my headphone. strange!

For those of you reading this just thought that I would update you. After spending 90 minutes on the phone and resetting/restoring the phone twice, with two different level of tech support they have deemed this a hardware issue now. This phone worked perfectly fine before the ios 6.1.2 update that was done yesterday. Worked fine, played music, took calls, did all the sounds, then updated and now nothing!
Our family has 4 iphones, several ipods and 2 ipads. I am now left with a phone just out of warranty (by 2 mo) and no choice but to pay the $200 to apple to get another phone. Apparently this is a steal because a new 4s costs $600.! lol. I am greatly disappointed. I have been given the corporate phone number and assured that there would be someone in customer service to talk to, but there was not, no surprise to me. Anyone else have any suggestions?

System freeze after resume from suspend

I am running arch for about 5 month now and I always had freezes after resuming from suspend (to ram - systemctl suspend) every once in a while (like once a week or less). The freezes increased massively over the last month or so and for about 2 weeks now it happens 95% of the times I resume from suspend.
The monitor turns on and shows things exactly how I left them, but is completely unresponsible EXCEPT for I can switch to another TTY (Ctrl+Shift+F*), however I cannot type or do anything in it...
It doesnt have anything to do with the X server as it also happens after I suspend from TTY (without any X running).
I also checked journalctl -b -1 (shows previous boot, since I always have to hard-reset the system) but it doesnt show anything after:
Mar 13 17:16:54 Ununhaswellium systemd-sleep[3624]: Suspending system...
(the suspend event before resuming)
Are there any log files that could give a hint on what exactly goes on after the resume?
Im running the latest official 3.13.6-1 kernel and updated my BIOS to the latest beta version yesterday - didnt help either...
Ive read pretty much every thread on the internet by now about freezes after resume from suspend but none really helped
Last edited by CharlieBra7o (2014-03-15 09:58:51)

Thank you for the link, unfortunally I don't have a NVIDIA card but use the Intel IGP (HD4600, Haswell) - maybe I should have mentioned that...
And other than in this bug report I cannot kill X or anything because neither other TTYs work - I cannot input anything (although the hotkeys work weird enough) nor is SSHD running because the system is completely frozen...
Very funny thing is that for the last 2 days my system didnt freeze once (suspended about 6-7 times during one boot), even though for the 2 weeks prior to that, it froze EVERY SINGLE TIME I resumed from suspend, it didnt work once...

USB ports don't work after resuming from standby with Windows 8 on X230 tablet

I have just done a clean install of Windows 8 on my X230 tablet. Before installing Windows 8 I installed the most recent BIOS for this machine (version 2.50). After installing Windows 8 I installed System Update from the Lenovo Website and downloaded all the recommended drivers and other files. I've also installed all the latest Windows 8 updates.
Here are the symptoms of my problem: After resuming from standby/sleep mode, my USB ports do not work. My computer has two USB 3.0 ports and one USB 2.0 ports. All exhibit the same behavior. After resuming from standby mode I have tried inserting both my mouse and a USB thumbdrive, but neither are recognized. After restarting Windows, the USB ports work again... until I resume from standby mode again.
I hope there is a solution to this issue. It is very frustrating.

Thanks for the suggestion about tweaking the "Allow this computer to turn off this device" feature. I un-checked that box for every entry I could find under "Universal Serial Bus Controllers" in the Devide Manager. Unfortunately, the same symptoms of my problem persisted.
I went back and looked at the README file associated with the BIOS 2.50 download on Lenvo's support site. At the bottom of the file it gives a "Summary of Changes". Under version 2.03 of the BIOS (the version just before version 2.50), it says:
- (Fix) Fixed an issue where USB device might not detected when system resume from sleep mode.
This indicates that Lenovo support was already aware of such issues. The problem was intended to be fixed in version 2.03 of the BIOS. However, the issue persists on my machine, even with the latest BIOS.
Hopefully someone from Lenovo can comment here.

System freeze after resume from suspend to RAM

Hi,
since quite a while (probably ever) I am unable to suspend my computer to RAM because everytime it freezes a few seconds after resuming, never to become alive again until a reboot. After some investigation, I managed to get kernel logs by taking a picture of my screen. The logs were not written to disk, hence I didn't see anything before. I had to write these by hand, I hope I didn't insert any mistakes:
kernel: sas: Enter sas_scsi_recover_host busy: 2 failed: 2
kernel: sas: trying to find task 0xfff880008b5b680
kernel: sas: sas_scsi_find_task: aborting task 0xfff880008b5b680
kernel: sas: sas_scsi_find_task: task 0xfff880008b5b680 is aborted
kernel: sas: sas_eh_handle_sas_errors: task 0xfff880008b5b680 is aborted
kernel: sas: trying to find task 0xffff8804606ccb40
kernel: sas: sas_scsi_find_task: aborting task 0xffff8804606ccb40
kernel: sas: sas_scsi_find_task: task 0xffff8804606ccb40 is aborted
kernel: sas: sas_eh_handle_sas_errors: task 0xffff8804606ccb40 is aborted
kernel: sas: ata7: end_device-0:0: cmd error handler
kernel: sas: ata8: end_device-0:1: cmd error handler
kernel: sas: ata7: end_device-0:0: dev error handler
kernel: ata7.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
kernel: ata7.00: failed command: READ VERIFY SECTOR(S)
kernel: ata7.00: cmd 40/00:01:00:00:00/00:00:00:00:00/e0 tag 11
res 40/00:48:a0:79:88/00:00:07:00:00/40 Emask 0x4 (timeout)
kernel: ata7.00: status { DRDY }
kernel: ata7: hard resetting link
kernel: sas: ata8: end_device-0:1: dev error handler
kernel: ata8.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
kernel: ata8.00: failed command: READ VERIFY SECTOR(S)
kernel: ata8.00: cmd 40/00:01:00:00:00/00:00:00:00:00/e0 tag 11
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
kernel: ata8.00: status { DRDY }
kernel: ata8: hard resetting link
This issue seems to be related to disk failures like bad sectors but I am quite sure, that my SSDs are in a good shape. I ran some SMART tests, they all turned out to be okay. Suspending from my dual-booted Windows works fine as well (although if the bad sector would be on the linux partition, it would probably not affect Windows).
Here's my setup:
$ lsblk -St
NAME HCTL TYPE VENDOR MODEL REV TRAN NAME ALIGNMENT MIN-IO OPT-IO PHY-SEC LOG-SEC ROTA SCHED RQ-SIZE RA WSAME
sda 1:0:0:0 disk ATA Corsair Force 3 2 sata sda 0 512 0 512 512 0 cfq 128 128 0B
sdb 7:0:0:0 disk ST1000DM 003-9YN162 NDP3 usb sdb 0 512 0 512 512 1 cfq 128 128 0B
sdc 0:0:0:0 disk ATA OCZ-REVODRIVE3 2.25 sas sdc 0 512 0 512 512 0 cfq 128 128 0B
sdd 0:0:1:0 disk ATA OCZ-REVODRIVE3 2.25 sas sdd 0 512 0 512 512 0 cfq 128 128 0B
sr0 2:0:0:0 rom TSSTcorp CDDVDW SH-222AL SB00 sata sr0 0 512 0 512 512 1 cfq 128 128 0B
$ lsblk -f
NAME FSTYPE LABEL UUID MOUNTPOINT
sda
├─sda1 ntfs Recovery 567437B974379B27
├─sda2 vfat DC2D-099E /boot
├─sda3
├─sda4 ntfs FEBED982BED933BD
├─sda5 ext4 arch 41bad924-84a2-4e0a-9cd4-4ea723a2a5a3 /
└─sda6 swap 793fb3c1-8bec-4023-a7c3-ee94eee2e67a [SWAP]
sdb
└─sdb1 ntfs HDDRIVE2GO 2212E50812E4E231
sdc
└─sdc1 linux_raid_member home:0 208937dc-2904-e71c-435a-9928671e07a3
└─md0 ext4 revodrive ffe9d38f-87f2-44e1-ae26-f36c910af3c5 /home
sdd
└─sdd1 linux_raid_member home:0 208937dc-2904-e71c-435a-9928671e07a3
└─md0 ext4 revodrive ffe9d38f-87f2-44e1-ae26-f36c910af3c5 /home
I am not sure which one of the disks causes the freeze but I assume it's the revodrive because the logs talk about two drives. The Revodrive internally holds two drives, which are set up to operate in a RAID 0. Windows is installed on the Corsair drive, and has no access to the Revodrive. However, I used to run Windows on the Revodrive a few years ago, and it worked just fine.
Another interesting thing is that when I try to test suspend to RAM, the system does not freeze, nor produce errors. This only happens if none is written to /sys/power/pm_test (which means no automated wake-up, no testing).
Any ideas on how I could narrow down this issue? Thanks a lot!
EDIT
I just checked and confirmed that this issue is originating from the OCZ Revodrive:
$ dmesg | grep ata7.00 | head
[ 7.136432] ata7.00: ATA-8: OCZ-REVODRIVE3, 2.25, max UDMA/133
[ 7.136436] ata7.00: 234441648 sectors, multi 16: LBA48 NCQ (depth 31/32)
[ 7.146442] ata7.00: configured for UDMA/133
$ dmesg | grep ata8.00 | head
[ 7.310018] ata8.00: ATA-8: OCZ-REVODRIVE3, 2.25, max UDMA/133
[ 7.310023] ata8.00: 234441648 sectors, multi 16: LBA48 NCQ (depth 31/32)
[ 7.320022] ata8.00: configured for UDMA/133
Last edited by tuttiarch (2015-01-31 15:54:29)

Thank you for the link, unfortunally I don't have a NVIDIA card but use the Intel IGP (HD4600, Haswell) - maybe I should have mentioned that...
And other than in this bug report I cannot kill X or anything because neither other TTYs work - I cannot input anything (although the hotkeys work weird enough) nor is SSHD running because the system is completely frozen...
Very funny thing is that for the last 2 days my system didnt freeze once (suspended about 6-7 times during one boot), even though for the 2 weeks prior to that, it froze EVERY SINGLE TIME I resumed from suspend, it didnt work once...

Cannot connect to X server after resume from suspend

Hello,
i'm a happy user of arch and i3, one and only thing that is not working correctly is that sometimes after resume from sleep (closing the lid, and then opening) I am not able to start any programs. this happens about 50% of the time. when it happens i have to exit i3 and login again, and everything works ok then.
I'd be grateful for any suggestion how can I debug and solve this problem.
y
Last edited by yemu (2014-04-09 08:53:12)

the error was, after running xterm:
No protocol specified
xterm: Xt error: Can't open display: :0.0
after running scrot
No protocol specified
giblib error: Can't open X display. It *is* running, yeah?
after running firefox
(process:2559): GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size == 0' failed
No protocol specified
No protocol specified
Error: cannot open display: :0.0
but I think I was able to fix the problem.
when I was browsing the internet for solution, I stumbled upon an info about similar problem caused by the hostname set to localhost. I checked my system, and apparently I haven't set my host name during install, and it was still localhost, so I changed it. and after that I tried suspending several times, and the problem never occured. I'll test in upcoming days, and if it works I will change the thread title to [SOLVED].
Last edited by yemu (2014-04-10 07:40:47)

Desktop visible after resume (from suspend) and before screen is locke

My desktop becomes visible for brief period (<1s) when the system resumes from suspended state. My desktop env. is XFCE4, it happens with both xscreensaver and gnome-screensaver (also with slimlock and i3lock), therefore I think it's not locker dependent. It's a major security flaw because sensitive information may be exposed (not just porn). Using both XFCE provided locking facilities (suspend/resume lock options in Power Manager and Session settings), and systemd suspend/resume hooks yields same result. I remember back then when I was using Gnome, I haven't had this issues. Does anyone have any idea how to prevent this desktop expose?

Have you tried this --> https://wiki.archlinux.org/index.php/Pm … or_suspend ?

Dell Inspiron 3420 microphone not working after update

I got myself a Dell Inspiron 3420 laptop, mostly because of the Dell's exceptional Linux support (it came with Ubuntu preinstalled, but I ran it over with Arch right away). Anyway, I've set up my system, installed GNOME, everything worked like a charm. And then this update came and internal mic ain't working. I'm using pulseaudio, and in pavucontrol when I head over to Input Devices card, I can see the entry, I can toggle the slider, but it's not working. I tried with alsamixer as well, but without success.
FTR, external mic is not working as well... when I plug it in, nothing happens. He's dead Jim, he's dead...
Ideas?
Last edited by mandalic (2013-03-25 15:06:57)

I am having the same problem . Siri is working fine , voice record not working... And people can only hear me if I talk with the speaker phone on . This is definitely a software issue because I replaced the mic and thunderbolt ,, still having the same problem

[Solved] No sound after resuming from suspend

After suspending and resuming I no longer have any sound output (through headphone jack or my laptop speaker). The laptop is a toshiba portege r835. I can't say how long this has been happening, since I've only tried to play any sounds after resuming recently.
Searching the forums I found the following thread: https://bbs.archlinux.org/viewtopic.php?id=151001
I haven't tried this because it isn't exactly the same problem, but mostly because I'm currently stuck on kernel 3.5.6 because of the sandy bridge power regression issues.
Does anyone have any other ideas on how to possibly fix this problem?
Thanks!!
Last edited by twistedcubic (2012-12-31 22:20:20)

Solved, sort of.
I had some double suspend issue: I had set up suspend with systemd before using xfce and then after installing xfce I set my power settings so that the computer would suspend after shutting the lid, so I would have to open the lid, shut it, and then open it again for the computer to actually resume. After turning off the suspend setting in the xfce power manager, and just using the systemd suspend, the sound works fine on resume (both headphones and speakers)!

[SOLVED]No sound after resuming from suspend thinkpad t23

On a T23 Thinkpad, suspend-to-ram works, but I have no sound and no network when resuming.
After googling for a while, it seems I must unload sound modules before going to sleep and then reload my sound modules after resuming.
lsmod|grep snd gives me this:
snd_intel8x0 28700 3
snd_ac97_codec 94756 1 snd_intel8x0
snd_pcm_oss 38432 0
snd_pcm 68996 3 snd_intel8x0,snd_ac97_codec,snd_pcm_oss
snd_timer 19332 1 snd_pcm
snd_page_alloc 8072 2 snd_intel8x0,snd_pcm
snd_mixer_oss 14464 1 snd_pcm_oss
snd 44388 12 snd_intel8x0,snd_ac97_codec,snd_pcm_oss,snd_pcm,snd_timer,snd_mixer_oss
soundcore 6496 1 snd
ac97_bus 2432 1 snd_ac97_codec
However, from the command line, after
modprobe -r snd_seq_oss snd_seq snd_seq_device snd_intel8x0 snd_ac97_codec snd_pcm_oss snd_pcm snd_timer snd_mixer_oss
I get:
FATAL: Module snd_intel8x0 is in use.
Even though I have no sound apps running.
I am planning on putting the modprobe -r command in /etc/pm/sleep.d/whatever to unload and then another to reload the mods.
Any help appreciated.
Last edited by Misfit138 (2008-01-07 02:27:07)

OK, solved it. Placed this in /etc/pm/sleep.d/11suspend
#!/bin/sh
mixers="Master PCM CD"
for mixer in $mixers ; do
/usr/bin/amixer -q sset $mixer mute
/usr/bin/amixer -q sset $mixer unmute
done
Just mutes and unmutes master, PCM and cd channels. Works perfectly. suspend-to-ram and hibernate now work 100%.
Thinkpads are so sweet.

USB Mouse / Keyboard doesn't work after resuming from hibernate

I am using a USB device that splits out to 2 PS2 ports, one for a mouse, one for a keyboard. It works great, but when I put my X61 into hibernate, the mouse and keyboard do not work when I resume from hibernate.
I installed all the relevant patches and power manager drivers from the driver downloads page, but my mouse still doesn't work.
Can someone point me to the correct download or shed some light on this?
Thank you!

I have this same problem with this same device. It is a "composite USB device".
What I've notice is that the problem happens mostly with USB 1.1 ports. When the device is connected to a USB 2.0 port the problem doesn't happen always.
It depends on the computer though. I added a PCMCIA USB 2.0 adaptor to my laptop that has USB 1.1 only. And when I connect the USB-to-PS/2 cable to the USB 2.0 my mouse sometimes work after suspend/hibernate but sometimes doesn't.
However, on my other desktop computer, which has integrated USB 2.0 ports, this problem has never happened (I haven't tested it exhaustively though).
This is a Windows bug of course. Everything related to USB 1.1 support is buggy in Windows. One more example is the annoying (and possibly catastrophic) "Delayed write error" that appears when you use a external hard drive plugged to a USB 1.1 port.
I guess M$ is focusing their efforts on making USB 2.0 to work well and they have forgotten about USB 1.1. Or it could a problem related to "USB composite devices", hard to know.
Message Edited by getfree on 02-22-2009 03:19 PM

Dell Inspiron 7537 - Sound only works after resuming from suspend

Similar Messages

Maybe you are looking for