Users report ongoing display problems in macOS Big Sur 11.1 and 11.2

Posted:
in General Discussion edited February 2021
A number of users running macOS Big Sur 11.1 or 11.2 are experiencing external display connection issues, according to reports across social media and support forums.

Credit: AppleInsider
Credit: AppleInsider


The issues appear to have started in macOS Big Sur 11.1, according to reports from Apple Support Communities, Reddit, and the MacRumors forum. The recently released macOS 11.2 update doesn't seem to have fixed all of the problems, and some reports indicate that it actually worsened them.

Although the issues are related to the use of external displays, users are reporting two different bugs. For example, some users are running into issues with USB-C ports failing to recognize external monitors. This specific issue appears to affect both HDMI and DisplayPort display connections, either directly connected to a Mac or routed through a hub.

Other reports indicate resolution problems with external displays. This issue seemingly prevents external displays from functioning at a 4K 60Hz resolution. Instead, displays are locked at 30Hz and may even be recognized only as 1080p HD displays.

The issues appear to be ongoing, and there doesn't appear to be a patch in the first macOS 11.3 beta. No functioning and reliable fix or workaround has been discovered for either problem.

Comments

  • Reply 1 of 20
    Originally with my M1 Mac Mini I couldn't lower the resolution down to 1080p without it causing issues and now it will not allow me to go any higher than 1080p. If it's software-related and I just have to settle for 1080p on my 4k TV until it gets resolved, no big deal. If it's a hardware problem, well, I guess that's what I get for being an early adopter. 
  • Reply 2 of 20
    And this doesn’t include the half opaque display right before shut down that is happening to some 2020 iMacs with info available as to why at different forums (including Apple communities as well). Frustrating to see this happen after having this issue start within a month of having the computer and upgrading to Big Sur (didn’t happen with Catalina) and with three months and no clarity of what is going on with it and paying over $2000 for an iMac to have this happen:


    edited February 2021
  • Reply 3 of 20
    With 11.1, macOS had major problems determining the resolution and refresh rate of my USB-C connected external BenQ EX2780Q to my 16" MacBook Pro.  Usually booted into a lower resolution and/or 60Hz refresh rate rather than 144Hz.  Switching the monitor off was a big no-no, as it'd lose the resolution or refresh rate again when switched back on.

    With 11.2, it boots up to the right resolution and refresh rate so far.  I have found, however, that if the monitor is switched off and the Mac then goes into sleep mode, switching the monitor back on and waking up the Mac can cause it to drop the resolution down - but then switching the monitor off and on again fixes it.  But this doesn't happen all the time.  So there appears to be some improvement (at least for me), but not by much.
  • Reply 4 of 20
    I don't have any problem described in the article with my Mac mini M1. However there is the very annoying problem that no good calibration software works on the M1. All developers (LG, Nec, X-Rite) point to a problem at Apple.
  • Reply 5 of 20
    netroxnetrox Posts: 1,159member
    fjho2000 said:
    And this doesn’t include the half opaque display right before shut down that is happening to some 2020 iMacs with info available as to why at different forums (including Apple communities as well). Frustrating to see this happen after having this issue start within a month of having the computer and upgrading to Big Sur (didn’t happen with Catalina) and with three months and no clarity of what is going on with it and paying over $2000 for an iMac to have this happen:


    They look like two separate images. They don't look the same. 
  • Reply 6 of 20
    My issue, as it was with 11.1, is that monitor will not wake properly after sleep. I'm using M1 MM 16g/1T, monitor is an LG 38wn95c, resolution=3840x1600, TB3 connection. The only way to get monitor to wake is to disconnect TB3 cable from back of panel and reconnect, super annoying. I was hoping this latest update would fix that but it hasn't.
    Never had any BT issues (knock on wood), using Magic Keyboard and Magic Trackpad 2.
  • Reply 7 of 20
    I have been experiencing the display problem since getting the M1 Mac as well. I have a M1 Mini 16gb and use the usb-c tb3 port to connect to a monitor. I also need to disconnect the cable and reconnect to make it work about 30% of the time. 

    Wood1030 said:
    My issue, as it was with 11.1, is that monitor will not wake properly after sleep. 

  • Reply 8 of 20
    Does this impact Intel Macs too? 
  • Reply 9 of 20
    fastasleepfastasleep Posts: 6,072member
    fjho2000 said:
    And this doesn’t include the half opaque display right before shut down that is happening to some 2020 iMacs with info available as to why at different forums (including Apple communities as well). Frustrating to see this happen after having this issue start within a month of having the computer and upgrading to Big Sur (didn’t happen with Catalina) and with three months and no clarity of what is going on with it and paying over $2000 for an iMac to have this happen:


    Weird, looks like the preview for the Dynamic Desktop, kinda. Color looks more like Night Shift on the left half though. Weird. If it's just before shutdown, who cares though? I get various graphical glitches during startup with an external monitor (in Mojave and then Catalina), but it doesn't affect actual use. 


    maltznetrox
  • Reply 10 of 20
    I'm using a M1 Mac mini (16MB), with a very old but beloved Apple 30" Cinema HD Display (2560x1600 @60Hz)

    It's attached using an Apple Mini DisplayPort to Dual-Link Adapter (firmware 1.0.3), then a Amiroko USB 3.1C to Mini DisplayPort. Believe me I'm surprised it still works at all : )

    However, under MacOS 11.2 I now have to unplug/replug the adapter from my M1 Mac mini about 90% of the time when the computer goes to sleep. Under MacOS 11.1 it was about 70% of the time. And under MacOS 11.1 using a Intel i7 Mac mini it was about 25% of the time.

    I understand my display is old and I've cobbled together adapters to make it work, and it's a miracle that it still works.

    But would love to have a better solution (other than the Apple Pro Display—Yikes! Beautiful monitor, but I'm not an artist, just have normal consumer needs). Or advice on better adapters until Apple or someone else makes a monitor that I can love as much as this one.
  • Reply 11 of 20
    Hi! I first had BigSur 11.1. installed and now have Big Sur 11.2, on my desktop. A very annoying problem with MICE is going on when I use the Apple MAIL program - the mice work erratically (whether bluetooth or USB), meaning they don't track correctly, or too slowly, or too fast. Had/have the problem even with version 11.2.  Also, the MAIL problem opens very S L O W L Y compared to when I had Catalina installed. I already tried deleting some start up files, re-started several times, re-installed BigSur 11.1 before 11.2 was available. I've now spent at least 2 working days on this but will have to downgrade to Catalina again if the problem doesn't go away soon. Any leads...? Thanks!
  • Reply 12 of 20
    bryankd said:
    I'm using a M1 Mac mini (16MB), with a very old but beloved Apple 30" Cinema HD Display (2560x1600 @60Hz)

    It's attached using an Apple Mini DisplayPort to Dual-Link Adapter (firmware 1.0.3), then a Amiroko USB 3.1C to Mini DisplayPort. Believe me I'm surprised it still works at all : )

    However, under MacOS 11.2 I now have to unplug/replug the adapter from my M1 Mac mini about 90% of the time when the computer goes to sleep. Under MacOS 11.1 it was about 70% of the time. And under MacOS 11.1 using a Intel i7 Mac mini it was about 25% of the time.

    I understand my display is old and I've cobbled together adapters to make it work, and it's a miracle that it still works.

    But would love to have a better solution (other than the Apple Pro Display—Yikes! Beautiful monitor, but I'm not an artist, just have normal consumer needs). Or advice on better adapters until Apple or someone else makes a monitor that I can love as much as this one.
    I just use a decent 4K TV. (Actually two of them, side by side). I get brilliant performance, rock solid pictures, 60Hz refresh rate, perfect colours. You do have to dive into the TV's own set up to get the exact right picture modes, but once you're there it's fantastic, and a heck of a lot cheaper than buying an equivalently sized monitor. Ultimately, they all end up using similar LCD panels. It's just tuning the settings on the TV.
  • Reply 13 of 20
    dysamoriadysamoria Posts: 3,430member
    CarmB said:
    Originally with my M1 Mac Mini I couldn't lower the resolution down to 1080p without it causing issues and now it will not allow me to go any higher than 1080p. If it's software-related and I just have to settle for 1080p on my 4k TV until it gets resolved, no big deal. If it's a hardware problem, well, I guess that's what I get for being an early adopter. 
    Why are you so eager to put the blame on customers, including your own damned self?

    What the hell with tech people being constantly willing to excuse perpetual tech problems??

    This issue sounds, once again, as though Apple don’t actually USE their own products. Issues with third-party displays have been ongoing since Apple ceased making their own. If they’re unwilling to build & sell their own displays, then they ought to be testing their computers with other displays. How else would they know if they’ve broken things in the OS or hardware that are required for reliable display usage?

    This is why I refused to buy the 2013 Mac Pro. Nine years later and all they have is an insanely expensive first-party display that only big studios can justify or afford, and third-party displays continue to be problematic.

    I’m so sick of the complacency in this whole stupid industry, as well as the blasé attitudes of tech industry-acculturated geeks (and some actual corporate bootlickers). None of this is okay.
  • Reply 14 of 20
    fastasleepfastasleep Posts: 6,072member
    dysamoria said:
    CarmB said:
    Originally with my M1 Mac Mini I couldn't lower the resolution down to 1080p without it causing issues and now it will not allow me to go any higher than 1080p. If it's software-related and I just have to settle for 1080p on my 4k TV until it gets resolved, no big deal. If it's a hardware problem, well, I guess that's what I get for being an early adopter. 
    Why are you so eager to put the blame on customers, including your own damned self?

    What the hell with tech people being constantly willing to excuse perpetual tech problems??

    This issue sounds, once again, as though Apple don’t actually USE their own products. Issues with third-party displays have been ongoing since Apple ceased making their own. If they’re unwilling to build & sell their own displays, then they ought to be testing their computers with other displays. How else would they know if they’ve broken things in the OS or hardware that are required for reliable display usage?

    This is why I refused to buy the 2013 Mac Pro. Nine years later and all they have is an insanely expensive first-party display that only big studios can justify or afford, and third-party displays continue to be problematic.

    I’m so sick of the complacency in this whole stupid industry, as well as the blasé attitudes of tech industry-acculturated geeks (and some actual corporate bootlickers). None of this is okay.
    Show the jury on the doll where Apple touched you. We're still waiting.
  • Reply 15 of 20
    Hey, I got a brand new MacBook Pro (13", M1, 2020) with Big Sur 11.2 and this is my display problem: At random my displays - extern and mac book -  freeze completely. Sometimes after a few minutes, sometimes only after 1 or 2 hrs of work. I never ever do anything special bevor, It just happens whilst movig the mouse rom left to right or just staring at the screen or scrolling down a website on Chrome or anything else.
    .
    If it happens, I have to disconnect the extern monitor and reconnect and everything's fine again. Except for my dead shadow priest or blindly unwillingly moved files by mouse action. Because whilst the screens are frozen the mac and software just go along an do their jobs.
    .
    :-/
  • Reply 16 of 20
    Does this impact Intel Macs too? 
    Yes. I am having all kinds of startup issues and external display issues with my 2017 iMac.
  • Reply 17 of 20
    I get the error report below about 50% of the time when restarting my 2017 iMac with 11.2 - and no idea what it means. Sometimes it freezes during startup, sometimes the screen goes black during startup, sometimes it gets stuck with a split screen of two different colors. Fingers crossed for 11.3 soon! I do have an external monitor hooked up.

    panic(cpu 0 caller 0xffffff800d9fe407): "AMDFramebufferVIB::setPowerState(0xffffff936efe8000 : 0xffffff7fada7a2bc, 0 -> 2) timed out after 45785 ms"@/AppleInternal/BuildRoot/Library/Caches/com.apple.xbs/Sources/xnu/xnu-7195.81.3/iokit/Kernel/IOServicePM.cpp:5382
    Backtrace (CPU 0), Frame : Return Address
    0xffffffb09b95bac0 : 0xffffff800d2bab4d 
    0xffffffb09b95bb10 : 0xffffff800d3fd7e3 
    0xffffffb09b95bb50 : 0xffffff800d3ede1a 
    0xffffffb09b95bba0 : 0xffffff800d25fa2f 
    0xffffffb09b95bbc0 : 0xffffff800d2ba3ed 
    0xffffffb09b95bce0 : 0xffffff800d2ba6d8 
    0xffffffb09b95bd50 : 0xffffff800dabef9a 
    0xffffffb09b95bdc0 : 0xffffff800d9fe407 
    0xffffffb09b95be10 : 0xffffff800d9fdd29 
    0xffffffb09b95be20 : 0xffffff800da167de 
    0xffffffb09b95be60 : 0xffffff800d9fcaa8 
    0xffffffb09b95be80 : 0xffffff800d2ff725 
    0xffffffb09b95bef0 : 0xffffff800d300634 
    0xffffffb09b95bfa0 : 0xffffff800d25f13e 

    Process name corresponding to current thread: kernel_task

    Mac OS version:
    20D64

    Kernel version:
    Darwin Kernel Version 20.3.0: Thu Jan 21 00:07:06 PST 2021; root:xnu-7195.81.3~1/RELEASE_X86_64
    Kernel UUID: C86236B2-4976-3542-80CA-74A6B8B4BA03
    KernelCache slide: 0x000000000d000000
    KernelCache base:  0xffffff800d200000
    Kernel slide:      0x000000000d010000
    Kernel text base:  0xffffff800d210000
    __HIB  text base: 0xffffff800d100000
    System model name: iMac18,2 (Mac-77F17D7DA9285301)
    System shutdown begun: NO
    Panic diags file available: NO (0xe00002bc)
    Hibernation exit count: 0

    System uptime in nanoseconds: 26537571231113
    Last Sleep:           absolute           base_tsc          base_nano
      Uptime  : 0x00001822c281a854
      Sleep   : 0x00001817f2e005bf 0x0000000084a60e0c 0x000014e6a9fda5fc
      Wake    : 0x00001817f7601720 0x000000008460e03f 0x00001817f63ecdc1
    last started kext at 26491764769221: >!UAudio 401.4 (addr 0xffffff7fad70f000, size 307200)
    last stopped kext at 23178678306043: >usb.cdc 5.0.0 (addr 0xffffff800e9de000, size 8192)
    loaded kexts:
    >usb.!UUserHCI 1
    >!ATopCaseHIDEventDriver 4030.5
    >AudioAUUC 1.70
    >AGPM 119
    >!APlatformEnabler 2.7.0d0
    >X86PlatformShim 1.0.0
    @fileutil 20.036.15
    >!AUpstreamUserClient 3.6.8
    >!AHDA 283.15
    >!AGraphicsDevicePolicy 6.2.2
    >pmtelemetry 1
    >LuaHardwareAccess 1.0.16
    |IOUserEthernet 1.0.1
    |IO!BSerialManager 8.0.3d9
    >eficheck 1
    |Broadcom!B20703USBTransport 8.0.3d9
    >!AHV 1
    >!ADiskImages2 1
    >!A!IPCHPMC 2.0.1
    >!A!IKBLGraphics 16.0.1
    >!AGFXHDA 100.1.431
    >!A!IKBLGraphicsFramebuffer 16.0.1
    >!AThunderboltIP 4.0.3
    >!ASMCLMU 212
    >!AMCCSControl 1.14
    >!A!ISlowAdaptiveClocking 4.0.0
    >AirPort.BrcmNIC 1400.1.1
    |!ABCM5701Ethernet 11.0.0
    >!ASDXC 1.9.0
    >!AAHCIPort 346
    >!AACPIButtons 6.1
    >!ARTC 2.0
    >!ASMBIOS 2.1
    >!AACPIEC 6.1
    >!AAPIC 1.7
    |IOKitRegistryCompatibility 1
    |EndpointSecurity 1
    >!UAudio 401.4
    >usb.cdc 5.0.0
    >!AMultitouchDriver 4400.28
    >!AInputDeviceSupport 4400.35
    >!AHS!BDriver 4030.5
    >IO!BHIDDriver 8.0.3d9
    >!AHIDKeyboard 223
    >DspFuncLib 283.15
    >!AGraphicsControl 6.2.2
    |IOSerial!F 11
    >!ASMBusPCI 1.0.14d1
    |Broadcom!BHost!CUSBTransport 8.0.3d9
    |IO!BHost!CUSBTransport 8.0.3d9
    |IO!BHost!CTransport 8.0.3d9
    |IOAVB!F 930.1
    >!AHDA!C 283.15
    |IOHDA!F 283.15
    |IONDRVSupport 585
    |IOAudio!F 300.6.1
    |IOAccelerator!F2 439.52
    |IOGraphics!F 585
    >!ASMBus!C 1.0.18d1
    >X86PlatformPlugin 1.0.0
    >IOPlatformPlugin!F 6.0.0d8
    |IOSlowAdaptiveClocking!F 1.0.0
    |IOEthernetAVB!C 1.1.0
    >usb.!UHub 1.2
    >usb.networking 5.0.0
    >usb.!UHostCompositeDevice 1.2
    >!AThunderboltDPInAdapter 8.1.4
    >!AThunderboltDPAdapter!F 8.1.4
    >!AThunderboltPCIDownAdapter 4.1.1
    >!AHPM 3.4.4
    >!A!ILpssI2C!C 3.0.60
    >!A!ILpssI2C 3.0.60
    >!A!ILpssDmac 3.0.60
    >!ABSDKextStarter 3
    |IOSurface 289.3
    |IOAHCIBlock!S 332
    >!AThunderboltNHI 7.2.8
    |IOThunderbolt!F 9.3.2
    |IO80211!F 1200.12.2b1
    |IOSkywalk!F 1
    >corecapture 1.0.4
    >mDNSOffloadUserClient 1.0.1b8
    |IOAHCI!F 294
    >usb.!UXHCIPCI 1.2
    >usb.!UXHCI 1.2
    |IOUSB!F 900.4.2
    >!AEFINVRAM 2.1
    >!AEFIRuntime 2.1
    |IOSMBus!F 1.1
    |IOHID!F 2.0.0
    $!AImage4 3.0.0
    |IOTimeSync!F 900.11
    |IONetworking!F 3.4
    >DiskImages 493.0.0
    |IO!B!F 8.0.3d9
    |IOReport!F 47
    |IO!BPacketLogger 8.0.3d9
    $quarantine 4
    $sandbox 300.0
    |CoreAnalytics!F 1
    >!ASSE 1.0
    >!AKeyStore 2
    >!UTDM 511.60.2
    |IOUSBMass!SDriver 184.40.6
    |IOSCSIBlockCommandsDevice 436.40.6
    |IO!S!F 2.1
    |IOSCSIArchitectureModel!F 436.40.6
    >!AMobileFileIntegrity 1.0.5
    >!AFDEKeyStore 28.30
    >!AEffaceable!S 1.0
    >!ACredentialManager 1.0
    >KernelRelayHost 1
    |IOUSBHost!F 1.2
    >!UHostMergeProperties 1.2
    >usb.!UCommon 1.0
    >!ABusPower!C 1.0
    >!ASEPManager 1.0.1
    >IOSlaveProcessor 1
    >!AACPIPlatform 6.1
    >!ASMC 3.1.9
    |IOPCI!F 2.9
    |IOACPI!F 1.4
    >watchdog 1


  • Reply 18 of 20
    @apgarscore11 ;
    Did you get anywhere with your issue? My Dad's 2017 imac has the same problem and has done for a while- was going it while on Mojave, skipped Catalina and updated straight to Big Sur 11.4 but is still doing it.

    panic(cpu 0 caller 0xffffff801e7d4e77): "AMDFramebufferVIB::setPowerState(0xffffff937ec92000 : 0xffffff7fb8f47c1c, 0 -> 1) timed out after 45651 ms"@/System/Volumes/Data/SWE/macOS/BuildRoots/e90674e518/Library/Caches/com.apple.xbs/Sources/xnu/xnu-7195.121.3/iokit/Kernel/IOServicePM.cpp:5382
    Backtrace (CPU 0), Frame : Return Address
    0xffffffa09384bac0 : 0xffffff801e08e0dd 
    0xffffffa09384bb10 : 0xffffff801e1d4f33 
    0xffffffa09384bb50 : 0xffffff801e1c552a 
    0xffffffa09384bba0 : 0xffffff801e032a2f 


    Also get this one now and again

    panic(cpu 3 caller 0xffffff7faac04deb): "virtual bool IOAccelLegacyDisplayMachine::display_mode_did_change(uint32_t): AMDRadeonAccelerator driver returns false"@/System/Volumes/Data/SWE/macOS/BuildRoots/e90674e518/Library/Caches/com.apple.xbs/Sources/IOAcceleratorFamily_kexts/IOAcceleratorFamily-442.9/Kext2/IOAccelLegacyDisplayMachine.cpp:267
    Backtrace (CPU 3), Frame : Return Address
    0xffffffa0c3be35b0 : 0xffffff800fe8e0dd 
    0xffffffa0c3be3600 : 0xffffff800ffd4f33 
    0xffffffa0c3be3640 : 0xffffff800ffc552a 


  • Reply 19 of 20
    IreneWIreneW Posts: 296member
    will_0407 said:
    @apgarscore11 ;
    Did you get anywhere with your issue? My Dad's 2017 imac has the same problem and has done for a while- was going it while on Mojave, skipped Catalina and updated straight to Big Sur 11.4 but is still doing it.

    panic(cpu 0 caller 0xffffff801e7d4e77): "AMDFramebufferVIB::setPowerState(0xffffff937ec92000 : 0xffffff7fb8f47c1c, 0 -> 1) timed out after 45651 ms"@/System/Volumes/Data/SWE/macOS/BuildRoots/e90674e518/Library/Caches/com.apple.xbs/Sources/xnu/xnu-7195.121.3/iokit/Kernel/IOServicePM.cpp:5382
    Backtrace (CPU 0), Frame : Return Address
    0xffffffa09384bac0 : 0xffffff801e08e0dd 
    0xffffffa09384bb10 : 0xffffff801e1d4f33 
    0xffffffa09384bb50 : 0xffffff801e1c552a 
    0xffffffa09384bba0 : 0xffffff801e032a2f 


    Also get this one now and again

    panic(cpu 3 caller 0xffffff7faac04deb): "virtual bool IOAccelLegacyDisplayMachine::display_mode_did_change(uint32_t): AMDRadeonAccelerator driver returns false"@/System/Volumes/Data/SWE/macOS/BuildRoots/e90674e518/Library/Caches/com.apple.xbs/Sources/IOAcceleratorFamily_kexts/IOAcceleratorFamily-442.9/Kext2/IOAccelLegacyDisplayMachine.cpp:267
    Backtrace (CPU 3), Frame : Return Address
    0xffffffa0c3be35b0 : 0xffffff800fe8e0dd 
    0xffffffa0c3be3600 : 0xffffff800ffd4f33 
    0xffffffa0c3be3640 : 0xffffff800ffc552a 


    Why do these reports suddenly throw me back to the old, bad, days of Windows BSOD?
    edited July 2021
  • Reply 20 of 20
    Mike WuertheleMike Wuerthele Posts: 6,428administrator
    will_0407 said:
    @apgarscore11 ;
    Did you get anywhere with your issue? My Dad's 2017 imac has the same problem and has done for a while- was going it while on Mojave, skipped Catalina and updated straight to Big Sur 11.4 but is still doing it.

    panic(cpu 0 caller 0xffffff801e7d4e77): "AMDFramebufferVIB::setPowerState(0xffffff937ec92000 : 0xffffff7fb8f47c1c, 0 -> 1) timed out after 45651 ms"@/System/Volumes/Data/SWE/macOS/BuildRoots/e90674e518/Library/Caches/com.apple.xbs/Sources/xnu/xnu-7195.121.3/iokit/Kernel/IOServicePM.cpp:5382
    Backtrace (CPU 0), Frame : Return Address
    0xffffffa09384bac0 : 0xffffff801e08e0dd 
    0xffffffa09384bb10 : 0xffffff801e1d4f33 
    0xffffffa09384bb50 : 0xffffff801e1c552a 
    0xffffffa09384bba0 : 0xffffff801e032a2f 


    Also get this one now and again

    panic(cpu 3 caller 0xffffff7faac04deb): "virtual bool IOAccelLegacyDisplayMachine::display_mode_did_change(uint32_t): AMDRadeonAccelerator driver returns false"@/System/Volumes/Data/SWE/macOS/BuildRoots/e90674e518/Library/Caches/com.apple.xbs/Sources/IOAcceleratorFamily_kexts/IOAcceleratorFamily-442.9/Kext2/IOAccelLegacyDisplayMachine.cpp:267
    Backtrace (CPU 3), Frame : Return Address
    0xffffffa0c3be35b0 : 0xffffff800fe8e0dd 
    0xffffffa0c3be3600 : 0xffffff800ffd4f33 
    0xffffffa0c3be3640 : 0xffffff800ffc552a 


    Both this and the other poster's log suggest a GPU hardware issue.
Sign In or Register to comment.