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 5 of 12 last Next
  • by Mlenny,

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

    Submitted Bug Report Too: 23897677.

  • by NiksApples,

    NiksApples NiksApples Dec 15, 2015 1:28 PM in response to Ruoyu
    Level 1 (12 points)
    Mac OS X
    Dec 15, 2015 1:28 PM in response to Ruoyu

    Same issue here. I have MacPro Late 2013, AMD FirePro D300, 2 Dell P2715Q 4K monitors and I can confirm the annoying issue with the monitors not waking up after go to sleep, after updating to 10.11.2. Some people here suggested that you should unplug/plug the monitors, but I found another (not so elegant) solution. In order to even get to my computer I VNC from another machine to mine, unlock, and then lock the screen remotely, after that my screens wake up and I can login. THIS IS ABSOLUTELY VERY SUPPER ANNOYING!!! "If you know what I mean" (some people around me say). I don't know how else to express my annoyance already to Apple. I've submitted a bug report on their site, but for so many years I've done this, I would doubt it that they will get back soon.

  • by Patrick Wilson1,

    Patrick Wilson1 Patrick Wilson1 Dec 15, 2015 11:21 PM in response to Ruoyu
    Level 1 (85 points)
    Dec 15, 2015 11:21 PM in response to Ruoyu

    Same issue. MacPro 2013, with Samsung UHD monitor using display port.

    Re-installed system software to 10.11.0 and system sleeps and wakes correctly.

    As soon as I updated to 10.11.2 the system will not wake at all. From any form of sleep.

    Bug reported: 23915985

     

    Apple this is serious. Please respond.

  • by Dak94,

    Dak94 Dak94 Dec 16, 2015 5:29 AM in response to Ruoyu
    Level 1 (0 points)
    Dec 16, 2015 5:29 AM in response to Ruoyu

    Same problem for me on a Macpro 2013 with D500 and the asus PB287Q.

     

    That was never perfect before and some time the screen do not wakeup on startup but after the last update, the wakeup only 1/10 time on startup.

     

    The other time the only solution i have to shutdown was to push the power botton of the macpro during 5 second.

     

    Seriously Apple, for the price of the Mac Pro, to have this problem with a screen, it is shameful.

  • by MarkPrzepiora,

    MarkPrzepiora MarkPrzepiora Dec 16, 2015 9:04 AM in response to Ruoyu
    Level 1 (0 points)
    Dec 16, 2015 9:04 AM in response to Ruoyu

    So like, has Apple even acknowledged this issue? This has been an on-again-off-again issue since I bought my display. Amazing how now it's even more broken after a software update. And it seems like the only reply you ever find from an actual Apple employee is a link to a completely irrelevant page.

     

    I bought myself a Mac Pro to use for work because I wanted a computer that would Just Work, would last me several years, wouldn't have to be fixed regularly, etc. In other words, I wanted a computer that wouldn't give me these issues and wouldn't waste my time and money in the form of lost productivity and frustration.

     

    This is totally bonkers. I have to fiddle with cables behind my several thousand dollar workstation computer just to get it to wake up after I go get a cup of coffee.

     

    My next upgrade is a Linux box with a MacBook on the side for Creative Suite.

  • by Ruoyu,

    Ruoyu Ruoyu Dec 16, 2015 11:53 AM in response to MarkPrzepiora
    Level 1 (0 points)
    Dec 16, 2015 11:53 AM in response to MarkPrzepiora

    I think at least they are reading this issue. on my bug report page, it says: Duplicate of 23828280 (Closed).

    this probably means they are taking a look.

  • by andrewkendall,

    andrewkendall andrewkendall Dec 16, 2015 2:01 PM in response to Ruoyu
    Level 1 (0 points)
    Dec 16, 2015 2:01 PM in response to Ruoyu

    Has anyone tried out OS X 10.11.3 beta yet?

  • by Ruoyu,

    Ruoyu Ruoyu Dec 16, 2015 3:21 PM in response to andrewkendall
    Level 1 (0 points)
    Dec 16, 2015 3:21 PM in response to andrewkendall

    I am still downloading 10.11.3 beta, I will let you know when it is installed. but it seems the connection is very slow here, only 2kb per second?

    I will try downthemall on Firefox.

    I think Apple will fix it in 10.11.3

  • by Cody_G,

    Cody_G Cody_G Dec 16, 2015 10:56 PM in response to Ruoyu
    Level 1 (0 points)
    Dec 16, 2015 10:56 PM in response to Ruoyu

    Heh mine is a duplicate of 23848748 but still open

  • by Cody_G,

    Cody_G Cody_G Dec 16, 2015 11:00 PM in response to Cody_G
    Level 1 (0 points)
    Dec 16, 2015 11:00 PM in response to Cody_G

    Actually, I'm curious.

     

    How many of you are using non-apple keyboards? I have been using a Corsair RGB gaming keyboard, and recently changed to the new apple bluetooth keyboard, seems I haven't had this problem since. (maybe just coincidence). This may explain why they haven't seen it as they may all be on pure apple hardware. Shot in the dark. Either way, I sent my diagnostic to them.

     

    I also encourage you guys to do a system diagnostic when reporting these bugs and attach the sysdiagnose file

     

    ...

     

    --- Sysdiagnose Instructions ---  How to run sysdiagnose  1) Enter the keyboard shortcut:  Command + Option + Control + Shift + period (.)  The command takes a few minutes to complete.  The compressed output file appears in /var/tmp. The folder should open once it's done.  Ex. file in /private/var/tmp: sysdiagnose_Aug.28.2012_13-56-53.tar.gz  2) You can also run sysdiagnose from the Terminal manually using these steps:  2.1) Launch Terminal.app (/Applications/Utilities/Terminal.app) 2.2) Enter the command text below followed by the Return key on the Terminal command line:  sudo ./sysdiagnose  2.3) Enter your admin password when prompted and wait for the all of the sysdiagnose processes to finish. 2.4) Attach the output file that looks like this: sysdiagnose-date-time.tar.gz that is written into the /tmp directory to the bug.

  • by Ruoyu,

    Ruoyu Ruoyu Dec 17, 2015 2:11 AM in response to Cody_G
    Level 1 (0 points)
    Dec 17, 2015 2:11 AM in response to Cody_G

    HI Cody, thank you very much for the reply, I have a usb apple keyboard, Magic Mouse and magic touchpad 2 , but the issue persists. Maybe I need to try the wireless keyboard?

  • by Paul Rutherford1,

    Paul Rutherford1 Paul Rutherford1 Dec 17, 2015 8:10 AM in response to Cody_G
    Level 1 (14 points)
    Dec 17, 2015 8:10 AM in response to Cody_G

    I have Magic Keyboard and Magic Trackpad 2 and problem persists for me.

  • by Cody_G,

    Cody_G Cody_G Dec 17, 2015 8:26 AM in response to Paul Rutherford1
    Level 1 (0 points)
    Dec 17, 2015 8:26 AM in response to Paul Rutherford1

    Ok that's out

     

    I just noticed that 10.11.3 was installed yesterday and I didn't realize it (I was out yesterday). Maybe that's why I'm not having issues now.

  • by andrewkendall,

    andrewkendall andrewkendall Dec 17, 2015 11:46 AM in response to Cody_G
    Level 1 (0 points)
    Dec 17, 2015 11:46 AM in response to Cody_G

    So we think 10.11.3 fixes this? I'm not keen on installing a beta on my main production machine, but this bug is so annoying that I'm tempted to risk it. Anyone else installed the beta and still had the issue?

  • by aydinj,

    aydinj aydinj Dec 17, 2015 11:50 AM in response to Ruoyu
    Level 1 (0 points)
    Dec 17, 2015 11:50 AM in response to Ruoyu

    I have the same problem. I don't know why mac pro has many problem with sleep mode. My sound card had problem now my monitor too. Mac pro is the worst apple product that i had. waste of money

first Previous Page 5 of 12 last Next