I upgraded today, first to apply the two security updates (I was on the last patch BEFORE the recent CVEs, so two versions behind), then to 7.3.0 hoping this second update would fix the issue, but it persists on latest.

The IT87 driver is broken. Setting fan speed simply doesn't work right, it sets it to a seemingly unrelated low PWM value instead of the correct one. Occasionally it works. Mostly it doesn't.

Eg, setting to 156 gives me 5 but sometimes I get other values like 28

This is new/recent behavior, unsure if anything changed on our end, just checking if anyone else is seeing the issue before I chase it upstream to the driver vendor.

Edit: Confirmed this is due to mmio=on, which is a new default behavior since the last time I updated. I filed a bug report on the it87 git. This almost cost me some hardware (Fans all silently stopped working HEH) so hopefully it can be resolved quickly.

For now, you can run
```
modprobe -r it87
modprobe it87 mmio=off ignore_resource_conflict=1
```
to reload without mmio if your board is also affected

Edited May 13May 13 by Spitko

1 hour ago, Spitko said:

modprobe -r it87
modprobe it87 mmio=off ignore_resource_conflict=1

I would rather recommend that you either create a modprobe.d file or that you pass over these arguments in your boot configuration file, with that you wouldn't have to unload and reload the driver.

1 hour ago, Spitko said:

This almost cost me some hardware (Fans all silently stopped working HEH) so hopefully it can be resolved quickly.

This needs to be solved in the GitHub repo, please keep me updated if there was anything changed there.

Why is this plugin no longer in community apps? If I remember correctly there was 2 different IT87 plugins? Was one of them removed? The current one I have installed seems to not be linked with the one in community apps...

2 hours ago, Laov said:

Why is this plugin no longer in community apps? If I remember correctly there was 2 different IT87 plugins? Was one of them removed? The current one I have installed seems to not be linked with the one in community apps...

I changed nothing, don't know why this is shown.

The plugin should also be available in CA, don't know what is going on.

@ich777 Thanks for your support providing these plugins. I also got that not part of CA warning. Maybe publishing a new version as I saw that behavior with some plugins in the past. Quick question regarding these drivers. I have a ugreen dxp4800 with the intel n100. I installed the ugreen led drivers and the Nuvoton NCT6687 Driver. And today I found the ITE IT87 Driver which is also published by you. Do you have a recommendation? Only install nuvoton, both, or the ITE driver? Currently I have the temp displayed which is often jumping from 40 to 60 degrees celcius, but the fan speed is not displayed and cannot be controlled. Would you have a recommendation here? Thanks again for your help.

19 hours ago, ich777 said:

I changed nothing, don't know why this is shown.

The plugin should also be available in CA, don't know what is going on.

Apparently it went away after update to 7.3... Weird...

51 minutes ago, chrneu said:

@ich777 Thanks for your support providing these plugins. I also got that not part of CA warning. Maybe publishing a new version as I saw that behavior with some plugins in the past. Quick question regarding these drivers. I have a ugreen dxp4800 with the intel n100. I installed the ugreen led drivers and the Nuvoton NCT6687 Driver. And today I found the ITE IT87 Driver which is also published by you. Do you have a recommendation? Only install nuvoton, both, or the ITE driver? Currently I have the temp displayed which is often jumping from 40 to 60 degrees celcius, but the fan speed is not displayed and cannot be controlled. Would you have a recommendation here? Thanks again for your help.

You have to research that yourself, usually you only have either a Nuvoton or an ITE Super I/O chip on your board, not both.

35 minutes ago, Laov said:

Apparently it went away after update to 7.3... Weird...

Sorry guys, I didn't change anything an it also doesn't has a max version attached therefore it should be listed in CA.

The plugin is the same at is was released 2 years ago and the driver packages are still compiled.

I would rather recommend creating a post in CA or Fix Common issues.

I'm seeing this after updating to 7.3:

Can't download NCT6687d Drivers-----------------------
plugin: run failed: '/bin/bash' returned 1
Executing hook script: CA_postHook
Clearing Community Applications plugin cache
Executing hook script: post_plugin_checks
Plugin installed

Update/Fix:

Root cause: kernel 6.18 loads the in-tree nct6683 driver instead of nct6687 for the NCT6687D chip. The plugin install script fails because nct6683 already claimed the chip — modprobe nct6687 fails and the script exits with code 1.

Solution: unload nct6683 first, then install the plugin via CLI:

rmmod nct6683

plugin install https://github.com/ich777/unraid-nct6687-driver/raw/master/nct6687-driver.plg

The plugin downloads the correct package for your kernel, blacklists nct6683 in /boot/config/modprobe.d/nct6683.conf, and loads nct6687 successfully. After reboot the blacklist prevents nct6683 from loading automatically.

Verify:

lsmod | grep nct

cat /sys/class/hwmon/hwmon5/name

Should return nct6687.

Edited May 18May 18 by Soulplayer

54 minutes ago, Soulplayer said:

Root cause: kernel 6.18 loads the in-tree nct6683 driver instead of nct6687 for the NCT6687D chip. The plugin install script fails because nct6683 already claimed the chip — modprobe nct6687 fails and the script exits with code 1.

Can you please double check if this is actually true, the plugin should already automatically install a blacklist file into the correct directory on your boot device.

Can't download NCT6687d Drivers-----------------------

This shows another issue and it seems like it actually can't download the package.

Hey,

i got an old Mellanox ConnectX-3, but the actual mstflint version does not support it.

Can you release a plugin with a old mstflint version, 4.25 should still support it?

4 hours ago, Darkestnoir said:

Can you release a plugin with a old mstflint version, 4.25 should still support it?

No sorry, the Mellanox Plugin is now deprecated.

14 hours ago, ich777 said:

No sorry, the Mellanox Plugin is now deprecated.

Why was the Mellanox plugin deprecated?? I don't see a replacement for it.

1 hour ago, irishdab said:

Why was the Mellanox plugin deprecated?? I don't see a replacement for it.

Too many different versions from MFT to support.

https://www.phoronix.com/news/AMDGPU-Pipe-Reset-Support

I really hope this finally contains the driver level support we will finally needed to get rid of the awful AMD reset bug for once and for all.

The UGREEN LED Driver plugin has a very minor bug. Steps to reproduce:

1. Stop the array

2. Pop out an HDD. The corresponding LED will turn red as expected.

3. Push the HDD back in. Unraid detected that the HDD was back right away, but even after waiting ~10 mins the corresponding LED never turned back to white.

This is a trivial matter since rebooting resolved the issue and hotswapping is uncommon to begin with, but I figure that it's better to report it than to not say anything.

On 5/17/2026 at 1:23 PM, chrneu said:

@ich777 Thanks for your support providing these plugins. I also got that not part of CA warning. Maybe publishing a new version as I saw that behavior with some plugins in the past. Quick question regarding these drivers. I have a ugreen dxp4800 with the intel n100. I installed the ugreen led drivers and the Nuvoton NCT6687 Driver. And today I found the ITE IT87 Driver which is also published by you. Do you have a recommendation? Only install nuvoton, both, or the ITE driver? Currently I have the temp displayed which is often jumping from 40 to 60 degrees celcius, but the fan speed is not displayed and cannot be controlled. Would you have a recommendation here? Thanks again for your help.

Hi,
We have two UGREEN DXP4800 PLUS's here, but as far as I know your DXP4800 uses the same ITE IT8613E Super IO chip as ours do. And unfortunately, ich77's ITE IT87 Driver plugin does not support this variant of the chip. At least this was reported by the terminal commands installed by the plugin when I last time attempted to use the plugin.

AFAIK the only way to control the fan of your NAS is possible only via its BIOS settings. Look for the ADVANCED panel in the BIOS, and the Hardware Monitoring sub-menu. There you'll find various settings like Fan PWM Slope, Fan Start PWM and Fan Start Temperature Limit. You need to play with/change these 3 settings only. In our NAS these have the following default values:

• Fan PWM Slope: 35 (how fast the PWM value of the fan increased if temp changes by 1C)

• Fan Start PWM: 51 (base PWM value of the fan, in our case this corresponded to approx. 600 RPM)

• Fan Start Temperature Limit: 25 (that is obvious: below this temp the fan does not run)

We've changed the above defaults to these values:

• Fan PWM Slope: 50

• Fan Start PWM: 62

• Fan Start Temperature Limit: 20

Since the change of these settings the temperature of the processor and the motherboard decreased by ~8-10 C, while the HDD's temp went down by ~5-6 C when not idle (at room temp of 26C).

Hope it helps.

@chrneu Aye, one more idea. Actually, you can install the ITE IT87 Driver plugin, but it will not control your fan. However - at leas on our NAS - it displayed an extra Airflow panel on the Dashboard page, and this panel displays the actual RPM of the case fan and the CPU fan.

Maybe you may try to install the Dynamix System Autofan plugin too, and to use these 2 plugins in conjunction. I didn't test this though, and AFAIK Autofan plugin is "still under development".

Installing Hailo RT Driver seems to work on Unraid 7.3.0 but I see these messages in the logs:

[ 226.772448] Modules linked in: macvlan xt_nat xt_tcpudp ipvlan br_netfilter xt_conntrack xt_MASQUERADE xfrm_user xfrm_algo ip6table_nat xt_set ip_set nfnetlink iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 xt_addrtype md_mod ip6table_filter ip6_tables iptable_filter ip_tables x_tables af_packet cfg80211 rfkill bridge 8021q garp mrp stp llc bonding tls amdgpu amdxcp mfd_core edac_mce_amd drm_panel_backlight_quirks gpu_sched edac_core intel_rapl_msr drm_buddy intel_rapl_common drm_ttm_helper ttm drm_client_lib drm_exec i2c_algo_bit drm_suballoc_helper kvm_amd drm_display_helper drm_kms_helper kvm drm cec ghash_clmulni_intel aesni_intel i2c_piix4 agpgart i2c_smbus rapl i2c_core k10temp hailo_pci(O) ccp crc16 wmi_bmof r8169 realtek tpm_crb sr_mod led_class tpm_tis cdrom tpm_tis_core tpm video libaescfb wmi ecdh_generic ecc backlight button zfs(PO) spl(O) [ 226.772574] hailo_vdma_buffer_map+0x9c/0x5a0 [hailo_pci] [ 226.772581] hailo_vdma_buffer_map_ioctl+0x10a/0x210 [hailo_pci] [ 226.772587] hailo_pcie_fops_unlockedioctl+0x1ec/0x4d0 [hailo_pci]

28 minutes ago, SG2Unrai48 said:

Hailo RT Driver seems to work on Unraid 7.3.0 but I see these messages in the logs

Only Diagnostics would give me a full picture.

However, is something not working?

3 hours ago, ich777 said:

Only Diagnostics would give me a full picture.

However, is something not working?

Frigate seems to be working with the Hailo-8 but the logs fill up with repeated message like the example.tower-one-diagnostics-20260613-1914.zip

28 minutes ago, SG2Unrai48 said:

Frigate seems to be working with the Hailo-8 but the logs fill up with repeated message like the example.tower-one-diagnostics-20260613-1914.zip

These are Kernel Panics, not sure if the Module causes that or Frigate:

```
Jun 13 19:13:20 tower-one kernel: WARNING: CPU: 2 PID: 12957 at ./include/linux/rwsem.h:80 find_vma+0x28/0x60

```

I would recommend that you ask in the Frigate support thread.

25 minutes ago, ich777 said:

These are Kernel Panics, not sure if the Module causes that or Frigate:

```
Jun 13 19:13:20 tower-one kernel: WARNING: CPU: 2 PID: 12957 at ./include/linux/rwsem.h:80 find_vma+0x28/0x60

```

I would recommend that you ask in the Frigate support thread.

I'm not sure either. I'm clutching at straws I guess but I found something similar albeit on a Raspberry Pi using the 'newer kernels'...
https://community.hailo.ai/t/bug-report-find-vma-called-before-mmap-read-lock-issued-in-usr-src-hailo-pci-4-23-0-linux-vdma-memory-c/19001

On 6/13/2026 at 8:23 PM, SG2Unrai48 said:

I'm not sure either. I'm clutching at straws I guess but I found something similar albeit on a Raspberry Pi using the 'newer kernels'...
https://community.hailo.ai/t/bug-report-find-vma-called-before-mmap-read-lock-issued-in-usr-src-hailo-pci-4-23-0-linux-vdma-memory-c/19001

I switched to using Viseron which needs the 4.22 driver and no more Kernel Panics...

15 minutes ago, SG2Unrai48 said:

Viseron

I'm not familiar what Viseron is.

However if everything is now working, glad that it's solved. :)

26 minutes ago, ich777 said:

I'm not familiar what Viseron is.

However if everything is now working, glad that it's solved. :)

If your curious https://viseron.netlify.app