Web lists-archives.com

Re: lm-sensors doesn't see the cpu rpm.....




Dear All,

The output of lsmod looks like this:

root@bong:/boot# lsmod

Module                  Size  Used by
uinput                 20480  1
snd_hda_codec_hdmi     49152  4
edac_mce_amd           28672  0
edac_core              57344  0
kvm_amd              2179072  0
kvm                   589824  1 kvm_amd
snd_hda_codec_realtek    90112  1
eeepc_wmi              16384  0
asus_wmi               28672  1 eeepc_wmi
sparse_keymap          16384  1 asus_wmi
serio_raw              16384  0
snd_hda_codec_generic    69632  1 snd_hda_codec_realtek
snd_hda_intel          36864  6
snd_hda_codec         135168  4 snd_hda_intel,snd_hda_codec_hdmi,snd_hda_codec_generic,snd_hda_codec_realtek
snd_hda_core           81920  5 snd_hda_intel,snd_hda_codec,snd_hda_codec_hdmi,snd_hda_codec_generic,snd_hda_codec_realtek
rfkill                 24576  4 asus_wmi
irqbypass              16384  1 kvm
crct10dif_pclmul       16384  0
fam15h_power           16384  0
k10temp                16384  0
pcspkr                 16384  0
crc32_pclmul           16384  0
snd_hwdep              16384  1 snd_hda_codec
snd_pcm               110592  5 snd_hda_intel,snd_hda_codec,snd_hda_core,snd_hda_codec_hdmi
ghash_clmulni_intel    16384  0
evdev                  24576  9
snd_timer              32768  1 snd_pcm
snd                    86016  19 snd_hda_intel,snd_hwdep,snd_hda_codec,snd_timer,snd_hda_codec_hdmi,snd_hda_codec_generic,snd_hda_codec_realtek,snd_pcm
shpchp                 36864  0
sg                     32768  0
soundcore              16384  1 snd
tpm_infineon           20480  0
sp5100_tco             16384  0
fuse                   98304  1
it87                   57344  0
hwmon_vid              16384  1 it87
parport_pc             28672  0
ppdev                  20480  0
lp                     20480  0
sunrpc                344064  1
parport                49152  3 lp,parport_pc,ppdev
ip_tables              24576  0
x_tables               36864  1 ip_tables
autofs4                40960  2
ext4                  585728  1
crc16                  16384  1 ext4
jbd2                  106496  1 ext4
crc32c_generic         16384  0
fscrypto               28672  1 ext4
ecb                    16384  0
mbcache                16384  2 ext4
hid_generic            16384  0
usbhid                 53248  0
hid                   122880  2 hid_generic,usbhid
sd_mod                 45056  3
ohci_pci               16384  0
crc32c_intel           24576  0
aesni_intel           167936  1
aes_x86_64             20480  1 aesni_intel
glue_helper            16384  1 aesni_intel
lrw                    16384  1 aesni_intel
gf128mul               16384  1 lrw
ablk_helper            16384  1 aesni_intel
cryptd                 24576  3 ablk_helper,ghash_clmulni_intel,aesni_intel
nouveau              1544192  9
mxm_wmi                16384  1 nouveau
i2c_piix4              24576  0
video                  40960  2 asus_wmi,nouveau
i2c_algo_bit           16384  1 nouveau
r8169                  81920  0
ttm                    98304  1 nouveau
ahci                   36864  2
mii                    16384  1 r8169
xhci_pci               16384  0
libahci                32768  1 ahci
drm_kms_helper        155648  1 nouveau
ehci_pci               16384  0
ohci_hcd               53248  1 ohci_pci
xhci_hcd              188416  1 xhci_pci
ehci_hcd               81920  1 ehci_pci
libata                249856  2 ahci,libahci
drm                   360448  12 nouveau,ttm,drm_kms_helper
usbcore               249856  7 usbhid,ehci_hcd,ohci_pci,xhci_pci,ohci_hcd,xhci_hcd,ehci_pci
usb_common             16384  1 usbcore
scsi_mod              225280  3 sd_mod,libata,sg
wmi                    16384  3 asus_wmi,mxm_wmi,nouveau
button                 16384  1 nouveau
root@bong:/boot#

I tried running


root@bong:/boot#  sudo modprobe coretemp
modprobe: ERROR: could not insert 'coretemp': No such device


This is odd because coretemp is set as a module option in the config file:

CONFIG_SENSORS_CORETEMP=m

Comments appreciared

Regards

MF







On 28 December 2017 at 12:52, Michael Fothergill <michael.fothergill@xxxxxxxxx> wrote:
Dear All,

I looked at the config-4.9.0-4-amd64 file for the current kernel:

# Native drivers
#
CONFIG_SENSORS_ABITUGURU=m
CONFIG_SENSORS_ABITUGURU3=m
# CONFIG_SENSORS_AD7314 is not set
CONFIG_SENSORS_AD7414=m
CONFIG_SENSORS_AD7418=m
CONFIG_SENSORS_ADM1021=m
CONFIG_SENSORS_ADM1025=m
CONFIG_SENSORS_ADM1026=m
CONFIG_SENSORS_ADM1029=m
CONFIG_SENSORS_ADM1031=m
CONFIG_SENSORS_ADM9240=m
# CONFIG_SENSORS_ADT7310 is not set
# CONFIG_SENSORS_ADT7410 is not set
CONFIG_SENSORS_ADT7411=m
CONFIG_SENSORS_ADT7462=m
CONFIG_SENSORS_ADT7470=m
CONFIG_SENSORS_ADT7475=m
CONFIG_SENSORS_ASC7621=m
CONFIG_SENSORS_K8TEMP=m
CONFIG_SENSORS_K10TEMP=m
CONFIG_SENSORS_FAM15H_POWER=m
CONFIG_SENSORS_APPLESMC=m
CONFIG_SENSORS_ASB100=m
CONFIG_SENSORS_ATXP1=m
CONFIG_SENSORS_DS620=m
CONFIG_SENSORS_DS1621=m
CONFIG_SENSORS_DELL_SMM=m
CONFIG_SENSORS_I5K_AMB=m
CONFIG_SENSORS_F71805F=m
CONFIG_SENSORS_F71882FG=m
CONFIG_SENSORS_F75375S=m
CONFIG_SENSORS_FSCHMD=m
CONFIG_SENSORS_FTSTEUTATES=m
CONFIG_SENSORS_GL518SM=m
CONFIG_SENSORS_GL520SM=m
CONFIG_SENSORS_G760A=m
# CONFIG_SENSORS_G762 is not set
# CONFIG_SENSORS_GPIO_FAN is not set
# CONFIG_SENSORS_HIH6130 is not set
CONFIG_SENSORS_IBMAEM=m
CONFIG_SENSORS_IBMPEX=m
# CONFIG_SENSORS_IIO_HWMON is not set
CONFIG_SENSORS_I5500=m
CONFIG_SENSORS_CORETEMP=m
CONFIG_SENSORS_IT87=m
CONFIG_SENSORS_JC42=m
# CONFIG_SENSORS_POWR1220 is not set
CONFIG_SENSORS_LINEAGE=m
# CONFIG_SENSORS_LTC2945 is not set
# CONFIG_SENSORS_LTC2990 is not set
CONFIG_SENSORS_LTC4151=m
CONFIG_SENSORS_LTC4215=m
# CONFIG_SENSORS_LTC4222 is not set
CONFIG_SENSORS_LTC4245=m
# CONFIG_SENSORS_LTC4260 is not set
CONFIG_SENSORS_LTC4261=m
CONFIG_SENSORS_MAX1111=m
CONFIG_SENSORS_MAX16065=m
CONFIG_SENSORS_MAX1619=m
CONFIG_SENSORS_MAX1668=m
# CONFIG_SENSORS_MAX197 is not set
# CONFIG_SENSORS_MAX31722 is not set
CONFIG_SENSORS_MAX6639=m
CONFIG_SENSORS_MAX6642=m
CONFIG_SENSORS_MAX6650=m
# CONFIG_SENSORS_MAX6697 is not set
# CONFIG_SENSORS_MAX31790 is not set
# CONFIG_SENSORS_MCP3021 is not set
CONFIG_SENSORS_MENF21BMC_HWMON=m
CONFIG_SENSORS_ADCXX=m
CONFIG_SENSORS_LM63=m
CONFIG_SENSORS_LM70=m
CONFIG_SENSORS_LM73=m
CONFIG_SENSORS_LM75=m
CONFIG_SENSORS_LM77=m
CONFIG_SENSORS_LM78=m
CONFIG_SENSORS_LM80=m
CONFIG_SENSORS_LM83=m
CONFIG_SENSORS_LM85=m
CONFIG_SENSORS_LM87=m
CONFIG_SENSORS_LM90=m
CONFIG_SENSORS_LM92=m
CONFIG_SENSORS_LM93=m
# CONFIG_SENSORS_LM95234 is not set
CONFIG_SENSORS_LM95241=m
CONFIG_SENSORS_LM95245=m
CONFIG_SENSORS_PC87360=m
CONFIG_SENSORS_PC87427=m
CONFIG_SENSORS_NTC_THERMISTOR=m
CONFIG_SENSORS_NCT6683=m
CONFIG_SENSORS_NCT6775=m
# CONFIG_SENSORS_NCT7802 is not set
# CONFIG_SENSORS_NCT7904 is not set
CONFIG_SENSORS_PCF8591=m
# CONFIG_PMBUS is not set
# CONFIG_SENSORS_SHT15 is not set
CONFIG_SENSORS_SHT21=m
# CONFIG_SENSORS_SHT3x is not set
# CONFIG_SENSORS_SHTC1 is not set
CONFIG_SENSORS_SIS5595=m
CONFIG_SENSORS_DME1737=m
CONFIG_SENSORS_EMC1403=m
CONFIG_SENSORS_EMC2103=m
CONFIG_SENSORS_EMC6W201=m
CONFIG_SENSORS_SMSC47M1=m
CONFIG_SENSORS_SMSC47M192=m
CONFIG_SENSORS_SMSC47B397=m
CONFIG_SENSORS_SCH56XX_COMMON=m
CONFIG_SENSORS_SCH5627=m
CONFIG_SENSORS_SCH5636=m
CONFIG_SENSORS_SMM665=m
# CONFIG_SENSORS_ADC128D818 is not set
CONFIG_SENSORS_ADS1015=m
CONFIG_SENSORS_ADS7828=m
CONFIG_SENSORS_ADS7871=m
CONFIG_SENSORS_AMC6821=m
# CONFIG_SENSORS_INA209 is not set
# CONFIG_SENSORS_INA2XX is not set
# CONFIG_SENSORS_INA3221 is not set
# CONFIG_SENSORS_TC74 is not set
CONFIG_SENSORS_THMC50=m
CONFIG_SENSORS_TMP102=m
# CONFIG_SENSORS_TMP103 is not set
CONFIG_SENSORS_TMP401=m
CONFIG_SENSORS_TMP421=m
CONFIG_SENSORS_VIA_CPUTEMP=m
CONFIG_SENSORS_VIA686A=m
CONFIG_SENSORS_VT1211=m
CONFIG_SENSORS_VT8231=m
CONFIG_SENSORS_W83781D=m
CONFIG_SENSORS_W83791D=m
CONFIG_SENSORS_W83792D=m
CONFIG_SENSORS_W83793=m
CONFIG_SENSORS_W83795=m
# CONFIG_SENSORS_W83795_FANCTRL is not set
CONFIG_SENSORS_W83L785TS=m
CONFIG_SENSORS_W83L786NG=m
CONFIG_SENSORS_W83627HF=m
CONFIG_SENSORS_W83627EHF=m

It seems that the kernel is configured with the module m setting consistently not the internal y setting so debian does not use the built in option by default here it would seem

so modifying the /etc/modules file works here.

I notice that
# CONFIG_SENSORS_W83795_FANCTRL is not set
has been commented out

and

# CONFIG_SENSORS_GPIO_FAN is not set

is in a similar state

I will continue looking at this in more detail.

Regards

MF











On 28 December 2017 at 12:14, Michael Fothergill <michael.fothergill@xxxxxxxxx> wrote:
I have 3 case fans in the box here but lm-sensors only sees two of them apparently as well as not seeing the cpu fan.

Funny stuff.

Regards

MF

On 28 December 2017 at 11:50, Michael Fothergill <michael.fothergill@xxxxxxxxx> wrote:
Dear Folks,

I am running stretch on an AMD FX8350 box which uses an Arctic Freezer 13 cooler.

I installed lm-sensors and ran the /etc module update command.

The output looks like this:

root@bong:/home/mikef# sensors
asus-isa-0000
Adapter: ISA adapter
cpu_fan:        0 RPM

k10temp-pci-00c3
Adapter: PCI adapter
temp1:        +21.9°C  (high = +70.0°C)
                       (crit = +90.0°C, hyst = +87.0°C)

nouveau-pci-0700
Adapter: PCI adapter
GPU core:     +0.90 V  (min =  +0.88 V, max =  +1.08 V)
temp1:        +35.0°C  (high = +95.0°C, hyst =  +3.0°C)
                       (crit = +105.0°C, hyst =  +5.0°C)
                       (emerg = +135.0°C, hyst =  +5.0°C)

fam15h_power-pci-00c4
Adapter: PCI adapter
power1:        6.75 W  (crit = 125.19 W)
                                                                                                                        
it8721-isa-0290                                                                                                         
Adapter: ISA adapter                                                                                                    
in0:          +2.83 V  (min =  +2.02 V, max =  +2.95 V)                                                                 
in1:          +2.83 V  (min =  +1.68 V, max =  +1.73 V)  ALARM                                                          
in2:          +0.98 V  (min =  +2.40 V, max =  +1.08 V)  ALARM                                                          
+3.3V:        +3.31 V  (min =  +0.38 V, max =  +0.96 V)  ALARM                                                          
in4:          +0.25 V  (min =  +0.41 V, max =  +0.20 V)  ALARM
in5:          +2.51 V  (min =  +0.12 V, max =  +0.00 V)  ALARM
in6:          +1.98 V  (min =  +1.54 V, max =  +0.59 V)  ALARM
3VSB:         +3.94 V  (min =  +3.31 V, max =  +0.89 V)  ALARM
Vbat:         +3.29 V 
fan1:        1814 RPM  (min =   87 RPM)
fan2:           0 RPM  (min =   46 RPM)  ALARM
fan3:        1125 RPM  (min =   29 RPM)
temp1:        +37.0°C  (low  = +34.0°C, high = +91.0°C)  sensor = thermistor
temp2:        +30.0°C  (low  = +45.0°C, high =  +9.0°C)  ALARM  sensor = thermistor
temp3:       -128.0°C  (low  = -60.0°C, high =  +4.0°C)  sensor = disabled
intrusion0:  OK

root@bong:/home/mikef#

The cpu fan is running at around 2500 rpm.

If the connector were 3 pin rather than 4 pin could that explain the zero here?

Suggestions on a tweak that could awaken the sensor or stimulate lm-sensors truffle hound hunting skills here would be appreciated.

Googling around gives quite complex suggestions.

Is there something simple I could try here?

Regards

Michael Fothergill