-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
It exits with status 255 and doesn't seem to do anything. #8
Comments
Hi @andrejpodzimek ! Seems your problem is the same as mine here: #5 Try to use |
Not sure how
|
And yet
|
Did you probe them with 'sudo', or does your Linux user in Seems that I can get same like results as your if I remove myself from the (With 'sudo' you should not get any problems, but you could drop yourself in that group for a test. Of course with session restart.) |
I don't have an |
My monitor also a Thunderbolt only monitor. The 2019 release of the smaller one: https://www.lg.com/us/monitors/lg-24MD4KL-B-4k-uhd-led-monitor 'All' things what Anyway if you do not have Just to show the background of mine:
also
So you can see there is no dedicated Thunderbolt bus handled by Linux. |
I don’t have any Ultimately I hacked it this way — that snippet shows the HID commands that control brightness on the 27MD5KL. (Nothing i2c-related seems to be involved. There is a similar HID-based protocol for (some) Apple / Samsung monitors, just a few magic numbers are different.) Just for the record, there is a Thunderbolt bus handled by Linux (not necessarily dedicated in any way or sense, but there is one):
(Side note 1: I guess the correct way to manage the (Side note 2: DisplayPort / Thunderbolt / USB co-existence is surprising in many ways. For example, adapters from Thunderbolt to DisplayPort show up on the USB bus as USB 2.0 devices. These USB “devices” are not directly involved in DisplayPort transfers; USB 2.0 is nowhere near fast enough for that anyway. They probably serve as identifiers of some sort, to tell the machine that there is a DisplayPort connected to a Thunderbolt port. In the past I thought that Thunderbolt->DisplayPort adapters were passive, until I got a few of them and realized they were semi-active, in a very strange way.)
|
Hi! As now I have some minutes to answer here are just some final thoughts.
So I just tried to spotlight that if you see through
But independently from these written lines I hope somehow you could reach successful result in any way as seems with my NUC8i7 and it's Thunderbolt control the result is fine with one 'almost' same like monitor as your with Best regards, |
OK, now I see that I had been completely wrong when I throught that there was no i2c involved. Oh yes, there is i2c, it was just that I didn't have the right kernel module loaded. Now I've also retried |
I glad for your success! Currently I'm automatically changing the brightness of mine based on my Spyder X colorimeter's ambient light measurement as I don't know how to reach any data from the monitor's own ambient light meter, and as I'm not a programmer there are limits in front of me:D My
If I could finish these 3 problems would be everything perfect.
|
Just to inform anybody about the result I find out that I missed to put myself into
|
The monitor is an UltraFine 27MD5KL. It works fine, albeit with certain difficulties.
Here's a full
strace -f
.The text was updated successfully, but these errors were encountered: