Hi!

Since updating to 7.0.1 from 6.12.5 I've encountered a driver issue. I've got @ich777 Nuvoton NCT6687 Driver plugin installed as that is needed for me to get sensors and pwmconfig working. For some reason after upgrading to 7.0.1 the system now loads the NCT6683 driver first and then also loads the NCT6687 from the plugin. This creates a problem as it seems to lock the /sys/class/hwmon/hwmon7/pwm* files from being modified. Thus I cannot change fan speed with my scripts. I only get "permissions denied".

The solution I've found is to remove both drivers:
 

modprobe -r nct6683
modprobe -r nct6687

Then reload the correct driver:
 

modprobe nct6687

 

After that sensors, pwmconfig and my fan scripts works again.

Tried blacklisting the NCT6683 driver by:
 

echo "blacklist nct6683" >> /boot/config/modprobe.d/nct6683.conf

After reboot the NCT6683 still loads as well as the NCT6687.

Tried adding the blacklist and the loading of the correct driver in the go file:

 

echo "blacklist nct6683" >> /boot/config/go

echo "modprobe nct6687" >> /boot/config/go

After reboot both drivers still loads.

Found that /boot/config/modprobe.d seems linked with /etc/modprobe.d so made sure it looked the same in both dirs.
After reboot it still loads both drivers.

My system now is on a Z590 MB with an 11600 CPU.


So what am I doing wrong?

 

Edited May 12, 20251 yr by b3rrytech
Brainfart and didnt think when I wrote, removed diagnostics

2 minutes ago, b3rrytech said:

After reboot both drivers still loads.

There was already a discussion about that here: https://github.com/ich777/unraid-nct6687-driver/issues/3 and I closed that issue today because nobody responded, so to speak in your case the nct6683 driver is necessary to be not loaded correct?

 

However the correct way would be to create /boot/config/modprobe.d/nct6683.conf with the contents:

install nct6683 /bin/false

 

I can of course implement that into the plugin if you confirm above is working.

Read though the github issue and feels like it's related. Do you know why this changed when updating to 7.0.1? Was the kernel driver updated upstream? Drivers are far from my comfort zone so apologies for perhaps a bit "slow" questions..

 

20 minutes ago, ich777 said:

However the correct way would be to create /boot/config/modprobe.d/nct6683.conf with the contents:

install nct6683 /bin/false

This seemed to fix it. Rebooted and only NCT6687 loaded.

root@Define7:~# lsmod | grep nct
nct6687                20480  0

Thanks for the help!

Just now, b3rrytech said:

Do you know why this changed when updating to 7.0.1? Was the kernel driver updated upstream?

Possibly, ITE and NCT drivers are a nightmare and support is sometimes implemented into a module that is not even related in the Kernel.

 

I already updated the plugin it now blacklists and prevents the installation with the latest version (2025-02-12) without user intervention.

sorry to kick in a bit offtopic, but I am too stupid to reach @ich777 per direct message:

 

Since a lot of versions UNRAID always tries to load a NCT Driver here (and always fails), the message scrolls offscreen too fast to be able to read the whole name.

But right now I was able to produce it manually (by reading and trying this thread):

root@F:~# modprobe nct6687
modprobe: FATAL: Module nct6687 not found in directory /lib/modules/6.12.24-Unraid

Yeah we are on 7.1.2 now already, so very likely the above path does not exist anymore. but for an unknown reason the path still exists (seems to be recreated on boot) ?!?!?

 

But still he tries to load it at boot time and I am not able to locate WHERE and HOW TO TO TURN IT OFF again!

 

Some hint for me ?

(since the driver is not found, nothing is loaded, nothing is harmed, its just this message that appears and obviously I am not able to load the driver even if I liked too)

 

Edited May 12, 20251 yr by MAM59

3 hours ago, MAM59 said:

Since a lot of versions UNRAID always tries to load a NCT Driver here (and always fails), the message scrolls offscreen too fast to be able to read the whole name.

Not with the new plugin version, at least not NCT6683.

 

3 hours ago, MAM59 said:

But right now I was able to produce it manually (by reading and trying this thread):

I'm not following, what Unraid version are you on?

 

3 hours ago, MAM59 said:

Yeah we are on 7.1.2 now already, so very likely the above path does not exist anymore. but for an unknown reason the path still exists (seems to be recreated on boot) ?!?!?

I'm still not following since Unraid 7.1.2 still uses Kernel 6.12.24 so the path is correct.

Did you possibly install the plugin package manually?

 

3 hours ago, MAM59 said:

But still he tries to load it at boot time and I am not able to locate WHERE and HOW TO TO TURN IT OFF again!

Are you using the nct6687 driver plugin or do you still want to blacklist or better speaking forbid installation?

58 minutes ago, ich777 said:

I'm still not following since Unraid 7.1.2 still uses Kernel 6.12.24 so the path is correct.

AAAH! I've mixed this (6.12) up with the UNRAID version.... now I see  that the path is recent. My fault, sorry!

58 minutes ago, ich777 said:

Are you using the nct6687 driver plugin or do you still want to blacklist or better speaking forbid installation?

I once tried it (long ago), but the fans did not work. So I deleted the plugin. Still it looks for this driver at boot time.

I'm just puzzled. "lsmod | grep nct" gives me nothing.

Wheras "modprobe -c  | grep nct" gives a lot (but only aliases):

 

root@F:~# modprobe -c | grep nct
alias i2c:nct1008 lm90
alias i2c:nct210 lm90
alias i2c:nct214 lm90
alias i2c:nct218 lm90
alias i2c:nct72 lm90
alias i2c:nct7802 nct7802
alias i2c:nct7904 nct7904
alias of:N*T*Connn,nct1008 lm90
alias of:N*T*Connn,nct1008C* lm90
alias of:N*T*Connn,nct214 lm90
alias of:N*T*Connn,nct214C* lm90
alias of:N*T*Connn,nct218 lm90
alias of:N*T*Connn,nct218C* lm90
alias of:N*T*Connn,nct72 lm90
alias of:N*T*Connn,nct72C* lm90
alias tty_ldisc_14 ppp_synctty
alias symbol:HWMON_NCT6775 nct6775_core
alias symbol:drm_helper_disable_unused_functions drm_kms_helper
alias symbol:ieee80211_emulate_add_chanctx mac80211
alias symbol:ieee80211_emulate_change_chanctx mac80211
alias symbol:ieee80211_emulate_remove_chanctx mac80211
alias symbol:ieee80211_emulate_switch_vif_chanctx mac80211
alias symbol:iwl_puncturing_is_allowed_in_bios iwlwifi
alias symbol:iwl_uefi_get_puncturing iwlwifi
alias symbol:mt76x02_mcu_function_select mt76x02_lib
alias symbol:mt792x_assign_vif_chanctx mt792x_lib
alias symbol:mt792x_unassign_vif_chanctx mt792x_lib
alias symbol:nct6775_probe nct6775_core
alias symbol:nct6775_reg_is_word_sized nct6775_core
alias symbol:nct6775_show_alarm nct6775_core
alias symbol:nct6775_show_beep nct6775_core
alias symbol:nct6775_store_beep nct6775_core
alias symbol:nct6775_update_device nct6775_core

(I CAN load that nct6775 driver, but at boot time it wants the nct6687 which does not exist (anymore?))

And I cannot find ANY reference to 6687 on the boot stick!

 

 

2 minutes ago, MAM59 said:

I once tried it (long ago), but the fans did not work. So I deleted the plugin. Still it looks for this driver at boot time.

When you deleted the plugin then it shouldn't look for this driver.

Are you sure that you don't have a user script or something in the go file which causes that?

 

4 minutes ago, MAM59 said:

And I cannot find ANY reference to 6687 on the boot stick!

Okay, probably the Kernel which tries to load that driver put AFAIK there is no official driver for that specific module.

Maybe give the plugin another go and see if it's now working for you.

9 minutes ago, ich777 said:

Are you sure that you don't have a user script or something in the go file which causes that?

Hmm, sure about the no-go, have to check user scripts...

No user script does even come close to kernel modules here, only "cleanup syslog" and other cleanup tasks.

9 minutes ago, ich777 said:

Okay, probably the Kernel which tries to load that driver put AFAIK there is no official driver for that specific module.

But then it must have been several kernels already, the message first appeared ages ago already I think on UNRAID 6.x.

 

I will try the plugin...

root@F:/boot/config# modprobe nct6687
modprobe: ERROR: could not insert 'nct6687': No such device

so far, so good (the errormessage changed 🙂 )

What next? I wanna get rid of them completely

 

Edited May 12, 20251 yr by MAM59

31 minutes ago, MAM59 said:

I wanna get rid of them completely

You want to get rid of those message, I wouldn't invest to much time into that since they won't harm anything.

 

However what you can try next is to add that to your Syslinux config:

acpi_enforce_resources=lax

and probably this will allow the module to load successful on your system.

 

However that all depends on which chip is on your motherboard and so on.

2 minutes ago, ich777 said:

You want to get rid of those message, I wouldn't invest to much time into that since they won't harm anything.

I did not invest much time, waited for ages. but this thread looked "alike" so I dared to ask.

I know its harmless and I can ignore it. I just thought you would say somethink like "OF COURSE! just hit... and... and..." 🙂

Obviously this is not the case, so we can forget it again for the next 20yrs 🙂

5 minutes ago, ich777 said:

However that all depends on which chip is on your motherboard and so on.

The system temp plugin shows nct6755 whereas sensors tells me about nct6798-isa-0290.

Which, once again, is very puzzling to me again...

But temps and fan speeds are shown (just the pwm management does not work from the fan plugin, but its also not needed, bios does a good job).

So there is nothing to complain or fix, just this strange message...