Lm_sensors failed to start

English Hardware
1

I need help with lm-sensors. CoolerControl requires it to work properly and even though I see lm-sensors in list of services in YaST, it always fails to start and I have no idea why. I already tried adding acpi_enforce_resources=lax to kernel parameters and still nothing.

~> systemctl status lm_sensors.service

× lm_sensors.service - Initialize hardware monitoring sensors
     Loaded: loaded (/usr/lib/systemd/system/lm_sensors.service; enabled; preset: disabled)
     Active: failed (Result: resources)
 Invocation: 0676aa77d8ca4034b257fe923750c823
        CPU: 0

Trying to start service via YaST shows this:

Writing the configuration failed:
Could not start ‘lm_sensors’ which is currently not running.
Would you like to continue editing?

sensors-detect doesn’t detect anything.

Sorry, no sensors were detected.
Either your system has no sensors, or they are not supported, or
they are connected to an I2C or SMBus adapter that is not
supported. If you find out what chips are on your board, check
https://hwmon.wiki.kernel.org/device_support_status for driver status.

Yet CoolerControl can read the temperatures from my components but doesn’t display nor controls any of fans.

I am getting pretty miserable trying to solve this. I think I have went through every thread that Google search gave me.

2

@voj0546 So you need to give some hardware details… System, Motherboard etc.

3

Operating System: openSUSE Tumbleweed 20251223
KDE Plasma Version: 6.5.4
KDE Frameworks Version: 6.21.0
Qt Version: 6.10.1
Kernel Version: 6.18.2-1-default (64-bit)
Graphics Platform: X11
Processors: 12 × AMD Ryzen 5 7600 6-Core Processor
Memory: 32 GB of RAM (30,5 GB usable)
Graphics Processor 1: AMD Radeon RX 7800 XT
Graphics Processor 2: AMD Ryzen 5 7600 6-Core Processor
Manufacturer: Gigabyte Technology Co., Ltd.
Product Name: B650 EAGLE AX
System Version: Default string-CF

4

@voj0546 If you run sensors-detect --auto and in the output does it find an ITE unknown chipset?

5

These are the only mentions of ITE in the output:

Trying family `National Semiconductor/ITE'...               No
Trying family `SMSC'...                                     No
Trying family `VIA/Winbond/Nuvoton/Fintek'...               No
Trying family `ITE'...                                      Yes
Found unknown chip with ID 0x8689
Probing for Super-I/O at 0x4e/0x4f
Trying family `National Semiconductor/ITE'...               No
Trying family `SMSC'...                                     No
Trying family `VIA/Winbond/Nuvoton/Fintek'...               No
Trying family `ITE'...                                      No

Full output here:

# sensors-detect version 3.6.2
# System: Gigabyte Technology Co., Ltd. B650 EAGLE AX [Default string-CF]
# Kernel: 6.18.2-1-default x86_64
# Processor: AMD Ryzen 5 7600 6-Core Processor (25/97/2)

Running in automatic mode, default answers to all questions
are assumed.

Some south bridges, CPUs or memory controllers contain embedded sensors.
Do you want to scan for them? This is totally safe. (YES/no): 
Module cpuid loaded successfully.
Silicon Integrated Systems SIS5595...                       No
VIA VT82C686 Integrated Sensors...                          No
VIA VT8231 Integrated Sensors...                            No
AMD K8 thermal sensors...                                   No
AMD Family 10h thermal sensors...                           No
AMD Family 11h thermal sensors...                           No
AMD Family 12h and 14h thermal sensors...                   No
AMD Family 15h thermal sensors...                           No
AMD Family 16h thermal sensors...                           No
AMD Family 17h thermal sensors...                           No
AMD Family 15h power sensors...                             No
AMD Family 16h power sensors...                             No
Hygon Family 18h thermal sensors...                         No
AMD Family 19h thermal sensors...                           No
Intel digital thermal sensor...                             No
Intel AMB FB-DIMM thermal sensor...                         No
Intel 5500/5520/X58 thermal sensor...                       No
VIA C7 thermal sensor...                                    No
VIA Nano thermal sensor...                                  No

Some Super I/O chips contain embedded sensors. We have to write to
standard I/O ports to probe them. This is usually safe.
Do you want to scan for Super I/O sensors? (YES/no): 
Probing for Super-I/O at 0x2e/0x2f
Trying family `National Semiconductor/ITE'...               No
Trying family `SMSC'...                                     No
Trying family `VIA/Winbond/Nuvoton/Fintek'...               No
Trying family `ITE'...                                      Yes
Found unknown chip with ID 0x8689
Probing for Super-I/O at 0x4e/0x4f
Trying family `National Semiconductor/ITE'...               No
Trying family `SMSC'...                                     No
Trying family `VIA/Winbond/Nuvoton/Fintek'...               No
Trying family `ITE'...                                      No

Some systems (mainly servers) implement IPMI, a set of common interfaces
through which system health data may be retrieved, amongst other things.
We first try to get the information from SMBIOS. If we don't find it
there, we have to read from arbitrary I/O ports to probe for such
interfaces. This is normally safe. Do you want to scan for IPMI
interfaces? (YES/no): 
Probing for `IPMI BMC KCS' at 0xca0...                      No
Probing for `IPMI BMC SMIC' at 0xca8...                     No

Some hardware monitoring chips are accessible through the ISA I/O ports.
We have to write to arbitrary I/O ports to probe them. This is usually
safe though. Yes, you do have ISA I/O ports even if you do not have any
ISA slots! Do you want to scan the ISA I/O ports? (YES/no): 
Probing for `National Semiconductor LM78' at 0x290...       No
Probing for `National Semiconductor LM79' at 0x290...       No
Probing for `Winbond W83781D' at 0x290...                   No
Probing for `Winbond W83782D' at 0x290...                   No

Lastly, we can probe the I2C/SMBus adapters for connected hardware
monitoring devices. This is the most risky part, and while it works
reasonably well on most systems, it has been reported to cause trouble
on some systems.
Do you want to probe the I2C/SMBus adapters now? (YES/no): 
Using driver `i2c-piix4' for device 0000:00:14.0: AMD KERNCZ SMBus

Next adapter: Synopsys DesignWare I2C adapter (i2c-0)
Do you want to scan it? (YES/no/selectively): 
Adapter doesn't support all probing functions.
Some addresses won't be probed.

Next adapter: Synopsys DesignWare I2C adapter (i2c-1)
Do you want to scan it? (YES/no/selectively): 
Adapter doesn't support all probing functions.
Some addresses won't be probed.

Next adapter: AMDGPU SMU 0 (i2c-2)
Do you want to scan it? (yes/NO/selectively): 

Next adapter: AMDGPU SMU 1 (i2c-3)
Do you want to scan it? (yes/NO/selectively): 

Next adapter: AMDGPU DM i2c hw bus 0 (i2c-4)
Do you want to scan it? (yes/NO/selectively): 

Next adapter: AMDGPU DM i2c hw bus 1 (i2c-5)
Do you want to scan it? (yes/NO/selectively): 

Next adapter: AMDGPU DM i2c hw bus 2 (i2c-6)
Do you want to scan it? (yes/NO/selectively): 

Next adapter: AMDGPU DM i2c hw bus 3 (i2c-7)
Do you want to scan it? (yes/NO/selectively): 

Next adapter: AMDGPU DM i2c OEM bus (i2c-8)
Do you want to scan it? (yes/NO/selectively): 

Next adapter: AMDGPU DM aux hw bus 1 (i2c-9)
Do you want to scan it? (yes/NO/selectively): 

Next adapter: AMDGPU DM aux hw bus 2 (i2c-10)
Do you want to scan it? (yes/NO/selectively): 

Next adapter: AMDGPU DM i2c hw bus 0 (i2c-11)
Do you want to scan it? (yes/NO/selectively): 

Next adapter: AMDGPU DM i2c hw bus 1 (i2c-12)
Do you want to scan it? (yes/NO/selectively): 

Next adapter: AMDGPU DM i2c hw bus 2 (i2c-13)
Do you want to scan it? (yes/NO/selectively): 

Next adapter: AMDGPU DM i2c hw bus 3 (i2c-14)
Do you want to scan it? (yes/NO/selectively): 

Next adapter: AMDGPU DM aux hw bus 1 (i2c-15)
Do you want to scan it? (yes/NO/selectively): 

Next adapter: AMDGPU DM aux hw bus 2 (i2c-16)
Do you want to scan it? (yes/NO/selectively): 

Next adapter: AMDGPU DM aux hw bus 3 (i2c-17)
Do you want to scan it? (yes/NO/selectively): 

Sorry, no sensors were detected.
Either your system has no sensors, or they are not supported, or
they are connected to an I2C or SMBus adapter that is not
supported. If you find out what chips are on your board, check
https://hwmon.wiki.kernel.org/device_support_status for driver status.
6

Accidentally replied to myself, it’s in this thread though.

7

Likely need to use the it87 kernel module for this system… it’s out of tree, so need to build/maintain yourself. Or just rely on the BIOS to take care of the system…

I see @pallaswept has a build (I do to…) maybe they can offer some hints.

8

OK, thank you. Honestly I have never compiled/built a thing so now going for a kernel module makes me affraid. Is there a tutorial I can follow to be sure I do everything right? Google wasn’t helpful much.

9

@voj0546 download the two rpms here and install with zypper and see how it goes…
https://download.opensuse.org/repositories/home:/kingy:/branches:/home:/pallaswept:/branches:/coolercontrol/openSUSE_Tumbleweed/x86_64/

10

I have installed both rpms via zypper (ignored that they are missing the signature key), rebooted my system and lm_sensors still cannot be started at all. Nor CoolerControl actually recongises all the fans and such + gives me Daemon error (which I thought was caused by the lm_sensors not running). Might try to reinstall it.

On the fresh install I have an error:

A connection to the CoolerControl Daemon could not be established.
Please make sure that the systemd service is running and available.

Check the docs website for installation instructions.

Some helpful commands to enable and verify the daemon status:

sudo systemctl enable --now coolercontrold
sudo systemctl status coolercontrold

If you have configured a non-standard address to connect to the daemon, you can set it in the following steps:

This is the log from CoolerControl:

[2025-12-28T09:17:17Z INFO  coolercontrold::logger] System Info:
    CoolerControlD:     3.0.2
    Name:               openSUSE Tumbleweed
    OS:                 Linux (openSUSE Tumbleweed 20251227)
    Host:               localhost.localdomain
    Kernel:             6.18.2-1-default
    Arch:               x86_64
    Board Manufacturer: Gigabyte Technology Co., Ltd.
    Board Name:         B650 EAGLE AX
    Board Version:      x.x
    BIOS Manufacturer:  American Megatrends International, LLC.
    BIOS Version:       5.35
    XDG Desktops:       KDE
    XDG Session Types:  unspecified, x11
[2025-12-28T09:17:17Z INFO  coolercontrold::config] Configuration file check successful
[2025-12-28T09:17:19Z INFO  coolercontrold] Initializing Devices...
[2025-12-28T09:17:19Z INFO  coolercontrold::liqctld] Python Version detected: 3.13.9 (main, Nov 23 2025, 01:32:31) [GCC]
[2025-12-28T09:17:19Z INFO  coolercontrold::liqctld] liquidctl version detected: 1.14.0
[2025-12-28T09:17:20Z INFO  coolercontrold::liqctld] Initializing liquidctl service...
[2025-12-28T09:17:20Z INFO  coolercontrold::liqctld] Devices found: ['Gigabyte RGB Fusion 2.0 5702 Controller']
[2025-12-28T09:17:20Z INFO  coolercontrold::liqctld] Exchanging handshake
[2025-12-28T09:17:20Z INFO  coolercontrold::repositories::liquidctl::liquidctl_repo] Initialized Liquidctl Devices: {"Gigabyte RGB Fusion 2.0 5702 Controller":{"driver version":["1.14.0"],"driver name":["RgbFusion2"],"locations":["/dev/hidraw5"]}}
[2025-12-28T09:17:20Z INFO  coolercontrold::repositories::cpu_repo] Initialized CPU Devices: {"AMD Ryzen 5 7600 6-Core Processor":{"driver name":["k10temp"],"driver version":["6.18.2-1-default"],"locations":["/sys/class/hwmon/hwmon3","/sys/devices/pci0000:00/0000:00:18.3","pci:v00001022d000014E3sv00000000sd00000000bc06sc00i00"]}}
[2025-12-28T09:17:20Z INFO  coolercontrold::repositories::hwmon::hwmon_repo] Initialized Hwmon Devices: {"acpitz":{"driver version":["6.18.2-1-default"],"driver name":[""],"locations":["/sys/class/hwmon/hwmon6","/sys/devices/virtual/thermal/thermal_zone1"]},"gigabyte_wmi":{"driver version":["6.18.2-1-default"],"driver name":["gigabyte-wmi"],"locations":["/sys/class/hwmon/hwmon4","/sys/devices/platform/PNP0C14:00/wmi_bus/wmi_bus-PNP0C14:00/DEADBEEF-2001-0000-00A0-C90629100000","wmi:DEADBEEF-2001-0000-00A0-C90629100000"]},"nvme":{"driver version":["6.18.2-1-default"],"locations":["/sys/class/hwmon/hwmon0","/sys/devices/pci0000:00/0000:00:01.2/0000:04:00.0/nvme/nvme0"],"driver name":[""]}}
[2025-12-28T09:17:20Z INFO  coolercontrold::repositories::gpu::gpu_repo] Initialized GPU Devices: {"amdgpu":{"locations":["/sys/class/hwmon/hwmon1","/sys/devices/pci0000:00/0000:00:01.1/0000:01:00.0/0000:02:00.0/0000:03:00.0","pci:v00001002d0000747Esv00001458sd00002413bc03sc00i00"],"driver name":["amdgpu"],"driver version":["6.18.2-1-default"]}}
[2025-12-28T09:17:20Z INFO  coolercontrold::repositories::custom_sensors_repo] Initialized Custom Sensors: ["sensor1", "sensor2"]
[2025-12-28T09:17:20Z INFO  coolercontrold::modes] Applying all saved device settings
[2025-12-28T09:17:20Z INFO  coolercontrold::engine::main] Successfully applied:: amdgpu | fan1 | Profile: GPU
[2025-12-28T09:17:20Z INFO  coolercontrold::api] API bound to address: 127.0.0.1:11987
[2025-12-28T09:17:20Z INFO  coolercontrold::api] API bound to address: [::1]:11987
[2025-12-28T09:17:20Z INFO  coolercontrold] Initialization Complete
[2025-12-28T09:17:21Z WARN  coolercontrold::repositories::gpu::amd] If you have an AMD RDNA3/4 (7000/9000 series) or newer card, kernel version >=6.12 is required to enable fan control.
[2025-12-28T09:17:21Z ERROR coolercontrold::engine::commanders::graph] Error applying Graph/Mix Profile calculated duty - Error on amdgpu:fan1 for duty 100 - Unable to set PWM value 255 for /sys/class/hwmon/hwmon1/pwm1 Reason: Invalid argument (os error 22)

So I have tried the commands suggested in in-app error message and after creating a symlink for CoolerControl I chcked the status of the Daemon:

~> sudo systemctl status coolercontrold
● coolercontrold.service - CoolerControl Daemon
     Loaded: loaded (/usr/lib/systemd/system/coolercontrold.service; enabled; preset: disabled)
     Active: active (running) since Sun 2025-12-28 10:17:17 CET; 5s ago
 Invocation: 844a19308a3743f2a121ba5af3cbc92c
   Main PID: 46276 (coolercontrold)
      Tasks: 9 (limit: 37353)
        CPU: 226ms
     CGroup: /system.slice/coolercontrold.service
             ├─46276 /usr/bin/coolercontrold
             └─46283 python3 -q

pro 28 10:17:20 localhost.localdomain coolercontrold[46276]: Initialized Hwmon Devices: {"acpitz":{"driver version":["6.18.2-1-default"],"driver name":[""],"locations":["/sys/class/hwmon/hwmon6","/sys/devices/virtual/thermal/thermal_zo>
pro 28 10:17:20 localhost.localdomain coolercontrold[46276]: Initialized GPU Devices: {"amdgpu":{"locations":["/sys/class/hwmon/hwmon1","/sys/devices/pci0000:00/0000:00:01.1/0000:01:00.0/0000:02:00.0/0000:03:00.0","pci:v00001002d000074>
pro 28 10:17:20 localhost.localdomain coolercontrold[46276]: Initialized Custom Sensors: ["sensor1", "sensor2"]
pro 28 10:17:20 localhost.localdomain coolercontrold[46276]: Applying all saved device settings
pro 28 10:17:20 localhost.localdomain coolercontrold[46276]: Successfully applied:: amdgpu | fan1 | Profile: GPU
pro 28 10:17:20 localhost.localdomain coolercontrold[46276]: API bound to address: 127.0.0.1:11987
pro 28 10:17:20 localhost.localdomain coolercontrold[46276]: API bound to address: [::1]:11987
pro 28 10:17:20 localhost.localdomain coolercontrold[46276]: Initialization Complete
pro 28 10:17:21 localhost.localdomain coolercontrold[46276]: If you have an AMD RDNA3/4 (7000/9000 series) or newer card, kernel version >=6.12 is required to enable fan control.
pro 28 10:17:21 localhost.localdomain coolercontrold[46276]: Error applying Graph/Mix Profile calculated duty - Error on amdgpu:fan1 for duty 100 - Unable to set PWM value 255 for /sys/class/hwmon/hwmon1/pwm1 Reason: Invalid argument (>
lines 1-21/21 (END)
11

@voj0546 your jumping too far ahead, slow down… Those rpms where for the sensors, so I was assuming you would run sensors-detect --auto again to test, nothing to do with cooler control…

So, install those rpms again, run sensors-detect --auto and check, if no output then run modprobe it87 and if it just returns to the command prompt without any output run sensors-detect --auto again.

For an AMD GPU, have you set the prefeature mask?

1 Like
12

So I force installed both RPMs again, still no sensors found, even after using modprobe it87 (without any output, as stated).

As for prefeature mask, I hear about this for the first time. So I don’t think I did? Google search told me it is a kernel parameter? In that case, my kernel parameters are as follow:

splash=silent quiet security=selinux selinux=1 usbcore.autosuspend=-1 cpi_enforce_resources=lax

13

Is it really cpi_ or a typo on your part?

So, no issues with the modprobe, so can you edit /etc/modprobe.d/70-it87.conf and add options it87 force_id=0x8689

Reboot and run;

modprobe it87
sensors-detect --auto
sensors

To unlock the amdgpu clocks and voltages, use;

update-bootloader --add-option amdgpu.ppfeaturemask=0xffffffff
update-bootloader
14

Hi @voj0546 :slight_smile:

I don’t usually come here, just saw a notification by accident… so if you don’t get replies from me, that would be why… But let’s see if I can cover off a few easy points while I’m in the neighbourhood.

First off, if you’re going to use a -kmp rpm, I’d currently recommend this one https://build.opensuse.org/package/show/home:Kimloc/it87

kimloc is one of the staff at the coolercontrol discord and runs this driver on his machine. That’s a branch of the current out-of-tree it87 driver, with extensive updates/improvements for newer hardware like yours, made by another of the cooler control staff (tsunami) who also runs this code of course, but isn’t using suse so doesn’t use our kmp package.

It is in testing at the moment, but it’s getting tested hard and no problems so far, and it definitely solves actual problems with newer boards, including your model. One that we see quite a bit is that only the first two fans can be controlled (because there’s actually a second superIO chip slaved behind this one, and only tsunami’s driver can talk to that)

The behaviour you’re seeing, where it lists the fans but you can’t control their speeds, is pretty normal for the in-tree it87 driver - and yes they have the exact same name and it can cause problems. I’d recommend running sudo modinfo it87 and checking the author line to see what names are listed there. If you don’t see Frank Crawford mentioned like this:
author: Chris Gauthron, Jean Delvare <jdelvare@suse.de>, Frank Crawford Then you’re using the in-tree driver, and fan control won’t work. Getting that -kmp installed should sort that out.

Starting the lm_sensors service is not critical, it serves to automatically load the it87 module at boot time. If you’re seeing the sensors in sensors and in coolercontrol, then that module is being loaded (perhaps you added config to /etc/modules-load.d or similar). I can’t say if it’s loaded the right one (see above) at this point, but it’s definitely loaded. I suspect that the lm_sensors service is failing to start because there’s no config saved for it because sensors-detect doesn’t find anything so doesn’t prompt you to save what it finds to that config file. But, if the module is loaded automatically by other means, that is sufficient…so I’d just ignore that lm_sensors.service fails.

I don’t know how you feel about discord, but the coolercontrol discord is very active and there’s no better place for current info when it comes to that driver, it’s very heavily developed upon in there right now (because the in-tree driver doesn’t work and nearly every current motherboard needs it). If you have an account or don’t mind making one, I’d say that’s a good place to try, to get things working.

1 Like
15

Is it really cpi_ or a typo on your part?

I have found it in some other tutorial so if it is, I am not aware of it.

Running sudo nano /etc/modprobe.d/70-it87.conf resulted in creating a new file so I stopped here and didn’t proceed any further. Or is it supposed to happen?

16

I’d recommend running sudo modinfo it87 and checking the author line to see what names are listed there. If you don’t see Frank Crawford mentioned like this:
author: Chris Gauthron, Jean Delvare <jdelvare@suse.de>, Frank Crawford Then you’re using the in-tree driver, and fan control won’t work. Getting that -kmp installed should sort that out.

The author is stated as supposed. I have reinstalled it87 from Kimloc via adding a repo and changing the provider (since it was already installed from RPMs provided above in the thread.

Even after the reboot, CoolerControl doesn’t run as supposed.

I guess I might give Discord a try but I do not use it as a support platform since things got lost in all the messages in channels…

17

@voj0546 if you installed both rpms then it should install that configuration file.