search

daitj / gnome-display-brightness-ddcutil

Display brightness slider for gnome shell using ddcutil backend
GNU General Public License v3.0
294 stars 36 forks source link

Extension doesn't seam to work with ddcutil 2.0.0 #115

Closed prodrigestivill closed 10 months ago

prodrigestivill commented 11 months ago

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

Nov 03 16:20:48 gnome-shell[4623]: display-brightness-ddcutil extension:
                                                display ROG PG279Q, current: 0.33 => 0.32, new brightness: NaN, new value: 32
Nov 03 16:20:48 gnome-shell[4623]: display-brightness-ddcutil extension:
                                                Write collector update, current countdown is 52 for 5
Nov 03 16:20:48 ddcutil[5514]: busno=5. Monitor apparently returns -EIO for unsupported features. This cannot be relied on.
Nov 03 16:20:48 gnome-shell[4623]: display-brightness-ddcutil extension:
                                                display ROG PG279Q, current: 0.32 => 0.31, new brightness: NaN, new value: 31
Nov 03 16:20:48 gnome-shell[4623]: display-brightness-ddcutil extension:
                                                Write collector update, current countdown is 44 for 5
Nov 03 16:20:48 gnome-shell[4623]: display-brightness-ddcutil extension:
                                                Write in queue countdown over for 5
Nov 03 16:20:48 gnome-shell[4623]: display-brightness-ddcutil extension:
                                                async /usr/bin/ddcutil setvcp 10 NaN --bus 5 --sleep-multiplier 1 
Nov 03 16:20:48 gnome-shell[5514]: Not a number: "NaN"
Nov 03 16:20:48 gnome-shell[5514]: Invalid VCP value: NaN
Nov 03 16:20:48 gnome-shell[5514]: busno=5. Monitor apparently returns -EIO for unsupported features. This cannot be relied on.
Nov 03 16:20:49 ddcutil[5520]: busno=5. Monitor apparently returns -EIO for unsupported features. This cannot be relied on.
Nov 03 16:20:49 gnome-shell[5520]: Not a number: "NaN"
Nov 03 16:20:49 gnome-shell[5520]: Invalid VCP value: NaN
Nov 03 16:20:49 gnome-shell[5520]: busno=5. Monitor apparently returns -EIO for unsupported features. This cannot be relied on.

Desktop (please complete the following information):

Additional context Downgraded to ddcutil to 1.4.1 and it works.

Susanthakuri92 commented 10 months ago

Thanks had a same problem downgraded and now its working.

daitj commented 10 months ago

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
prodrigestivill commented 10 months ago

The requested output is:

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
trucndt commented 10 months ago

Same issue here, it is stuck at "Initializing" with ddcutil 2.0.0

daitj commented 10 months ago

@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
prodrigestivill commented 10 months ago

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.

prodrigestivill commented 10 months ago

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.

daitj commented 10 months ago

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: @.***>