2020-11-09 16:08:59 +01:00
![https://valid.x86.fr/vsb4yv ](https://valid.x86.fr/cache/banner/vsb4yv-6.png )
2021-10-14 22:33:42 +02:00
![https://valid.x86.fr/20aiek ](https://valid.x86.fr/cache/banner/20aiek-6.png )
2023-01-04 18:52:38 +01:00
# NCT6687D Kernel module
2020-11-08 00:19:03 +01:00
This kernel module permit to recognize the chipset Nuvoton NCT6687-R in lm-sensors package.
This sensor is present on some B550 motherboard such as MSI or ASUS.
The implementation is minimalist and was done by reverse coding of Windows 10 source code from [LibreHardwareMonitor ](https://github.com/LibreHardwareMonitor/LibreHardwareMonitor )
2022-04-22 18:16:02 +02:00
< br > < br >
2020-11-08 00:19:03 +01:00
## Installation
2023-01-04 18:52:38 +01:00
### .deb package
- Clone this repository
```shell
~$ git clone https://github.com/Fred78290/nct6687d
~$ cd nct6687d
```
- Build package
```shell
~$ make deb
```
- Install package
```shell
~$ dpkg -i ../nct6687d-dkms_*.deb
```
< br >
### .rpm package (akmod)
- Clone this repository
```shell
~$ git clone https://github.com/Fred78290/nct6687d
~$ cd nct6687d
```
- Build & install package
```shell
~$ make akmod
```
< br > < br >
## Manual Install
### Dependencies:
2022-04-22 18:16:02 +02:00
- Ubuntu/Debian:
```apt-get install build-essential linux-headers-$(uname -r) dkms```
- Fedora/CentOS/RHEL:
```yum install make automake gcc gcc-c++ kernel-devel kernel-headers dkms```
- ArchLinux:
```pacman -S make automake linux-firmware linux-headers dkms base-devel```
2022-04-25 16:37:50 +02:00
- openSUSE:
```zypper in git make gcc dkms```
2022-04-22 18:16:02 +02:00
< br >
### Build with DKMS
2020-11-08 00:19:03 +01:00
```shell
2022-04-22 18:16:02 +02:00
~$ git clone https://github.com/Fred78290/nct6687d
~$ cd nct6687d
~$ make dkms/install
2020-11-08 00:19:03 +01:00
```
2022-04-22 18:16:02 +02:00
< br >
2020-11-08 00:19:03 +01:00
2022-04-22 18:16:02 +02:00
### Manual build
2020-11-08 00:19:03 +01:00
```shell
2022-04-22 18:16:02 +02:00
~$ git clone (this-repo)
~$ cd nct6687d
~$ make install
2020-11-08 00:19:03 +01:00
```
2022-04-22 18:16:02 +02:00
< br >
2020-11-08 00:19:03 +01:00
## Sensors
By running the command sensors, you got this output
```
nct6687-isa-0a20
Adapter: ISA adapter
2020-11-08 17:22:25 +01:00
+12V: 12.17 V (min = +12.17 V, max = +12.19 V)
+5V: 5.14 V (min = +5.14 V, max = +5.14 V)
+3.3V: 3.38 V (min = +3.38 V, max = +3.38 V)
CPU Soc: 1.11 V (min = +1.11 V, max = +1.11 V)
CPU Vcore: 1.05 V (min = +0.97 V, max = +1.05 V)
CPU 1P8: 1.84 V (min = +1.84 V, max = +1.84 V)
CPU VDDP: 0.00 V (min = +0.00 V, max = +0.00 V)
DRAM: 1.34 V (min = +1.34 V, max = +1.35 V)
Chipset: 890.00 mV (min = +0.89 V, max = +0.89 V)
CPU Fan: 1192 RPM (min = 1192 RPM, max = 1202 RPM)
Pump Fan: 1538 RPM (min = 1526 RPM, max = 1538 RPM)
System Fan #1: 922 RPM (min = 920 RPM, max = 922 RPM)
System Fan #2: 953 RPM (min = 953 RPM, max = 953 RPM)
System Fan #3: 1393 RPM (min = 1393 RPM, max = 1393 RPM)
System Fan #4: 0 RPM (min = 0 RPM, max = 0 RPM)
System Fan #5: 1007 RPM (min = 1007 RPM, max = 1007 RPM)
System Fan #6: 0 RPM (min = 0 RPM, max = 0 RPM)
CPU: +59.0°C (low = +52.0°C, high = +59.0°C)
System: +34.0°C (low = +34.0°C, high = +34.0°C)
VRM MOS: +31.0°C (low = +31.0°C, high = +31.0°C)
PCH: +40.0°C (low = +40.0°C, high = +40.0°C)
CPU Socket: +33.0°C (low = +33.0°C, high = +33.0°C)
PCIe x1: +32.0°C (low = +32.0°C, high = +32.0°C)
M2_1: +0.0°C (low = +0.0°C, high = +0.0°C)
2020-11-08 00:19:03 +01:00
```
2022-04-22 18:16:02 +02:00
< br >
2021-07-06 07:48:51 +02:00
## Load(prob) Sensors on boot
To make it loaded after system boots
Just add nct6687 into /etc/modules
`sudo sh -c 'echo "nct6687" >> /etc/modules'`
2023-03-10 18:28:03 +01:00
### Arch-Linux with systemd
`sudo sh -c 'echo "nct6687" >> /etc/modules-load.d/nct6687.conf'`
2022-04-22 18:16:02 +02:00
< br >
2020-11-08 17:22:25 +01:00
## Gnome sensors extensions
2020-11-08 22:17:01 +01:00
![Fan ](./images/fan.png ) ![Voltage ](./images/voltage.png )
2022-04-22 18:16:02 +02:00
< br >
2020-11-08 00:19:03 +01:00
## Tested
2022-02-15 23:21:10 +01:00
This module was tested on Ubuntu 20.04 with all kernel availble on motherboard [MAG-B550-TOMAHAWK ](https://www.msi.com//Motherboard/MAG-B550-TOMAHAWK ) running an [AMD 3900X/AMD 5900X ](https://www.amd.com/en/products/cpu/amd-ryzen-9-3900x )
2020-11-08 00:19:03 +01:00
2022-04-22 18:16:02 +02:00
< br >
2022-02-15 23:21:10 +01:00
2022-04-22 18:16:02 +02:00
## Other motherboard supported
- Many people have reported compatibility with MB having Intel H410M & H510M chipset from some manufacturer. See [issue ](https://github.com/Fred78290/nct6687d/issues ) report.
< br >
2022-02-15 23:21:10 +01:00
## CHANGELOG
- Add support for MSI B460M Bazooka having NCT6687 with another device ID
2022-07-17 11:48:26 +02:00
- Add support to use generic voltage input without multiplier, allows sensors custom conf
2022-04-22 18:16:02 +02:00
< br >
2022-02-15 23:21:10 +01:00
2022-07-17 11:48:26 +02:00
## VOLTAGE MANUAL CONFIGURATION
Some people report that voltage are wrong. The reason is with some motherboard, voltage sensors are not connected on the same nct6687 register.
As example the **VCore** sensor is connected on the **5th** register for AMD but is connected on the **3rd** register for INTEL.
< br >
Also the **DIMM** sensor is connected on the **4th** register for AMD but connected to **5th** register for INTEL.
To allow customize voltage configuration you must add **manual=1** parameter passed to the module at load
`sudo sh -c 'echo "nct6687 manual=1" >> /etc/modules'`
And use a sensors conf like this ** /etc/sensors.d/B460M-7C83.conf**
```
# Micro-Star International Co., Ltd.
# MAG B460M BAZOOKA (MS-7C83)
chip "nct6687-*"
label in0 "+12V"
label in1 "+5V"
label in2 "VCore"
label in3 "Voltage #1 "
label in4 "DIMM"
label in5 "CPU I/O"
label in6 "CPU SA"
label in7 "Voltage #2 "
label in8 "+3.3V"
label in9 "VTT"
label in10 "VRef"
label in11 "VSB"
label in12 "AVSB"
label in13 "VBat"
ignore in3
ignore in7
ignore in9
ignore in10
ignore in13
ignore temp6
ignore temp7
compute in0 (@ * 12), (@ / 12)
compute in1 (@ * 5), (@ / 5)
compute in4 (@ * 2), (@ / 2)
```
2022-02-15 23:21:10 +01:00
## VERIFIED
2020-11-08 00:19:03 +01:00
**1. Fan speed control**
2023-01-04 18:52:38 +01:00
- Changing fan speed was tested succesfuly by users, see reported issue.