I recently upgraded from a 7 year old laptop to a 3700x and a 2070S with an Asus prime x570-pro motherboard, and ever since the upgrade, I have been battling to get temp monitoring working.
First was the saga with the k10temp module, and a kernel patch. But now thanks to official updates coming around, I have that working.
What I don’t have working is the motherboard monitoring:
Running sudo sensors-detect –auto reveals that the motherboard uses a NCT6798dchip and requires the nct6775 module. But when I try to load it, I get a whole load of nothing.
dmesg sheds some more light on the problem by telling me that the nct6775 is having problems
nct6775: Found NCT6798D or compatible chip at 0x2e:0x290
[ 28.373543] ACPI Warning: SystemIO range 0x0000000000000295-0x0000000000000296 conflicts with OpRegion 0x0000000000000290-0x0000000000000299 (\AMW0.SHWM) (20190703/utaddress-204)
[ 28.373550] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
A quick google search later reveals that in order to get the module to load and read temps, I need to set the kernel parameter acpi_enforce_resources=lax [1]
However after even more digging, I see that setting this can cause issues [2].
(I did go and do it anyway, and it does seem to work)
So finally my question:
How should I go about permanently fixing this? it seems to me that just leaving the acpi as lax is a horrid idea, and I have yet to find anything else online as to how to fix without without the lax method.
(I have attached a github gist containing all of the fun dmesg/sensors stuff so I don’t assault your eyes)
-Skipp1
Amd 3700x
Nvidia 2070 Super
Asus Prime x570-pro (BIOS 1201 (the latest with ABBA))
OpenSUSE Tumbleweed (20191012) (5.3.5-1-default)
[gist] https://gist.github.com/Skipp1/9d38c585b16e3ea3222972c271ef529c
[1] https://bbs.archlinux.org/viewtopic.php?id=210351
[2] https://web.archive.org/web/20150823051215/http://www.lm-sensors.org/wiki/FAQ/Chapter3
(Section 39: My sensors have stopped working in kernel 2.6.31)