Previous 1 2 3 Next 81 Replies Latest reply: Nov 4, 2013 9:51 PM by danb1974
danb1974 Level 1 Level 1 (0 points)

MBP 13" mid 2010 (7.1) just installed a fresh copy of Lion. After reboot volume control does not work (audio device - which is internal speakers - has no controls), but there is sound. After inserting headphones the volume control starts working, and remains functional after removing the headphones.


Basically after each reboot I have to temporary plug headphones to get volume control working. Nothing in dmesg or system.log


I'm familiar with linux so if you tell me how to debug this I'll happily do it, not afraid at all of command line or searching through logs.


(and you'd think that having control both over hardware and software would prevent such frustrating problems)

Macbook Pro 2010, Mac OS X (10.7)
  • leroydouglas Level 6 Level 6 (15,235 points)

    I would first try resetting the pram


  • danb1974 Level 1 Level 1 (0 points)

    First thing I tried, didn't help.

  • MJNC Level 1 Level 1 (0 points)

    I'm having exactly the same issue.  Volume keys (F10-F12) don't work until I plug in headphones.  Then when I reboot the problem comes back. I've tried resetting PRAM and that didn't fix it.  I also tried playing around with the "Use all F1, F2, etc." button in System Preferences -> Keyboard.  Turning it on made things behave bizarrely -- F11 seemed to be taking me to Dashboard.  With it off (default) it also doesn't work.


    Any suggestions?  These keys are two of my most used keys...



  • adambomb13 Level 1 Level 1 (0 points)

    I too am having the exact problem, resetting PRAM works sometimes, I also tried deleting plist sound files, no go. I have created a new users, no go. I have ran Apple hardware test, nothing detected.  Yes plugging in the headphones works until I reboot or shutdown still irrating...I have been working on this issue all day... I just called an Apple Store and they to have heard of this and recommended a fresh install of Lion or wait for an Apple fix through Software Update



  • kracek Level 1 Level 1 (0 points)

    Same here. Macbook Pro 8,1 Early 2011.

  • danb1974 Level 1 Level 1 (0 points)

    It looks more like a race condition or uninitialized variable in the kernel sound driver. That's not good since it may not affect too many people and may not be easy to reproduce by the developers (if it makes it onto apple's bug list)


    One day it happened after every restart, for at least 5 restarts.


    The other day it happened only after shutdown/poweron.


    So I don't think the pram reset is more then a coincidence.


    Only good think is you don't need to reboot often, sleep (standby) works just fine and the battery drain is minimal.

  • adambomb13 Level 1 Level 1 (0 points)

    Ok I located this command somewhere in Apple Support Communities (so no credit to me)

    sudo kill -9 `ps ax|grep 'coreaudio[a-z]' |awk '{print $1}'`


    then I used the pico command to create a file then made it executable then placed it into the login Items but so far it requires a admin password to execute (this does the same thing as plugging in the headphones)



  • dlee31217 Level 1 Level 1 (0 points)

    I'm not sure if this will work for everyone, but I had the same issue and I got it to work after this.


    1.  I enabled the F1, F2, etc keys to function as standard function keys option.

    2.  I held down the fn key and the shift key to increase/decrease volume  (using fn+shift let's you increase/decrease volume without the sound effects.


    Doing this somehow made the volume controls work again.

    Might just be coincidence...

  • SundanceX Level 1 Level 1 (5 points)

    same problem here  with a MacBook Pro 13 Mid 2010. The MacBook Pro 17 Mid 2008 runs fine.

  • rk-MA Level 1 Level 1 (0 points)

    Same problem Mac Pro early 2011, 12 core

  • GFernandes Level 1 Level 1 (0 points)

    Same problem here.  I hope this affects enough people for a fix to come out soon!

  • danb1974 Level 1 Level 1 (0 points)

    Seems there is an issue with the moment at which coreaudiod is started. A possible fix is to change coreaudiod startup mode.


    Edit /System/Library/LaunchDaemons/, look for keepalive word and change the following <false/> to <true/>


    (you have to do this as root)


    Save, reboot, tell us if it works. For me it seems to help.

  • chartake Level 1 Level 1 (10 points)

    Thanks, it works for me.

  • hiukong Level 1 Level 1 (0 points)

    Seems it works for me. Mine is MBP 2010 13". Thanks danb1974!

Previous 1 2 3 Next