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

MacOS Ventura + M1 Macs + external displays

EugW said:
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.
Click to expand...
P.S. I should mention that some of the ProArts had macOS compatibility issues with early versions of Monterey that were fixed either by a ProArt firmware update or by updating the Mac to a later version of Monterey, or both. However, I didn’t see any of that since I only bought these monitors this month (December 2022) with recent firmwares, to use with a Ventura machine.
 
I have this problem, PLUS another one -- LG 4K Monitor (the USB-C one that came out before the TB version)...if running through a dock, in my case the TS4, it will not only have the sleep issue (which also happens without the dock) but the added bonus of reducing the refresh rate to 30 and no setting to change it (Only 30hz is available). CalDigit says it's a Mac issue, Apple gives a shrug.

Edit: I am able to get the 60hz option back if I run the monitor through the TS4 DisplayPort, but then it will never wake up and I have to unplug it and plug it in, which is why it sits plugged into the MBP along side the dock...
 
Last edited:
rickeames said:
I have this problem, PLUS another one -- LG 4K Monitor (the USB-C one that came out before the TB version)...if running through a dock, in my case the TS4, it will not only have the sleep issue (which also happens without the dock) but the added bonus of reducing the refresh rate to 30 and no setting to change it (Only 30hz is available). CalDigit says it's a Mac issue, Apple gives a shrug.

Edit: I am able to get the 60hz option back if I run the monitor through the TS4 DisplayPort, but then it will never wake up and I have to unplug it and plug it in, which is why it sits plugged into the MBP along side the dock...
Click to expand...
LG has released a lot of USB-C 4K monitors, including multiple UltraFine 4K monitors. They may behave differently from one another, due to having different firmwares, etc.

Also, it depends on which version of macOS you are running.
 
I just bought an LG Ultrafine 4K 32UN880 for a great deal on sale. The display looks great when its on but I am having all the same issues you guys described and more on Mac OS Ventura. I pretty much have tried all the settings mentioned to no avail. If I shut my MacBook m1 down with the USB C connected, the display shuts off and will not wake up. The only thing that works is disconnecting the power from the back of the display and plugging it back in. Every time I do this it seems to reset the scaling that I set on Mac OS display settings so that has to be fixed every time and is just a headache in general for someone who uses their Mac everyday.

In addition to that main issue, I am also having an issue where I shut down the MacBook and the display will somehow restart the Mac right back up, so essentially I have to shut it down twice every time unless the USB-C is disconnected. Lastly I have had mixed results where I have shutdown my M1 and the charging chime will continually repeat the sound like it's connecting to a power source over and over about every 5 seconds or so unless I disconnect the USB-C.

I have the display connected directly to my M1 MBP without any hub at the moment. Wondering if I should just return the monitor (I have 30 days), wait for an update or pray to the electronic Gods to bless this issue. Sounds like this isn't just an LG monitor issue but more of and Apple OS issue at the moment?
 
I tried hard to get my mac to *not* wake from sleep, because I think it's a problem with iterating connected TB devices and then going back to sleep. I tried to tinker with pmset and a tool called sleepaid.
These are my current settings and the problem didn't appear since.

Bash: 
❯ pmset -g custom
Battery Power:
 Sleep On Power Button 1
 lowpowermode         0
 standby              1
 ttyskeepawake        0
 hibernatemode        3
 powernap             0
 hibernatefile        /var/vm/sleepimage
 displaysleep         2
 womp                 0
 networkoversleep     0
 sleep                1
 lessbright           1
 tcpkeepalive         0
 disksleep            10
 SleepServices        0
AC Power:
 Sleep On Power Button 1
 lowpowermode         0
 standby              1
 ttyskeepawake        0
 hibernatemode        3
 powernap             0
 hibernatefile        /var/vm/sleepimage
 displaysleep         10
 womp                 0
 networkoversleep     0
 sleep                1
 tcpkeepalive         1
 disksleep            10
 SleepServices        0
 
  • Like
Reactions: harshw
urandom said:
I tried hard to get my mac to *not* wake from sleep, because I think it's a problem with iterating connected TB devices and then going back to sleep. I tried to tinker with pmset and a tool called sleepaid.
[/CODE]
Click to expand...

So what does pmset -g log|grep -e " Sleep " -e " Wake " give ?

Are you saying your M1 MBP goes into deep sleep and wakes up the connected displays without a problem?
 
This is just the log for when the system wakes and sleeps.
Maybe disabling powernap solved the problem, not sure.
Can you show the output of your pmset -g custom ?
 
urandom said:
This is just the log for when the system wakes and sleeps.
Maybe disabling powernap solved the problem, not sure.
Can you show the output of your pmset -g custom ?
Click to expand...

Here's the output for pmset -g custom


Code: 
$ pmset -g custom
Battery Power:
 Sleep On Power Button 1
 powermode            0
 standby              1
 ttyskeepawake        1
 hibernatemode        3
 powernap             0
 hibernatefile        /var/vm/sleepimage
 displaysleep         60 
 womp                 0
 networkoversleep     0
 sleep                1
 lessbright           1
 tcpkeepalive         1
 disksleep            10
AC Power:
 Sleep On Power Button 1
 powermode            0
 standby              1
 ttyskeepawake        1
 hibernatemode        3
 powernap             0
 hibernatefile        /var/vm/sleepimage
 displaysleep         60 
 womp                 1
 networkoversleep     0
 sleep                0
 tcpkeepalive         1
 disksleep            10
 
Here's the diff for our settings.

Diff: 
--- /tmp/pmset.urandom    2023-01-11 10:29:52
+++ /tmp/pmset.harshw    2023-01-11 10:30:15
@@ -1,31 +1,29 @@
 Battery Power:
  Sleep On Power Button 1
- lowpowermode         0
+ powermode            0
  standby              1
- ttyskeepawake        0
+ ttyskeepawake        1
  hibernatemode        3
  powernap             0
  hibernatefile        /var/vm/sleepimage
- displaysleep         2
+ displaysleep         60
  womp                 0
  networkoversleep     0
  sleep                1
  lessbright           1
- tcpkeepalive         0
+ tcpkeepalive         1
  disksleep            10
- SleepServices        0
 AC Power:
  Sleep On Power Button 1
- lowpowermode         0
+ powermode            0
  standby              1
- ttyskeepawake        0
+ ttyskeepawake        1
  hibernatemode        3
  powernap             0
  hibernatefile        /var/vm/sleepimage
- displaysleep         10
- womp                 0
+ displaysleep         60
+ womp                 1
  networkoversleep     0
- sleep                1
+ sleep                0
  tcpkeepalive         1
  disksleep            10
- SleepServices        0


And this is what I changed from the defaults, which you can restore with sudo pmset restoredefaults

Diff: 
--- /tmp/pmset.urandom  2023-01-11 10:29:52
+++ /tmp/pmset.defaults 2023-01-11 10:32:22
@@ -2,30 +2,28 @@
  Sleep On Power Button 1
  lowpowermode         0
  standby              1
- ttyskeepawake        0
  hibernatemode        3
- powernap             0
+ powernap             1
  hibernatefile        /var/vm/sleepimage
- displaysleep         2
+ ttyskeepawake        1
  womp                 0
+ displaysleep         2
  networkoversleep     0
  sleep                1
  lessbright           1
- tcpkeepalive         0
+ tcpkeepalive         1
  disksleep            10
- SleepServices        0
 AC Power:
  Sleep On Power Button 1
  lowpowermode         0
  standby              1
- ttyskeepawake        0
  hibernatemode        3
- powernap             0
+ powernap             1
  hibernatefile        /var/vm/sleepimage
+ ttyskeepawake        1
+ womp                 1
  displaysleep         10
- womp                 0
  networkoversleep     0
  sleep                1
  tcpkeepalive         1
  disksleep            10
- SleepServices        0


I just reset mine to the defaults and restored the tweaked state with:

Bash: 
sudo pmset -a ttyskeepawake 0
sudo pmset -a powernap 0
sudo pmset -a tcpkeepalive 0
sudo pmset -a SleepServices 0
sudo pmset -a womp 0

I also just found this thread: https://forums.macrumors.com/threads/darkwake-0-please-tell-me-how.2349833/ with some more info related to power settings. Notice that one person claimed you can disable darkwake via an nvram setting. Haven't tried that yet
 
Last edited:
It is still unbelievable that I have to go back decades ago and get into programming to set my on/off schedule which Apple decided to exclude from MacOS Ventura in all her wisdom… (By the way in Dutch -dom- is freely interpreted as 'STUP!D')
 
  • Like
Reactions: zakarhino and urandom
Maybe a separate dock firmware version for M2 vs. M1 chips? The M2's do not use Intel thunderbolt/USB chips, while the M1's still use an Intel TB/USB chip. Or, maybe the firmware or other software is not correctly detecting the manufacturer of the TB/USB chip.
www.macworld.com

Apple's M2 MacBooks no longer have any sign of Intel inside

The last Intel chips have been replaced as the Apple silicon transition expands to smaller parts.
www.macworld.com www.macworld.com
 
BlueGhost said:
Maybe a separate dock firmware version for M2 vs. M1 chips? The M2's do not use Intel thunderbolt/USB chips, while the M1's still use an Intel TB/USB chip. Or, maybe the firmware or other software is not correctly detecting the manufacturer of the TB/USB chip.
www.macworld.com

Apple's M2 MacBooks no longer have any sign of Intel inside

The last Intel chips have been replaced as the Apple silicon transition expands to smaller parts.
www.macworld.com www.macworld.com
Click to expand...

The JHL8040R is just a re-timer. It's simply a little chip that natively understands the TB3/TB4/USB4 protocol and re-transmits the signal. The actual TB3/TB4/USB4 brains is inside the M1 and M2 SoC. It's totally conceivable that the retimer isn't playing nice with the Apple Silicon TB4 implementation and that the M2 would make the display problem go away. But if so it will be really sad for those of us who are stuck with an expensive M1 laptop that doesn't play nice with USB-C displays

I did see some folks on the forum posting that 'Apple is aware of this' so one can hope for a fix via software.
 
Been reading other sources in preparation for attempt to connect a TB-2/HDMI 1.4 monitor to a M2Pro 14" in a few weeks. On the HDMI side, some claim that using cables under 1 meter or over 2 meters can be problematic, especially with "Amazon special" type cables. For the over 2 meter lengths, you may need a hybrid optical cable or a HDMI cable with USB power (especially at high rates). On the TB-3/4 side, be careful of supported refresh rates.

Will try the HDMI route first, at macOS 13.2. May be simpler with M2Pro, since M2* uses a non-Intel USB/TB chip. The M1* units still use a Intel USB/TB chip. Mactracker application implies that M1Pro/M1Max supports a maximum of 60Hz refresh rate (but I've seen this free application differ from other sources in the past). I understand the maximum supported refresh rate on the M2* HDMI port is higher than on the M1* models. May also be true for TB4.

Looks like over 60Hz refresh rates are only supported on M1* with ProMotion (and only at 120Hz on the internal display). My older Lenovo 24" should fall well under the 60Hz refresh rate, and has a maximum resolution around 2560 x 1600 or so, if I remember correctly. Attaching link to M1* 14" specifications (Apple).

MacBook Pro (14-inch, 2021) - Technical Specifications - Apple Support (IE)

support.apple.com support.apple.com

If using a newer monitor, and use of a TB-4 port was desired, I'd be sure to use Intel certified TB4 cables from Caldigit, OWC or another manufacturer, not the half-price ones from unknown manufacturers on Amazon. Cable quality will only become more of an issue as newer standards become available. (Will likely junk all USB-2 and USB-3 items after transition to M2Pro, to prevent any mistaken use, also, that stuff is approaching its 10th birthday.)
 
Last edited:
I just upgraded from an m1 max mbp to the new m2 and I now have this issue with the new machine but never on the old one. As soon as the monitors turn off I can't wake them back up without a minimum of an unplug and replug and sometimes a full reboot. The only thing thats changed from the old to the new is the laptop itself, dock, screens etc are all the same. I tried the various suggestions here adjusting system prefs and so far none of them have worked.
 
Strangely reminds me of a similar problem at work about 7-10 years ago (but with Windows 7, Dell laptops, Dell docs and Dell VGA monitors). After reboots or on first attachment to dock at start of day, external display would not come on. I think this was eventually fixed either by a driver update on pc, or with a firmware update to doc (although it may have been fixed with a patch to extensive security software required and supplied by corporate to meet requirements from Boeing and DoD).

Wasn't there a change in Ventura that now requires manual confirmation on the attachment of new USB devices? Wonder if issue is related to that change. Maybe the docs do not retain/transfer whatever is used to identify whatever identifies the USB attached device as "new"? Has anyone tried connecting a display directly to the HDMI port on the mbp or a HDMI port on the doc?
 
Why do the Apple Silicon Macs struggle so hard with external displays? I also have display issues with my M2 Mac mini and Ventura.

I've tried different cables, ports, sleep settings and all of that and my windows won't remember their sizes after waking the monitor up.
 
Yeah I’ve noticed weird issues with external displays and my M1 Pro.

I use my MBP in clamshell mode permanently connected via power delivery, leaving my MacBook overnight and when I want to eventually use it, the external display doesn’t come on by spamming the keyboard or any other method one might take when waking up from sleep, I resort to lifting the mbp screen up so it lights up on the lock screen then I close it again.. then suddenly the external springs to life and I can use it. Rather annoying but I can live with it for now.

Setup
MBP 16” M1 Pro
49” External Monitor
USBC to displayport 1.4 cable
Dual Displayport dock with one button click to switch DP inputs.
(Also switching inputs from the dock the MacBook input doesn’t wake up the external monitor until I open and close the mbp lid.
 
urandom said:
Nope. I have a CalDigit TS4 Dock. Would this DisplayLink software work with it? Or is it just for DisplayLink hardware? The webpage is kind of confusing
Click to expand...
I think it would for at least the DisplayPort port. Not sure about the rest. I know that my Targus dock needed it.
 
harshw said:
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)
Click to expand...

I have a Studio connected to 4 Dell monitors (3x4k, 1x2k) and have no problems with wake or sleep. 3 are via USB-C and 1 is via HDMI. The monitors are all directly connected. I think that I'm using three of the built-in monitor hubs to connect a large number of devices.
 
I own a M1 Studio Max and connect it to a LG5k thunderbolt monitor via a TB3 hub. e.g. TB cable from Studio to hub, then a TB cable from the hub to the LG 5k. No issues at all. Sleep, wake, ... On all versions of Ventura so far.
 
pshufd said:
I have a Studio connected to 4 Dell monitors (3x4k, 1x2k) and have no problems with wake or sleep. 3 are via USB-C and 1 is via HDMI. The monitors are all directly connected. I think that I'm using three of the built-in monitor hubs to connect a large number of devices.
Click to expand...

So it seems the Studio is better at connecting monitors than the MacBook Pros etc. Seeing that the Studio and M1 MacBooks use the same M1 CPU - I really hope the MacOS 13.3 update can solve this via a firmware update or similar

whodiini said:
I own a M1 Studio Max and connect it to a LG5k thunderbolt monitor via a TB3 hub. e.g. TB cable from Studio to hub, then a TB cable from the hub to the LG 5k. No issues at all. Sleep, wake, ... On all versions of Ventura so far.
Click to expand...

What specific TB3 hub are you using ?
 
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back