Abscence capteurs de température

wardidi · 18-10-2023 17:09:10

Bonjour,

Je souhaite "enfermer" mon (vieux) PC/serveur de musique pour plus de discrétion dans le salon.
Il ne sert qu'aà la lecture de musique, sans graphique, avec gestion à distance via ssh.
J'aimerais vérifier les températures à l'intérieur avant ET après la mise en boite pour être certain de ne pas tout surchauffer.

Mais sensors renvoie seulement

~$ sensors

acpitz-acpi-0

Adapter: ACPI interface

temp1:        +40.0°C  (crit = +75.0°C)

Si j'ai bien compris il s'agit simplement d'un capteur 'ambiance" de la CM.
Quid du cpu?
Est-ce à dire que je n'ai pas d'autres capteurs.

La réinstall de lm-sensors me dit que j'ai la dernière version.

Voici ce que me donnait sensors-detect.

~$ sudo sensors-detect

[sudo] Mot de passe de didier : 

# sensors-detect version 3.6.0

# System: MEDIONPC MS-7048

# Board: MICRO-STAR INTERNATIONAL CO., LTD MS-7048

# Kernel: 6.1.0-12-686 i686

# Processor: Intel(R) Pentium(R) 4 CPU 3.00GHz (15/2/9)

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): yes

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...                           No

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): yes

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 `Winbond W83637HF/HG Super IO Sensors'                Success!

    (address 0x290, driver `w83627hf')

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): yes

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): yes

Using driver `i2c-i801' for device 0000:00:1f.3: Intel 82801EB ICH5

Module i2c-dev loaded successfully.

Next adapter: SMBus I801 adapter at 0500 (i2c-0)

Do you want to scan it? (yes/NO/selectively): yes

Client found at address 0x2f

Probing for `National Semiconductor LM78'...                No

Probing for `National Semiconductor LM79'...                No

Probing for `National Semiconductor LM80'...                No

Probing for `National Semiconductor LM96080'...             No

Probing for `TI / National Semiconductor ADC128D818'...     No

Probing for `Analog Devices ADT7470'...                     No

Probing for `Winbond W83781D'...                            No

Probing for `Winbond W83782D'...                            No

Probing for `Winbond W83791D'...                            No

Probing for `Winbond W83792D'...                            No

Probing for `Winbond W83793R/G'...                          No

Probing for `Nuvoton W83795G/ADG'...                        No

Probing for `Nuvoton NCT7802Y'...                           No

Probing for `Winbond W83627HF'...                           No

Probing for `Winbond W83627EHF'...                          No

Probing for `Winbond W83627DHG/W83667HG/W83677HG'...        No

Probing for `Asus AS99127F (rev.1)'...                      No

Probing for `Asus AS99127F (rev.2)'...                      No

Probing for `Asus ASB100 Bach'...                           No

Probing for `Winbond W83L786NR/NG/R/G'...                   No

Probing for `Analog Devices ADM9240'...                     No

Probing for `Dallas Semiconductor DS1780'...                No

Probing for `National Semiconductor LM81'...                No

Probing for `Maxim MAX6639'...                              No

Probing for `Analog Devices ADM1029'...                     No

Probing for `ITE IT8712F'...                                No

Probing for `SMSC EMC2104'...                               No

Probing for `Fintek custom power control IC'...             No

Probing for `Winbond W83791SD'...                           No

Client found at address 0x50

Probing for `Analog Devices ADM1033'...                     No

Probing for `Analog Devices ADM1034'...                     No

Probing for `SPD EEPROM'...                                 Yes

    (confidence 8, not a hardware monitoring chip)

Probing for `EDID EEPROM'...                                No

Client found at address 0x51

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 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)

Now follows a summary of the probes I have just done.

Just press ENTER to continue: 

Driver `w83627hf':

  * ISA bus, address 0x290

    Chip `Winbond W83637HF/HG Super IO Sensors' (confidence: 9)

To load everything that is needed, add this to /etc/modules:

#----cut here----

# Chip drivers

w83627hf

#----cut here----

If you have some drivers built into your kernel, the list above will

contain too many modules. Skip the appropriate ones!

Do you want to add these lines automatically to /etc/modules? (yes/NO)yes

Successful!

Monitoring programs won't work until the needed modules are

loaded. You may want to run '/etc/init.d/kmod start'

to load them.

Unloading i2c-dev... OK

Unloading cpuid... OK

Merci de votre aide.

Croutons · 18-10-2023 19:38:38

hello
à lire avant de lancer sensors-detect, dans de rare cas il risque d’abîmé le matériel voir le rendre untilisable
moi aussi je l'ai vu que plus tard ce message, heureusement tout c'est bien passé, depuis j'ai température CM, CPU et alimentation
pareil pour les ventilateurs
par contre pour les numéros des capteurs c'est pas évident, on ne sait pas trop lequel est ce
je m'en suis rendu compte en stressant le processeur avec l'utilitaire stress

Description: tool to impose load on and stress test a computer system
'stress' is a tool that imposes a configurable amount of CPU, memory, I/O,
or disk stress on a POSIX-compliant operating system and reports any errors
it detects.
.
'stress' is not a benchmark. It is a tool used by system administrators to
evaluate how well their systems will scale, by kernel programmers to evaluate
perceived performance characteristics, and by systems programmers to expose
the classes of bugs which only or more frequently manifest themselves when
the system is under heavy load.

man sensors-detect a écrit :

WARNING
sensors-detect needs to access the hardware for most of the chip detections. By definition, it doesn't know which chips are there before it manages to identify them. This
means that it can access chips in a way these chips do not like, causing problems ranging from SMBus lockup to permanent hardware damage (a rare case, thankfully.)

The authors made their best to make the detection as safe as possible, and it turns out to work just fine in most cases, however it is impossible to guarantee that sensors-
detect will not lock or kill a specific system. So, as a rule of thumb, you should not run sensors-detect on production servers, and you should not run sensors-detect if
can't afford replacing a random part of your system. Also, it is recommended to not force a detection step which would have been skipped by default, unless you know what
you are doing.

normalement tu as laissé sensors-detect ajouter le module
essai la ligne suggéré

/etc/init.d/kmod start

après vérifie que le module est bien chargé

lsmod|grep w83627hf

Dernière modification par Croutons (19-10-2023 08:46:36)

wardidi · 19-10-2023 14:38:09

Bonjour Croutons et merci de prendre le temps de me renseigner.

Croutons a écrit :

normalement tu as laissé sensors-detect ajouter le module
essai la ligne suggéré
/etc/init.d/kmod start

En attendant une réponse j'avais déja essayé ça et aussi le reboot. Mais j'obtiens un failed

sudo /etc/init.d/kmod start

[sudo] Mot de passe de didier : 

Starting kmod (via systemctl): kmod.serviceJob for systemd-modules-load.service failed because the control process exited with error code.

See "systemctl status systemd-modules-load.service" and "journalctl -xeu systemd-modules-load.service" for details.

 failed!

Pour les détails

~$ sudo systemctl status systemd-modules-load.service

× systemd-modules-load.service - Load Kernel Modules

     Loaded: loaded (/lib/systemd/system/systemd-modules-load.service; static)

     Active: failed (Result: exit-code) since Thu 2023-10-19 15:00:35 CEST; 56s ago

       Docs: man:systemd-modules-load.service(8)

             man:modules-load.d(5)

    Process: 1249 ExecStart=/lib/systemd/systemd-modules-load (code=exited, status=1/FAILURE)

   Main PID: 1249 (code=exited, status=1/FAILURE)

        CPU: 22ms

oct. 19 15:00:34 debian systemd[1]: Starting systemd-modules-load.service - Load Kernel Modules...

oct. 19 15:00:35 debian systemd-modules-load[1249]: Failed to insert module 'w83627hf': Device or resource busy

oct. 19 15:00:35 debian systemd[1]: systemd-modules-load.service: Main process exited, code=exited, status=1/FAILURE

oct. 19 15:00:35 debian systemd[1]: systemd-modules-load.service: Failed with result 'exit-code'.

oct. 19 15:00:35 debian systemd[1]: Failed to start systemd-modules-load.service - Load Kernel Modules.

Et aussi

~$ sudo journalctl -xeu systemd-modules-load.service

░░ Support: https://www.debian.org/support

░░ 

░░ L'unité (unit) systemd-modules-load.service a commencé à démarrer.

oct. 19 12:21:53 debian systemd[1]: systemd-modules-load.service: Main process exited, code=exited, status=1/FAILURE

░░ Subject: Unit process exited

░░ Defined-By: systemd

░░ Support: https://www.debian.org/support

░░ 

░░ An ExecStart= process belonging to unit systemd-modules-load.service has exited.

░░ 

░░ The process' exit code is 'exited' and its exit status is 1.

oct. 19 12:21:53 debian systemd[1]: systemd-modules-load.service: Failed with result 'exit-code'.

░░ Subject: Unit failed

░░ Defined-By: systemd

░░ Support: https://www.debian.org/support

░░ 

░░ The unit systemd-modules-load.service has entered the 'failed' state with result 'exit-code'.

oct. 19 12:21:53 debian systemd[1]: Failed to start systemd-modules-load.service - Load Kernel Modules.

░░ Subject: L'unité (unit) systemd-modules-load.service a échoué

░░ Defined-By: systemd

░░ Support: https://www.debian.org/support

░░ 

░░ L'unité (unit) systemd-modules-load.service a échoué, avec le résultat failed.

oct. 19 15:00:34 debian systemd[1]: Starting systemd-modules-load.service - Load Kernel Modules...

░░ Subject: L'unité (unit) systemd-modules-load.service a commencé à démarrer

░░ Defined-By: systemd

░░ Support: https://www.debian.org/support

░░ 

░░ L'unité (unit) systemd-modules-load.service a commencé à démarrer.

oct. 19 15:00:35 debian systemd-modules-load[1249]: Failed to insert module 'w83627hf': Device or resource busy

oct. 19 15:00:35 debian systemd[1]: systemd-modules-load.service: Main process exited, code=exited, status=1/FAILURE

░░ Subject: Unit process exited

░░ Defined-By: systemd

░░ Support: https://www.debian.org/support

░░ 

░░ An ExecStart= process belonging to unit systemd-modules-load.service has exited.

░░ 

░░ The process' exit code is 'exited' and its exit status is 1.

oct. 19 15:00:35 debian systemd[1]: systemd-modules-load.service: Failed with result 'exit-code'.

░░ Subject: Unit failed

░░ Defined-By: systemd

░░ Support: https://www.debian.org/support

░░ 

░░ The unit systemd-modules-load.service has entered the 'failed' state with result 'exit-code'.

oct. 19 15:00:35 debian systemd[1]: Failed to start systemd-modules-load.service - Load Kernel Modules.

░░ Subject: L'unité (unit) systemd-modules-load.service a échoué

░░ Defined-By: systemd

░░ Support: https://www.debian.org/support

░░ 

░░ L'unité (unit) systemd-modules-load.service a échoué, avec le résultat failed.

J'ai lancé 3 fois sensors detect dont une fois après avoir commanté la ligne w83627hf dans le fichier /etc/modules

# /etc/modules: kernel modules to load at boot time.

#

# This file contains the names of kernel modules that should be loaded

# at boot time, one per line. Lines beginning with "#" are ignored.

# Parameters can be specified after the module name.

#firewire-sbp2

# Generated by sensors-detect on Wed Oct 18 15:03:36 2023

# Chip drivers

#w83627hf

# Generated by sensors-detect on Wed Oct 18 17:44:38 2023

# Chip drivers

w83627hf

Du coup

Croutons a écrit :

après vérifie que le module est bien chargé
lsmod|grep w83627hf

Ne ramène rien.

Si je comprend bien module 'w83627hf est bien enregistré mais pose problème pour lancé systemd-modules-load.service.

J'ai bien compris?
Comment résoudre la problème????
EDIT: Que penser de la solution trouvé ici https://ubuntuforums.org/showthread.php … ost8485676
Elle consiste à ajouter

GRUB_CMDLINE_LINUX="acpi_enforce_resources=lax" 

dans /etc/default/grub puis mise à jour du grub et reboot.

Je n'aime pas touché au grub....
Pour info

nano /etc/default/grub

  GNU nano 7.2                                               /etc/default/grub                                                         

# If you change this file, run 'update-grub' afterwards to update

# /boot/grub/grub.cfg.

# For full documentation of the options in this file, see:

#   info -f grub -n 'Simple configuration'

GRUB_DEFAULT=0

GRUB_TIMEOUT=5

GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`

GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"

GRUB_CMDLINE_LINUX="acpi_osi=Linux"

# If your computer has multiple operating systems installed, then you

# probably want to run os-prober. However, if your computer is a host

# for guest OSes installed via LVM or raw disk devices, running

# os-prober can cause damage to those guest OSes as it mounts

# filesystems to look for things.

#GRUB_DISABLE_OS_PROBER=false

# Uncomment to enable BadRAM filtering, modify to suit your needs

# This works with Linux (no patch required) and with any kernel that obtains

# the memory map information from GRUB (GNU Mach, kernel of FreeBSD ...)

#GRUB_BADRAM="0x01234567,0xfefefefe,0x89abcdef,0xefefefef"

# Uncomment to disable graphical terminal

#GRUB_TERMINAL=console

# The resolution used on graphical terminal

# note that you can use only modes which your graphic card supports via VBE

# you can see them in real GRUB with the command `vbeinfo'

#GRUB_GFXMODE=640x480

# Uncomment if you don't want GRUB to pass "root=UUID=xxx" parameter to Linux

#GRUB_DISABLE_LINUX_UUID=true

# Uncomment to disable generation of recovery mode menu entries

#GRUB_DISABLE_RECOVERY="true"

# Uncomment to get a beep at grub start

#GRUB_INIT_TUNE="480 440 1"

Croutons · 19-10-2023 19:17:05

tu peux toujours essayer, j'ai trouver un post ou l'utilisateur se posait la question de savoir si c'est sur de mettre ce parametre
il a fini par le mettre et ne constate pas de dysfonctionnement sur sa machine
https://bbs.archlinux.org/viewtopic.php?id=265939

wardidi · 25-10-2023 19:35:24

Croutons a écrit :

tu peux toujours essayer, j'ai trouver un post ou l'utilisateur se posait la question de savoir si c'est sur de mettre ce parametre
il a fini par le mettre et ne constate pas de dysfonctionnement sur sa machine
https://bbs.archlinux.org/viewtopic.php?id=265939

En fait, ca me pose un vrai problème de toucher au grub.
J'ai aussi vu https://forums.debian.net/viewtopic.php?t=124192 que ça pouvait engendrer des instabilités.

Je n'ai pas de carte graphique, donc en cas de plantage du grub et de non démarrage dedebian , je ne pourrais rien faire.
Donc je pense que je prendrais le risque d'enfermer le pc sans connaitre la T° du CPU si je ne suis pas certains de rien risquer.

Je continue mes recherches en attendant.

Dernière modification par wardidi (25-10-2023 20:15:12)

Croutons · 25-10-2023 19:43:35

de toute façon c'est gadget de connaître la température, j'ai déjà eu un ventilateur qui c'est arrêter de tourner ta pas le temps de faire grand chose l'ordi émet des bip interne et coupe vite fait le courant

Debian-facile

#1 18-10-2023 17:09:10

Abscence capteurs de température

#2 18-10-2023 19:38:38

Re : Abscence capteurs de température

#3 19-10-2023 14:38:09

Re : Abscence capteurs de température

#4 19-10-2023 19:17:05

Re : Abscence capteurs de température

#5 25-10-2023 19:35:24

Re : Abscence capteurs de température

#6 25-10-2023 19:43:35

Re : Abscence capteurs de température

Pied de page des forums