Installer pilote Nuvoton NTC6798D pour CM Asus Rog Stricks X570 Gaming-F

Bonjour à tous.

Via "sensors-detect" il semble nécessaire d'installer le pilote Nuvoton NTC6798D afin d'accéder notamment aux différentes températures.

Voici ce que je trouve:
https://github.com/LibreHardwareMonitor ... 835cbab145

En effet, mon Ryzen chauffe pas mal et je peine à régler mon watercooling sans infos précises.
Comme je suis newbie, j'ignore comment procéder...

Aussi, juste après grub, j'ai 7 ou 8 messages "No irq handler for vector" et j'ignore si cela a un rapport.
Je suis sous Manjaro 20 xfce kernel 5.8, ma CM est une Asus Rog Stricks X570 Gaming-F, mon CPU: Ryzen 7 3700x et mon bios est à jour.

Merci d'avance pour toute aide possible !

que retourne sensors dans ton cas ?
aussi inxi -Fxza --no-host

pour le message ""No irq handler for vector" , il faut attendre un correctif général sur le kernel pour amd

Bonjour, désolé pour le retard de ma réponse et merci pour votre aide

Voici le retour de inxi -Fxza --no-host:

System:    Kernel: 5.8.3-2-MANJARO x86_64 bits: 64 compiler: N/A 
           parameters: BOOT_IMAGE=/boot/vmlinuz-5.8-x86_64 root=UUID=057a6f7f-7c80-4b55-968e-a67bdb2c73f5 rw quiet apparmor=1 
           security=apparmor udev.log_priority=3 
           Desktop: Xfce 4.14.2 tk: Gtk 3.24.20 info: xfce4-panel wm: xfwm4 dm: LightDM 1.30.0 Distro: Manjaro Linux 
Machine:   Type: Desktop Mobo: ASUSTeK model: ROG STRIX X570-F GAMING v: Rev X.0x serial: <filter> UEFI: American Megatrends 
           v: 2606 date: 08/13/2020 
CPU:       Topology: 8-Core model: AMD Ryzen 7 3700X bits: 64 type: MT MCP arch: Zen 2 family: 17 (23) model-id: 71 (113) 
           stepping: N/A microcode: 8701021 L2 cache: 4096 KiB 
           flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm bogomips: 115037 
           Speed: 2913 MHz min/max: 2200/3600 MHz boost: enabled Core speeds (MHz): 1: 2795 2: 1863 3: 1858 4: 1858 5: 2047 
           6: 3592 7: 2048 8: 2046 9: 1862 10: 1863 11: 2048 12: 3593 13: 2053 14: 2051 15: 2795 16: 1859 
           Vulnerabilities: Type: itlb_multihit status: Not affected 
           Type: l1tf status: Not affected 
           Type: mds status: Not affected 
           Type: meltdown status: Not affected 
           Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl and seccomp 
           Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization 
           Type: spectre_v2 mitigation: Full AMD retpoline, IBPB: conditional, STIBP: conditional, RSB filling 
           Type: srbds status: Not affected 
           Type: tsx_async_abort status: Not affected 
Graphics:  Device-1: NVIDIA GP106 [GeForce GTX 1060 6GB] vendor: Gigabyte driver: nvidia v: 440.100 
           alternate: nouveau,nvidia_drm bus ID: 09:00.0 chip ID: 10de:1c03 
           Display: x11 server: X.Org 1.20.8 driver: nvidia display ID: :0.0 screens: 1 
           Screen-1: 0 s-res: 3440x1440 s-dpi: 109 s-size: 802x333mm (31.6x13.1") s-diag: 868mm (34.2") 
           Monitor-1: HDMI-2 res: 3440x1440 hz: 50 dpi: 110 size: 797x333mm (31.4x13.1") diag: 864mm (34") 
           OpenGL: renderer: GeForce GTX 1060 6GB/PCIe/SSE2 v: 4.6.0 NVIDIA 440.100 direct render: Yes 
Audio:     Device-1: NVIDIA GP106 High Definition Audio vendor: Gigabyte driver: snd_hda_intel v: kernel bus ID: 09:00.1 
           chip ID: 10de:10f1 
           Device-2: Advanced Micro Devices [AMD] Starship/Matisse HD Audio vendor: ASUSTeK driver: snd_hda_intel v: kernel 
           bus ID: 0b:00.4 chip ID: 1022:1487 
           Sound Server: ALSA v: k5.8.3-2-MANJARO 
Network:   Device-1: Intel I211 Gigabit Network vendor: ASUSTeK driver: igb v: 5.6.0-k port: f000 bus ID: 05:00.0 
           chip ID: 8086:1539 
           IF: enp5s0 state: up speed: 1000 Mbps duplex: full mac: <filter> 
Drives:    Local Storage: total: 5.46 TiB used: 806.86 GiB (14.4%) 
           SMART Message: Required tool smartctl not installed. Check --recommends 
           ID-1: /dev/nvme0n1 vendor: Samsung model: SSD 970 EVO Plus 500GB size: 465.76 GiB block size: physical: 512 B 
           logical: 512 B speed: 31.6 Gb/s lanes: 4 serial: <filter> rev: 2B2QEXM7 scheme: GPT 
           ID-2: /dev/nvme1n1 vendor: Crucial model: CT1000P1SSD8 size: 931.51 GiB block size: physical: 512 B logical: 512 B 
           speed: 31.6 Gb/s lanes: 4 serial: <filter> rev: P3CR013 scheme: GPT 
           ID-3: /dev/sda vendor: Toshiba model: MQ01ABB200 size: 1.82 TiB block size: physical: 4096 B logical: 512 B 
           speed: 3.0 Gb/s rotation: 5400 rpm serial: <filter> rev: 0U scheme: GPT 
           ID-4: /dev/sdb vendor: Western Digital model: WD30EZRX-00DC0B0 size: 2.73 TiB block size: physical: 4096 B 
           logical: 512 B speed: 6.0 Gb/s serial: <filter> rev: 0A80 scheme: GPT 
Partition: ID-1: / raw size: 306.57 GiB size: 300.76 GiB (98.10%) used: 66.76 GiB (22.2%) fs: ext4 dev: /dev/nvme0n1p5 
Swap:      Alert: No Swap data was found. 
Sensors:   System Temperatures: cpu: 44.0 C mobo: N/A gpu: nvidia temp: 45 C 
           Fan Speeds (RPM): N/A gpu: nvidia fan: 0% 
Info:      Processes: 307 Uptime: 1h 15m Memory: 15.61 GiB used: 2.87 GiB (18.4%) Init: systemd v: 246 Compilers: gcc: 10.2.0 
           Packages: pacman: 1216 lib: 349 flatpak: 0 Shell: Bash v: 5.0.18 running in: xfce4-terminal inxi: 3.1.05

...et le retour de sensors:

k10temp-pci-00c3
Adapter: PCI adapter
Vcore:       931.00 mV 
Vsoc:          1.10 V  
Tctl:         +34.6°C  
Tdie:         +34.6°C  
Tccd1:        +34.8°C  
Icore:         5.00 A  
Isoc:          6.25 A  

nvme-pci-0400
Adapter: PCI adapter
Composite:    +39.9°C  (low  = -273.1°C, high = +69.8°C)
                       (crit = +79.8°C)
Sensor 1:     +40.9°C  (low  = -273.1°C, high = +65261.8°C)
Sensor 2:     +38.9°C  (low  = -273.1°C, high = +65261.8°C)
Sensor 5:     +48.9°C  (low  = -273.1°C, high = +65261.8°C)

nvme-pci-0100
Adapter: PCI adapter
Composite:    +39.9°C  (low  = -273.1°C, high = +84.8°C)
                       (crit = +84.8°C)
Sensor 1:     +39.9°C  (low  = -273.1°C, high = +65261.8°C)
Sensor 2:     +37.9°C  (low  = -273.1°C, high = +65261.8°C)

utilisez la balise CODE plutôt que la balise LIST

administration/modération

bonjour

alors a priori si tu ne rencontre pas de souci avec ce ryzen 2 , pense quand même a jouter ce paramètre
"idle=nomwait" au démarrage
il y a 2 autres point a vérifier , pas de mode C6 actif dans le bios ,
et si jamais tu as des erreurs mce qui apparaisse , il faudra voir pour recompiler le noyau pour ajouter option
nocbs=0-16 ( attention nécessite une modifier la configuration noyau et de recompiler le noyau pour cela )

pas trouvé de driver NTC6798D dans AUR
a vérifier si nct6775 permet de gérer cela , qui existe dans AUR

https://github.com/electrified/asus-wmi-sensors concernent les cartes avant les 570 series

Merci, je vais checker le tout, je posterai mes retours, bonne journée

Salut,

Jeanfourne a écrit : ↑il y a 3 ans
Via "sensors-detect" il semble nécessaire d'installer le pilote Nuvoton NTC6798D afin d'accéder notamment aux différentes températures.

Apparemment le pilote ntc6775 gère aussi les puces NTC6798D, mais n'affiche pas toujours la vitesse du ventilateur suivant les cartes mères.

Charger le module temporairement :

sudo modprobe nct6775

Refaire une détection :

sudo sensors-detect

et lancer la commande :

sensors

pour voir le résultat.

Merci Smurf ! J'essaye de suite...

Pilote chargé, sensors-detect complet, reboot puis sensors mais aucun changement...

Merci tt de même

Jeanfourne a écrit : ↑il y a 3 ans Pilote chargé, sensors-detect complet, reboot puis sensors mais aucun changement...

Il ne fallait pas rebooter, modeprobe sert à charger le pilote seulement pendant que le système est actif, si tu rebootes, ton module ntc6775 ne seras pas chargé au démarrage. C'était temporaire avant de faire le changement définitif, si l'essai est concluant.
Pour charger un pilote au démarrage définitivement, il faut l'ajouter dans /etc/modules-load.d/modules.conf

Ok, je procède sans reboot dans ce cas...

Voici toutes ces étapes sans reboot:

[vltz@Man-F ~]$ sudo modprobe nct6775
[sudo] Mot de passe de vltz : 
[vltz@Man-F ~]$ sudo sensors-detect
# sensors-detect version 3.6.0
# Board: ASUSTeK COMPUTER INC. ROG STRIX X570-F GAMING
# Kernel: 5.8.3-2-MANJARO x86_64
# Processor: AMD Ryzen 7 3700X 8-Core Processor (23/113/0)

This program will help you determine which kernel modules you need
to load to use lm_sensors most effectively. It is generally safe
and recommended to accept the default answers to all questions,
unless you know what you're doing.

Some south bridges, CPUs or memory controllers contain embedded sensors.
Do you want to scan for them? This is totally safe. (YES/no): 
Module cpuid loaded successfully.
Silicon Integrated Systems SIS5595...                       No
VIA VT82C686 Integrated Sensors...                          No
VIA VT8231 Integrated Sensors...                            No
AMD K8 thermal sensors...                                   No
AMD Family 10h thermal sensors...                           No
AMD Family 11h thermal sensors...                           No
AMD Family 12h and 14h thermal sensors...                   No
AMD Family 15h thermal sensors...                           No
AMD Family 16h thermal sensors...                           No
AMD Family 17h thermal sensors...                           Success!
    (driver `k10temp')
AMD Family 15h power sensors...                             No
AMD Family 16h power sensors...                             No
Hygon Family 18h thermal sensors...                         No
Intel digital thermal sensor...                             No
Intel AMB FB-DIMM thermal sensor...                         No
Intel 5500/5520/X58 thermal sensor...                       No
VIA C7 thermal sensor...                                    No
VIA Nano thermal sensor...                                  No

Some Super I/O chips contain embedded sensors. We have to write to
standard I/O ports to probe them. This is usually safe.
Do you want to scan for Super I/O sensors? (YES/no): 
Probing for Super-I/O at 0x2e/0x2f
Trying family `National Semiconductor/ITE'...               No
Trying family `SMSC'...                                     No
Trying family `VIA/Winbond/Nuvoton/Fintek'...               Yes
Found `Nuvoton NCT6798D Super IO Sensors'                   Success!
    (address 0x290, driver `nct6775')
Probing for Super-I/O at 0x4e/0x4f
Trying family `National Semiconductor/ITE'...               No
Trying family `SMSC'...                                     No
Trying family `VIA/Winbond/Nuvoton/Fintek'...               No
Trying family `ITE'...                                      No

Some systems (mainly servers) implement IPMI, a set of common interfaces
through which system health data may be retrieved, amongst other things.
We first try to get the information from SMBIOS. If we don't find it
there, we have to read from arbitrary I/O ports to probe for such
interfaces. This is normally safe. Do you want to scan for IPMI
interfaces? (YES/no): 
Probing for `IPMI BMC KCS' at 0xca0...                      No
Probing for `IPMI BMC SMIC' at 0xca8...                     No

Some hardware monitoring chips are accessible through the ISA I/O ports.
We have to write to arbitrary I/O ports to probe them. This is usually
safe though. Yes, you do have ISA I/O ports even if you do not have any
ISA slots! Do you want to scan the ISA I/O ports? (yes/NO): yes
Probing for `National Semiconductor LM78' at 0x290...       No
Probing for `National Semiconductor LM79' at 0x290...       No
Probing for `Winbond W83781D' at 0x290...                   No
Probing for `Winbond W83782D' at 0x290...                   No

Lastly, we can probe the I2C/SMBus adapters for connected hardware
monitoring devices. This is the most risky part, and while it works
reasonably well on most systems, it has been reported to cause trouble
on some systems.
Do you want to probe the I2C/SMBus adapters now? (YES/no): 
Using driver `i2c-piix4' for device 0000:00:14.0: AMD KERNCZ SMBus
Module i2c-dev loaded successfully.

Next adapter: SMBus PIIX4 adapter port 0 at 0b00 (i2c-0)
Do you want to scan it? (YES/no/selectively): 
Client found at address 0x52
Probing for `Analog Devices ADM1033'...                     No
Probing for `Analog Devices ADM1034'...                     No
Probing for `SPD EEPROM'...                                 Yes
    (confidence 8, not a hardware monitoring chip)
Client found at address 0x53
Probing for `Analog Devices ADM1033'...                     No
Probing for `Analog Devices ADM1034'...                     No
Probing for `SPD EEPROM'...                                 Yes
    (confidence 8, not a hardware monitoring chip)
Client found at address 0x58
Probing for `Analog Devices ADT7462'...                     No
Probing for `Andigilog aSC7512'...                          No

Next adapter: SMBus PIIX4 adapter port 2 at 0b00 (i2c-1)
Do you want to scan it? (YES/no/selectively): 

Next adapter: SMBus PIIX4 adapter port 1 at 0b20 (i2c-2)
Do you want to scan it? (YES/no/selectively): 

Next adapter: NVIDIA i2c adapter 1 at 9:00.0 (i2c-3)
Do you want to scan it? (yes/NO/selectively): 

Next adapter: NVIDIA i2c adapter 2 at 9:00.0 (i2c-4)
Do you want to scan it? (yes/NO/selectively): 

Next adapter: NVIDIA i2c adapter 4 at 9:00.0 (i2c-5)
Do you want to scan it? (yes/NO/selectively): 

Next adapter: NVIDIA i2c adapter 5 at 9:00.0 (i2c-6)
Do you want to scan it? (yes/NO/selectively): 

Next adapter: NVIDIA i2c adapter 6 at 9:00.0 (i2c-7)
Do you want to scan it? (yes/NO/selectively): 

Next adapter: NVIDIA i2c adapter 7 at 9:00.0 (i2c-8)
Do you want to scan it? (yes/NO/selectively): 

Next adapter: NVIDIA i2c adapter 8 at 9:00.0 (i2c-9)
Do you want to scan it? (yes/NO/selectively): 

Next adapter: NVIDIA i2c adapter 9 at 9:00.0 (i2c-10)
Do you want to scan it? (yes/NO/selectively): 


Now follows a summary of the probes I have just done.
Just press ENTER to continue: 

Driver `nct6775':
  * ISA bus, address 0x290
    Chip `Nuvoton NCT6798D Super IO Sensors' (confidence: 9)

Driver `k10temp' (autoloaded):
  * Chip `AMD Family 17h thermal sensors' (confidence: 9)

Do you want to overwrite /etc/conf.d/lm_sensors? (YES/no): 
Unloading i2c-dev... OK
Unloading cpuid... OK
[vltz@Man-F ~]$ sensors
k10temp-pci-00c3
Adapter: PCI adapter
Vcore:       938.00 mV 
Vsoc:          1.09 V  
Tctl:         +34.5°C  
Tdie:         +34.5°C  
Tccd1:        +34.5°C  
Icore:         4.00 A  
Isoc:          5.25 A  

nvme-pci-0100
Adapter: PCI adapter
Composite:    +38.9°C  (low  = -273.1°C, high = +84.8°C)
                       (crit = +84.8°C)
Sensor 1:     +38.9°C  (low  = -273.1°C, high = +65261.8°C)
Sensor 2:     +36.9°C  (low  = -273.1°C, high = +65261.8°C)

nvme-pci-0400
Adapter: PCI adapter
Composite:    +38.9°C  (low  = -273.1°C, high = +69.8°C)
                       (crit = +79.8°C)
Sensor 1:     +39.9°C  (low  = -273.1°C, high = +65261.8°C)
Sensor 2:     +37.9°C  (low  = -273.1°C, high = +65261.8°C)
Sensor 5:     +46.9°C  (low  = -273.1°C, high = +65261.8°C)

[vltz@Man-F ~]$

(bis) utilisez la balise CODE plutôt que la balise LIST

administration/modération

Driver `nct6775':
  * ISA bus, address 0x290
    Chip `Nuvoton NCT6798D Super IO Sensors' (confidence: 9)

On voit qu'il a bien trouvé l'interface, mais je n'ai aucune idée de pourquoi il n'affiche pas les sondes avec la commande sensors.