After multiple searches I found a bunch of posts about loud fans for the DXP2800 but not how to control the fans. This applies to those who do not use UGOS PRO but unRAID, Debian, Ubuntu, Fedora etc.

What's currently being supported:

• DXP2800
• DXP8800
• DXP4800 (Issue #11 resolved — fan visibility and PWM control implemented; see the pwmconfig prompt selections in the Troubleshooting section for DXP4800 specifics)
• iDX6011 (IT8622E at ioreg 0x4e; OEM chip ID 0x5571; force_activate=1 is handled automatically via DMI — only needed as a fallback if auto-detection fails, see Troubleshooting section)

What's currently being partially supported:

• DXP6800Pro (See Issue #6 for now)

What's currently under investigation / testing:

• DXP6011 Pro (Issue #23 closed, triaged in PR #24 — reported on unRAID with an unknown Super I/O ID 0x5571 at 0x4e; plain modprobe it87 ignore_resource_conflict=1 still fails with No such device, so support is pending register-dump analysis and force_id testing. UGREEN's published kernel-6.12 GPL tree also contains a vendor drivers/ugreen/ area that references ug_idx6011pro-sio.o and leds-mcu.o, and ug_it55pro_functions.c identifies the vendor product string as iDX6011 Pro and the chip as ITE5571, with OEM fan-control code paths that are useful reverse-engineering material even though the source drop appears incomplete.)

What's not supported by this driver (investigation completed — Issue #18):

• DXP2800 GT / DXP4800 GT — these GT models use an AMD Ryzen Embedded R2514 CPU (unlike the Intel N100 in the DXP2800) and a different Super I/O chip (a National Semiconductor / Texas Instruments chip with ID 0x2011 at I/O port 0x2e). The it87 driver does not apply to this hardware. Diagnostic details and findings are documented in the closed Issue #18.

modprobe i2c-designware-platform   # pulls in i2c-designware-core

Here is a step by step guide on how to do this:

• gcc
• make
• dkms
• dwarves
• kernel-headers
• lm_sensors
• git

• SSH Client
• Basic knowledge with Linux and terminal commands

The automated installer handles driver building via DKMS, systemd service setup, and automatic fan control. Fan speed is managed fully automatically — no additional configuration is required after running the installer.

1. SSH into your UGREEN NAS

2. Install the required packages

# Fedora/RHEL
sudo dnf install gcc make dkms dwarves kernel-headers lm_sensors git

# Debian/Ubuntu
sudo apt install gcc make dkms dwarves linux-headers-$(uname -r) lm-sensors git

# Arch
sudo pacman -S gcc make dkms linux-headers lm_sensors git

3. Clone the repository and run the installer

git clone --recurse-submodules https://github.com/IT-Kuny/UGREEN-DXP-FAN-NAS-Driver.git
cd UGREEN-DXP-FAN-NAS-Driver
sudo ./scripts/install.sh

That's it. The installer:

• Builds and installs the it87 kernel driver via DKMS
• Enables and starts ugreen-fan-control.service — a Bash-native fan control daemon that auto-detects the PWM channel and adjusts fan speed based on CPU and disk temperatures
• Sets up proper service ordering so the driver is always loaded before the daemon

Fan control is running immediately and will survive reboots and kernel updates.

To verify:

systemctl status ugreen-fan-control.service
journalctl -u ugreen-fan-control.service -f

To adjust the fan curves or mode, edit /etc/ugreen/ugreen-fan-control.env and restart the service:

sudo systemctl restart ugreen-fan-control.service

On the iDX6011 Pro, the supplied fan-control register map is supported directly: auto hands all four fans back to the EC, while silent, quiet, turbo, and max drive the CPU and system fan pairs. A 25% floor prevents stalled fans, critical temperatures force 100%, and a zero-RPM watchdog temporarily drives both pairs at full speed. Other models continue to use the generic silent / normal / powerful curves.

The installer automatically sets up systemd services that ensure:

• The hwmon-vid dependency module is loaded before it87
• The it87 driver is loaded before the fan daemon starts (prevents race conditions)
• The fan daemon auto-detects the PWM sysfs path at startup

hwmon-vid is used as the canonical name in this repo; hwmon_vid is an equivalent module alias on some distros/kernels.

sudo dnf install gcc make dkms dwarves kernel-headers lm_sensors

cd it87
make -j4
sudo make install

sudo install -m 755 scripts/ugreen-fan-control.sh /usr/local/sbin/ugreen-fan-control.sh
sudo mkdir -p /etc/ugreen
sudo install -m 644 config/ugreen-fan-control.env /etc/ugreen/ugreen-fan-control.env
sudo cp config/ugreen-fan-control.service /etc/systemd/system/
sudo systemctl daemon-reload
sudo systemctl enable --now ugreen-fan-control.service

If your target system has no DKMS/gcc/systemd (for example unRAID), you can build a precompiled module artifact in GitHub Actions:

1. Open Actions → Build Prebuilt it87.ko
2. Run the workflow and provide:
   • kernel_version from uname -r on the target box
   • kernel_headers_url to a prepared headers/build-tree archive for that exact kernel (must include generated files, e.g. from modules_prepare)
   • kernel_build_path only if auto-detection fails (path inside the archive to the kernel build directory)
   • build_mode (prod for stripped module, dev for debug symbols)
3. Download artifact it87-ko-<kernel_version> from the workflow run

The artifact contains:

• it87.ko
• modinfo.txt
• it87.ko.sha256
• kernel-version.txt
• kernel-build-dir.txt

To remove the driver, services, and configuration files:

sudo ./scripts/uninstall.sh

This preserves your /etc/ugreen/ configuration directory. Remove it manually if no longer needed.

Errors, known issues and their fixes have moved to the dedicated FAQ.md:

• Fan control stops working after reboot
• it87 fails to load with Unknown symbol vid_from_reg / vid_which_vrm
• Installer aborts because hwmon-vid is unavailable
• Fan daemon not running or applying incorrect PWM
• iDX6011 — it87 reports "not activated, skipping"
• DKMS module fails to build after kernel update
• TrueNAS SCALE — DKMS build killed / symbol version mismatch

For anything else, check FAQ.md or open an issue.

The idea for this project has been brought by this Reddit post

That was written by

• Copyright (C) 2001 Chris Gauthron
• Copyright (C) 2005-2010 Jean Delvare jdelvare@suse.de and archived by a1wong.

Official kernel documentation: docs.kernel.org/hwmon/it87.html

Tested with

# sensors-detect version 3.6.0
# System: UGREEN DXP2800 [EM_DXP2800_V1.0.25]
# Board: Default string Default string
# OS: Fedora 42 Server Edition
# Kernel: 6.14.5-300.fc42.x86_64 x86_64
# Processor: Intel(R) N100 (6/190/0)

The automated installer ships ugreen-fan-control.service, which manages the fan curve on its own — no fancontrol setup is needed anymore. Verify it is running:

systemctl status ugreen-fan-control.service

Example sensors output with the driver loaded: it8613-isa-0a30

Adapter: ISA adapter
in0:         660.00 mV (min =  +0.00 V, max =  +2.81 V)
in1:           1.12 V  (min =  +0.00 V, max =  +2.81 V)
in2:           2.07 V  (min =  +0.00 V, max =  +2.81 V)
in4:           2.06 V  (min =  +0.00 V, max =  +2.81 V)
in5:           2.08 V  (min =  +0.00 V, max =  +2.81 V)
3VSB:          3.30 V  (min =  +0.00 V, max =  +5.61 V)
Vbat:          3.15 V  
+3.3V:         3.37 V  
fan2:           0 RPM  (min =    0 RPM)
fan3:        1726 RPM  (min =    0 RPM)
temp1:        +40.0°C  (low  = -128.0°C, high = +127.0°C)  sensor = thermistor
temp2:        +23.0°C  (low  = -128.0°C, high = +127.0°C)  sensor = thermistor
temp3:        +42.0°C  (low  = -128.0°C, high = +127.0°C)
intrusion0:  ALARM

acpitz-acpi-0
Adapter: ACPI interface
temp1:        +27.8°C  

coretemp-isa-0000
Adapter: ISA adapter
Package id 0:  +49.0°C  (high = +105.0°C, crit = +105.0°C)
Core 0:        +49.0°C  (high = +105.0°C, crit = +105.0°C)
Core 1:        +49.0°C  (high = +105.0°C, crit = +105.0°C)
Core 2:        +49.0°C  (high = +105.0°C, crit = +105.0°C)
Core 3:        +49.0°C  (high = +105.0°C, crit = +105.0°C)

Want to add support for a new UGREEN NAS model? Start with DEVELOPER.md — it covers the full diagnostics process: chip identification, Super I/O register dumps, OEM custom IDs, and what to include in your issue.

No schematics, no datasheets — we figure it out the hard way.

Please report them here.

It took me a few hours to prepare, testing and deliver this for you. :) I'll appreciate any contribution to the coffee fund :3

BTC: 3EdkooEbQJurjCHScwUjPHGCCszoFh1pmM

ETH: 0x0dB50ef6C03c354795e306133B71A69d8F2e9cc6