Closed dfaulkner closed 1 year ago
I had a similar problem with a docking station (MacBook -> Thunderbolt -> Docking Station -> DisplayPort -> Display). In 19 cases out of 20 everything was working fine, then I just couldn't control the monitor via ddcctl
until restart.
I simply returned the docking station and never had a problem ever since, not a single one. I know it might not solve your issue, just FYI.
Absent the dock, how are you converting Thunderbolt to your external display? I'll try to find a higher quality dock/adapter, but that will take a while.
I'm using this guy: (I wanted a direct laptop-display cable instead of a cable + an adapter)
I'm closing my original issue. After reporting this, I discovered my MacBook had hardware issues with its main logic board. After the repair, everything seems to work just fine.
2019 MacBook Pro with a pair of identical HP external monitors (HP EliteDisplay E232), connected to my MacBook via HDMI, via a couple of adapters:
Display 1: j5 create JCA374 USB-C Multi-Adapter - HDMI/Ethernet/USB 3.1 HUB/PD 2.0 Display 2: Satechi ST-TCPHEM Type-C Pro Hub adapter with ethernet
I'm able to use ddccdl to talk to the monitors some times, but not always. My Primary use case is to change the input. When ddcctl detects the monitors, this works every time: I can switch to DisplayPort (-i 15) or to HDMI (-i 17), regardless of which of the two inputs the monitors are on when I start.
More than half of the time, ddcctl just doesn't see the monitors. It will inform me "I: found 0 external display" and exit. I can't seem to find a circumstance that makes a difference between detecting the monitors and not detecting the monitors.
Here is the identity string output by ddccdl (when it works):