Package: ddcutil Version: 0.9.9-2 Severity: important Tags: upstream X-Debbugs-Cc: jo...@v5.be
-- System Information: Debian Release: bullseye/sid APT prefers testing-security APT policy: (500, 'testing-security'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-6-amd64 (SMP w/8 CPU threads) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages ddcutil depends on: ii i2c-tools 4.2-1+b1 ii libc6 2.31-11 ii libdrm2 2.4.104-1 ii libglib2.0-0 2.66.8-1 ii libudev1 247.3-5 ii libx11-6 2:1.7.0-2 ii libxrandr2 2:1.5.1-1 ii pci.ids 0.0~2021.02.08-1 ii usb.ids 2021.03.31-1 ii usbutils 1:013-3 ddcutil recommends no packages. ddcutil suggests no packages. -- no debconf information >From the release information on ddcutil >(http://www.ddcutil.com/release_notes/) it seems Linux kernel 5.10 made >changes. They are listed as "docking stations" but in my experience also apply >to directly connected HDMI and Thunderbolt displays. Ddcutil 1.0.1 and 1.1.0 include workarounds for this kernel. On my system bringing back the same capabilities I had under kernel 5.8, whereas with ddcutil 0.9.9 on kernel 5.10 there was simply no device detected. As 5.10 seems to be the default in the upcoming Debian release, it would be very nice to get ddcutil updated as well. I had no issue building ddcutil from source.
