Resolved Startup Chime stopped working 10.11.6

Discussion in 'OS X El Capitan (10.11)' started by crjackson2134, Jul 29, 2016.

  1. crjackson2134 macrumors 68020

    crjackson2134

    Joined:
    Mar 6, 2013
    Location:
    Charlotte, NC
    #1
    After installing the newest update, my startup chime quit working.

    I've tried all sound settings and output devices as well as a NVRAM (PRAM) reset to no avail.

    When doing the reset, the chime works, but when booting to OS X 10.11.6 there is no chime. I've googled around and tried various things but so far not having any success.

    Suggestions?
     
  2. crjackson2134 thread starter macrumors 68020

    crjackson2134

    Joined:
    Mar 6, 2013
    Location:
    Charlotte, NC
  3. Veldhuis macrumors newbie

    Veldhuis

    Joined:
    Aug 13, 2015
    #3
    Type this in Terminal, see if it helps:

    sudo nvram -d SystemAudioVolume
     
  4. flowrider macrumors 601

    flowrider

    Joined:
    Nov 23, 2012
    #4
    I remember having that problem over a year ago on an OS update. IIRC, the fix for me was to unplug my external speakers, go into the Sound Control Panel and select the internal speaker and turn up the volume. I then reconnected the external speakers, chose them again and restarted and voila the chime was back.

    Lou
     
  5. crjackson2134 thread starter macrumors 68020

    crjackson2134

    Joined:
    Mar 6, 2013
    Location:
    Charlotte, NC
    #5
    Thanks for both suggestions, I'll try that tomorrow Lou.
     
  6. spooned12000rpm macrumors regular

    Joined:
    Jun 4, 2009
    Location:
    York, UK
    #6
    I had a similar issue a few upgrades ago, it's like the system couldn't 'see' the speakers on my old MBP. The volume control was greyed out and changing settings for output device in sound settings had no effect. (even weirder was if I booted into my Snow Leopard partition everything was fine!).

    What cured it for me was putting some headphones into the 3.5mm socket and taking them out again, it was like the switch in the socket had got 'stuck' (odd as I never use headphones and Snow Leopard could see the speakers fine) and this seemed to 'reset' the software into recognising that the speakers were there!

    A simple but unnecessary fix as this shouldn't happen!
     
  7. crjackson2134, Jul 31, 2016
    Last edited: Jul 31, 2016

    crjackson2134 thread starter macrumors 68020

    crjackson2134

    Joined:
    Mar 6, 2013
    Location:
    Charlotte, NC
    #7
    Okay, so I've tried all the suggestions and still no chime. Kind of irritating ...

    I even tried reinstalling from a USB stick... Still no chime.
     
  8. flowrider macrumors 601

    flowrider

    Joined:
    Nov 23, 2012
    #8
    Charles

    Sorry to hear that! Bit, as I said it worked for me:oops:

    Lou
     
  9. crjackson2134 thread starter macrumors 68020

    crjackson2134

    Joined:
    Mar 6, 2013
    Location:
    Charlotte, NC
    #9
    I'm not going obsess on it. Everything else is working fine. I may tinker with it a little later when I have time to kill.

    Thanks for the suggestions...
     
  10. rshrugged macrumors 6502a

    Joined:
    Oct 11, 2015
    #10
    You might want to try the Term cmd with SIP disabled. (Afterwards, you have to reenable SIP to use its protection.)
     
  11. crjackson2134 thread starter macrumors 68020

    crjackson2134

    Joined:
    Mar 6, 2013
    Location:
    Charlotte, NC
    #11
    I'll give it shot tomorrow. I doubt it'll work but it's worth trying.
     
  12. crjackson2134 thread starter macrumors 68020

    crjackson2134

    Joined:
    Mar 6, 2013
    Location:
    Charlotte, NC
    #12
    So, magically.... The chime started working again without any remedies performed by me. WTH?

    Anyway, all seems normal now, so thanks for all the help guys.
     
  13. flowrider macrumors 601

    flowrider

    Joined:
    Nov 23, 2012
  14. crjackson2134 thread starter macrumors 68020

    crjackson2134

    Joined:
    Mar 6, 2013
    Location:
    Charlotte, NC
    #14
    I'm guessing that one of the suggestions DID actually work. Just not immediately as expected.
     

Share This Page