Skip to content
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

Error when trying to get capabilities #5

Open
Hexalyse opened this issue Jun 20, 2022 · 1 comment
Open

Error when trying to get capabilities #5

Hexalyse opened this issue Jun 20, 2022 · 1 comment

Comments

@Hexalyse
Copy link

Hexalyse commented Jun 20, 2022

Hello,

I've been trying to use your crate unsuccessfully. When trying to get the capabilities of my screen, I get this error :

The unwrap returns thread 'main' panicked at 'called Result::unwrap() on an Err value: Failed to read capabilities string

And the detail is : An error occurred while transmitting data to the device on the I2C bus. (os error -1071241854)'

I'm on Windows, and I don't understand why it's having an error about I2C, while it's supposed to be using winapi to communicate with the screen (and the display.info.backend value indeed is"winapi").

@ThalusA
Copy link

ThalusA commented Jul 8, 2022

I also have this problem, For the i2C error it was from the NVIDIA-API side for me but it's not problematic in my context.

The thing I don't understand is that display.update_capabilities() is never used in ddcset-rs except for winapi but it's implemented in all ddc api. Every time I use this function I get an error saying Failed to read capabilities string.

So my final question, is why and how we should use the update_capabilities method ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants