Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
I have the opposite problem: Mac mini M1 with 32" Samesung via DisplayPort and the mini won't let the Samesung sleep; I get a constant cycling of the monitor trying to wake then going dark briefly before it tries to wake again. Hitting the spacebar brings it to life without a hitch.
 
I have a M1 Air connected to a LG 32" 4k display via a StarTech hub, using DisplayPort. Initially, I had a lot of flickering with Big Sur but over time that seems to have gone away. Seemed to occur mostly on dark screens. But, the most recent beta caused me all sorts of display problems, enough so I bailed out of the public beta entirely. Basically, when the display "woke up" from sleep, it was fuzzy and washed out all over. Only a reboot or a power off/on cycle could return the display to normal. Consistent enough I filed a bug report before I exited. Now back on 11.2.3 I have had no issues with sleep and the display at all.

Ken
 
A few people might have faulty machines as well, but considering lots of Intel users (me included) have reported these kinds of issues since upgrading to Big Slur, I suspect it is all just an OS issue.
 
  • Like
Reactions: SpacemanSpiffed
I have my Mac mini connected to LG28inch 4K monitor using displayport to thunderbolt. This has happened to me a couple of times power fixes it but not ideal. Latest solution is to disconnect and reconnect cable, seems to work…
 
Had this issue on my 2018 Intel Mac mini when it was new. Then after a few months an update fixed it. Never had an issue since.
(Haven’t updated to big sur so hopefully that doesn’t bring the issue back)
 
  • Like
Reactions: jcd3rd
Had this happen a couple of times so far in 3 months on my Apple Thunderbolt monitor so it's not just third-party displays, and a more frequent issue i am having is that they won't stay asleep due to what feels to me like bluetooth waking them up a fraction of time after putting it to sleep.
 
  • Like
Reactions: peanuts_of_pathos
If it doesn't wake a third party display, and Apple no longer produces any first-party consumer displays (I'm not counting a $5K Pro Display XDR as "consumer") doesn't that mean....it doesn't wake any displays?
Stop being so logical or I will have to report and flag you!!!
 
I've had all manner of external display problems with Intel 16" MBP and the 13" M1 MacBook Pro. The truth is that Big Sur's display drivers are a bunch of arse across both architectures, and Apple needs to do better. The DisplayPort over USB-C support seems particularly buggy to me, but I've switched to plain 'ol HDMI now which seems to work a little better on the M1 MacBook Pro.
 
  • Like
Reactions: peanuts_of_pathos
I no longer try to wake my M1 Mac mini with the keyboard or the trackpad. I just press & hold the power button for a 4 count, wakes mini and display every time.
 
  • Like
Reactions: NMBob
Had the pink dots issue with my M1 Mac mini, exchanged for another... same issue. What I did was, I changed the refresh rate on the display from 60Hz to the Max supported on my monitor at 165Hz and the issue went away. I do notice it takes a while longer to wake the display on Mac mini than when I was using a MacBook Pro with a connected external display. Growing pains I guess...
 
2018 Mac Mini and this happened to me a lot for the first few months (summer of 2019) then just stopped happening randomly around summer 2020.
 
Was having a bunch of sleep/wake issues with my M1 Mac mini 16gb and LG Ultrafine (not the Apple versions, newer one) and external hard drives. I had to adjust some energy saving settings (Prevent the computer from sleeping when the display is off: checked, Put Hard disks to sleep when possible: uncheck). Plus my monitor I believe was causing kernel panic crashes when my mini went to sleep it would just crash and reboot. SOLUTION was to change the DisplayPort settings on my monitor from 1.4 to 1.2.

Apple needs to play better with non-Apple external monitors (unless they intend to start making their own that aren't more than a Kidney) OR LG needs update their software and drives, I don't know who to blame for these problems. Getting the reality check on not being able to control brightness and volume with keyboard since replacing my iMac.

Also having audio issues with FaceTime. The speakers in my monitor don't work. the only output that works is the mini’s speaker which are… not great.
Apple confirmed to me that M1 Macs have an issue with DP 1.4. A direct cable connection using DP1.4 on my 5K monitor doesn’t work, but when I insert a Thunderbolt 3 to DP1.2 adapter made by OWC, the monitor works and I get a 5K signal via the monitor’s DP port. Go figure. Apple is no help at all.

The same monitor works fine via a USB-C to DP1.4 cable with a 2020 13” Intel MacBook Pro (Intel Gen 10 CPU). So, the M1 Macs definitely have a problem with DP1.4 displays.
 
This is not a new issue. I've seen exactly this for nearly a decade with my 2012 Mac Mini as well as the Mac Mini I had before that (don't remember the year).

The frequent-enough-to-be-really-annoying issue of waking to a "No Connection" message on an external monitor (and having to remote desktop my way in to save open files and reboot) is one of the reasons my new computer is an iMac instead of another Mac Mini.
 
This happened to me quite often with my MBP 2018 13-inch, though I were never sure if it was because of my 3rd-party-USB-C-HDMI-adapter (there unfortunately is no 4k60 Adapter from Apple for my MBP). Incredibly annoying. Always had to unplug and replug in this case to get it to work.
The current iteration of Apple’s USB-C Digital AV multi port adapter is capable of 4K/60Hz. Originally, it would not do that, but they revised it specifically adding 4K/60 to the HDMI port.
 
I somewhat wonder if it's an issue with USB-C and the included protocols for delivering video. I have similar issues with a range of machines and monitors including my Chromebooks and PCs; this doesn't seem to just affect my Macs.
 


Some customers who have purchased an M1 Mac mini have been experiencing an issue that causes the machine not to wake a connected third-party display from sleep.

m1-mac-mini-vignette.jpg-feature.jpg

This is not an issue that's affecting all M1 Mac mini owners, but there are numerous complaints on the MacRumors forums and the Apple Support Communities dating back to November when the Mac mini was first released. MacRumors reader gooimac explains:MacRumors reader Mike, who emailed us about the issue, has seen the same problems.This issue appears to be affecting a wide range of displays that connect over Thunderbolt, HDMI, and DisplayPort adapters, but there are also plenty of people who are having no issues at all.

It's not clear what the problem is, but Apple has been looking into one M1 Mac mini display issue that causes strange pink squares to appear on displays connected to one of the machines.

Apple is aware of the issue, and there could be a fix in the works that's coming in a future update. One solution for now may be to disable the feature that puts the Mac mini to sleep, but that's not ideal. The other solution is to unplug and replug in a display that's not responding after a Mac mini wakes from sleep, but that too is an inelegant solution. There appears to be no other fix available at this time.

Article Link: M1 Mac Mini Won't Wake Connected Displays, Some Owners Complain
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.