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
VG248 : Invalid display #381
Comments
It's not clear if invalid data or no data is being returned from the monitor. Option --ddc should give more information. Using a large sleep-multiplier value is the first thing to try. It might help to upgrade to the latest 2.1.3 ddcutil release. |
I added the ddc option , see attached log. Right now, glib-2.0 is required to be >= 2.40 to build, which isn't distributed in Ubuntu 24.04 (currently 2.38). So it won't be trivial to test the latest version, will check see how I can test that. |
I think you're confusing glib with glibc. glib 2.40 was released in 2014. glib 2.40 glibc is currently under development. |
Try running ddcutil getvcp 10 --ddc --bus 5 and ddcutil getvcp 10 --ddc --bus 6*. I expect you'll lots of garbage response packets for the former. |
|
After figuring out my mistake about glib and building the latest version, here is more logs about the issue.
|
Let's deal with the crash first. Add tracing to the command that triggers the crash: .ddcutil getvcp 10 --ddc --bus 5 --sleep-multiplier 4 --trcfile dsa2.c Setting the sleep multiplier without disabling dynamic sleep adjustment just discards cached dsa data and starts with the specified sleep multiplier. I very much doubt it changes anything, but try: ddcutil getvcp 10 --bus 5 --ddc --sleep_multiplier 4 --disable-dynamic-sleep Drive i2c_dev actually has 2 interfaces, one using ioctl() and one using file write()/read(). Normally ddcutil uses the ioctl() interface. To use the file io interface: ddcutil getvcp 10 --bus 5 --ddc --sleep-multiplier 4 --disable-dynamic-sleep --use-file-io Please submit the output of these 3 commands. (Note that tracing is enabled only on the first.) There's no need to continue to send output from ddcutil interrogate. |
Here is all the logs for the different commands: |
I have two screens connected to my desktop. Both are displaying and working correctly.
One is fully working including DDC with it.
One is detected but
DDC communication failed
.I verified that DDC is enabled on the screen menu.
Attached the output of
interrogate
.ddcutil.log
I tried to increase the sleep multiplier, without success.
The text was updated successfully, but these errors were encountered: