systemd: Run lm-sensors after modprobe

0 votes
1 answer
121 views
                          I have a Gigabyte X570 GAMING X motherboard and want to control the fans from my XUbuntu 24.04, but it has issues detecting the fans. There is [a suggested solution](https://github.com/lm-sensors/lm-sensors/issues/154) , but modprobe it87 force_id=0x8628 only works on the console (I don't want to use dkms). Now I want this to work directly after a reboot.

So I now have:

	root@runlikehell:~# cat /etc/modprobe.d/fans.conf 
	options it87 force_id=0x8628

	root@runlikehell:~# 

and added these to the "[Unit]"-section in /usr/lib/systemd/system/lm-sensors.service:

	Requires=systemd-modules-load.service
	After=systemd-modules-load.service

Note that I asked AI and it halucinates as it suggests this:

	After=modprobe@*.service
	Wants=modprobe@*.service

but [systemd doesn't allow wildcards there](https://github.com/systemd/systemd/issues/5388) .

After a reboot I see this, so the conf-file was loaded:

	root@runlikehell:~# modprobe -c | grep it87
	blacklist it8712f_wdt
	blacklist it87_wdt
	blacklist it8712f_wdt
	blacklist it87_wdt
	blacklist it8712f_wdt
	blacklist it87_wdt
	blacklist it8712f_wdt
	blacklist it87_wdt
	blacklist it8712f_wdt
	blacklist it87_wdt
	blacklist it8712f_wdt
	blacklist it87_wdt
	blacklist it8712f_wdt
	blacklist it87_wdt
	blacklist it8712f_wdt
	blacklist it87_wdt
	options it87 force_id=0x8628
	alias dmi*:rvn*GigabyteTechnologyCo.,Ltd.*:rn*AB350*: it87
	alias dmi*:rvn*GigabyteTechnologyCo.,Ltd.*:rn*AX370*: it87
	alias dmi*:rvn*GigabyteTechnologyCo.,Ltd.*:rn*B550AORUSPROAC*: it87
	alias dmi*:rvn*GigabyteTechnologyCo.,Ltd.*:rn*TRX40AORUSXTREME*: it87
	alias dmi*:rvn*GigabyteTechnologyCo.,Ltd.*:rn*X570AORUSMASTER*: it87
	alias dmi*:rvn*GigabyteTechnologyCo.,Ltd.*:rn*X570AORUSPRO*: it87
	alias dmi*:rvn*GigabyteTechnologyCo.,Ltd.*:rn*X570AORUSPROWIFI*: it87
	alias dmi*:rvn*GigabyteTechnologyCo.,Ltd.*:rn*X570SAEROG*: it87
	alias dmi*:rvn*GigabyteTechnologyCo.,Ltd.*:rn*Z390AORUSULTRA_CF*: it87
	alias dmi*:rvn*GigabyteTechnologyCo.,Ltd.*:rn*Z690AORUSPRO*: it87
	alias dmi*:rvn*GigabyteTechnologyCo.,Ltd.*:rn*Z690AORUSPRODDR4*: it87
	alias dmi*:rvn*GigabyteTechnologyCo.,Ltd.*:rn*Z97X_GamingG1*: it87
	alias dmi*:rvn*nVIDIA*:rn*FN68PT*: it87
	root@runlikehell:~# 

The lm-sensors.service is running, but it didn't find the it87-related stuff:

	root@runlikehell:~# journalctl -b 0 -u lm-sensors.service 
	... systemd: Starting lm-sensors.service - Initialize hardware monitoring sensors...
	... sensors: k10temp-pci-00c3
	... sensors: Adapter: PCI adapter
	... sensors: Tctl:         +48.4°C
	... sensors: Tccd1:        +56.5°C
	... sensors: acpitz-acpi-0
	... sensors: Adapter: ACPI interface
	... sensors: temp1:        +16.8°C
	... sensors: temp2:        +16.8°C
	... sensors: temp3:        +16.8°C
	... sensors: gigabyte_wmi-virtual-0
	... sensors: Adapter: Virtual device
	... sensors: temp1:        +25.0°C
	... sensors: temp2:        +26.0°C
	... sensors: temp3:        +48.0°C
	... sensors: temp4:        +26.0°C
	... sensors: temp5:        +28.0°C
	... sensors: temp6:        +39.0°C
	... sensors: nvme-pci-0300
	... sensors: Adapter: PCI adapter
	... sensors: Composite:    +40.9°C  (low  =  -0.1°C, high = +74.8°C)
	... sensors:                        (crit = +79.8°C)
	... systemd: Finished lm-sensors.service - Initialize hardware monitoring sensors.
	root@runlikehell:~# 

So to me it means that the configuration of modprobe hasn't been read or applied when lm-sensors.service starts.

journalctl -b 0 doesn't contain "it87" at all (I don't know if it should).

How do I run the lm-sensors.service after the modprobe-stuff properly?
                        
Asked by sjngm (547 rep)
Feb 11, 2025, 10:49 PM
Last activity: Feb 13, 2025, 06:30 AM
systemd: Run lm-sensors after modprobe

Related Questions
