Vicnowo

Q: sleep wake problem with Yosemite on my Mac Mini Mid 2012

I have a problem with Sleep Wake on a Mac Mid 2012 Mac Mini running 10.10, I was also a beta test user, and had seen the same problem before the official release. After the Mac Mini goes to sleep, and you try to wake it, it sits frozen, you can not enter your password, after about 5 minutes, the Mac reboots, and you can enter your password, the keyboard works again. I am using the Apple bluetooth MC184LL/A wireless keyboard. This same problem is occurring with the Logitech K760 bluetooth solar keyboard. I am now going to try only a standard USB keyboard, to see if the problem is somehow related to bluetooth? I been sending the reports to Apple about this problem since I started the beta testing from the start of the Yosemite beta test. It seems this is low on the list or is somehow related to my machine only? I have never had any problems with my Mac Mini, and have never done anything to the device (I never opened the Mac).

Any one else with the same problem? Thanks!


Vicnnowo

Mac mini (Late 2012), OS X Yosemite (10.10), Wake Sleep Bluetooth Keyboard

Posted on Oct 18, 2014 5:35 AM

Close

Q: sleep wake problem with Yosemite on my Mac Mini Mid 2012

  • All replies
  • Helpful answers

first Previous Page 5 of 23 last Next
  • by Stcroix95,

    Stcroix95 Stcroix95 Oct 21, 2014 1:21 PM in response to Vicnowo
    Level 1 (0 points)
    Oct 21, 2014 1:21 PM in response to Vicnowo

    Same problem here as well, late 2012 mini with speakers going through the headphone jack.  When it first boots after the crash if often doesn't recognize the auto output until I unplug and replug it

  • by Tom in London,

    Tom in London Tom in London Oct 21, 2014 1:40 PM in response to Stcroix95
    Level 4 (1,626 points)
    Mac OS X
    Oct 21, 2014 1:40 PM in response to Stcroix95

    Interesting comments here.

     

    It seems that when the computer wants to wake from sleep, it looks for various things and can't find them even though they are there. Some kind of hardware problem.

     

    I'm not going to start plugging/unplugging stuff just because I want the computer to wake from sleep. I'd rather just turn it off completely and then turn it on again when I need it.

  • by vaikl2,

    vaikl2 vaikl2 Oct 21, 2014 1:46 PM in response to Stcroix95
    Level 1 (5 points)
    Oct 21, 2014 1:46 PM in response to Stcroix95

    Seems that the sleep wake issue is strictly assigned to the headphone/audio jack. It doesn't make a difference if i assign any audio routing to the standard out or not, it all works when *no* audio cable is plugged in and sleep wake doesn't work and/or crashes (could be the same, because SystemUIserver "prints" a picture of the latest working desktop status when the system crashes) when a plug is plugged in. That could only be a hardware controller driver bug or something in that range.

  • by icerabbit,

    icerabbit icerabbit Oct 21, 2014 2:10 PM in response to Vicnowo
    Level 3 (775 points)
    iPhone
    Oct 21, 2014 2:10 PM in response to Vicnowo

    Been having this exact problem since running Yosemite beta, certainly 2, possibly 1. Initially I thought they keyboard was rejected as the mouse worked.  Sent the problem in via the Feedback Assistant with every update. Figured it was something Apple would sort out by public release time. Eh, no, they didn't.

     

    Has everybody filed a bug report via Apple Feedback online?

     

    I'm tired of force shutting down my mini every time I want to use it after an hour or more of inactivity.

     

    '12 mini bumped up with 16GB RAM and Mercury Pro 6G SSD, logitech keyboard & mouse, no hub; wifi OFF.

  • by ancorasudigiri,

    ancorasudigiri ancorasudigiri Oct 21, 2014 2:33 PM in response to Vicnowo
    Level 1 (0 points)
    Oct 21, 2014 2:33 PM in response to Vicnowo

    I invite everyone of you to file a bug report at the address below. More we are, the sooner they fix it.

     

    https://www.apple.com/support/feedback/

  • by vaikl2,

    vaikl2 vaikl2 Oct 21, 2014 4:00 PM in response to Tom in London
    Level 1 (5 points)
    Oct 21, 2014 4:00 PM in response to Tom in London

    Different logfiles tell me that a very high numbers of wake-up procedure calls from two core frameworks, SystemUIServer and Spotlight, cause that crash, because the system becomes unanswerable. But this could also be only a symptom for a prior crash of hardware drivers in the audio framework.

  • by ill0gitech,

    ill0gitech ill0gitech Oct 21, 2014 4:19 PM in response to Vicnowo
    Level 1 (0 points)
    Oct 21, 2014 4:19 PM in response to Vicnowo

    Mid 2012 Mac Mini

    Wake from Display sleep = ok

    Wake from Hard Disc sleep = ok

    Wake from full sleep = not ok

    Clean install, EPROM and SMC reboots have had no effect.

     

    I had the same issue with Beta 2 - not Beta 1. Rolled back to Mavericks at the time, but inc eI've upgraded icloud that's not a good solution.

  • by gary321,

    gary321 gary321 Oct 21, 2014 5:44 PM in response to Vicnowo
    Level 1 (0 points)
    Oct 21, 2014 5:44 PM in response to Vicnowo

    I had the same issue.  Speakers connected directly to mac mini.  When I disconnected them and moved them to the output of my monitor (sound over HDMI), everything works right.  Wake now works.

  • by sjs123456,

    sjs123456 sjs123456 Oct 21, 2014 6:51 PM in response to Vicnowo
    Level 1 (0 points)
    Oct 21, 2014 6:51 PM in response to Vicnowo

    Same exact problem as many others have reported.  Late 2012 Mac Mini, with speakers plugged into headphone jack.  On wake from sleep, the mouse cursor moves, but nothing else is responsive.

     

    Setting it to computer sleep never worked for me as a temporary workaround.  I have two monitors and I'm able to let the monitors sleep with no problem.

  • by nick baccante,

    nick baccante nick baccante Oct 21, 2014 7:19 PM in response to gary321
    Level 1 (10 points)
    Desktops
    Oct 21, 2014 7:19 PM in response to gary321

    hi

    I just tried the same thing: disconnected the speakers from the headphone jack and now I can bring my Mac Mini back from the sleep state..hardware conflict of some kind I would think

  • by Vicnowo,

    Vicnowo Vicnowo Oct 21, 2014 7:38 PM in response to nick baccante
    Level 1 (0 points)
    Oct 21, 2014 7:38 PM in response to nick baccante

    I have the same setup, speakers connected to the audio line in / headphone jack, I disconnected the speakers, now it's not frozen when going to sleep. I have a Logitech USB based speaker, I tried using this USB based speaker, no sleep wake problem. This is somehow tied to the audio line in / headphone jack!

     

    Thanks everyone for your find!

  • by gmoi12305,

    gmoi12305 gmoi12305 Oct 21, 2014 7:52 PM in response to Vicnowo
    Level 1 (0 points)
    Oct 21, 2014 7:52 PM in response to Vicnowo

    I have the same exact problem my mac mini 2013 seems to freeze when I wake it up it use to have a pass code I thought that was the problem I disabled it and it is still doing the same thing today actually the sound settings were messed up and external speakers were disabled..it seems after 5 minutes it reboots itself

  • by Captain Beaky,

    Captain Beaky Captain Beaky Oct 21, 2014 10:09 PM in response to Vicnowo
    Level 1 (0 points)
    Oct 21, 2014 10:09 PM in response to Vicnowo

    Well my mid 2010 mac mini has the same issue, except neither the "push power button to wake" trick or the "remove speakers from the line out port" work. I push audio through HDMI and am still having wake up problems. 

  • by soul1964,

    soul1964 soul1964 Oct 22, 2014 1:30 AM in response to kenfromnorth shields
    Level 1 (0 points)
    Oct 22, 2014 1:30 AM in response to kenfromnorth shields

    My sleep function so far seems to be working after i disconnected a headphone extension cord from the back of my mac mini so whoever suggested it was a sound hardware  conflict,thank you

  • by Vicnowo,

    Vicnowo Vicnowo Oct 22, 2014 2:19 AM in response to soul1964
    Level 1 (0 points)
    Oct 22, 2014 2:19 AM in response to soul1964

    This has helped me as well. Others are not being helped. There is some sort of hardware conflict related to Input / Output.

first Previous Page 5 of 23 last Next