Closed prodrigestivill closed 1 year ago
Thanks had a same problem downgraded and now its working.
I just built ddcutil v2.0.0 from the source https://github.com/rockowitz/ddcutil/tree/2.0.0-release in my Debian system and I cannot reproduce the error. It could of course be just the Arch release has some issues.
@prodrigestivill could you post the output of in your system with 2.0.0
ddcutil getvcp 10 --brief --bus 5
The requested output is:
Using version 1.4.1
$ ddcutil getvcp 10 --brief --bus 5
VCP 10 C 0 100
Using version 2.0.0
$ ddcutil getvcp 10 --brief --bus 5
busno=5. Monitor apparently returns -EIO for unsupported features. This cannot be relied on.
VCP 10 C 0 100
But I'm starting to thing it might not only be a ddcutil version issue.
It is true, that I require to enable this extension setting:
Otherwise no brightnes bar appear.
Here is the output using version 1.4.1 without disabling display state check:
gnome-shell[1887]: display-brightness-ddcutil extension:
ddcutil brief info:
Display 1
I2C bus: /dev/i2c-5
DRM connector: card1-DP-1
Monitor: ACI:ROG PG279Q:#ASNlg6FzuzPd
gnome-shell[1887]: display-brightness-ddcutil extension:
ddcutil brief info found bus line:
I2C bus: /dev/i2c-5
gnome-shell[1887]: display-brightness-ddcutil extension:
ddcutil reading display state for bus: 5
gnome-shell[1887]: display-brightness-ddcutil extension:
ddcutil reading display status for bus: 5 is: VCP D6 ERR
Also as a note, I'm using nvidia propietary driver that requires the following module options (/etc/modprobe.d/nvidia.conf
):
options nvidia NVreg_RegistryDwords=RMUseSwI2c=0x01;RMI2cSpeed=100
Same issue here, it is stuck at "Initializing" with ddcutil 2.0.0
@prodrigestivill What is the output of
ddcutil getvcp D6 --brief --bus 5
I want to know if monitor's state is detect correctly and also
ddcutil getvcp 10 --brief --bus 5 2>/dev/null
I want to know if that busno=5. Monitor apparently returns -EIO for unsupported features. This cannot be relied on.
message is redirected ot stdout ot stderr
Just FYI, in newer version of Nvidia driver you do not need this anymore. I do not think this is the issu though.
options nvidia NVreg_RegistryDwords=RMUseSwI2c=0x01;RMI2cSpeed=100
Hello @daitj,
I removed the NVreg_RegistryDwords
module option and it work the same way using the 1.4.1 without issues.
I also upgraded to 2.0.0 and those are the output you requested:
$ ddcutil getvcp D6 --brief --bus 5
busno=5. Monitor apparently returns -EIO for unsupported features. This cannot be relied on.
VCP D6 ERR
$ ddcutil getvcp 10 --brief --bus 5 2>/dev/null
busno=5. Monitor apparently returns -EIO for unsupported features. This cannot be relied on.
VCP 10 C 0 100
It looks like this error is printed to stdout, :(
Thanks for all the effort.
Perfect version 47 works with ddcutil 2.0.0!!! Thanks!
PD: as a note the version 47 is not yet uploaded to gnome extensions repository.
It is already uploaded but review is pending.
On November 14, 2023 7:48:05 PM GMT+02:00, Pau RE @.***> wrote:
Perfect version 47 works with ddcutil 2.0.0!!! Thanks!
PD: as a note the version 47 is not yet uploaded to gnome extensions repository.
-- Reply to this email directly or view it on GitHub: https://github.com/daitj/gnome-display-brightness-ddcutil/issues/115#issuecomment-1810809131 You are receiving this because you modified the open/close state.
Message ID: @.***>
Describe the bug The extension is unable to read the current brightness nor change it.
To Reproduce Update to ddcutil 2.0.0.
Delete cache file if it exists and try again Deleted
$XDG_CACHE_HOME/ddcutil
folder and$XDG_CACHE_HOME/ddcutil_detect
and still fails.Journal logs
Desktop (please complete the following information):
Additional context Downgraded to ddcutil to 1.4.1 and it works.