On 5/27/2026 at 4:45 AM, DelDadam said:

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.

thanks for the detailed explanation, I run DXP4800 PRO (which uses the same Super IO ITE8613E) and saw this comment which upset me initially. But I then decided to try the ITE IT87 DRIVER and FanCtrl Plus, turns out, both work great in my setup. Not only I can see the new dashboard panel with the fan speed and reason for it, FanCtrl actually does control the fan. I first tried the "fan discovery" which was able to max-spin both the CPU fan and Rear fan (Noctua in my case) and then I tried changing the Fan speed percentage to see if those would make a change and they did.

Hi ich777 — I think I've hit a packaging/registration issue with the AMD Vendor Reset plugin on my kernel version. I've narrowed it down fairly far before posting; details and exact command output below.

System

• Unraid 7.3.1

• Kernel: 6.18.33-Unraid

• Board/CPU: ASRock Rack ROMED8-2T / EPYC 7543P

• GPU (passthrough target): AMD reference RX 6900 XT, Navi 21, all four functions stubbed to vfio-pci from boot via vfio-pci.cfg

• Host boots on onboard ASPEED VGA; video=efifb:off on the append line so the host never touches the 6900 XT.

Symptom The plugin installs and the module loads (hook reports installed), but the reset method never becomes device_specific — it stays bus, and writing device_specific fails with write error: Invalid argument. This happens even with the card idle, no VM running, in a clean vfio-bound state.

Exact output

Kernel and module (vermagic matches the running kernel):

# uname -r
6.18.33-Unraid

# modinfo vendor_reset
filename:       /lib/modules/6.18.33-Unraid/updates/vendor-reset.ko.xz
version:        0.1.1
author:         Adam Madsen <[email protected]>
author:         Geoffrey McRae <[email protected]>
license:        GPL v2
srcversion:     9DB935EFAD3315A519FE253
depends:
name:           vendor_reset
retpoline:      Y
vermagic:       6.18.33-Unraid SMP preempt mod_unload
parm:           install_hook:bool

Package folder matches the kernel:

# ls /boot/config/plugins/amd-vendor-reset/packages/
6.18.33/

Hook reports installed:

# dmesg | grep -i vendor
[   67.711636] vendor_reset_hook: installed

Reset method stays bus and rejects device_specific:

# cat /sys/bus/pci/devices/0000:07:00.0/reset_method
bus

# echo device_specific > /sys/bus/pci/devices/0000:07:00.0/reset_method
bash: echo: write error: Invalid argument

GPU (all four functions, vfio-pci bound):

# lspci -nnk -s 07:00.
07:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Navi 21 [Radeon RX 6800/6800 XT / 6900 XT] [1002:73bf] (rev c0)
        Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Radeon RX 6900 XT [1002:0e3a]
        Kernel driver in use: vfio-pci
        Kernel modules: amdgpu
07:00.1 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] Navi 21/23 HDMI/DP Audio Controller [1002:ab28]
        Kernel driver in use: vfio-pci
07:00.2 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:73a6]
        Kernel driver in use: vfio-pci
07:00.3 Serial bus controller [0c80]: Advanced Micro Devices, Inc. [AMD/ATI] Navi 21 USB [1002:73a4]
        Kernel driver in use: vfio-pci

Boot command line:

# cat /proc/cmdline
BOOT_IMAGE=/bzimage initrd=/bzroot video=efifb:off

What I've ruled out

• Wrong/mismatched module: vermagic is 6.18.33-Unraid, matching the running kernel exactly; package folder is 6.18.33/.

• vfio-lock / timing: I unbound 07:00.0 from vfio-pci and the write still failed with Invalid argument; rebound it to vfio-pci (clean state) and it still fails. Same result in both states, card idle, no VM.

• Unsupported card: Navi 21 1002:73bf is reported working with vendor-reset elsewhere (same device IDs).

• Conflicting local config: removed earlier manual go-file reset_method write and a modprobe.d softdep; go is back to stock, only zfs.conf remains in modprobe.d.

My read (could be wrong) The hook installs, but the module's device_specific handler does not appear to register into the kernel PCI reset infrastructure on this kernel — the kernel rejects device_specific as invalid for the device even when idle and regardless of bind state. This looks like it could be a build/registration issue with the pre-built package for 6.18.33-Unraid, rather than a config problem on my end.

Question Is the pre-built vendor-reset package for 6.18.33-Unraid known-good, or might it need a rebuild against this kernel? Anything else I can check to confirm whether the handler is registering? Happy to provide full diagnostics or test a rebuilt package.

unraid-diagnostics-20260630-2029.zip

Hello All,

I am in need of some assistance with the UGreen LED driver. I just purchased the DXP8800 Plus and installed Uraid on it. I downloaded the ugreen LED driver from ich777 and followed the instructions (At least I think) but I can only get the Network, HD1 and HD3 lights working. I have tried leaving it as default, (ata), serial and adding in my serial numbers in order (ST26000NM001C-XXXXXX_XXXXXXXX) with a space in between as well as the hctl option with (0:0:0:0 1:0:0:0 etc) but nothing seems to change after rebooting. I have been able to successfully change the LED colors but nothing else. When the unit firsts boots, it does light up all of the hard drive LED's in white for a brief moment but then turns off and only shows the network, 1st and 3rd again. What am I missing here? The model is listed as compatible but for the life of me, can't find the correct configuration.

Below is a screenshot of the hard drives and current layout. Disk1 is parity (currently building), Disk2 is a future parity so it is empty, Disk3, 4 and 5 are 26TB drives in the pool. Any help would be greatly appreciated.

On 7/1/2026 at 4:20 PM, Bigsease30 said:

Hello All,

I am in need of some assistance with the UGreen LED driver. I just purchased the DXP8800 Plus and installed Uraid on it. I downloaded the ugreen LED driver from ich777 and followed the instructions (At least I think) but I can only get the Network, HD1 and HD3 lights working. I have tried leaving it as default, (ata), serial and adding in my serial numbers in order (ST26000NM001C-XXXXXX_XXXXXXXX) with a space in between as well as the hctl option with (0:0:0:0 1:0:0:0 etc) but nothing seems to change after rebooting. I have been able to successfully change the LED colors but nothing else. When the unit firsts boots, it does light up all of the hard drive LED's in white for a brief moment but then turns off and only shows the network, 1st and 3rd again. What am I missing here? The model is listed as compatible but for the life of me, can't find the correct configuration.

Below is a screenshot of the hard drives and current layout. Disk1 is parity (currently building), Disk2 is a future parity so it is empty, Disk3, 4 and 5 are 26TB drives in the pool. Any help would be greatly appreciated.

Does anyone know anything about this driver and how to make it work? Any help would be appreciated.

Subject/context: IT8689E rev 2 — PWM writes accepted but have no effect (fix available in upstream PR #114)

Hi ich777, first of all thanks for all your driver plugins!

System: Unraid 7.3.1 · Gigabyte B760I AORUS PRO DDR4 · IT8689E revision 2 (detected via your IT87 plugin: it87: Found IT8689E chip at 0xa40 [MMIO at 0x00000000fc000000], revision 2)

Problem: Sensors and fan RPM readings work perfectly, but manual PWM control has no effect:

• echo 1 > pwmN_enable succeeds and persists

• echo <duty> > pwmN succeeds and persists (value reads back correctly)

• Fan RPM never changes — on any of the 5 channels

• Tested with mmio=on (default) and mmio=off ignore_resource_conflict=1 — same result

• BIOS Smart Fan curves set to flat 40% per the CoolerControl docs workaround — the EC respects the flat curve (fans dropped from 100% to 40%), but sysfs writes still have no effect on top of it

This is exactly the symptom tracked in frankcrawford/it87 issue #96 (IT8689E: PWM writes accepted, zero effect, works fine on Windows via LibreHardwareMonitor).

The good news: there is now a minimal tested fix upstream — PR #114 (https://github.com/frankcrawford/it87/pull/114). Root cause: on these FEAT_BRIDGE_MMIO chips the internal "vector" fan controller only releases the channel in manual mode when all temp-map-select bits are set; LibreHardwareMonitor writes 0x7f to the base PWM control register on Windows, which is why it works there. The PR is a one-line change in set_pwm_enable() and a reviewer confirmed this method is specifically needed on the IT8689 (the IT8696 is unaffected).

Request: would it be possible to get a test build of the IT87 plugin with the PR #114 patch applied (kernel 6.18.33-Unraid / Unraid 7.3.1)? Happy to test and report back — I have a reproducible setup and can validate manual control + enable=2 auto-restore on all channels.

Thanks a lot!