External Displays Disconnect Intermittently with Sequoia Update

Question

Level 1

7 points

External Displays Disconnect Intermittently with Sequoia Update

Hi, I just updated to Sequoia (15.1) on my 2019 iMac I have two external displays (A Samsung monitor w/ HDMI 2, 3840x2160 resolution, 135.0kHz, 60Hz and a Wacom Cintiq Pro 16) and ever since I updated, about every 10-15 minutes (give or take) the monitors disconnect, and then automatically reconnect. I've done further research and it appears to be a common bug with the newest MacOS update, but it's incredibly disruptive to my workflow.

Both displays are connected with extra dongles due to the nature of ports available on this aging machine, and I suspect that might be the problem, but I thought I would reach out here first to see if there's anything that could be done before I spend more money.

Before updating this was not an issue in the slightest, so I can't imagine what must've changed.

(Just in case, my mac specs are: 3GHz 6-Core Intel Core i5 processor, 64 GB memory.)

Any advice would be appreciated. Thanks!

iMac 27″, macOS 15.1

Posted on Oct 29, 2024 2:09 PM

Reply

Answer 1

h3ct0rjs

Level 1

8 points

Nov 6, 2024 8:11 AM in response to Mothymoth

Hey, I hope you're doing well. I'm also experimenting with this weird behavior in my MacBook air I'm looking for technical answers but I haven't been able to find anything on the Internet.

MacBook Air 13″ Apple M1 2020, macOS Sequoia version 15.1, 16 GB memory. Checking the kernel I'm only seen disconnection from the Display :

2024-11-06 10:33:24.894374-0500 0x8b26     Default     0x0                  0      0    kernel: (IODisplayPortFamily) IOAV[428] AppleDisplayCrossbar(display-crossbar0)<0x100000320>::triggerDisplayAllocation: caller=setDisplayHints; signaling display allocation event source; thread call was pending=NO
2024-11-06 10:33:24.894726-0500 0x8b26     Default     0x0                  0      0    kernel: (IODisplayPortFamily) IOAV[436] AppleDisplayCrossbar(display-crossbar0)<0x100000320>::displayAllocationEventOccurred: DFPs processed: 0 allocated: 0 domains: 0x0
2024-11-06 10:33:24.894841-0500 0x28c      Default     0x0                  0      0    kernel: (DCPEXT)  [DCPAVServiceEDID.cpp::3946] DCPAV[80] DCPDP13Service::enumerateElements _current.displayAllocation: extraPipes=0, mainUFP=0, peerUFP=0
2024-11-06 10:33:25.036065-0500 0x28c      Default     0x0                  0      0    kernel: (RTBuddy) [DCPEXT:eoInterfaceIOAV.cpp:801] plug_gated: display HPD asserted.
2024-11-06 10:33:25.090972-0500 0xe8c      Default     0x0                  0      0    kernel: (IOMobileGraphicsFamily) request_power_change second_external 0 powerstate1 fdisplaytype 1
2024-11-06 10:33:25.364365-0500 0xd70      Default     0x0                  0      0    kernel: (IOMobileGraphicsFamily) static IOReturn IOMobileFramebufferUserClient::s_map_display_type(IOMobileFramebufferUserClient *, void *, IOExternalMethodArguments *) UserClient display type is 1
2024-11-06 10:33:29.645599-0500 0x8c0e     Default     0x0                  0      0    kernel: (IODisplayPortFamily) IOAV[1042] AppleDisplayCrossbar(display-crossbar0)<0x100000320>::triggerDisplayAllocation: caller=eventOccurredOnDFP_block_invoke; signaling display allocation event source; thread call was pending=NO
2024-11-06 10:33:29.645631-0500 0x8c0e     Default     0x0                  0      0    kernel: (IODisplayPortFamily) IOAV[1046] AppleDisplayCrossbar(display-crossbar0)<0x100000320>::displayAllocationEventOccurred_block_invoke_2: no available UFP for DFP(0x100000339) on domain0; It remains pending; continue..
2024-11-06 10:33:29.645639-0500 0x8c0e     Default     0x0                  0      0    kernel: (IODisplayPortFamily) IOAV[1048] AppleDisplayCrossbar(display-crossbar0)<0x100000320>::displayAllocationEventOccurred: Attempting to free resources for pending DFPs..
2024-11-06 10:33:29.645645-0500 0x8c0e     Default     0x0                  0      0    kernel: (IODisplayPortFamily) IOAV[1050] AppleDisplayCrossbar(display-crossbar0)<0x100000320>::makeInactiveUFPAvailable: searching for inactive UFP with domain-mask 1...
2024-11-06 10:33:29.645652-0500 0x8c0e     Default     0x0                  0      0    kernel: (IODisplayPortFamily) IOAV[1052] AppleDisplayCrossbar(display-crossbar0)<0x100000320>::makeInactiveUFPAvailable_block_invoke_2: checking ufp(100000585) -> dfp(10000031f)...
2024-11-06 10:33:29.645663-0500 0x8c0e     Default     0x0                  0      0    kernel: (IODisplayPortFamily) IOAV[1054] AppleDisplayCrossbar(display-crossbar0)<0x100000320>::makeInactiveUFPAvailable_block_invoke_2: skipping ufp(1000005a5) -> noconnect...
2024-11-06 10:33:29.645669-0500 0x8c0e     Default     0x0                  0      0    kernel: (IODisplayPortFamily) IOAV[1056] AppleDisplayCrossbar(display-crossbar0)<0x100000320>::displayAllocationEventOccurred: DFPs processed: 1 allocated: 0 domains: 0x1
2024-11-06 11:02:59.644843-0500 0x28c      Default     0x0                  0      0    kernel: (RTBuddy) [DCPEXT:oInterfaceIOAV.cpp:1234] unplug_gated: display HPD removed
2024-11-06 11:02:59.684451-0500 0xe8c      Default     0x0                  0      0    kernel: (IOMobileGraphicsFamily) request_power_change second_external 0 powerstate0 fdisplaytype 1
2024-11-06 11:03:01.828515-0500 0x28c      Default     0x0                  0      0    kernel: (RTBuddy) [DCPEXT:eoInterfaceIOAV.cpp:801] plug_gated: display HPD asserted.
2024-11-06 11:03:01.885620-0500 0xe8c      Default     0x0                  0      0    kernel: (IOMobileGraphicsFamily) request_power_change second_external 0 powerstate1 fdisplaytype 1
2024-11-06 11:03:02.166894-0500 0xd70      Default     0x0                  0      0    kernel: (IOMobileGraphicsFamily) static IOReturn IOMobileFramebufferUserClient::s_map_display_type(IOMobileFramebufferUserClient *, void *, IOExternalMethodArguments *) UserClient display type is 1

Any Idea can be done here ? Any apple expert ?

Reply

Answer 2

Dec 10, 2024 10:26 AM in response to supercondr

Yes, I have an ultrawide LG monitor. Worked great before Sequoia. I do see multiple color profiles are being created, they look like duplicates. But deleting them doesn't fix the issue, it ends up creating them again.

I called support twice about this. I took the following steps, to no avail:

1) Deleted the duplicate color profiles for my LG monitor. Didn't fix it. It creates duplicates again.

2) Tried Safe Mode.

3) Tried to create a 2nd user/account on my macbook, it still does it on the second user.

4) Re-installed Sequoia (was hoping I'd get the option to downgrade, but no go). Still does it on a clean install.

5) I also wondered if it was connected to the new Sequoia motion backgrounds, so I turned those off. Didn't help.

6) Tried a different HDMI cable.

So now every single Zoom meeting I just lose my screens and my meeting blips several times. It's endlessly frustrating. I hope someone prioritizes this fix soon. It seems to me the macbook loses it's connection to the 2nd monitor, as my windows all momentarily move to the macbook as if I unplugged my monitor, but then instantly re-connects. So you get a blink, flash, and then another blink while it reconnects and then it's back to normal. But it's terribly disruptive.

Reply

Answer 3

h3ct0rjs

Level 1

8 points

Dec 10, 2024 10:48 AM in response to Mothymoth

Yep, I have seen this issue over all the internet, in my case I also use LG. The final solution was to reformat my Mac Book Air a go back to Sonoma, I also identified the wifi connect and disconnect..

Not really cool. I will wait for a long time to update to the new OS version.

Reply

Answer 4

Mothymoth Author

Level 1

7 points

Dec 10, 2024 12:32 PM in response to h3ct0rjs

Yeah, same here. I went back to Monterey. that's what I was running before all this.

Out of curiosity, have you run into this issue on Sonoma or the other OS's before Sequoia but after Monterey? I would like some newer features without my displays being compromised.

Reply

Answer 5

Dec 21, 2024 2:45 AM in response to Mothymoth

So I replaced my $70 Mac USB-C to HDMI (Multiport) adapter with a much less expensive Anker USB-C to HDMI adapter and it fixed this problem. Something in Sequoia broke the mac version of this adapter, which is ironic considering it's so expensive. I also tested with a Nintendo Switch USB-C to HDMI adapter with the same results. They work fine, the disconnecting/blinking went away.

Reply

Answer 6

Dec 10, 2024 10:03 AM in response to Mothymoth

Same here. The moment I upgraded to Sequoia a few months ago this started. It's awfully disruptive. It really needs to be fixed.

Reply

Answer 7

Dec 10, 2024 10:08 AM in response to Mothymoth

I have seen this issue on a number of systems I help support. Even a Mac mini running an earlier vers of OS. The thing that’s odd, it doesn’t happen onANY Apple monitors, only in my case LG monitors

Reply