@rich.ayotte @vinod272, I believe the brightness controls are working for me on my p1 gen5. I’m running Hyprland WM on SDDM on a 6.3.3-arch1-1 kernel booted with the following parameters:
quiet loglevel=3 nosplash fbcon=nodefer nvidia_drm.modeset=1
nvidia-dkms version 530.41.03-1.
I think the first thing to chech is that the virtual files in
/sys/class/backlight/nvidia_0/* work. My understanding from reading the
/usr/share/doc/nvidia/README installed by the driver package is that:
o When available, the NVIDIA driver installs a backlight handler that
allows access to the driver’s backlight controller through
/sys/class/backlight/nvidia_0. This option can be disabled by passing the
parameter to the nvidia kernel module.
So, the /sys/class interface is automatically presented if/when the hardware is discovered. You shouldn’t need to set that to 1.
Indeed, in my case, the hardware is discovered, and the driver presents the interface:
├── device -> ../../../0000:01:00.0
│ ├── autosuspend_delay_ms
│ ├── control
│ ├── runtime_active_time
│ ├── runtime_status
│ └── runtime_suspended_time
├── subsystem -> ../../../../../../class/backlight
AND I can peek and poke at the files (as described here, and in fact everything works, HOWEVER, max_brightness is WRONG, for me it’s reported as 100, however I can only set brightness between 1 and 10. It appears to apply modulo 10 math when setting brightness higher than 10, so setting it to 1, 11, 21… have identical effect (min bright)…