Keyboard volume keys don't work after waking from sleep

This problem has existed for many months on my 2009 Mac Pro. I'm running 10.6.3. The problem is reproducible 100% of the time. I use external speakers. Sound output is set to "Line Out."
1. Boot machine. External speakers work fine. Volume keys on keyboard (F11, F12) work correctly.
2. Put machine to sleep.
3. After waking from sleep, F11 and F12 no longer control the volume of the external speakers. The "pop" noise when hitting F11 and F12 is emitted from the internal speaker. The mute key (F10) does work for the external speakers, however.
4. The keyboard volume controls become responsive again by switching the sound output from Line Out to another output option and then back to Line Out.
This bug is a huge hassle. Does anyone have a solution?

I have several mid-2009 8-core Mac Pro's, all running Snow Leopard, and all have been having this problem as well.
I will not guarantee this is going to work for anyone else....but we have found a (slightly inelegant) workaround for it that has been working for several weeks now without fail.
Prior to putting your MacPro to sleep, run the volume all the way up and leave it there. Afterwards, put it to sleep as usual. We use the keyboard to do this, but I would imagine any method should have the same affect. However, I've not experimented.
Anyway...this has worked 100% of the time for us. The only downside of it is that you have to remember to run it up before....and then back down after waking (else that first alert sound or music file you play will really wake YOU up!)
If this works for anyone else, let me know.
Apple should never have let this one out the door with this bug. Especially, as Apple Support is....wanting, at best.
...sT

Similar Messages

My zero Key isn't working after waking from sleep mode. This is a real problem for me because my password contains a zero

My zero Key isn't working after waking from sleep mode. This is a real problem for me because my password contains a zero. I don't recall spilling anything or jamming it just that it worked before I closed the computer and wasn't after I woke it up.
I would like to fix the key but if that's not possible right away , Is there a way to reset my password without being able to type with a key thats in it?

Start by swapping the keyboard. You don't need to spend a fortune, and handy to have spare. USB cables can be bad even new.
When I had some problems Apple wanted to blame the mouse, keyboard, cable, but in the end I found
A. run Disk Warrior
B. Corrupt pref or conflict with version of Hardware Monitor and other background tasks

Ping and ssh don't work after waking from sleep

Hi!
I have been running Arch on my 2010 Macbook since May and there's always been this one annoyance which I can't figure out: after it is woken from sleep, the wireless (using netctl) happily reconnects and I can browse, check email, run pacman, do dns lookups---everything, it seems, apart from ssh or ping. Both ping and ssh seem to hang. If I reboot or restart [email protected], then they both work.
Running :
$ ssh XXX.XXX.XXX.XXX
connect(3, {sa_family=AF_INET, sin_port=htons(22), sin_addr=inet_addr("XXX.XXX.XXX.XXX")}, 16
where XXX.XXX.XXX.XXX is my work computer. (Full strace: http://pastie.org/private/xhmee0oltrnx3qmblnzq)
Running strace ping google.com (as root) gives the repeated lines:
$ strace ping google.com
sendmsg(3, {msg_name(16)={sa_family=AF_INET, sin_port=htons(0), sin_addr=inet_addr("173.194.34.102")}, msg_iov(1)=[{"\10\0\270\345b\325\0\2\336\36QR\0\0\0\0\353\376\2\0\0\0\0\0\20\21\22\23\24\25\26\27"..., 64}], msg_controllen=0, msg_flags=0}, 0) = 64
recvmsg(3, 0x7fff2f6d6f90, 0) = -1 EAGAIN (Resource temporarily unavailable)
(Full strace: http://pastie.org/private/bfygaqtccz0ms2w8hqea4g)
I can, however, sucessfully ping my router and other devices connected to it. I have not been able to find out anything relevant that might fix this. I've checked the MTU settings match those on the router and my other laptop running Arch does not have this problem.
Any suggestions on how to debug this further?
Thanks!

I have several mid-2009 8-core Mac Pro's, all running Snow Leopard, and all have been having this problem as well.
I will not guarantee this is going to work for anyone else....but we have found a (slightly inelegant) workaround for it that has been working for several weeks now without fail.
Prior to putting your MacPro to sleep, run the volume all the way up and leave it there. Afterwards, put it to sleep as usual. We use the keyboard to do this, but I would imagine any method should have the same affect. However, I've not experimented.
Anyway...this has worked 100% of the time for us. The only downside of it is that you have to remember to run it up before....and then back down after waking (else that first alert sound or music file you play will really wake YOU up!)
If this works for anyone else, let me know.
Apple should never have let this one out the door with this bug. Especially, as Apple Support is....wanting, at best.
...sT

New wireless keyboard & volume keys don't work

I just replaced my wireless keyboard because a few of the keys stopped working. Now the volume keys don't work on the new one. When I push them one of them brings up my widgets and the others minimize the screen. Any Ideas?

Put truly fresh batteries in the keyboard.
Un-pair and re-pair the keyboard with the computer.
Attempt the PRAM reset again.
If you do not get the 2 boot chimes then I would suggest you reset using a USB keyboard. Any USB keyboard will do. If you don't get the 2 chimes when using a USB keyboard then either you are not holding down the keys correctly / early enough or there is something wrong with the computer itself.
If you do get the 2 boot chimes you can then go back to the wireless keyboard and re-pair it.
Take a peak at this article. It is fairly exhaustive in troubleshooting suggestions for this type of issue: http://support.apple.com/kb/TS3048
Hope that helps.

Nothing works after waking from sleep

I've been having an issue where randomly when I wake my computer from sleep wifi isn't working and all the apple apps have crashed or crash at start up. If I try to restart nothing will happen and it stay on the grey screen for a long time after force quitting almost everything. I've tried doing a restore and that didn't help at all. Any ideas?

For problems like this you need to start as small as possible because it can be rather difficult to figure out just what the problem is and you can wind up spending lots of time blundering about when the problem turns out to be right under your nose. So:
Step 1: unplug everything from the computer but monitor, keyboard, mouse, and Internet cable. If the problem stops you know it was a peripheral device and you can start adding them back one by one.
Step 2: create a new account and log into it. Don't configure anything, just spend a bit of time browsing the Internet and then let it sleep. If nothing happens you'll know there's something in your account or some program you are using that is causing the problem. Otherwise:
Step 3: Run the Apple Hardware Tests and boot into the Recovery Partition to run Disk Utility. If the hardware test passes and the drive directory is okay then we move on to the last 2 bits.
Step 4: The next time this happens make a note of the time and force quit, then as soon as the computer has finished rebooting, start the Console program (it is in Utilities) and scroll down to the bottom (those are the most recent). Look at the time stamp of the log and find the ones closest to the time you force quit the computer. You may find a hint there about what caused the crash.
And finally: If you booted into the OS X Recovery system and used TimeMachine to restore your computer it is entirely possible that all you did was restore the program right back onto the computer. Boot back into the Recovery system, erase the hard drive, download OS X 10.7 again and then use Setup Assistant to migrate your account and applications. Doing this is different from a restore because you'll be installing a fresh copy of OS X rather than copying it from your TimeMachine backup.
Steps 1-4 can be done in any order really but the last step really should be the last step because it is the most time consuming and so often the problem is found in steps 1-4

Can't get yosemite to working after waking from sleep mode

I just installed Yosemite to my Mac Mini. When the computer goers to sleep for more then 30 seconds I can wake the computer but then after i see the desktop I can't do anything on the computer every click i make does not respond and I have to force the computer to shut down and I have to reboot every time my computer goes to sleep.

I have the exact same issue for the first time after installing Yosemite. On resume from sleep, I can see the desktop, and can move the cursor with the mouse, but clicking on icons, etc. does nothing, and the keyboard does nothing. A cold boot works fine. This is a Mac Mini bought in the Summer of 2014. I run no unusual software. I have eliminated all log in items in Preferences/Accounts, reset the NPRAM, have no peripherals (other than standard Apple mini mouse and wireless keyboard), and have shutdown and unplugged to reset. It makes no difference whether a password is required or not - once it goes to sleep, this is the result, and only a forced shut-down by holding the power button and a cold boot give me control back. This problem does not appear if it merely goes into screensaver mode - which I invoke with a hot corner.

Wireless Mouse Doesn't Work After Waking From Sleep Mode

I have a MacBook Pro 13" 2.9 GHZ running on OSX 10.8 and when it wakes from sleep the wireless usb mouse no longer functions. I have to continually unplug then plug the mouse back in for it to work. Is there a way to solve this problem? I haven't found any definitive answers through searching the web. It's minor but irritating as I'm not fond of using the trackpad.

Would like to backtrack this discussion to
Re: iMac 2014 5K Bluetooth Trackpad Problem after sleep
Please add your system configuration and Wifi details (G, N or AC) to the mentioned thread if possible

External UCube speakers don't work after awakening from sleep mode since 10.7.5 upgrade

Ever since I upgraded to 10.7.5 when I wake my computer from sleep mode...my external UCube speakers don't work unless I unplug them and plug them back in. I've already tried resetting the SMC. It recognizes and shows the speakers in the sound preferences...but no sound unless I reconnect the usb cable. Worked fine in 10.7.4
Any ideas? Its ridiculous all the audio problems being reported.

I have a mac mini (A1283) with OS 10.7.4. Upon upgrading to 10.7.5 it did not start up again. Instead, the light was on and the hard drive did not start up. The light on the connected USB mouse was not lit.
My solution:
Cold start with Command-v pressed.
This should start Verbose mode (see http://support.apple.com/kb/HT1492 ).
What happened on my mac mini was that the grey startup screen with the Apple logo appeared for a long while before the login screen came.
Maybe Cmd-v set open firmware params and fixed some corruption.
Anyway: my mac mini works again.

Network mounts don't reconnect after waking from sleep

Hi,
I'm a network administrator for a small TV studio that's Mac-based. We had an up-to-date upgrade from Lion to Mountain Lion on one of our iMacs, plus updated a couple of our others for testing purposes. They're connected to a Lion server with Open Directory, and network shares are set up such that when a user logs in, the shares are mounted and available on their desktop.
Unfortunately, on the Mountain Lion machines, when the computers are woken from sleep, the shares are no longer mounted. I thought that maybe this might be resolved in 10.8.1, but it's still not fixed in 10.8.3. It's especially a problem when a document is open on one of those shares, and then the app fails because the file is no longer available. Note that this does not happen on the Lion machines.
Has anyone else come across this problem? Is there any way to fix it, or is it an OS bug? I'm not willing to roll this out to the rest of the network until I can get this sorted out.
James.
EDIT: I've just found other discussions with a similar question to this (a search before posting didn't show anything until I posted this one!). That said, there's still no answer to the problem. Can we get Apple's attention with this one??

James Hope wrote:
What can one do????
Prevent them from sleeping? Apple is moving towards a more mobile world where wireless resources come and go. If you are still working with wired connections, you might need to make some changes. Not sleeping is once answer. AFP has some issues with passwords that cause problems with automount. I think they are fixable and I've always had a plan to write a little Keychain-aware command-line mounter for autofs. Always too busy though. I know that AFP supports Kerberos with automount. Since you have all Mac equipment, it seems like you could implement that pretty easily, well, as easily as Kerberos. I've never used it but I've heard stories. If you ware workng with an old-school topology, you could go to an old-school network like NFS. There are any number of hack-arounds. There are tools that will automatically run scripts (or mount drives) upon wake. You could replace those mounts with aliases (not symbolic links, true Mac aliases) that will get automatically mounted when you double-click on them.

Mutiple monitor setup not working after waking from sleep

Mac Mini 2011
Mavericks (10.9.3)
Monitor 1 Mini->HDMI Cable->Monitor
Monitor 2 Mini->Mini Display Port to HDMI Adapter->HDMI Cable->Monitor
Monitors are not the same size
Thw adapter is PNY (PNY A-DM-HD-W01)
Upgraded to Mavericks, second monitor works nicely. However, when waking the system up after it goes to sleep, the second monitor does not turn on. Further, the primary montior blinks every few seconds between the usual display and shrinking the windows to a smaller size. Unplugging the second monitor from the HDMI adapter cable stops the blinking, but connecting it again (even after waiting a few minutes) makes the blinking continue and the second monitor does not wake up. On reboot, all works fine again.

Hello chacham,
The article linked below provides some useful troubleshooting steps that can help resolve the issues you're experiencing with your display.
Apple computers: Troubleshooting issues with video on internal or external displays
http://support.apple.com/kb/HT1573
Cheers,
Allen

Macbook Air (mid-2011) Facetime HD Camera stops working after waking from sleep

Hi, for the past week or so (no more than a week), my computer has not been able to connect to my built-in camera. I have a mid-2011 Macbook Air (running version 10.7.5) and a Facetime HD Camera (version 6.46). I don't usually restart my computer unless I am having issues with it being slow or freezing and so usually just close the top of my laptop when I am sleeping or at work. When I wake my computer up and attempt to use Skype, Photobooth, or Facetime, I cannot connect to the camera. Restarting my computer fixes this issue but that's as far as I've gotten since I am not very tech savvy and do not want to do anything to jeopardize the data and documents stored on my Air (I'm in school so losing anything would be very stressful for me). I have gone into the System Information in my Utilities folder and my camera is listed under the USB tab but my computer refuses to connect unless I restart it.
Any suggestions or help would be greatly appreciated! Thanks in advance!

my computer has not been able to connect to my built-in camera
iSight is the built-in camera.
Help here > How to Troubleshoot iSight

Mission control inactive after waking from sleep

Having an intermittant issue where the mission control functions are no longer working after waking from sleep. I can't swipe between desktops, or activate mission control by clicking on the dock icon. The only way to get it back is to use the Activity Monitor to force quick the dock and have it re-launch. Then everything is fine. Doesn't happen all the time on sleep.

Did it happen each time?
As I know, if you press at touch panel while system booting.
It maybe influence touchpanel initial. ->It will cause touchpanel no function when you enter system.

Volume keys don't work anymore after Gnome 2.26 upgrade

I have two pc: a desktop and a laptop. The desktop doesn't have this problem. While on the laptop, a sony vaio fz21s, after the recent gnome 2.26 upgrade, the volume keys don't work. The osd appears on the screen but no change in volume is observed. Through the gnome-volume-applet i set "Principal" as main device. Controlling the volume with the gnome-volume-applet works.

ad1g3n wrote:I solve this problem with adding alsa to DAEMONS array in /etc/rc.conf
I have it too
My laptop works perfect, i need to solve only this

Macbook pro 13inch,mid2010 qwertyu keys don't work after upgrade os x Yosemite

macbook pro 13inch,mid2010 qwertyu keys don't work after I upgrade os x 10.10 Yosemite. but it works on keyboard viewer. I'm not sure if it's hardware or software problem, how can I fix it?

Hello there, kipolo.
Great job using the Keyboard viewer to troubleshoot your issue so far. The following Knowledge Base article provides a great checklists of steps to pinpoint the issue a bit further:
One or more keys on the keyboard do not respond - Apple Support
Some keys don't work as expected
From the Apple menu, choose System Preferences.
From the View menu, choose Speech.
Click the Text to Speech tab.
If "Speak selected text when the key is pressed" is enabled, the key or key combination set to speak text cannot be used for other purposes or used to type text--click Set Key and change it to a less-commonly used key combination (try to use modifier keys such as Shift, Command, Option, and Control). Or, disable the "Speak selected text when the key is pressed" option.
Click the Accessibilty or Universal Access pane in System Preferences, then click the Keyboard tab.
Make sure that Slow Keys is turned off. With Slow Keys on, you need to press a key for a longer period of time for it to be recognized.
In the Accessibilty or Universal Access pane, click the Mouse tab, and make sure Mouse Keys is turned off. With Mouse Keys enabled, you cannot use the Numeric Keypad to enter numbers--instead the keypad moves the pointer (cursor). (There is an option to enable Mouse Keys with five presses of the Option key; you may want to turn that option off to avoid accidentally enabling it.) If Mouse Keys is enabled and you are using a keyboard with no numeric keypad or Num Lock function, see Unable to type while Mouse Keys is enabled in Mac OS X.
If the function keys on the top row of the keyboard are not working as expected, see Mac OS X: How to change the behavior of function keys.
If the issue persists, use Keyboard Viewer to help isolate the issue:
Click the Language & Text pane (Mac OS X v10.6) or International pane (Mac OS X v10.5.8 or earlier) in System Preferences.
Click the Input Sources tab (or Input Menu tab in Mac OS X 10.5.8 or earlier).
Click the Keyboard & Character Viewer "On" checkbox to select it (click the Keyboard Viewer "On" checkbox in Mac OS X 10.5.8 or earlier).
From the Input (flag) menu, choose Show Keyboard Viewer.
If the keyboard is connected and detected by OS X, the keys you type will highlight in the Keyboard Viewer window. Open TextEdit (or any text application), and try to type something using the keys that were previously not responding to see if they highlight in Keyboard Viewer.
Start from the Mac OS X Install Disc, choose Terminal from the Utilities menu and test the keys which were previously not working. If the keys work while started from the Install disc, then the keyboard itself is working correctly. Use How to troubleshoot a software issue to isolate the software issue that may be causing the keys to not respond.
Thanks for reaching out to Apple Support Communities.
Cheers,
Pedro.

Fn+b keys don't work after installing Win7 Ultimate (HP Envy 14 BE)

Fn+b keys don't work after installing Win7 Ultimate (HP Envy 14 BE) --not able to use the Beats Speakers. Any software updates I need to install?
This question was solved.
View Solution.

Hi Jim,
You're welcome
Is the version of Windows 7 Ultimate you have installed 32bit or 64bit?
Open windows Control Panel, open Device Manager and open up Sound, Video and Game Controllers - do you see an existing entry for the IDT High Definition Audio CODEC listed here?
There is an alternative IDT Audio driver you may wish to try on the following link.
http://ftp.hp.com/pub/softpaq/sp53001-53500/sp53281.exe
Let me know if you get the same error with this version.
Regards,
DP-K
****Click the White thumb to say thanks****
****Please mark Accept As Solution if it solves your problem****
****I don't work for HP****
Microsoft MVP - Windows Experience

Keyboard volume keys don't work after waking from sleep

Similar Messages

Maybe you are looking for