Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
M1 MacBook Air: External display not recognized after waking from sleep
- Thread starter superamit
- Start date
-
- Tags
- hdmi monitor 4k
- Sort by reaction score
Yes, are there any beta 3 users out there that can confirm if this is still an issue? I read in another thread someone said it was fixed but I haven't seen any other comments.
Had the same yellow display issue after sleep with 11.2.3. Installed 11.3 beta 5 today, and it seems the issue is solved.
Did you reset the settings or delete the settings files first?
Happy to say that upgrading to 11.3 Big Sur fixed most of the wake sleep problems with a MacBook Air M1 with an external UltraWide display LG34WK95U. It seems to work well except if I start using my MacBook Air M1 before the LG34WK95U external monitor (running in Display Port ver 1.4 mode) wakes up which seems to take 10-20 seconds. Better than it was but not 100%. If I start typing or moving the cursor before the LG34WK95U external monitor has woken up I loose the resolution and Arrangement of the external Display in relationship to the MacBook Air M1 screen, and I have to restart the MacBook and redo the resolution and Arrangement in System Preferences > Displays. Wondering if someone has found a better solution than a restart.
I am on 11.3 and the monitor wake problem is still with me. I think that the frequency that I can't get the M1 mac mini to see the monitor connected to it's HDMI port got better at some point with 11.2.1 or 11.2.2. When I first got the computer I had to force a reboot by holding down the power button every morning and sometimes again later during the day. With 11.2.? things got a little better. I now have to do this every 3 or 4 days. With 11.3 nothing has changed. The problem is still with us. Occasionally it seems to partially wake up. I get a monitor full of snow. When this happens I can usually fix it by pressing the power button for about 1 or 2 seconds. That fix only works when I get the screen full of snow.
Last edited:
I updated to 11.3.1 the minute it came out. The problem is still here. I had to power cycle the computer two days in a row. I'd like to find a program that would run in the background all the time and look for an "F" key press and then gracefully reboot if it saw one. I am pretty sure my M1 mac mini is running perfectly well and can see the keyboard.
My first post and I'm still angry with this such problems. I've already posted on dell community at https://www.dell.com/community/Moni...e-C-signal-search-issue-6/m-p/7870462#M134852
It seems the problem causes by macos i think.
Macbookpro M1 Big Sur 11.4 Beta
Whenever I shutdown my computer, monitor is not waking up "no signal, searching" via type-c cable.
No fix yet.
It seems the problem causes by macos i think.
Macbookpro M1 Big Sur 11.4 Beta
Whenever I shutdown my computer, monitor is not waking up "no signal, searching" via type-c cable.
No fix yet.
Mac mini (M1) connected via USB C to an HP U28 4k monitor with a 3-port USB A hub. macOS Big Sur 11.4. The main issue is that the hub in the monitor is invisible to the Mac mini unless and until the power cable to the monitor is removed and replaced whilst the Mac mini is active. Deeply frustrated, after wasting several hours with Apple support trying First Aid and reinstalling macOS. I have received a replacement Mac mini that exhibits the same issue :-(
Last edited:
Does anyone know if Apple is working on this? I opened a support ticket and after working with one of there 2nd level engineers he left me an email with a link to keep him posted. I have the feeling that nobody is getting those emails as I have never received a response.
I certainly hope so. This particular issue places a huge damper on the M1 hype. It's a bit like buying a fancy new car that won't start most mornings.
This issue isn't new, nor is it relegated to the new M1 Macs. Been having the same exact problem on an 2012 Mac Mini (though not consistently) and now that I've just upgraded to the latest M1 Mac Mini, I'm still experiencing it.
Working around this by powering on the monitor first before the Mac. Annoying.. but I suspect it's a DP compatibility issue
Working around this by powering on the monitor first before the Mac. Annoying.. but I suspect it's a DP compatibility issue