[SOLVED] linux kernel update 5.3 hwmon temp_input no such file

Yann · 2019-10-23 10:43:23

Hi everyone,
I have been blocking the linux kernel update for a few weeks now because passing from linux 5.2 to 5.3 (more or less) makes that there is no files /sys/class/hwmon/hwmonX/tempX_input.
However some of my codes are calling these files to get some temperatures, getting some errors such as:

/usr/lib/python3.7/site-packages/psutil/_pslinux.py:1222: RuntimeWarning: ignoring FileNotFoundError(2, 'No such file or directory') for file '/sys/class/hwmon/hwmon1/temp1_input'

What do you think?
Is this well an issue that these files don't exist anymore?
Or should I check my temperature sensors somewhere else?

Thanks for your time.

Last edited by Yann (2019-10-25 14:04:54)

loqs · 2019-10-23 10:48:06

Does /sys/class/hwmon/hwmon1/ exist under 5.3?

schard · 2019-10-23 10:48:20

This may be a regression in the respective driver if you could read the temperature information with an older kernel.
On my system the respective paths are still in place with kernel 5.3.7.
Does lm_sensors still recognize the sensors?

Yann · 2019-10-23 11:12:45

Thanks a lot for the rapid answers.

/sys/class/hwmon/hwmon1/ does exist

/sys/class/hwmon/hwmon1/ $ ls -lart
drwxr-xr-x 3 root root    0 Oct 23  2019 ./
drwxr-xr-x 4 root root    0 Oct 23  2019 ../
lrwxrwxrwx 1 root root    0 Oct 23 12:23 device -> ../../hidpp_battery_0/
-r--r--r-- 1 root root 4.0K Oct 23 12:25 name
drwxr-xr-x 2 root root    0 Oct 23 12:25 power/
lrwxrwxrwx 1 root root    0 Oct 23 12:22 subsystem -> ../../../../../../../../../../../class/hwmon/
-r--r--r-- 1 root root 4.0K Oct 23 12:25 temp1_label
-r--r--r-- 1 root root 4.0K Oct 23 12:25 temp2_label
-rw-r--r-- 1 root root 4.0K Oct 23  2019 uevent

schard wrote:

Does lm_sensors still recognize the sensors?

It is well installed but don't know how to check that.

$ sensors

dell_smm-virtual-0
Adapter: Virtual device
fan1:           0 RPM
fan2:           0 RPM

BAT0-acpi-0
Adapter: ACPI interface
in0:          13.03 V  
curr1:       1000.00 uA 

acpitz-acpi-0
Adapter: ACPI interface
temp1:        +25.0°C  (crit = +107.0°C)

ath10k_hwmon-pci-3b00
Adapter: PCI adapter
temp1:        +48.0°C  

coretemp-isa-0000
Adapter: ISA adapter
Package id 0:  +52.0°C  (high = +100.0°C, crit = +100.0°C)
Core 0:        +49.0°C  (high = +100.0°C, crit = +100.0°C)
Core 1:        +52.0°C  (high = +100.0°C, crit = +100.0°C)
Core 2:        +48.0°C  (high = +100.0°C, crit = +100.0°C)
Core 3:        +47.0°C  (high = +100.0°C, crit = +100.0°C)
Core 4:        +48.0°C  (high = +100.0°C, crit = +100.0°C)
Core 5:        +49.0°C  (high = +100.0°C, crit = +100.0°C)

pch_cannonlake-virtual-0
Adapter: Virtual device
temp1:        +37.0°C

Last edited by Yann (2019-10-23 11:15:06)

merlock · 2019-10-23 12:44:55

You can try running:

sudo sensors-detect

with the 5.3 kernel.

Also, what is the output of

cat /sys/class/hwmon/hwmon1/temp1_label

and

cat /sys/class/hwmon/hwmon1/temp2_label

As it is on your system above?

Last edited by merlock (2019-10-23 12:46:23)

Yann · 2019-10-23 13:20:34

$ sudo sensors-detect

# sensors-detect version 3.6.0
# System: Dell Inc. XPS 15 9570 (laptop)
# Board: Dell Inc. 0D0T05
# Kernel: 5.3.7-arch1-1-ARCH x86_64
# Processor: Intel(R) Core(TM) i7-8750H CPU @ 2.20GHz (6/158/10)

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...                           No
AMD Family 15h power sensors...                             No
AMD Family 16h power sensors...                             No
Hygon Family 18h thermal sensors...                         No
Intel digital thermal sensor...                             Success!
    (driver `coretemp')
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'...                                     Yes
Found unknown chip with ID 0x3082
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 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): 
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.4: Cannon Lake-H (PCH)

Next adapter: SMBus I801 adapter at efa0 (i2c-0)
Do you want to scan it? (YES/no/selectively): 
Client found at address 0x29
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 `Winbond W83781D'...                            No
Probing for `Winbond W83782D'...                            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 `Analog Devices ADM1021'...                     No
Probing for `Analog Devices ADM1021A/ADM1023'...            No
Probing for `Maxim MAX1617'...                              No
Probing for `Maxim MAX1617A'...                             No
Probing for `Maxim MAX1668'...                              No
Probing for `Maxim MAX1805'...                              No
Probing for `Maxim MAX1989'...                              No
Probing for `Maxim MAX6655/MAX6656'...                      No
Probing for `TI THMC10'...                                  No
Probing for `National Semiconductor LM84'...                No
Probing for `Genesys Logic GL523SM'...                      No
Probing for `Onsemi MC1066'...                              No
Probing for `Maxim MAX1618'...                              No
Probing for `Maxim MAX1619'...                              No
Probing for `National Semiconductor LM82/LM83'...           No
Probing for `Maxim MAX6654'...                              No
Probing for `Maxim MAX6690'...                              No
Probing for `Maxim MAX6680/MAX6681'...                      No
Probing for `Maxim MAX6695/MAX6696'...                      No
Probing for `Texas Instruments TMP400'...                   No
Probing for `National Semiconductor LM95235'...             No
Probing for `National Semiconductor LM95245'...             No
Probing for `Analog Devices ADM1029'...                     No
Probing for `ITE IT8712F'...                                No
Probing for `SMSC EMC1402'...                               No
Probing for `SMSC EMC1403'...                               No
Probing for `SMSC EMC1404'...                               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 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)

Next adapter: i915 gmbus dpb (i2c-1)
Do you want to scan it? (yes/NO/selectively): 

Next adapter: i915 gmbus dpc (i2c-2)
Do you want to scan it? (yes/NO/selectively): 

Next adapter: i915 gmbus misc (i2c-3)
Do you want to scan it? (yes/NO/selectively): 

Next adapter: i915 gmbus dpd (i2c-4)
Do you want to scan it? (yes/NO/selectively): 

Next adapter: DPDDC-A (i2c-5)
Do you want to scan it? (yes/NO/selectively): 

Next adapter: DPDDC-B (i2c-6)
Do you want to scan it? (yes/NO/selectively): 

Next adapter: DPDDC-C (i2c-7)
Do you want to scan it? (yes/NO/selectively): 

Next adapter: DPDDC-D (i2c-8)
Do you want to scan it? (yes/NO/selectively): 

Next adapter: Synopsys DesignWare I2C adapter (i2c-9)
Do you want to scan it? (YES/no/selectively): 
Adapter doesn't support all probing functions.
Some addresses won't be probed.

Next adapter: Synopsys DesignWare I2C adapter (i2c-10)
Do you want to scan it? (YES/no/selectively): 
Adapter doesn't support all probing functions.
Some addresses won't be probed.
Client at address 0x2c can not be probed - unload all client drivers first!


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

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

Do you want to overwrite /etc/conf.d/lm_sensors? (YES/no): 
Unloading cpuid... OK

$ cat /sys/class/hwmon/hwmon1/temp1_label
temp ambient

$ cat /sys/class/hwmon/hwmon1/temp2_label
temp

merlock · 2019-10-23 13:48:35

Yann wrote:

$ sudo sensors-detect

Trying family `SMSC'...                                     Yes
Found unknown chip with ID 0x3082

You'll have to research what your mobo uses for it's Super I/O, then possibly look at the kernel docs to see if another SMSC sensor driver will work. Note, it took me a bit of digging to find out what my ASUS mobo uses, and what kernel driver to load.

You can also run

lsmod | grep -i smsc

to see if any of the SMSC drivers are loaded.

Yann wrote:

$ cat /sys/class/hwmon/hwmon1/temp1_label
temp ambient

$ cat /sys/class/hwmon/hwmon1/temp2_label
temp

Only having labels is probably one result of not recognizing your sensor.

Yann · 2019-10-23 13:58:13

Thanks for the answer.

lsmod | grep -i smsc

returns nothing.

I have found others ways to get temperatures such as the PySensors library (python).

I think what you suggest is the good way to do it, but it might take me a few time too and this is not my priority right now. I am probably going to content myself with another way to get my temperature.

Not having /sys/class/hwmon/hwmonX/tempX_input files anymore is not issue?

Last edited by Yann (2019-10-23 13:58:35)

merlock · 2019-10-23 16:11:29

Yann wrote:

Not having /sys/class/hwmon/hwmonX/tempX_input files anymore is not issue?

Well, it's not an issue if you don't have drivers. You'll still have inputs for the coretemp driver. On my system:

 ls -la /sys/class/hwmon
total 0
drwxr-xr-x  2 root root 0 Oct 23 11:50 .
drwxr-xr-x 58 root root 0 Oct 23 11:50 ..
lrwxrwxrwx  1 root root 0 Oct 23 11:50 hwmon0 -> ../../devices/virtual/thermal/thermal_zone0/hwmon0
lrwxrwxrwx  1 root root 0 Oct 23 11:50 hwmon1 -> ../../devices/platform/coretemp.0/hwmon/hwmon1
lrwxrwxrwx  1 root root 0 Oct 23 11:50 hwmon2 -> ../../devices/pci0000:00/0000:00:01.0/0000:01:00.0/hwmon/hwmon2
lrwxrwxrwx  1 root root 0 Oct 23 11:50 hwmon3 -> ../../devices/platform/nct6775.656/hwmon/hwmon3

hwmon0 is a virtual device...meaningless in my case.

hwmon1 is coretemp. Has tempX_input(s)

hwmon2 is my AMD GPU. Also has tempX_inputs.

hwmon3 is my mobo Super I/O. Whole bunch of temp inputs.

As an aside:

Yann wrote:

Do you want to overwrite /etc/conf.d/lm_sensors? (YES/no):

You did answer 'yes', right? So you'd at least have your coretemp sensor working.

Yann · 2019-10-25 14:04:30

Thanks for the reply,
I have the impression that the hwmonX change at every new boot (it's the case on my system). I did press Enter every time, I think it was interpreted as Yes for the program.
I solved my problem by using another way to get these infos.

I am going to edit it as SOLVED.

Thanks for your time.

Arch Linux

#1 2019-10-23 10:43:23

[SOLVED] linux kernel update 5.3 hwmon temp_input no such file

#2 2019-10-23 10:48:06

Re: [SOLVED] linux kernel update 5.3 hwmon temp_input no such file

#3 2019-10-23 10:48:20

Re: [SOLVED] linux kernel update 5.3 hwmon temp_input no such file

#4 2019-10-23 11:12:45

Re: [SOLVED] linux kernel update 5.3 hwmon temp_input no such file

#5 2019-10-23 12:44:55

Re: [SOLVED] linux kernel update 5.3 hwmon temp_input no such file

#6 2019-10-23 13:20:34

Re: [SOLVED] linux kernel update 5.3 hwmon temp_input no such file

#7 2019-10-23 13:48:35

Re: [SOLVED] linux kernel update 5.3 hwmon temp_input no such file

#8 2019-10-23 13:58:13

Re: [SOLVED] linux kernel update 5.3 hwmon temp_input no such file

#9 2019-10-23 16:11:29

Re: [SOLVED] linux kernel update 5.3 hwmon temp_input no such file

#10 2019-10-25 14:04:30

Re: [SOLVED] linux kernel update 5.3 hwmon temp_input no such file

Board footer