Ruoyu

Q: with 10.11.2, Mac Pro 2013 will not wake up 4k displays after sleep like before.

I have installed 10.11.2 today and found the Mac Pro will not wake up the 4k displays connected to thunderbolt ports. I tried many kinds of 4k displays including u28e590d, u24e590d, p2716q etc, but none of them would wake up after sleep. the only resolution is to unplug and replug the thunderbolt (display port) cable to a different thunderbolt port.

those displays all work perfectly with 10.11 and 10.11.1.

 

Steps to Reproduce:

1: have a Mac Pro 2013, any configurations and install 10.11.2

2: plug a 4k display like u28e590d to thunderbolt port using mini-displayport cable.

3: let the Mac Pro go sleep

4: when press a key or click the mouse, the Mac Pro will wake up but the 4k display will not wake up.

 

anyone is experiencing the same problem?

Posted on Dec 9, 2015 1:25 AM

Close

Q: with 10.11.2, Mac Pro 2013 will not wake up 4k displays after sleep like before.

  • All replies
  • Helpful answers

first Previous Page 10 of 12 last Next
  • by pacioccone,

    pacioccone pacioccone Jan 17, 2016 10:39 AM in response to CodedGames
    Level 1 (0 points)
    Jan 17, 2016 10:39 AM in response to CodedGames

    I've had a case opened with AppleCare since I purchased the Mac Pro in 2014 and the 2 Samsung U28D590 4K monitors. The original techs weren't able to solve the issue and I resorted to unplugging and plugging the cables back in to wake the monitors up from sleep and to force the monitors to wake during start up.

     

    I called today on a whim. The tech I spoke with today seemed knowledgeable and had me do a few steps which previous techs didn't walk me through.

     

    I'm currently on OS 10.11.2, Mac Pro (Late 2013), 3GHz 8-Core, 32 GB RAM, AMD FirePro D500 3072 MB

     

    When you follow these steps, the Display preferences will be wiped out so you'll have to set them again.

     

    1. Ensure the monitors cables are not plugged into Thunderbolt ports that are on the same bus on the Mac Pro. I have one connected top right and the other lower left.
    2. Open a Finder window, click Option, then Go and navigate to the Library folder.
    3. Navigate to /user/Library/Preferences/ByHost/.
    4. Delete the com.apple.windowserver.########-####-####-####-##########.plist file in the list including the *.plist.lockfile. There were 3 files in my Library folder and I got rid of them all.
    5. Navigate to /Macintosh HD/Library/Preferences/.
    6. Delete the com.apple.windowserver.plist file.
    7. Shut down the computer.
    8. Reset the PRAM during a restart of the computer.

     

    I tested by shutting down the compute, powered up and both monitors woke.

     

    I tested putting the computer to sleep, waited 3 minutes, woke the computer from sleep and both monitors woke.

     

    I hope this solution works for you as it seems to be working for me. And I've lived with it for almost 2 years!

     

     

  • by ProhibitedLovex,

    ProhibitedLovex ProhibitedLovex Jan 17, 2016 1:35 PM in response to NycSmart1
    Level 1 (0 points)
    Jan 17, 2016 1:35 PM in response to NycSmart1

    After reading most of the posts on this topic, I'm still at a lost and seeking solution. I've bought my 4K monitor over a month ago and have been waiting if any update from Apple will fix any problems. While awaiting, I've called both Apple Support and ASUS Customer Service. The Apple representative is saying it's a problem with the monitor since the Mac Pro fully supports 4k monitors and ASUS says the fault is on the computer's end because the computer is not recognizing the display. They are basically pointing fingers at each other but nothing is getting resolved. I thought maybe it's the cable but I've used different cables and no difference. Someone on YouTube have stated people with the higher end of the graphics' card which is D700 are having problems with the connection but that video was posted barely when Mac Pro Late 2013 came out. Now that I see this forum, both parties with lower or higher graphics' card is having problems so it's not just me. (I don't know if I'm relieved or more frustrated).

    Right now, I'm resorting to just turning off and on my Mac Pro, unplugging and plugging. I know I shouldn't because it can wear out the connection but do I really have an alternative?!

     

    (Monitor: ASUS PB287Q; Graphics Configuration: D700; Running: OSX El Capitan 10.11.2)

  • by Mlenny,

    Mlenny Mlenny Jan 17, 2016 1:51 PM in response to ProhibitedLovex
    Level 1 (0 points)
    Jan 17, 2016 1:51 PM in response to ProhibitedLovex

    like to post it again : i had the same problem with my macpro late 2013 and 2x samsung 4k displays after installing 10.11.2 before everything worked perfectly fine!! After that update the displays didn't wake up from sleep anymore, BUT after installing the BETA of 10.11.3 all worked AGAIN as before, without changing cables or anything else... So since 7-10days working under the beta 10.11.3 everything is fine!

     

    AS there should be a release very soon of this update i think most problems will be solved after apple releases 10.11.3 as again,

    now everything waking up from sleep and working with 2x 4k samsung 31.5" displays is as it shoulde be....

     

    I can feel your feustration, but just want to write that there might be abfix for your cases soon when 10.11.3 is out. Maybe (if you can't wait) install the public beta of 10.11.3 i have nor problems with that version...

  • by pacioccone,

    pacioccone pacioccone Jan 17, 2016 2:32 PM in response to Mlenny
    Level 1 (0 points)
    Jan 17, 2016 2:32 PM in response to Mlenny

    Thanks for your post. I must have missed your original reply. I have 10.11.3 beta installed on my laptop and it seems to be working well. Now I'm dying to get it installed on my Mac Pro so I can move on from this once and for all!

  • by ProhibitedLovex,

    ProhibitedLovex ProhibitedLovex Jan 17, 2016 4:11 PM in response to Mlenny
    Level 1 (0 points)
    Jan 17, 2016 4:11 PM in response to Mlenny

    Thank you ver much for reposting! I will be looking forward for the update!

  • by NycSmart1,

    NycSmart1 NycSmart1 Jan 17, 2016 4:45 PM in response to ProhibitedLovex
    Level 1 (1 points)
    Jan 17, 2016 4:45 PM in response to ProhibitedLovex

    Can anyone confirm the betas solve this issue with FileVault enabled? FileVault seems to have amplified the problem for me with no workaround.

  • by ProhibitedLovex,

    ProhibitedLovex ProhibitedLovex Jan 20, 2016 12:48 PM in response to NycSmart1
    Level 1 (0 points)
    Jan 20, 2016 12:48 PM in response to NycSmart1

    Apple just released a software update and I had just installed it. It works perfectly fine now. I've put it to sleep several times now and wake up every time. I honestly do not know about if you have FireVault enabled since I do not have mine enabled.

  • by AppleNerd1984,

    AppleNerd1984 AppleNerd1984 Jan 20, 2016 9:42 PM in response to Ruoyu
    Level 1 (0 points)
    Jan 20, 2016 9:42 PM in response to Ruoyu

    Installed 10.11.3 today, and sleep/wake on my Samsung 4K display has appeared to have returned to normal, finally.

  • by aydinj,

    aydinj aydinj Jan 21, 2016 3:03 AM in response to Ruoyu
    Level 1 (0 points)
    Jan 21, 2016 3:03 AM in response to Ruoyu

    My problem solved too but I think Apple must change their policy towards situations like this, it took near two months for fixing the problem. They must release hot fix and update sooner in these situations.

  • by pacioccone,

    pacioccone pacioccone Jan 21, 2016 6:04 AM in response to aydinj
    Level 1 (0 points)
    Jan 21, 2016 6:04 AM in response to aydinj

    Try 2 years! I reported this issue to them when I bought my Mac Pro and monitors February 2014.

  • by CodedGames,

    CodedGames CodedGames Jan 21, 2016 12:34 PM in response to Ruoyu
    Level 1 (8 points)
    Desktops
    Jan 21, 2016 12:34 PM in response to Ruoyu

    Well guys, so far so good. It appears that it has been fixed but I never was able to have the problem consistently so only time will tell if it's really fixed.

     

    I have learned to wait and check to forums to see if an update completely breaks my computer. Thank's Apple!

  • by DBBowser,

    DBBowser DBBowser Jan 21, 2016 1:20 PM in response to Ruoyu
    Level 1 (4 points)
    Mac OS X
    Jan 21, 2016 1:20 PM in response to Ruoyu

    10.11.3 has the fix for me.

     

    I have an Asus PB287Q connected via DisplayPort. All working now.

  • by Cody_G,

    Cody_G Cody_G Jan 21, 2016 9:28 PM in response to DBBowser
    Level 1 (0 points)
    Jan 21, 2016 9:28 PM in response to DBBowser

    DBBowser, do you have rev a or rev b? I have that same monitor and I can not get it to wake consistently under 10.11.3 or 10.11.4

  • by DBBowser,

    DBBowser DBBowser Jan 21, 2016 10:37 PM in response to Cody_G
    Level 1 (4 points)
    Mac OS X
    Jan 21, 2016 10:37 PM in response to Cody_G

    I can't seem to see a Rev on the label. The manufacture date is May 2014 if that helps. I am assuming it is Rev A because I pre-ordered it as soon as it had a listed price on Newegg. The one I have is an RMA replacement for the first one (DOA). I actually received it in June 2014.

     

    My testing process was:

     

    1. Restore Defaults on Energy Saver settings. I had turned off sleep for the Mac and the monitor as a work around.

    2. Reboot

    3. Force sleep from the Apple menu.

    4. Wait a few minutes (grab a coffee).

    5. Wake using mouse clicks (USB mouse)

     

    I have not had any problems when the computer falls asleep on its own either.

     

    Side note - I cannot get it to consistently wake from sleep with my USB Apple keyboard by hitting Spacebar or arrow keys, but I have not really spent any time testing that part yet.

  • by Patrick Wilson1,

    Patrick Wilson1 Patrick Wilson1 Jan 23, 2016 4:09 PM in response to DBBowser
    Level 1 (85 points)
    Jan 23, 2016 4:09 PM in response to DBBowser

    It appears the 10.11.4 beta15E27e has reintroduced the problem on a more hap hazard scale. 4K monitors wake up after short periods of sleep, but after longer periods such as 2 hours or more they do not respond to keyboard.  Apple needs to figure this out. Stay are 10.11.3 for now, but this indicates they don't know exactly what causes this.

first Previous Page 10 of 12 last Next