mirror of
https://github.com/MonitorControl/MonitorControl.git
synced 2026-05-15 14:15:55 -06:00
[GH-ISSUE #252] LG HDR 5K not accepting commands via Thunderbolt but Displayport? #198
Labels
No labels
Status: Abandoned
arm64
beta
beta
bug
done
duplicate
enhancement
feedback needed from reporter
in progress
invalid
investigating
known Issue
monitor Issue
pull-request
translation
unable to reproduce
unreleased
x86
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/MonitorControl#198
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @dieoma76 on GitHub (Jul 9, 2020).
Original GitHub issue: https://github.com/MonitorControl/MonitorControl/issues/252
Setup is a MacMini 2018 i5 latest OS (10.15.5) connected to a LG 34WK95U via LG provided Thunderbolt Cable. Neither Volume nor Brightness can be adjusted via MoniktorControl (1.7.1 b574). If i connect the Monitor via Displayport i can change Volume and Brightness. Accoding to Monitor Control the Modell ID of the Monitor is 0x7721 from Vendor 0x9E6D.
Expected behavior
same functionality via Thunderbolt as well as via Displayport Connection
Screenshots
Any ideas? Any way to troubleshoot?
@daffydowden commented on GitHub (Aug 3, 2020):
I'm in the same boat. @dieoma76, did you get any further with this?
@JoniVR commented on GitHub (Aug 14, 2020):
Read the troubleshooting wiki as advised in the checklist (which you removed) on this issue. It's a known issue that some cables/connections don't work or support DDC, it's not a software issue most of the time, it's hardware.
@dieoma76 commented on GitHub (Aug 14, 2020):
well, it´s NOT the cable. This issue is related to this one: In essence: Connecting the same cable to a MacBook Pro MonitorControl works as expected. I assume it´s related to a Combination of integrated Intel GPU and MonitorControl...
@JoniVR commented on GitHub (Aug 14, 2020):
Apologies if I came off rude, it's easy to get in an automated reply state with these issues but it's no excuse.
That makes sense. I'm going to be closing that one and the other ones as there seem to be a lot of issues that basically point to the same issue with the Mac Mini. Duplicate issues will only lower the chances of finding a solution I think. So I'll try to keep the best one open and reference.
@dieoma76 commented on GitHub (Aug 15, 2020):
no Problem and fully agree: Let´s follow up on #267 - i assume many tickets can be closed if we can fix this one finally. Let me know if i can help with tests or further diagnostics...