I am trying to load kernel driver it87 for my Gigabyte Z790 AERO G motherboard (it is not loaded automatically). The Z790 AERO G has two chips, ITE IT8689E & ITE IT87952E. Trying "modprobe it87 ignore_resource_conflict=1 force_id=0x8695,0x8689" loads, but I see in dmesg: [ 1240.576414] it87: Found IT87952E chip at 0xa40, revision 2 [ 1240.576558] it87: Beeping is supported [ 1240.576564] ACPI Warning: SystemIO range 0x0000000000000A45-0x0000000000000A46 conflicts with OpRegion 0x0000000000000A45-0x0000000000000A46 (\GSA1.SIO1) (20221020/utaddress-204) [ 1240.576575] ACPI: OSL: Resource conflict; ACPI support missing from driver? Only the second chip is detected (but then its not visible in lm_sensors). The same happens if I change the ids of the two chips: force_id=0x8689,0x8695 If I try "modprobe it87 ignore_resource_conflict=1 force_id=0x8689" I get the following error: modprobe: ERROR: could not insert 'it87': No such device I was looking at the source of it87 in kernel, and around line 3414, there are references to specific motherboards: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/tree/drivers/hwmon/it87.c?h=linux-6.3.y#n3414 Can the string "Z790 AERO G" be also added there? dmidecode|grep -i z790 Product Name: Z790 AERO G Family: Z790 MB Product Name: Z790 AERO G Reproducible: Always Steps to Reproduce: 1.modprobe it87 ignore_resource_conflict=1 ignore_resource_conflict=1 force_id=0x8689,0x8695 Has to be run on Gigabyte Z790 AERO G boards Actual Results: Only one of the two io-sensors chips detected. Expected Results: Both io-sensors chips detected, and lm_sensors able to use them to report, voltages, fan speeds, etc.
As a workaround, you can append "acpi_enforce_resources=lax" to the kernel command-line: https://hansdegoede.livejournal.com/7932.html That worked for me on an ASUS motherboard with a different I/O chip until the the bug was fixed: Bug 2127658 - nct6775 does not populate /sys/class/hwmon/ on ASUS motherboard with NCT6798D sensor chip
Fedora Linux 38 entered end-of-life (EOL) status on 2024-05-21. Fedora Linux 38 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed.