rockowitz

Is this something you've actually experienced with **ddcutil**, or just a general heads up? In normal operation, **ddcutil** prefilters the i2c devices using /sys. If the device has a class...

I've added "AMDGPU SMU" to the list of names for devices that should be ignored, and pushed the change to branch 1.1.0-dev. Let me know if it works. The problem...

The current 1.1.0-dev branch contains a fix to the check if a /dev/i2c device is ignorable. First the device name is checked. If the device name is not on the...

What is the context in which backporting a fix to a prior release is important? The only situation in which I could see this mattering is if an application is...

In general, ddcutil avoids probing SMU devices if possible. Not only can this cause hard failures, but probing I2C buses is an expensive operation, to be avoided when we know...

@ltuikov Luben, I assume you're an appropriate person to ask the following questions. If not, can you pass it on or redirect me? I'm continuing to see problem reports with...

I strongly suspect that your V7 monitor on /dev/i2c-0 has a marginal I2C implementation. Responses to DDC/CI requests should start with a single x6e byte. In your case there are...

I have uploaded additional diagnostics to branch 1.2.3-dev. Please build from that branch, execute the following commands, and submit the output as an attachment: ~~~ ddcutil --version ddcutil detect --ddc...

Be careful using multiple DDC programs. There can be conflict. In ddcutil, they appear as EBUSY errors. The solution is command line option ***--force-slave-address*** which tries to seize the /dev/i2c...

@laggykiller Just want you to know that I'm not ignoring your issue. I had minor surgery on Thursday and my brain is mush. Will get back to you when I'm...