-
All replies
-
Helpful answers
-
Oct 26, 2013 4:33 PM in response to adrian-polglaseby Chris Such,I just came back to my mac after leaving it overnight and the TBD woke up correctly.
This was with the System Preferences > Mission Control > Checkbox for 'Displays have seperate Spaces' unslected.
Adrian, if that didn't work for you though, then the underlying cause must be deeper. I think we just need to hold on and wait for a fix from Apple.
Cheers, Chris.
-
Oct 27, 2013 1:45 AM in response to Chris Suchby extankerman,After following the: 'System Preferences > Mission Control > Checkbox for 'Displays have seperate Spaces' unslected.' sequence, my TBD woke up as normal this morning, too.
Time will tell if that was the correct thing to do or just a handy workaround!
-
Oct 27, 2013 4:51 PM in response to brian_marsby John McPeake,I have the same system setup as the rest of the thread essentially. Did the "displays have separate spaces unselect" and it still doesn't work. How thorough is the Apple testing and regression? Apple by definition is dealing with an all-Apple-controlled hardware environment (unlike Microsoft which has to deal with HP, Dell, AMD, Intel, etc.) and they still can't get this stuff right? Wake from sleep has been an on-and-off issue through multiple releases of OS X by Apple. Hello???
-
Oct 27, 2013 6:32 PM in response to brian_marsby Karl Kaufmann,Did two SMC resets, and it appears the issue is solved. Will check throughout the week if the problem crops up again...
-
Oct 28, 2013 10:54 AM in response to brian_marsby adrian-polglase,Okay. So after trying a few things from here which didn't work, I remembered I had some AppleCare left and decided to chat to some Apple support specialists. They told me to create a test User account with which, I discovered, didn't have the problem. So then he told me to do the following...
- Shut down my Mac
- Disconnect the Thunderbolt Monitor from both the Mac completely and the power source (and any other attachments to the monitor using the peripheral ports) and leave unplugged for about 30 seconds
- Perform a SMC reset on my Mac (Plug in seperate MagSafe charger > Press (left-side) Shift+Control+Option keys and the power button at the same time > Release all keys and power button at the same time)
- Then power the Mac back on and reconnect the monitor
After performing all of these steps, the problem has resolved itself. Basically, it is a reset of both the Thunderbolt Display and the Mac's Power settings.
Hope this helps!!!
-
Oct 28, 2013 6:35 PM in response to Karl Kaufmannby John McPeake,I did this Karl, and it worked, thank you! That said, Apple needs to know that probably less than 3% of their users read these support threads. The Mavericks update needs to either be re-written or perform an SMC reset (or two) as part of the install. I'm sure there are (literally) millions of people that will have this same issue, which doesn't do great things for customer sat...
-
Oct 29, 2013 3:54 PM in response to brian_marsby epgraeff,Same problem, same solution.
MacBook Pro didn't detect Thunderbolt display after upgrade to Mavericks.
SMC reset solved it.
-
Oct 30, 2013 3:37 PM in response to adrian-polglaseby Chris Such,Hi,
This fixed it for me ... temporarily.
I did the various resets to both the MBP & TBD. I left everything unplugged from the TBD and the next morning it woke up correctly. Last night however, I plugged all the hard drives back in (along with ethernet) and this morning, the problem was back again.
I am going to test various configurations over the next few days to see if I can pin it down any further.
Cheers, Chris.
-
Nov 1, 2013 5:01 AM in response to brian_marsby adrian-polglase,I'd like to chip in and also say the problem was only fixed for me temporarily after doing an SMC and Monitor Reset. Might get back onto Apple soon and see what they have to say.
Grrrrr.
-
Nov 1, 2013 10:21 AM in response to brian_marsby brian_mars,OP here.
I have tried the various solutions here and am still experiencing problems. In fact, a new symptom has appeared.
I can work uninterrupted, glitch-free for hours at a time, as long as I prevent it from going to sleep. If it does sleep (either automatically or intentionally), upon wake, the screens glitch out (pixelated squares over the majority of both screens and the system becomes unresponsive. Sometimes the cursor is still movable but keyboard never is. This always requires a reboot.
-
Nov 3, 2013 6:02 PM in response to brian_marsby R Harbick,Like many here my MacBook Pro 15" Mid 2011 refused to start my 27" Thunderbolt Monitor upon wake up from sleep mode. Just a real pain in the southern reachs getting it started. Did an SMC reset and problem fixed. It's at least worth a shot before you break out the Apple approved Chicken blood and Holy Waters.
-
Nov 4, 2013 8:39 AM in response to brian_marsby John Willsey,Hello Everyone,
I found this post series because of similiar behavior on my system as well. However I have a 2008 MacPro with 30" cinema display and 3rd party 20" display. Never had the issue till Mavericks. One additional bit of troubleshooting you might want to try, especially Adrian, since you still have applecare is enable ssh login and when it happens try to login from another computer. On mine, all processes are running fine, just no display and black screen. I also found that if I reset the Windows Display server, the system comes back without a reboot, but all previous open apps get relaunched and one still loses any open unsaved work....
sudo killall -HUP WindowServerIf you have this behavior, I'd suggest this issue is not macbook or thunderbolt related.
-
Nov 5, 2013 1:26 PM in response to R Harbickby One of the users,Same here (in other words, you're not alone guys). After 10.9/Mavericks upgrade my TBD is ignoring my MBP.
Tried the following w/out sucess - the problem still exists:
1) SMC reset
2) PRAM reset (I think it may have helped once)
3) Turning off the "Displays have separate spaces" settings
4) Connecting my wired keyboard to TBD, then to a USB hub, then directly to my MBP
What does work is unplugging TBD connection and pluging it back to my MBP. Only then it wakes up.
-
Nov 13, 2013 11:18 AM in response to brian_marsby crs1un,Glad I found this thread to learn I'm not alone with my TBD
I don't use MBP, I have a late 2012 Mac Mini also with second display attached via HDMI.
I've tried all the same things suggested, but no luck. The only fix has been to unplug and plug back in,
but that's not an option when I have thunderbolt HDs daisy chained for video editing, so I end up having to restart my system.
Looking forward to a fix.
-
Nov 14, 2013 3:16 PM in response to brian_marsby adrian-polglase,I was led to believe that the cause of this problem was to do with my user account, but I have since tried using a brand new admin account and have encountered the same problems... soooo with that, an SMC, PRAM and monitor reset, it's back to the drawing board...
Come on Apple!