mirror of
https://github.com/MonitorControl/MonitorControl.git
synced 2026-05-15 22:01:08 -06:00
[GH-ISSUE #495] ASUS VG289Q1A detected but not supported #389
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#389
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 @Agusum on GitHub (Aug 2, 2021).
Original GitHub issue: https://github.com/MonitorControl/MonitorControl/issues/495
Checklist
Describe the bug
The ASUS VG289Q1A monitor is detected but brightness and volume doesn't change when moving the sliders or using the keyboard.
To Reproduce
Steps to reproduce the behavior:
Sliders are greyed out and even when moving them up or down it doesn't change the brightness nor volume of the display.
Expected behavior
Volume and brightness adjusted
Screenshots
https://imgur.com/a/gNyGlQL
Additional context
Add any other context about the problem here.
Environment Information (please complete the following information):
@waydabber commented on GitHub (Aug 20, 2021):
Hi @Agusum
2.2.0 was pulled due to various issues. Do you have this problem with 2.1.0 or the latest 3.0.0 beta? Thank you!
@Agusum commented on GitHub (Aug 21, 2021):
I updated to 3.0.0 beta 8 and it is still not working: https://imgur.com/a/IzTxgPy. Thanks for looking into it!
@waydabber commented on GitHub (Aug 21, 2021):
Hi Agusum. The fact that the sliders are grayed out is normal (this is the standard Apple designed look of the sliders in dark mode in Big Sur and Monterey, it does not mean that they are disabled).
What you should try is whether using a different tool, can you control brightness or volume? If not, then it's probably a monitor issue and we can't do much about it. Please see the instructions here:
https://github.com/MonitorControl/MonitorControl/wiki/Monitor-Troubleshooting
Thank you!
@Agusum commented on GitHub (Aug 21, 2021):
I tried doing that when I got the monitor and raised an issue in the ddcctl repo but I don't know if the error I get is because my monitor doesn't support it or because there's a bug in the software. Would you know based on the error message I get?
Thanks!
@waydabber commented on GitHub (Aug 21, 2021):
I think something is wrong there then. I see that you are using a dock. Can you try it directly?
@Agusum commented on GitHub (Aug 21, 2021):
I did that now with an old MacBook Pro that has an HDMI port (I don't have a HDMI to USB-C cable for the 15" atm) and MonitorControl works fine. Any idea how I can make it work with the dock or how to know which docks are compatible?
This is the dock I'm using.
@waydabber commented on GitHub (Aug 21, 2021):
This dock uses DisplayLink which does not support DDC at all on mac and is more like a virtual display. You'll need a dock that routes the native displayport stream to the display. Such USB-C docks are available but they have USB2 only (because of bandwidth limitations), or there might be some more expensive Thunderbolt docks. The main thing is to avoid anything that has the DisplayLink logo or name in its product description.
I'll close this issue for now. Best of luck and thanks for the feedback!
@Agusum commented on GitHub (Aug 21, 2021):
Thanks for the info @waydabber! How did you know the dock uses DisplayLink? I don't see any description of it nor the logo in the Amazon page.
@waydabber commented on GitHub (Aug 21, 2021):
I found it somewhere (probably on the US amazon site). But every dock that is simple USB-C and has multiple display outputs or claims USB3 or gigabit lan while still providing 4K-60Hz out can only be displaylink (it uses a compressed USB video basically).
You can also try 3.0.0 and see if it reports the display controllable or as unsupported/virtual display.