rockowitz
rockowitz
> Let me rephrase that, just to make sure. Options like --edid are used to identify a matching I2C bus number that corresponds to the monitor. However, --bus forces the...
> However, --bus forces the I2C bus number to be the specified one, and ddcutil will merely verify that the number corresponds to a monitor. Is this correct? > >...
Thank you for the detailed report. I have some questions. Background: It is desirable to read more that the expected number of bytes from the I2C bus to aid in...
First, I want you to know that I don't expect to have much time for ddcutil in the coming week. I do regard this as a significant issue however, so...
I have time again to devote to ddcutil. Please submit the output of the tests I outlined and I'll try to figure out what's going on.
As you've noted, implementations of feature x60 can be wonky. I am surprised though that you're having problems on an HP Z series monitor as that's a professional quality line....
Ouch! There have been a few reports of bricked Xaomi Mi monitors, but I don't recall one with a name brand like Asus and in a documented feature no less....
I agree that some sort of warning is in order. The question for me is how to do it in a way that's proportionate to the risk. Bricking a monitor...
Suggest you use an identification option such as ***--sn*** that is unaffected by bus assignment or display id assignment.
Looking more closely, I see that both your U2414H monitor is connected both to HDMI and DP-3. (Or is it the pathological situation where there are two monitors with identical...