Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

harshw

macrumors regular
Original poster
Feb 19, 2009
202
54
UPDATE: updated to MacOS 13.1 and the problem is still there

I am at my wits end with MacOS Ventura. I used the M1 Max MBP with my TB3 dock connected to two external LG 4KUL850 displays. Although the M1MBP wasnt as good as the Intel 2019 MBP with wake-from-sleep and external displays - if I disconnected and re-connected the TB3 cable from the MBP to the TB3 dock - it did wake up the macbook

After upgrading to Ventura - if the M1MBP goes to sleep, whether on power or on battery - it will simply not recognize ANY external displays whether connected to the TB3 dock or directly unless it is rebooted

Tested with
HP Envy 4K 27" monitor
LG UL850W 27" monitor

OWC TB3 Dock
CalDigit TS3+
Kensington TB3 dock


Has anyone on the forums gotten any M1 Mac (M1 studio or M1 MBP) working with MacOS Ventura and connected via a TB3 dock?

At this point the M1MBP is unusable for my daily work so I can either
- roll back to MacOS 12
- sell it and buy a M1 Studio if that works better
- get rid of the LG monitors and buy two overpriced Studio Displays
- move off the mac platform entirely

Does anyone on the forums have a M1 Studio connected via a TB3 dock? does it work well with monitors connected via TB3 after wake-from-sleep?

I've tried different monitors (tried with 4K HP Envy), docks and cables, also tried all different settings in Security & Privacy and tried deleting the com.apple.windowserver.display.xxx plist files - all to no avail. I've submitted feedback to Apple and written to them but they're silent on this issue. I do see quite a few folks on the forum having problems with the combination of external displays, MacOS Ventura and M1 based macs - you'd think that Apple would rush some kind of bug fix but they don't seem to care about mac laptop users much ... no sign of a bug fix or any acknowledgement of the issue or anything at all

At this point - would like to be optimistic and upbeat on Apple but it's becoming increasingly difficult to do so :-(

Update: apparently the issue occurs most frequently with the combination of Apple Silicon, MacOS 13 and displays connected via USB-C/Thunderbolt whether directly or via a TB3 dock. Changing system preferences to prevent displays from sleeping when powered helps somewhat, as does changing the value of  > System Settings > Privacy & Security > "Allow accessories to connect" to Always (which is probably a big security risk)

All these fixes are band-aids as the problem will occur again when the USB-C/TB3 accessory is connected and the Macs go into deep sleep - which usually happens in a few hours to overnight. If the accessory isn't connected - it will work fine when the Mac wakes up.
 
Last edited:
  • Like
Reactions: robd003
Downgrading doesnt work either, I tried downgrading to Big Sur to Monterey and my display hasnt worked since updating to Ventura. MBP 2020 M1
 
Have you tried plugging the external displays directly into the Mac to see if the problem persists?

I have multiple LG displays plugged directly into my Studio Mac and don't have this issue at all. I suspect this is an issue with the dock you're using, but obviously it's a difficult problem to diagnose.
 
At this point the M1MBP is unusable for my daily work so I can either
- roll back to MacOS 12
- sell it and buy a M1 Studio if that works better
- get rid of the LG monitors and buy two overpriced Studio Displays
- move off the mac platform entirely
It's not unusable. Try setting the MacBook Pro to never sleep when connected to the power adapter. Use a hot corner to put turn off the displays or just let them turn off after a set time.

Screenshot 2022-11-27 at 6.08.40 AM.png
 
I suspect this is an issue with the dock you're using

I've used the following docks with the same result:

- Kensington TB3 dock
- Caldigit TS3 Plus dock
- OWC TB3 dock

All three exhibit the same behavior. I can understand one dock being problematic - but all three docks exhibiting the same behavior under MacOS 13 - especially when MacOS 12 was a lot better in this regard - points to a software issue rather than a hardware problem with the docks ...
 
It's not unusable. Try setting the MacBook Pro to never sleep when connected to the power adapter. Use a hot corner to put turn off the displays or just let them turn off after a set time.

View attachment 2119426

Yes I have that setting enabled. I found it through trial and error that reduces the occurrence of the problem - but it does not eliminate it entirely.

One issue I have is that I have two MacBook Pros that I switch between - so the problem comes when the M1 MBP is on battery and goes to sleep.

The other issue is that even on the power adapter with that setting, the M1 MBP will sometimes go into deep sleep, say if you leave it for a couple of days. And then it's the same behavior - the M1 MBP won't recognize displays until you reboot the machine
 
I've used the following docks with the same result:

- Kensington TB3 dock
- Caldigit TS3 Plus dock
- OWC TB3 dock

All three exhibit the same behavior. I can understand one dock being problematic - but all three docks exhibiting the same behavior under MacOS 13 - especially when MacOS 12 was a lot better in this regard - points to a software issue rather than a hardware problem with the docks ...
Did you try what I said in my previous post (plugging in directly to the Mac instead of the Dock(s)?
 
Kind of the same problem here.
I'm on Ventura with 14"MBP & Apple Studio Display.
When I plug in the TB cable from the Studio Display the display turn on/off every 3 seconds.

To resolve it temporarly I have to reboot my MBP with the TB cable attached to the MBP.
 
Both my M1 Mini and M1 MacBook Pro 14 inch will not output video via USB C or USB C to HDMI. Today I wiped my Mac mini and reinstalled macOS using Apple Configurator on another Mac and it still will not work. I called Apple explained to support that the issue occurs on multiple Macs, multiple monitors, multiple cables, etc basically it has to either 1 be software related or 2 an update somewhere in macOS 13 has broken something related to USB C. Because it's not related to 1 Mac. All they could tell me was "take it to the Apple Store".
 
Both my M1 Mini and M1 MacBook Pro 14 inch will not output video via USB C or USB C to HDMI. Today I wiped my Mac mini and reinstalled macOS using Apple Configurator on another Mac and it still will not work. I called Apple explained to support that the issue occurs on multiple Macs, multiple monitors, multiple cables, etc basically it has to either 1 be software related or 2 an update somewhere in macOS 13 has broken something related to USB C. Because it's not related to 1 Mac. All they could tell me was "take it to the Apple Store".
Try booting to Recovery - press & hold power button on startup. If you’re getting video there, then it might be related to macOS. If you’re not, it’s probably something with the specific USB-C cables you’re using. I have two M1 minis, both work with USB-C displays (one using USB-C to HDMI cable, one using USB-C to USB-C directly on the display).

“Take it to the store” is probably good advice, so they can test your cable on a known-working Mac & display, and your Mac on a known-working cable & display.
 
Try booting to Recovery - press & hold power button on startup. If you’re getting video there, then it might be related to macOS. If you’re not, it’s probably something with the specific USB-C cables you’re using. I have two M1 minis, both work with USB-C displays (one using USB-C to HDMI cable, one using USB-C to USB-C directly on the display).

“Take it to the store” is probably good advice, so they can test your cable on a known-working Mac & display, and your Mac on a known-working cable & display.
I’ve tried 2 C to C cables including the one I had been using that came with the monitor and worked fine. I tried C to HDMI. I’ve tried 2 monitors and 2 macs. I’ve ruled out everything it has to be software.
 
Did you try what I said in my previous post (plugging in directly to the Mac instead of the Dock(s)?
I have not because of how I work with two MBPs (one for home and another for office). It will take time to set it up so that the monitors are plugged in directly and everything else goes to a dock - will need to do that over the coming week.

Keep in mind that the exact config worked under MacOS 12 (both the 2019 MBP and 2021 MBP were able to turn on when the TB3 cable was reconnected) so that pretty much rules out the dock(s) - else why would it work under 12 and not 13?

What connections are you using from your Mac Studio? TB3/USB-C to USB-C or HDMI/DP ?
 
Some docks have their own video driver that needs to be updated after updating macOS.
Do you have a link for that? I thought TB3 docks are passthrough i.e. they dont have or do any video processing whatsoever

AFAIK, none of the three docks I have used have any 'driver' - they have utilities for ejecting USB mass storage drives but that is more a convenience than a necessary driver
 
Keep in mind that the exact config worked under MacOS 12 (both the 2019 MBP and 2021 MBP were able to turn on when the TB3 cable was reconnected) so that pretty much rules out the dock(s) - else why would it work under 12 and not 13?
Keep in mind that you're not running macOS 12 anymore. Every OS brings new issues. The fact that it worked before is now irrelevant, much to our frustration. "It worked fine before the update" is the most common issue people have.

You've got to narrow down the possibilities here, so if you're not willing to try things because they're slightly inconvenient, then you'll be stuck with the issue you're having.
 
Last edited by a moderator:
  • Like
Reactions: eltoslightfoot
Do you have a link for that? I thought TB3 docks are passthrough i.e. they dont have or do any video processing whatsoever

AFAIK, none of the three docks I have used have any 'driver' - they have utilities for ejecting USB mass storage drives but that is more a convenience than a necessary driver

The docks I use regularly have firmware and drivers that are updated occasionally. Sometimes the drivers are on the dock and sometimes they're for your laptop's OS. I don't believe the TS3+ needs a display driver (i.e. DisplayLink), but it definitely has firmware updates.
 
The docks I use regularly have firmware and drivers that are updated occasionally. Sometimes the drivers are on the dock and sometimes they're for your laptop's OS. I don't believe the TS3+ needs a display driver (i.e. DisplayLink), but it definitely has firmware updates.
Yep that's one the things I checked - the TS3+ has had only one firmware update (v44.1) and I do have it, actually the dock came with that firmware.

Reached out to CalDigit asking if they have any firmware update for this issue - let's see what they come back with ...
 
I upgraded my Intel 2019 MacBook Pro to MacOS 13.1 and it works fine with the TB3 dock + displays. It wakes up from sleep without problems and wakes the displays up properly.

Updated to MacOS 13.1 on my M1 Macbook Pro and the problem still exists. Same behavior - the computer goes to sleep and after waking up the external displays either wont get recognized if they are connected via TB3 or then they act weird & glitchy or stay off when connected directly (update verified that even directly connected displays don't wake up or show any display when the MBP wakes from sleep)

Looking at the forums - there's a significant number of people on the forums who have issues with M1 Macs and external displays. Makes one wonder what Apple is doing so far to address this.
 
Last edited:
Same issue noticed.

I have Macbook M2 Air in Clamshell mode connected using:

- Dell S2723DGF 27" 1440p at @144Hz connected to my dock via DisplayPort 1.2 cable
- HP USB-C Dock G5 on latest firmware
- Ventura 13.0.1

1. If I try to wake up my my monitor by pressing keyboard only 20 minutes after my Mac goes to sleep it wakes up with no issue.

2. If I come back from work next day and try to wake up, it won't wake up monitor. But when I pickup my laptop and open lid I see it already woke up and it's on Lock Screen. Still monitor does not wake up. Disconnecting and reconnecting usb-c cable to docking station fixes the issue but it's temporary.

3. I did not have this issue with my old work Intel MacBook Pro 2019 on Monterey or my personal Dell XPS 13 laptop running Linux.

Also both Linux (via LVFS) and Windows supported firmware upgrade of my docking station just fine. Not sure if I can still do that using MacOS.
 
  • Like
Reactions: harshw
I am working with a MacBook Pro M1 with two external LG Ultrafine monitors. one connected straight to and 1 througha TB4 OWC dock (not the hub). I do find some quirky behaviour now and then (auto on/off scheduleer lost in MacOS an often have to start manually) but generally all is working as expected (both screens operational with lid closed).
 
  • Like
Reactions: harshw
Maybe because Apple changed the `hibernatemode`
Looking at https://apple.stackexchange.com/que...yhigh-and-standbydelaylow-on-macbook-pro-2021 we don't get all settings on a M1/M2

I forced hibernate (you can check the timestamp of your sleepimage) but could not reproduce the issue

Code:
❯ ls -la /var/vm/sleepimage

-rw------T  1 root  wheel  1837105152 Dec 17 12:12 /var/vm/sleepimage

Maybe changing the `hibernatemode` back to 0 fixes it. Just don't travel too long with your MacBook then :)
 
Same issue noticed.

I upgraded my LG monitor firmware from 3.03 to 3.18, tried with setting the Display Port versions to 1.1, 1.2, 1.4 - even tried connecting the monitors directly via USB-C. The docks all have the latest firmware except for the Kensington dock - where they wont let me have the firmware because 'it's out of warranty'

perhaps we should start collecting info on what does work
I am working with a MacBook Pro M1 with two external LG Ultrafine monitors. one connected straight to and 1 througha TB4 OWC dock

What is the model of the LG Ultrafine that you’re using?

Maybe because Apple changed the `hibernatemode`
Looking at https://apple.stackexchange.com/que...yhigh-and-standbydelaylow-on-macbook-pro-2021 we don't get all settings on a M1/M2

There’s something to that. If I change  > System Settings > Privacy & Security > "Allow accessories to connect" to Always and I disable sleep when displays are off - the problem occurs a lot less.

What it points do is that the Apple thunderbolt controller wakes up and doesn’t initialize the monitor correctly so ends up not waking the monitor.

What’s strange is that it worked under MacOS 12 so I wonder if there was some firmware update or code change for the TB4 controller under MacOS 13
 
Bash:
pmset -g log|grep -e " Sleep  " -e " Wake  "

You can see if we woke up from `Hibernate` or `DarkWake` or whatever. Next time I get the issue, I'll check what State changes happened.

Previously waking the display was also unreliable, but could be fixed by plugging/unplugging the cable. Since 13.x only a reboot fixes the issue
 
  • Like
Reactions: harshw
These combinations with my M1 Mac mini, Plugable Thunderbolt 4 hub, and these monitors all work with no sleep issues. Note I'm only running one monitor at a time. The only thing is that the monitor takes a few seconds to wake up. ie. Mac wakes up immediately, and then it's another several seconds before I see the macOS desktop on screen.

M1 Mac mini --> Plugable 5-in-1 Thunderbolt 4 hub --> USB-C Asus ProArt PA328CGV (32" 2560x1440 at native resolution)
M1 Mac mini --> Plugable 5-in-1 Thunderbolt 4 hub --> USB-C Asus ProArt PA329CV (32" 3840x2160 scaled to 2560x1440)
M1 Mac mini --> Plugable 5-in-1 Thunderbolt 4 hub --> USB-C Huawei MateView 28 (28.2" 3840x2560 scaled to 2304x1536)
M1 Mac mini --> Plugable 5-in-1 Thunderbolt 4 hub --> USB-C Club 3D CAC-1510 DL-DVI adapter --> Apple Cinema Display (30" 2560x1600 at native resolution)

I didn't like the ProArts, so I returned them. The ancient Apple Cinema Display has image retention and HDCP doesn't work (on Apple Silicon), so I've retired that. I'm currently running the MateView.
 
Last edited:
  • Like
Reactions: harshw
Previously waking the display was also unreliable, but could be fixed by plugging/unplugging the cable. Since 13.x only a reboot fixes the issue
^^^^^^
💯 this

Some folks on this thread were trying to gaslight claiming that it had nothing to do with the OS.

But I (and others) have had this exact problem. MacOS 12 was something I could live with because all you had to do was disconnect & reconnect the cable

But MacOS 13 just makes the mbp unusable
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.