https://bugzilla.kernel.org/show_bug.cgi?id=204807 --- Comment #96 from Tom Lloyd (napalmllama@xxxxxxxxx) --- (In reply to Denis Pauk from comment #88) > Created attachment 298669 [details] > POC: Add support for access via Asus WMI to nct6775 by board/vendor name > detect > > Updated version with check vendor name and fix for possible issues with non > ASUS motherboards, added names of motherboards have mentioned in bug. I will > also check possible way for use functions pointers instead conditional > checks equal to access_wmi. After that I will try to send patch to review. > > (In reply to comment #87) > > I added my board "ROG STRIX B550-F GAMING (WI-FI)" and added patch against > > 5.14.1-arch1-1 BIOS 2423 08/10/2021. > > Thank you, I have added your board also. > > (In reply to comment #86) > > Please add my board name "TUF GAMING B550-PLUS". > > Thank you, I have added it to list. What the distro do you use? > > For debian it can be: > * git clone > git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git > * cd linux-stable > * git check v5.14 > * cp /boot/config-5.10.0-8-amd64 .config > * make CC="ccache gcc" -j 32 > * make CC="ccache gcc" -j 32 bindeb-pkg > * sudo dpkg -i ../linux-image-5.14.0+_5.14.0+-1_amd64.deb > > Look to https://wiki.debian.org/BuildADebianKernelPackage Denis, I'm on Gentoo, and already have the kernel sources unpacked and ready to go (5.13.13-gentoo). I did the following: # rmmod nct6775 # cd /usrc/src/linux # patch -i ~/nct6775_wmi_v3.patch -p1 # make modules -j12 # mv /lib/modules/5.13.13-gentoo-splig-3-sensors/kernel/drivers/hwmon/nct6775.ko /lib/modules/5.13.13-gentoo-splig-3-sensors/kernel/drivers/hwmon/nct6775.ko.orig # cp drivers/hwmon/nct6775.ko /lib/modules/5.13.13-gentoo-splig-3-sensors/kernel/drivers/hwmon/nct6775.ko # modprobe nct6775 "sensors" output remains the same: nct6798-isa-0290 Adapter: ISA adapter in0: 376.00 mV (min = +0.00 V, max = +1.74 V) in1: 1000.00 mV (min = +0.00 V, max = +0.00 V) ALARM in2: 3.39 V (min = +0.00 V, max = +0.00 V) ALARM in3: 3.30 V (min = +0.00 V, max = +0.00 V) ALARM in4: 1.01 V (min = +0.00 V, max = +0.00 V) ALARM in5: 880.00 mV (min = +0.00 V, max = +0.00 V) ALARM in6: 256.00 mV (min = +0.00 V, max = +0.00 V) ALARM in7: 3.39 V (min = +0.00 V, max = +0.00 V) ALARM in8: 3.28 V (min = +0.00 V, max = +0.00 V) ALARM in9: 904.00 mV (min = +0.00 V, max = +0.00 V) ALARM in10: 264.00 mV (min = +0.00 V, max = +0.00 V) ALARM in11: 1.02 V (min = +0.00 V, max = +0.00 V) ALARM in12: 1.04 V (min = +0.00 V, max = +0.00 V) ALARM in13: 368.00 mV (min = +0.00 V, max = +0.00 V) ALARM in14: 272.00 mV (min = +0.00 V, max = +0.00 V) ALARM fan1: 0 RPM (min = 0 RPM) fan2: 716 RPM (min = 0 RPM) fan3: 496 RPM (min = 0 RPM) fan4: 327 RPM (min = 0 RPM) fan5: 0 RPM (min = 0 RPM) fan6: 0 RPM (min = 0 RPM) fan7: 0 RPM (min = 0 RPM) SYSTIN: +33.0°C (high = +80.0°C, hyst = +75.0°C) sensor = thermistor CPUTIN: +35.0°C (high = +80.0°C, hyst = +75.0°C) sensor = thermistor AUXTIN0: +85.0°C sensor = thermistor AUXTIN1: +55.0°C sensor = thermistor AUXTIN2: -61.0°C sensor = thermistor AUXTIN3: +79.0°C sensor = thermistor PECI Agent 0 Calibration: +34.5°C PCH_CHIP_CPU_MAX_TEMP: +0.0°C PCH_CHIP_TEMP: +0.0°C PCH_CPU_TEMP: +0.0°C intrusion0: ALARM intrusion1: ALARM beep_enable: disabled dmesg with tree module: [ 3596.867638] nct6775: Found NCT6798D or compatible chip at 0x2e:0x290 [ 3596.867642] ACPI Warning: SystemIO range 0x0000000000000295-0x0000000000000296 conflicts with OpRegion 0x0000000000000290-0x0000000000000299 (\AMW0.SHWM) (20210331/utaddress-204) [ 3596.867645] ACPI: OSL: Resource conflict; ACPI support missing from driver? [ 3596.867646] ACPI: OSL: Resource conflict: System may be unstable or behave erratically dmesg with patched module: [ 3681.885428] nct6775: Using Asus WMI to access chip [ 3681.885468] nct6775: Found NCT6798D or compatible chip at 0x2e:0x290 /proc/cmdline: BOOT_IMAGE=/boot/vmlinuz-5.13.13-gentoo-splig-3-sensors root=/dev/nvme0n1p3 ro module_blacklist=nouveau acpi_enforce_resources=lax I hope that's of some use. The differing dmesg output suggests that the patch is helping, but shouldn't there be a change (improvement) to the sensors output? -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.
