brian_mars

Q: After upgrading to Mavericks, my Thunderbolt display does not wake from sleep.

Upgraded to Mavericks. Using a 15" Early 2011 MBP with a Thunderbolt display attached. A Firewire drive is connected to the display. Every time the MBP is awoken from sleep, the display stays off, and a notification is displayed saying the drive was not ejected properly.

 

Each time, I need to unplug the thunderbolt connector and reattach it.

 

Has anyone else seen this behavior/have a fix?

MacBook Pro, OS X Mavericks (10.9)

Posted on Oct 24, 2013 12:24 PM

Close

Q: After upgrading to Mavericks, my Thunderbolt display does not wake from sleep.

  • All replies
  • Helpful answers

first Previous Page 4 of 7 last Next
  • by p.andersen69,

    p.andersen69 p.andersen69 Jan 13, 2014 3:20 AM in response to Kibuk
    Level 1 (0 points)
    Jan 13, 2014 3:20 AM in response to Kibuk

    Same for me. Thunderbolt display and MacPro mid 2012

  • by zchannie,

    zchannie zchannie Jan 20, 2014 10:13 AM in response to brian_mars
    Level 1 (0 points)
    Jan 20, 2014 10:13 AM in response to brian_mars

    Same here. It does seem intermittent - sometimes it wakes properly, sometimes I have to unplug the Thunderbolt and re-plug it in. Then it protests I have not unplugged peripherals properly, and a couple of times it has told me "The name of your computer "Computer Name" is already in use on this network. The name has been changed to "Computer Name (2)"." Which is kind of disturbing.

     

    Thunderbolt display and MBP early 2011.

  • by jendrus,

    jendrus jendrus Jan 20, 2014 11:52 AM in response to One of the users
    Level 1 (0 points)
    Jan 20, 2014 11:52 AM in response to One of the users

    Spent lots of time fighting with this. Setting hibernatemode to 0 indeed solved the problem. Use "pmset -g" to check what's your setting. This value has been reset by the system in response to updates and setting default energy saving values, so I had to reset it 2 or 3 times. Each time it fixed the problem. Use "man pmset" to get the details.

     

    BTW: I wanted to mark the original poster os this tip with "This solved my question", but I do not see the button that would allow me to do that. Any ideas why?

     

    Message was edited by: jendrus

  • by tbirdvet,

    tbirdvet tbirdvet Jan 20, 2014 5:16 PM in response to jendrus
    Level 4 (3,012 points)
    Mac OS X
    Jan 20, 2014 5:16 PM in response to jendrus

    I would also like to know where the "this solved my question" button is.  It is never on any of my screens.

  • by Brian Mull,

    Brian Mull Brian Mull Jan 21, 2014 2:16 PM in response to jendrus
    Level 1 (19 points)
    Jan 21, 2014 2:16 PM in response to jendrus

    My hibernatemode is set to 0 (confirmed using pmset -g). Still a no go for me.

     

    Frustrating.

  • by Media_Maven,

    Media_Maven Media_Maven Jan 23, 2014 10:33 AM in response to brian_mars
    Level 1 (0 points)
    Jan 23, 2014 10:33 AM in response to brian_mars

    Same problem here. Early 2011 MBP with 27 inch TB display. I usually run docked with 2 remote drives and USB hub. Intermittently TB display or sometimes entire system will not wake. Removing Sonos antivirus helped a bit, but the problem is not solved.

     

    I was concerned about system stability and stayed with Snow leopard until about a month after Mavericks became available. I'm beginning to think that I should have stayed with Snow Leopard. I used to just love how apple stuff 'just worked' . Since this problem has been going on for months with no fix from Apple, I am losing my confidence in Apple. They read this forum and must know about the problem. It clearly relates to their new deep sleep code. They know what kinds of hardware is having the problem. How hard can it be to fix it if they really gave a ****

  • by per arvid,

    per arvid per arvid Jan 23, 2014 7:41 PM in response to brian_mars
    Level 1 (0 points)
    Jan 23, 2014 7:41 PM in response to brian_mars

    Same problem here.

  • by mfromsoest,

    mfromsoest mfromsoest Jan 24, 2014 3:13 AM in response to brian_mars
    Level 1 (0 points)
    Jan 24, 2014 3:13 AM in response to brian_mars

    I tried everything, still the same problem!

  • by jcmAZ,

    jcmAZ jcmAZ Feb 2, 2014 7:40 AM in response to One of the users
    Level 1 (0 points)
    Feb 2, 2014 7:40 AM in response to One of the users

    This didn't work for me on my  Late 2011 MBP.

  • by sakers,

    sakers sakers Feb 3, 2014 2:45 AM in response to jcmAZ
    Level 1 (0 points)
    Feb 3, 2014 2:45 AM in response to jcmAZ

    This issue only just started for me recently when I had my logic board replaced, before then everything was fine. I'm running Mavericks on an early 2011 MBP. I just tried the pmset fix, will see how it goes.

  • by Media_Maven,

    Media_Maven Media_Maven Feb 3, 2014 5:02 AM in response to brian_mars
    Level 1 (0 points)
    Feb 3, 2014 5:02 AM in response to brian_mars

    Over the past few days I've found that if my thunderbolt display does not wake up, unplugging and replugging the TB cable on my MacBook wakes the display

  • by jason1881,

    jason1881 jason1881 Feb 5, 2014 2:56 PM in response to brian_mars
    Level 1 (0 points)
    Feb 5, 2014 2:56 PM in response to brian_mars

    I have the same issue.  I took it to my local apple store, where they "genius" spent less than 5 minutes looking at my setup.  He left to check what "part" they would need, and reccommened replacing the LCD panel at a cost of $850.  My response was laughter.  He than pulled up amazon to show me that there were a lot cheaper options. 

     

    We all pay a 200-300% premium to purchase Apple products because they just work...Well my TBD was purchased in December 2011, so basically just over 2 years old.  If I wanted to replace my technology every two year, I would buy a Windows product.  I guess this should be my mentatlity for Apple now...Dissapointing...

  • by DoruCenuse,

    DoruCenuse DoruCenuse Feb 5, 2014 5:48 PM in response to jason1881
    Level 1 (0 points)
    Feb 5, 2014 5:48 PM in response to jason1881

    Actually I got the same problem. The Thunderbolt display started having problems after the last Apple software update, Finally quit waking-up when I start the system. I discussed with Apple, and, since was outside waranty I took it to the repair service, a company in Stockton. I am a LCD expert understandign all issues about displays and monitors and I thought it is the best to take it to service since they have a source for replacement parts. My expectation was that the LED driver circuit broked. Today I talked with Computer Link, Inc. in Stockton, the certified repair service for Apple and I got a very dissapointing message. Computer Link, inc. claimed that they could not get connected to my phone (very strange since is a land lane phone) and informed me that the controller board did not solved the problem and I have to pay $700+ to replace the LCD. Total BS, I bouth the Thunderbolt monitoer in 2012 and, as I know the LCD reliability is no way the LCD went down. For $1000 monitor I expect better service and full service support fore more than 3 years, This *****!!!!! I find

    QNIX QX2710 LED Evolution ll DPort 27" 2560x1440 Samsung PLS (LG IPS) Matt Screen Panel HDMI, Display Port (Thunderbolt Display), PC 27-inch Monitor *Perfect Pixel

    at Amazon for about $450 which may be a solution to replace my Thunderbolt. Still I have to look for an adapter for the interface since I plan to use it for my MacBook Pro notebook and I am connecting another monitor on the HDMI port. Toptally upset about Apple support....

  • by dkardell,

    dkardell dkardell Feb 6, 2014 5:46 AM in response to brian_mars
    Level 1 (5 points)
    Mac OS X
    Feb 6, 2014 5:46 AM in response to brian_mars

    I still can not believe this has been fixed!  I submitted an Apple Bug report back in Dec and was told its a dup of 15398523.

     

    How 3 months later is there still no patch for this????

  • by sakers,

    sakers sakers Feb 7, 2014 3:19 PM in response to sakers
    Level 1 (0 points)
    Feb 7, 2014 3:19 PM in response to sakers

    The pmset option didn't work for me either. Still need to physically remove the cable and reconnect for the screen to come back on.

first Previous Page 4 of 7 last Next