Fedora-Fr - Communauté francophone Fedora - Linux

Communauté francophone des utilisateurs de la distribution Linux Fedora.

  

Dernière news : Fedora Linux 37 est disponible !

#1 20/06/2009 08:14:02

pmarion
Pacsé avec le forum
Lieu : 95000 CERGY
Inscription : 14/11/2006
Messages : 8 032

Fonctionnalités de lm_sensors entre F10 et F11

En F10 32b la commande «sensors» m'affiche

w83627ehf-isa-0a10
Adapter: ISA adapter
VCore:       +1.37 V  (min =  +0.00 V, max =  +1.74 V)   
in1:        +10.61 V  (min =  +9.93 V, max =  +6.65 V)   ALARM
AVCC:        +3.30 V  (min =  +1.49 V, max =  +3.94 V)   
3VCC:        +3.31 V  (min =  +1.23 V, max =  +0.93 V)   ALARM
in4:         +0.14 V  (min =  +2.04 V, max =  +1.12 V)   ALARM
in5:         +0.14 V  (min =  +1.26 V, max =  +0.23 V)   ALARM
in6:         +0.46 V  (min =  +3.25 V, max =  +3.76 V)   ALARM
VSB:         +3.30 V  (min =  +3.20 V, max =  +0.50 V)   ALARM
VBAT:        +3.20 V  (min =  +2.21 V, max =  +0.34 V)   ALARM
in9:         +0.14 V  (min =  +2.01 V, max =  +1.85 V)   ALARM
Case Fan:   1074 RPM  (min = 2721 RPM, div = 8)  ALARM
CPU Fan:    2096 RPM  (min =    0 RPM, div = 4)
Aux Fan:       0 RPM  (min = 5273 RPM, div = 128)  ALARM
fan5:          0 RPM  (min = 10546 RPM, div = 128)  ALARM
Sys Temp:    +23.0°C  (high =  +0.0°C, hyst = +127.0°C)  sensor = thermistor
CPU Temp:    +34.0°C  (high = +44.0°C, hyst =  +0.0°C)  ALARM  sensor = diode
AUX Temp:    +45.5°C  (high = +127.0°C, hyst =  +0.0°C)  sensor = thermistor
cpu0_vid:   +1.219 V

coretemp-isa-0000
Adapter: ISA adapter
Core 0:      +54.0°C  (high = +84.0°C, crit = +100.0°C)

En F11 64b la même commande me donne

coretemp-isa-0000
Adapter: ISA adapter
Core 0:      +50.0°C  (high = +84.0°C, crit = +100.0°C)

D'autre part, gkrellm ne me propose plus l'affichage des ventilateurs, la température dans le boitier, ......

Différences entre le fichier lm_sensors de mon F10 et de mon F11
diff /mnt/tmp/etc/sysconfig/lm_sensors /etc/sysconfig/lm_sensors | grep -v '#'

1,28c1,11
---
> 
> HWMON_MODULES="coretemp w83627ehf"
> 
30,35c13,16
< MODULE_0=w83627ehf
< MODULE_1=coretemp
---
> 
> MODULE_0=coretemp
> MODULE_1=w83627ehf

Dernière modification par pmarion (20/06/2009 08:15:46)

Hors ligne

#2 20/06/2009 08:49:54

VINDICATORs
RédactWikix and the graphicatorix!
Modérateur
Lieu : Toulouse(31) France
Inscription : 23/11/2004
Messages : 18 984
Site Web

Re : Fonctionnalités de lm_sensors entre F10 et F11

En root fait un "sensor-detect" et relance le service "lm_sensor".


AMD R7 5800x X470 64Go DDR4 3.6Ghz, RX5700XT+AMD R7 2700x A320 + 32Go DDR4 3.2Ghz, rx6500xt 4Go
AMD R5 2600 A320, 32Go DDR4 2.9Ghz,1030GT 2Go + AMD A6 9500 A320, 16Go DDR4 2.1Ghz
ARM Rpi4 4Go, à venir Pine64 2xQuartzB 2/4Go

Hors ligne

#3 20/06/2009 08:56:13

pmarion
Pacsé avec le forum
Lieu : 95000 CERGY
Inscription : 14/11/2006
Messages : 8 032

Re : Fonctionnalités de lm_sensors entre F10 et F11

En root fait un "sensor-detect" et relance le service "lm_sensor".

Merci, mais cela fait déjà deux fois que je lance sensors-detect (je pense que c'est de celui là dont tu parles).  Comme c'est un script perl je l'ai exécuté une fois en mode debug pour voir.

Dernière modification par pmarion (20/06/2009 08:57:08)

Hors ligne

#4 20/06/2009 10:01:08

pmarion
Pacsé avec le forum
Lieu : 95000 CERGY
Inscription : 14/11/2006
Messages : 8 032

Re : Fonctionnalités de lm_sensors entre F10 et F11

Voici la trace du dernier sensors-detect

[root@patmar ~]# sensors-detect
Stopping lm_sensors:                                       [  OK  ]
# sensors-detect revision 5666 (2009-02-26 17:15:04 +0100)
# System: MICRO-STAR INTERNATIONAL CO., LTD MS-7235

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):    
Silicon Integrated Systems SIS5595...                       No
VIA VT82C686 Integrated Sensors...                          No
VIA VT8231 Integrated Sensors...                            No
AMD K8 thermal sensors...                                   No
AMD K10 thermal sensors...                                  No
Intel Core family thermal sensor...                         Success!
    (driver `coretemp')
Intel AMB FB-DIMM thermal sensor...                         No
VIA C7 thermal and voltage sensors...                       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'...                   No
Trying family `SMSC'...                                     No
Trying family `VIA/Winbond/Fintek'...                       Yes
Found `Winbond W83627EHF/EF/EHG/EG Super IO Sensors'        Success!
    (address 0xa10, driver `w83627ehf')
Probing for Super-I/O at 0x4e/0x4f
Trying family `National Semiconductor'...                   No
Trying family `SMSC'...                                     No
Trying family `VIA/Winbond/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 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-i801' for device 0000:00:1f.3: Intel 82801H ICH8
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 `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 `Winbond W83627HF'...                           No
Probing for `Winbond W83627EHF'...                          No
Probing for `Winbond W83627DHG'...                          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 `Analog Devices ADM1029'...                     No
Probing for `ITE IT8712F'...                                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)

Next adapter: NVIDIA i2c adapter  (i2c-1)
Do you want to scan it? (YES/no/selectively): 
Client found at address 0x50
Probing for `Analog Devices ADM1033'...                     No
Probing for `Analog Devices ADM1034'...                     No
Probing for `SPD EEPROM'...                                 No
Probing for `EDID EEPROM'...                                Yes
    (confidence 8, not a hardware monitoring chip)

Next adapter: NVIDIA i2c adapter  (i2c-2)
Do you want to scan it? (YES/no/selectively): 

Next adapter: NVIDIA i2c adapter  (i2c-3)
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 `w83627ehf':
  * ISA bus, address 0xa10
    Chip `Winbond W83627EHF/EF/EHG/EG Super IO Sensors' (confidence: 9)

Driver `coretemp':
  * Chip `Intel Core family thermal sensor' (confidence: 9)

Do you want to overwrite /etc/sysconfig/lm_sensors? (YES/no): 
Starting lm_sensors: loading module coretemp w83627ehf     [  OK  ]
Unloading i2c-dev... OK

Dernière modification par pmarion (20/06/2009 10:04:49)

Hors ligne

#5 20/06/2009 10:03:35

VINDICATORs
RédactWikix and the graphicatorix!
Modérateur
Lieu : Toulouse(31) France
Inscription : 23/11/2004
Messages : 18 984
Site Web

Re : Fonctionnalités de lm_sensors entre F10 et F11

Ta relancé le service lm_sensor? voir l'ordinateur?

Sinon c'est peut être un bogue...

Edit Ok... c'est le bordel... sur F11 il ne me détecte plus rien...

Dernière modification par VINDICATORs (20/06/2009 10:06:52)


AMD R7 5800x X470 64Go DDR4 3.6Ghz, RX5700XT+AMD R7 2700x A320 + 32Go DDR4 3.2Ghz, rx6500xt 4Go
AMD R5 2600 A320, 32Go DDR4 2.9Ghz,1030GT 2Go + AMD A6 9500 A320, 16Go DDR4 2.1Ghz
ARM Rpi4 4Go, à venir Pine64 2xQuartzB 2/4Go

Hors ligne

#6 20/06/2009 10:07:07

pmarion
Pacsé avec le forum
Lieu : 95000 CERGY
Inscription : 14/11/2006
Messages : 8 032

Re : Fonctionnalités de lm_sensors entre F10 et F11

Ta relancé le service lm_sensor? voir l'ordinateur?

Je pense que sensors-detect fait un arrêt du service en début de script et un démarrage en fin de script.
J'ai aussi fait un reboot sur disque dur car, entretemps,  j'ai essayé sensors-detect/sensors sur un LiveCD 32b  pour voir.

Hors ligne

#7 20/06/2009 10:21:52

Did
Membre
Lieu : nul part
Inscription : 11/01/2005
Messages : 2 465

Re : Fonctionnalités de lm_sensors entre F10 et F11

Salut,

Idem pour moi, il manque quelques détecteurs depuis le passage vers F11...
(sensors-detect et lm_sensors relancé)

Hors ligne

Pied de page des forums