In Unraid 6.8 I used to have the following in my go file:

modprobe it87 force_id=0x8728

and it allowed motherboard temperature and fan speeds to be monitored.

 

In Unraid 6.9 it still works but since a new mechanism has been provided for passing parameters to modules I commented this out and created a file called /boot/config/modprobe.d/it87.conf with the contents

options it87 force_id=0x8728

but it doesn't automatically load on boot. What am I missing?

 

root@Pusok:~# ls -l /boot/config/modprobe.d/
total 4
-rw------- 1 root root  0 Feb 12 14:10 amdgpu.conf
-rw------- 1 root root 29 Mar  2 18:05 it87.conf
root@Pusok:~# cat /boot/config/modprobe.d/it87.conf 
options it87 force_id=0x8728
root@Pusok:~# 

 

Dont you just need the force=   part in the conf file?

42 minutes ago, SimonF said:

Dont you just need the force=   part in the conf file?

 

I'll give that a try when I'm able to reboot, later. But the example in the 6.9.0 wiki uses the "options <module-name> <parameter>=<value>" syntax:

 

options bonding primary=eth1

 

Editing the /boot/config/modprobe.d/it87.conf file to contain just

force_id=0x8728

and rebooting didn't work.

 

root@Pusok:~# lsmod | grep it87
root@Pusok:~# modprobe it87
libkmod: kmod_config_parse: /etc/modprobe.d/it87.conf line 1: ignoring bad line starting with 'force_id=0x8728'
modprobe: ERROR: could not insert 'it87': No such device
root@Pusok:~# 

 

So I restored it to

options it87 force_id=0x8728

and rebooted. Again, the module wasn't inserted automatically but manually modprobe-ing it inserted it with the correct parameter:

 

root@Pusok:~# lsmod | grep it87
root@Pusok:~# modprobe it87
root@Pusok:~# lsmod | grep it87
it87                   45056  0
hwmon_vid              16384  1 it87
root@Pusok:~# 

 

So I have to conclude that adding an it87.conf file to /boot/config/modprobe.d only allows parameters to be passed - it doesn't automatically load the module at boot time. So I've put the "modprobe it87" line (without the additional parameter) back in my go file.