<html><head></head><body><div>The issue was module renaming, using nvidia-current fixed the issue. </div><div><br></div><div>Thanks.</div><div><br></div><div>On Sun, 14 Nov 2021 20:15:38 +0100 Andreas Beckmann <<a href="mailto:anbe@debian.org">anbe@debian.org</a>> wrote:<br></div><div>> On 14/11/2021 17.30, themightydeity wrote:<br></div><div>> > Package: nvidia-driver<br></div><div>> > Version: 470.82.00-1<br></div><div>> > Severity: normal<br></div><div>> > Tags: newcomer<br></div><div>> > X-Debbugs-Cc: <a href="mailto:themightydeity@gmail.com">themightydeity@gmail.com</a><br></div><div>> > <br></div><div>> > As mentioned here: <a href="https://www.ddcutil.com/nvidia/">https://www.ddcutil.com/nvidia/</a> for ddcutil (DDC/CI) (i2c<br></div><div>> > communication) to work properly in nvidia's proprietary driver. This conf is<br></div><div>> > needed in modprobe:<br></div><div>> > <br></div><div>> > options nvidia NVreg_RegistryDwords=RMUseSwI2c=0x01;RMI2cSpeed=100<br></div><div>> <br></div><div>> You have these settings in /etc/modprobe.d/nvidia-extra.conf<br></div><div>> <br></div><div>> Please try<br></div><div>> options nvidia-current key=value...<br></div><div>> Perhaps the options don't get activated because of the module renaming ...<br></div><div>> <br></div><div>> I noticed you have a /etc/modules-load.d/nouveau.conf ... does it <br></div><div>> somehow interfere?<br></div><div>> <br></div><div>> <br></div><div>> Andreas<br></div><div>> <br></div><div>> <br></div><div><br></div><div><span></span></div></body></html>