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 8 of 12 last Next
  • by AppleNerd1984,

    AppleNerd1984 AppleNerd1984 Dec 28, 2015 9:22 AM in response to AppleNerd1984
    Level 1 (0 points)
    Dec 28, 2015 9:22 AM in response to AppleNerd1984

    The thing that is most frustrating about this is Apple pushed 4k/HiDPI displays so hard in their marketing for the 2013 Mac Pro. Then they never released a first-party display of their own. Then they outright break 3rd party display support.

     

    When I first saw the Mac Pro, I thought maybe they were re-committing to the Pro market segment. These days, I certainly don't feel that way.

  • by NycSmart1,

    NycSmart1 NycSmart1 Dec 29, 2015 6:13 PM in response to AppleNerd1984
    Level 1 (1 points)
    Dec 29, 2015 6:13 PM in response to AppleNerd1984

    I'm dealing with the same issue, though I turned on Filevault, and I can't get the Mac Pro to display anything on the 4K monitors at this point. It does work fine on my 14 year old 1600 x 1200 monitor, though I can't really work on this.

  • by andrewkendall,

    andrewkendall andrewkendall Dec 30, 2015 1:15 AM in response to Ruoyu
    Level 1 (0 points)
    Dec 30, 2015 1:15 AM in response to Ruoyu

    For me this has been one of the worst Apple bugs in years, it made my Mac Pro pretty much unusable for the past 20 days. As it's been Christmas I've been getting away with mainly working from my MacBook Pro, but today I decided to try reverting to 10.11.1 as I need to get back to full productivity. I already had the App Store installer for 10.11.1 backed up on a drive, so used that with DiskMaker X (http://diskmakerx.com/) to create a USB install drive. Booting from that I was able to install over the top of 10.11.2 without any issues. Hassle, but having everything back working was worth it. Hope that helps someone!

  • by MarkPrzepiora,

    MarkPrzepiora MarkPrzepiora Dec 31, 2015 3:01 PM in response to andrewkendall
    Level 1 (0 points)
    Dec 31, 2015 3:01 PM in response to andrewkendall

    > For me this has been one of the worst Apple bugs in years, it made my Mac Pro pretty much unusable for the past 20 days

     

    Hear, hear.

     

    I'm less annoyed by the bug itself—okay, maybe not, this is pretty awful—than I am with the fact that we have gotten zero communication from Apple on this issue. These are $3,000–$10,000 computers. What on earth is happening to Apple's OSX/Mac division?

  • by aydinj,

    aydinj aydinj Jan 1, 2016 10:45 PM in response to Ruoyu
    Level 1 (0 points)
    Jan 1, 2016 10:45 PM in response to Ruoyu

    The problem is not solved

  • by CodedGames,

    CodedGames CodedGames Jan 2, 2016 2:22 PM in response to Ruoyu
    Level 1 (8 points)
    Desktops
    Jan 2, 2016 2:22 PM in response to Ruoyu

    Also having this problem with 2013 Mac Pro with dual Samsung U590's. I have found that forcing the monitors to wake by going through menus and changing input + spamming CMD + F1 and CMD + F2 can get them to wake.

     

    Very glad that I am not the only person having this issue. Thought my Mac/Monitors actually had a hardware issue. Don't worry guys, as long as we make Apple aware of the problem it will get fixed.

     

    Filled a bug report (which everyone here should do).

  • by CodedGames,

    CodedGames CodedGames Jan 3, 2016 11:03 PM in response to CodedGames
    Level 1 (8 points)
    Desktops
    Jan 3, 2016 11:03 PM in response to CodedGames

    Ok I found a pretty reliable method of getting my monitors to wake up. So far it has worked 100% of the time for me.

     

    1. Wake computer by shaking mouse, clicking, tapping keys, whatever. Wait a couple seconds.

    2. Log in blind. If you only have one account it's pretty easy, just type your password and hit enter. This may be difficult depending on your setup.

    3. Spam CMD + F1 and CMD + F2 back and forth until monitor wakes up. Should take a few seconds.

     

    There you go! This method literally has saved my Mac Pro for me. The unplugging/replugging method was getting rather unreliable and the unnecessary wear and tear of it was bothering me. I also didn't like the leaving my computer and monitors on 24/7 either.

  • by Muzzman1,

    Muzzman1 Muzzman1 Jan 5, 2016 11:00 PM in response to CodedGames
    Level 1 (14 points)
    Jan 5, 2016 11:00 PM in response to CodedGames

    Thanks @CodedGames!  I've used your method no less than 20 times without fail, it has worked every time. 

     

    Thank you!

  • by aydinj,

    aydinj aydinj Jan 6, 2016 8:34 AM in response to Ruoyu
    Level 1 (0 points)
    Jan 6, 2016 8:34 AM in response to Ruoyu

    It is not working for me.

  • by Cody_G,

    Cody_G Cody_G Jan 6, 2016 8:42 AM in response to aydinj
    Level 1 (0 points)
    Jan 6, 2016 8:42 AM in response to aydinj

    It works for me if I keep hitting cmd-f1. Doesn't work if I toggle between f1 and f2

     

    Note: Make sure you have your f keys disabled without hitting the fn key. You can check by going into keyboard settings and verifying "Use all F1, F2, etc. keys as standard function keys" is unchecked.

  • by Cody_G,

    Cody_G Cody_G Jan 6, 2016 11:48 AM in response to Cody_G
    Level 1 (0 points)
    Jan 6, 2016 11:48 AM in response to Cody_G

    I got an email from Apple saying the latest 10.11.3b possibly fixes this issue. Willing to bet some of you have received one as well.

  • by Cody_G,

    Cody_G Cody_G Jan 6, 2016 12:11 PM in response to Cody_G
    Level 1 (0 points)
    Jan 6, 2016 12:11 PM in response to Cody_G

    Looks like 10.11.3b2 has fixed this issue for me.

  • by crhendo1,

    crhendo1 crhendo1 Jan 6, 2016 1:52 PM in response to Cody_G
    Level 1 (30 points)
    Jan 6, 2016 1:52 PM in response to Cody_G


    I to can confirm that the latest beta (build 15D13b) appears to have fixed this problem.

  • by Cody_G,

    Cody_G Cody_G Jan 6, 2016 5:19 PM in response to crhendo1
    Level 1 (0 points)
    Jan 6, 2016 5:19 PM in response to crhendo1

    Well, it worked, then it didn't.

  • by Patrick Wilson1,

    Patrick Wilson1 Patrick Wilson1 Jan 6, 2016 8:55 PM in response to crhendo1
    Level 1 (85 points)
    Jan 6, 2016 8:55 PM in response to crhendo1

    beta 2 10.11.3 worked for me. Fixed wake up issue. Using MacPro and Samsung U28E590 Display.

    Will report the overnight wake up tomorrow am.

first Previous Page 8 of 12 last Next