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

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.

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

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

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

Frustrating.

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 ****

Same problem here.

I tried everything, still the same problem!

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

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.

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

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...

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....

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????

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.

I use to have this problem. The Thunderbolt would go black and I would have to unplug it from the wall before it would work again... for a short time anyway.

While I can not predictably recreate this, I have stopped it from happening.

I updated my Thunderbolt display settings so:

• automatically adjust brightness is off
• Brightness level is NOT at the max

Note: This is the Thunderbolt display settings, not the MBP display settings. If your display preferences are only showing control for your MBP. Then:

• Close the lid of your MBP
• Open system preferences
• Goto Displays
• Make the adjustments noted above

Prior, I called up Apple support and even brought it into the apple store. They could not stop it. But these changes did make it stop.

Note to Apple tech:

I think it has something to do with Automatic brightness setting. I think when you have it set to maximum brightness and the automatic brightness setting decided to dim the monitor, it dims it all the way down to 0.

This happens in both clamshell and duel monitor mode.

This may not be the root cause, but the setting adjustments I made above have worked for the past month.