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

I can confirm that with 10.11.3, you will still NOT get any video to a 4K monitor out if you have FileVault enabled. The good news is that I was able to clean the dust from around the Mac Pro at this point as it's been sitting idle on my desk for months....

Hi all,

I updated to 10.11.3 shortly after final version came out (a week ago?). Prior to that and while using 10.11.2, I had consistent lock-ups after a display sleep with my 4K monitor. The only way I could use 10.11.2 was to disable display sleep in Energy CP and just manually powered down display and re-powered back on later when I wanted to use. For 10.11.1, I could not use this version at all because of multiple install/boot-up issues, so just used 10.10.5 until 10.11.2 came out.

Anyway, when 10.11.3 came out, I was hoping it would solve the display lock-up problems that I and many others have encountered in this thread. My computer did run fine for a number of days until today when locked up again. I used my computer earlier today, maybe a couple hours before the lockup and the display did come out of it's sleep with no problem. But I took a break and encountered the lock-up about an hour later. I had to reboot to get out of lock-up. I have since gone back into Energy CP to disable display sleep and will manually power down/up display as before using 10.11.2..

So I'm now hoping 10.11.4 will provide a fix to my display lock-up problem, although I'm able to use my Mac Pro (late 2013) with no problems when the display is manually powered up. Btw, I'm attaching the last 3-4 minutes from console error log prior to reboot in case anyone can decipher anything important. I can't make anything out except for WindowServer unresponsive error, which may be a side effect of lock-up.

Thanks and Good Luck to everyone else! :-)

Paul

---

1/24/16 3:36:05.029 PM com.apple.WebKit.WebContent[4908]: [15:36:05.029] <<<< IQ-CA >>>> piqca_setUsePreQueue: (0x7fecda028400) rejecting report of layer being serviced - IQ has not yet begun to update

1/24/16 3:36:05.029 PM com.apple.WebKit.WebContent[4908]: [15:36:05.029] FigAgglomeratorSetObjectForKey signalled err=-16020 (kFigStringConformerError_ParamErr) (NULL key) at /Library/Caches/com.apple.xbs/Sources/CoreMedia/CoreMedia-1731.15.33/Prototypes /LegibleOutput/FigAgglomerator.c line 92

1/24/16 3:36:05.035 PM com.apple.WebKit.WebContent[4908]: [15:36:05.035] <<<< IQ-CA >>>> piqca_setUsePreQueue: (0x7fecda83e600) rejecting report of layer being serviced - IQ has not yet begun to update

1/24/16 3:36:05.035 PM com.apple.WebKit.WebContent[4908]: [15:36:05.035] FigAgglomeratorSetObjectForKey signalled err=-16020 (kFigStringConformerError_ParamErr) (NULL key) at /Library/Caches/com.apple.xbs/Sources/CoreMedia/CoreMedia-1731.15.33/Prototypes /LegibleOutput/FigAgglomerator.c line 92

1/24/16 3:36:05.043 PM AppleIDAuthAgent[572]: SERVER checkAccount: Apple ID "ma...33@???.???" doesn't have a password; no next action. (checkAccountAndDetermineNextAction()/AppleIDAuthenticationImpl.cpp #1681) client 504

1/24/16 3:36:05.077 PM AppleIDAuthAgent[572]: SERVER checkAccount: Apple ID "ma...33@???.???" doesn't have a password; no next action. (checkAccountAndDetermineNextAction()/AppleIDAuthenticationImpl.cpp #1681) client 504

1/24/16 3:36:05.093 PM sharingd[504]: 15:36:05.093 : Discoverable mode changed to Contacts Only

1/24/16 3:36:05.093 PM sharingd[504]: 15:36:05.093 : BTLE scanning started

1/24/16 3:36:05.093 PM sharingd[504]: 15:36:05.093 : Scanning mode Contacts Only

1/24/16 3:36:05.094 PM sharingd[504]: 15:36:05.094 : BTLE scanner Powered On

1/24/16 3:36:05.000 PM kernel[0]: IOThunderboltSwitch<0>(0x0)::listenerCallback - Thunderbolt HPD packet for route = 0x0 port = 12 unplug = 0

1/24/16 3:36:05.000 PM kernel[0]: IOThunderboltSwitch<0>(0x0)::listenerCallback - Thunderbolt HPD packet for route = 0x0 port = 12 unplug = 1

1/24/16 3:36:22.065 PM watchdogd[304]: [watchdog_daemon] @(_wd_daemon_service_thread) - service (com.apple.WindowServer) reported as unresponsive

1/24/16 3:36:26.347 PM spindump[664]: Saved userspace_watchdog_timeout.spin report for WindowServer version ??? (???) to /Library/Logs/DiagnosticReports/WindowServer_2016-01-24-153626_Pauls-Mac-Pro.us erspace_watchdog_timeout.spin

1/24/16 3:36:26.365 PM watchdogd[304]: [watchdog_daemon] @(__wd_service_report_unresponsive_block_invoke) - spindump gathered for (com.apple.WindowServer) at (/Library/Logs/DiagnosticReports/WindowServer_2016-01-24-153626_Pauls-Mac-Pro.u serspace_watchdog_timeout.spin)

1/24/16 3:36:37.000 PM kernel[0]: Sound assertion in AppleHDADriver at line 3033

1/24/16 3:36:38.000 PM kernel[0]: IOThunderboltSwitch<0>(0x0)::listenerCallback - Thunderbolt HPD packet for route = 0x0 port = 12 unplug = 0

1/24/16 3:36:38.000 PM kernel[0]: IOThunderboltSwitch<0>(0x0)::listenerCallback - Thunderbolt HPD packet for route = 0x0 port = 12 unplug = 1

1/24/16 3:36:47.196 PM watchdogd[304]: [watchdog_daemon] @(_wd_daemon_service_thread) - service (com.apple.WindowServer) reported as unresponsive

1/24/16 3:36:49.320 PM spindump[664]: Saved userspace_watchdog_timeout.spin report for WindowServer version ??? (???) to /Library/Logs/DiagnosticReports/WindowServer_2016-01-24-153649_Pauls-Mac-Pro.us erspace_watchdog_timeout.spin

1/24/16 3:36:49.321 PM watchdogd[304]: [watchdog_daemon] @(__wd_service_report_unresponsive_block_invoke) - spindump gathered for (com.apple.WindowServer) at (/Library/Logs/DiagnosticReports/WindowServer_2016-01-24-153649_Pauls-Mac-Pro.u serspace_watchdog_timeout.spin)

1/24/16 3:37:07.485 PM com.apple.WebKit.WebContent[4908]: [15:37:07.485] <<<< IQ-CA >>>> piqca_setUsePreQueue: (0x7fecda028400) rejecting report of layer being serviced - IQ has not yet begun to update

1/24/16 3:37:07.485 PM com.apple.WebKit.WebContent[4908]: [15:37:07.485] <<<< IQ-CA >>>> piqca_setUsePreQueue: (0x7fecda83e600) rejecting report of layer being serviced - IQ has not yet begun to update

1/24/16 3:37:07.485 PM com.apple.WebKit.WebContent[4908]: [15:37:07.485] <<<< IQ-CA >>>> piqca_setUsePreQueue: (0x7fecda028400) rejecting report of layer being serviced - IQ has not yet begun to update

1/24/16 3:37:07.485 PM com.apple.WebKit.WebContent[4908]: [15:37:07.485] <<<< IQ-CA >>>> piqca_setUsePreQueue: (0x7fecda83e600) rejecting report of layer being serviced - IQ has not yet begun to update

1/24/16 3:37:07.912 PM com.apple.WebKit.WebContent[4908]: [15:37:07.912] FigFileForkOpenMainByCFURL signalled err=35 (errno) (open failed) at /Library/Caches/com.apple.xbs/Sources/CoreMedia_frameworks/CoreMedia-1731.15.33 /Sources/Platform/Darwin/DarwinFile.c line 456

1/24/16 3:37:07.912 PM com.apple.WebKit.WebContent[4908]: [15:37:07.912] <<<< FigFile >>>> FigFileForkOpenMainByCFURL: opening url "file:///var/folders/jk/0_jgpvx56q1dr3tl3j_q0nj80000gn/T//MediaCache/CachedMedi a-PhU7pR", path "/var/folders/jk/0_jgpvx56q1dr3tl3j_q0nj80000gn/T//MediaCache/CachedMedia-PhU7p R" options 0x00000480 failed errno 35 Resource temporarily unavailable

1/24/16 3:37:07.924 PM com.apple.WebKit.WebContent[4908]: [15:37:07.924] FigFileForkOpenMainByCFURL signalled err=35 (errno) (open failed) at /Library/Caches/com.apple.xbs/Sources/CoreMedia_frameworks/CoreMedia-1731.15.33 /Sources/Platform/Darwin/DarwinFile.c line 456

1/24/16 3:37:07.924 PM com.apple.WebKit.WebContent[4908]: [15:37:07.924] <<<< FigFile >>>> FigFileForkOpenMainByCFURL: opening url "file:///var/folders/jk/0_jgpvx56q1dr3tl3j_q0nj80000gn/T//MediaCache/CachedMedi a-kvUxTm", path "/var/folders/jk/0_jgpvx56q1dr3tl3j_q0nj80000gn/T//MediaCache/CachedMedia-kvUxT m" options 0x00000480 failed errno 35 Resource temporarily unavailable

1/24/16 3:37:07.924 PM com.apple.WebKit.WebContent[4908]: [15:37:07.924] FigFileForkOpenMainByCFURL signalled err=35 (errno) (open failed) at /Library/Caches/com.apple.xbs/Sources/CoreMedia_frameworks/CoreMedia-1731.15.33 /Sources/Platform/Darwin/DarwinFile.c line 456

1/24/16 3:37:07.924 PM com.apple.WebKit.WebContent[4908]: [15:37:07.924] <<<< FigFile >>>> FigFileForkOpenMainByCFURL: opening url "file:///var/folders/jk/0_jgpvx56q1dr3tl3j_q0nj80000gn/T//MediaCache/CachedMedi a-Rkn3oZ", path "/var/folders/jk/0_jgpvx56q1dr3tl3j_q0nj80000gn/T//MediaCache/CachedMedia-Rkn3o Z" options 0x00000480 failed errno 35 Resource temporarily unavailable

1/24/16 3:37:07.927 PM com.apple.WebKit.WebContent[4908]: [15:37:07.927] FigFileForkOpenMainByCFURL signalled err=35 (errno) (open failed) at /Library/Caches/com.apple.xbs/Sources/CoreMedia_frameworks/CoreMedia-1731.15.33 /Sources/Platform/Darwin/DarwinFile.c line 456

1/24/16 3:37:07.927 PM com.apple.WebKit.WebContent[4908]: [15:37:07.927] <<<< FigFile >>>> FigFileForkOpenMainByCFURL: opening url "file:///var/folders/jk/0_jgpvx56q1dr3tl3j_q0nj80000gn/T//MediaCache/CachedMedi a-Rkn3oZ", path "/var/folders/jk/0_jgpvx56q1dr3tl3j_q0nj80000gn/T//MediaCache/CachedMedia-Rkn3o Z" options 0x00000480 failed errno 35 Resource temporarily unavailable

1/24/16 3:37:09.191 PM com.apple.WebKit.WebContent[4908]: <<<< FigByteStream >>>> FigByteStreamStatsLogOneRead: ByteStream read of 8 bytes @ 6919 took 0.613576 sec. to complete, 1 reads >= 0.5 sec.

1/24/16 3:37:09.200 PM com.apple.WebKit.WebContent[4908]: [15:37:09.200] FigAgglomeratorSetObjectForKey signalled err=-16020 (kFigStringConformerError_ParamErr) (NULL key) at /Library/Caches/com.apple.xbs/Sources/CoreMedia/CoreMedia-1731.15.33/Prototypes /LegibleOutput/FigAgglomerator.c line 92

1/24/16 3:37:09.204 PM com.apple.WebKit.WebContent[4908]: [15:37:09.204] <<<< IQ-CA >>>> piqca_setUsePreQueue: (0x7fecdb219600) rejecting report of layer being serviced - IQ has not yet begun to update

1/24/16 3:37:09.290 PM com.apple.WebKit.WebContent[4908]: <<<< FigByteStream >>>> FigByteStreamStatsLogOneRead: ByteStream read of 8 bytes @ 25654 took 0.710441 sec. to complete, 1 reads >= 0.5 sec.

1/24/16 3:37:09.536 PM com.apple.WebKit.WebContent[4908]: <<<< FigByteStream >>>> FigByteStreamStatsLogOneRead: ByteStream read of 8 bytes @ 12660 took 0.709081 sec. to complete, 1 reads >= 0.5 sec.

1/24/16 3:37:09.536 PM com.apple.WebKit.WebContent[4908]: <<<< FigByteStream >>>> FigByteStreamStatsLogOneRead: ByteStream read of 8 bytes @ 9840 took 0.986907 sec. to complete, 1 reads >= 0.5 sec.

1/24/16 3:37:09.926 PM com.apple.WebKit.WebContent[4908]: [15:37:09.926] FigAgglomeratorSetObjectForKey signalled err=-16020 (kFigStringConformerError_ParamErr) (NULL key) at /Library/Caches/com.apple.xbs/Sources/CoreMedia/CoreMedia-1731.15.33/Prototypes /LegibleOutput/FigAgglomerator.c line 92

1/24/16 3:37:09.930 PM com.apple.WebKit.WebContent[4908]: [15:37:09.930] <<<< IQ-CA >>>> piqca_setUsePreQueue: (0x7fecda1eba00) rejecting report of layer being serviced - IQ has not yet begun to update

1/24/16 3:37:09.939 PM com.apple.WebKit.WebContent[4908]: [15:37:09.939] FigAgglomeratorSetObjectForKey signalled err=-16020 (kFigStringConformerError_ParamErr) (NULL key) at /Library/Caches/com.apple.xbs/Sources/CoreMedia/CoreMedia-1731.15.33/Prototypes /LegibleOutput/FigAgglomerator.c line 92

1/24/16 3:37:09.943 PM com.apple.WebKit.WebContent[4908]: [15:37:09.943] <<<< IQ-CA >>>> piqca_setUsePreQueue: (0x7fecdb01d400) rejecting report of layer being serviced - IQ has not yet begun to update

1/24/16 3:37:10.350 PM com.apple.WebKit.WebContent[4908]: <<<< FigByteStream >>>> FigByteStreamStatsLogOneRead: ByteStream read of 8 bytes @ 30305 took 0.809272 sec. to complete, 1 reads >= 0.5 sec.

1/24/16 3:37:10.366 PM com.apple.WebKit.WebContent[4908]: <<<< FigByteStream >>>> FigByteStreamStatsLogOneRead: ByteStream read of 12040 bytes @ 750 took 0.702126 sec. to complete, 2 reads >= 0.5 sec.

1/24/16 3:37:10.377 PM com.apple.WebKit.WebContent[4908]: [15:37:10.377] FigAgglomeratorSetObjectForKey signalled err=-16020 (kFigStringConformerError_ParamErr) (NULL key) at /Library/Caches/com.apple.xbs/Sources/CoreMedia/CoreMedia-1731.15.33/Prototypes /LegibleOutput/FigAgglomerator.c line 92

1/24/16 3:37:10.381 PM com.apple.WebKit.WebContent[4908]: [15:37:10.381] <<<< IQ-CA >>>> piqca_setUsePreQueue: (0x7fecd3be5000) rejecting report of layer being serviced - IQ has not yet begun to update

1/24/16 3:37:10.782 PM com.apple.WebKit.WebContent[4908]: [15:37:10.782] FigAgglomeratorSetObjectForKey signalled err=-16020 (kFigStringConformerError_ParamErr) (NULL key) at /Library/Caches/com.apple.xbs/Sources/CoreMedia/CoreMedia-1731.15.33/Prototypes /LegibleOutput/FigAgglomerator.c line 92

1/24/16 3:37:10.786 PM com.apple.WebKit.WebContent[4908]: [15:37:10.786] <<<< IQ-CA >>>> piqca_setUsePreQueue: (0x7fecdb0c6000) rejecting report of layer being serviced - IQ has not yet begun to update

1/24/16 3:37:12.337 PM watchdogd[304]: [watchdog_daemon] @(_wd_daemon_service_thread) - service (com.apple.WindowServer) reported as unresponsive

1/24/16 3:37:14.549 PM spindump[664]: Saved userspace_watchdog_timeout.spin report for WindowServer version ??? (???) to /Library/Logs/DiagnosticReports/WindowServer_2016-01-24-153714_Pauls-Mac-Pro.us erspace_watchdog_timeout.spin

1/24/16 3:37:14.551 PM watchdogd[304]: [watchdog_daemon] @(__wd_service_report_unresponsive_block_invoke) - spindump gathered for (com.apple.WindowServer) at (/Library/Logs/DiagnosticReports/WindowServer_2016-01-24-153714_Pauls-Mac-Pro.u serspace_watchdog_timeout.spin)

1/24/16 3:37:37.481 PM watchdogd[304]: [watchdog_daemon] @(_wd_daemon_service_thread) - service (com.apple.WindowServer) reported as unresponsive

1/24/16 3:38:02.621 PM watchdogd[304]: [watchdog_daemon] @(_wd_daemon_service_thread) - service (com.apple.WindowServer) reported as unresponsive

1/24/16 3:38:17.000 PM kernel[0]: IOThunderboltSwitch<0>(0x0)::listenerCallback - Thunderbolt HPD packet for route = 0x0 port = 12 unplug = 0

1/24/16 3:38:17.000 PM kernel[0]: IOThunderboltSwitch<0>(0x0)::listenerCallback - Thunderbolt HPD packet for route = 0x0 port = 12 unplug = 1

1/24/16 3:38:21.000 PM kernel[0]: IOThunderboltSwitch<0>(0x0)::listenerCallback - Thunderbolt HPD packet for route = 0x0 port = 12 unplug = 0

1/24/16 3:38:23.000 PM kernel[0]: IOThunderboltSwitch<0>(0x0)::listenerCallback - Thunderbolt HPD packet for route = 0x0 port = 12 unplug = 1

1/24/16 3:38:27.760 PM watchdogd[304]: [watchdog_daemon] @(_wd_daemon_service_thread) - service (com.apple.WindowServer) reported as unresponsive

1/24/16 3:38:52.881 PM watchdogd[304]: [watchdog_daemon] @(_wd_daemon_service_thread) - service (com.apple.WindowServer) reported as unresponsive

1/24/16 3:39:18.021 PM watchdogd[304]: [watchdog_daemon] @(_wd_daemon_service_thread) - service (com.apple.WindowServer) reported as unresponsive

1/24/16 3:39:36.846 PM BezelServices 255.10[93]: ASSERTION FAILED: dvcAddrRef != ((void *)0) -[DriverServices getDeviceAddress:] line: 2789

1/24/16 3:39:36.846 PM BezelServices 255.10[93]: ASSERTION FAILED: dvcAddrRef != ((void *)0) -[DriverServices getDeviceAddress:] line: 2789

1/24/16 3:39:43.162 PM watchdogd[304]: [watchdog_daemon] @(_wd_daemon_service_thread) - service (com.apple.WindowServer) reported as unresponsive

1/24/16 3:40:08.300 PM watchdogd[304]: [watchdog_daemon] @(_wd_daemon_service_thread) - service (com.apple.WindowServer) reported as unresponsive

1/24/16 3:40:11.000 PM kernel[0]: USBF: 173654.996 IOUSBHIDDriver(AppleHIDMouse)::RearmInterruptRead returning error 0xe00002d8 (device is not ready), not issuing any reads to device

1/24/16 3:40:11.201 PM BezelServices 255.10[93]: ASSERTION FAILED: dvcAddrRef != ((void *)0) -[DriverServices getDeviceAddress:] line: 2789

I'm hoping this is an issue with OS X. I have a Dell 2415Q (24" 4K) and can't get it to wake from sleep if it's been asleep for more than 20 minutes or so. I had read online that it was a problem with the P2415Q and that the latest revision (A03) fixes the issue, though I have at least one report that the issue still exists with A03 (I have A02 and getting A03 means sending my new monitor in to Dell for a refurb... No way.).

I'm on 10.11.4 beta. I have mixed success with Cmd+F1/ Cmd+F2. I'm wondering now if it is OS X and plan on experimenting with Windows 10 in Bootcamp to see if the sleep/wake issues persist. In Bootcamp I'm using 15.11 Crimson driver (not the official Apple Bootcamp driver) for the AMD R9 M370X GPU, so maybe that has a fix for this issue.

Same problem with rMBP 13 Early 2015, OS X 10.11.3, and ASUS PB287Q. I am using the famed "Accell B143B-003J UltraAV Mini DisplayPort to DisplayPort 1.2 Cable" which everyone seems to like, but it does not make any difference. I think the problem started with 10.11.2, seems to maybe have gotten worse with 10.11.3 and it is driving me crazy. Rebooting definitely fixes it. Sometimes I can get the display to work again after sleep, sometimes I can't. Apple please fix!!!

Wake issue fixed with the latest OS X beta (15E33e).

An update to my post of Jan. 24, 2016. My 4K monitor has now been running well for the last 9-10 days on 10.11.3. What I think made a difference may be related to how my monitor was connected on my Mac Pro Thunderbolt buses. Shortly after my last post, I noticed that I had connected my 4K display on the same Thunderbolt bus as some of my other Thunderbolt devices (mostly a bunch of external hard drives). I found the following article that suggested putting the display on a separate bus, so I did this.

http://www.tekrevue.com/tip/mac-pro-thunderbolt-performance/

After making this change, I haven't since had a display sleep/wake-up problem with my 4K display, other than a separate (I think) unrelated issue below. Interestingly, I also found another article today about someone having a problem with sleep/wake-up on a Mac Pro with 3-4k displays, as well as another article on an iMac with a 5K display sleep/wake-up problem. See the 2 articles posted for Jan. 21. 2016.

http://macperformanceguide.com/

Regarding the separate unrelated issue, about 3-4 days ago I was trying to add some new hard drives (JBOD box) using the USB3 port on the Mac. The hard drives I had were E-Sata drives and I was trying to connect them using a USB to E-Sata interface device I had. I plugged in the interface device directly on my Mac USB3 port and my hard drives came online OK, but after a short time my 4K screen started acting weird with freezes, lock-ups, and no response. To get out of this, I had to reboot, but the problem came back. Eventually, I surmised the display problems may have something to do with the USB/E-Sata device, which btw needed power from the Mac USB3 port. So I moved the USB/E-Sata device to a separate self powered USB3 hub, and since then, no more weird problems encountered on my 4K display. and my drives are running fine. I have no other USB devices connected to my Mac USB3 ports which need power from the ports. Maybe there's a possible power problem on Mac Pro with USB ports that can affect the display graphics?

So I wanted to let others know of my recent 4K display experiences on my Mac Pro (late 2013) with D300 graphics. Hopefully, it will help someone else. If I run into any other problems, I will post here. Keeping my fingers crossed. :-)

Paul

Running 10.11.3 on a MBP 13 (Early 2015) with ASUS PB287Q 4K monitor, I finally figured out a fix:

Before reconnecting the monitor, unplug the monitor from the wall and plug it back in. Then when waking up the MBP, it always successfully connects to the monitor on the first try. This seems to be 100% reproducible for me.

Give it a try. But I really hope they fix this in 10.11.4!

It looks like this topic went a little dead with the release of 10.11.3 which seemed to fix most peoples problems including my own. I'd like to know if anyone who has upgraded to 10.11.4 experiences any problems because I will definitely wait a while before I upgrade and don't want my computer to get screwed up again.

I have a samsung U28E590 4K display and this issue happened in 10.11.2, but was fixed in 10.11.3.

Now i've installed 10.11.4 and the issue is back

Well done Apple

Well thats really unfortunate. Looks like I won't be updating anytime soon. Hopefully you had a Time Machine backup and can downgrade back to 10.11.3.

I installed 10.11.4 6 days ago. So far running pretty well with my 4K monitor. I had one instance of Display sleep lockup shortly after installing 10.11.4, but none since. This is similar to my experience with 10.11.3, so if you have a recent backup of 10.11.3, might be worth trying the 10.11.4 update.

I'm having this problem as well with my ASUS PB287Q. It's done it since the day I bought the computer, despite the OS version.

Changing Thunderbolt ports doesn't work, nor does using the power button to wake it up. I have found the problem to be specific to using a Displayport/Thunderbolt cable. When I use a HDMI/Thunderbolt cable, I have no issues. This doesn't work for me, since I have to use a DisplayPort cable to run my monitor at 60hz.

I'm taking my machine in to have it checked out. A $5k machine shouldn't have such a glaring bug.

Dj Twelvizm wrote:

I'm taking my machine in to have it checked out. A $5k machine shouldn't have such a glaring bug.

Its not your machine that is the problem, it is the OS software.

I am having exactly this same problem. Finally said goodbye to my trusty 30inch Cinema Display as Apple seem to have completely forgotten about a 4k/retina display of the quality of their old displays. I went for the Asus PB279Q which is a stunning monitor, but for love nor money i cannot once the system goes to sleep, get the display to recognise an input. Changing port doesn't do anything, the only way i can get the display to come back is to force the system to shutdown and restart. For a professional this is incredibly annoying.

I'm with you here a £7.5k system with the power it has should not have such a basic issue. I too am running via mini display port to use the full range of the monitor.

DaveedJackson wrote:

Changing port doesn't do anything, the only way i can get the display to come back is to force the system to shutdown and restart. For a professional this is incredibly annoying.

The situation with my Dell UP2414Qs (4K 24") is similar, if not quite as desperate. They will wake up from sleep but not every time. It has been this way -- exactly the same way, for the last 2 years, regardless of system updates, etc. The situation has never really improved.

My answer to this is to leave the system running 24x7 (the cylinder) and to use the power button to power the monitor on in the morning and off at night. That is the only thing that seems to work reliably. Also, I have "Displays have separate spaces" on in the "Mission Control" control panel. This causes all windows that were open on a particular display to "pop back" to right monitor (obviously not needed for a one monitor setup).

This combination makes life livable here. Of course, YMMV. Good luck!