LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Software (https://www.linuxquestions.org/questions/linux-software-2/)
-   -   lm-sensors does not detect intel gpu (https://www.linuxquestions.org/questions/linux-software-2/lm-sensors-does-not-detect-intel-gpu-4175585339/)

naikin 07-23-2016 06:57 AM

lm-sensors does not detect intel gpu
 
I want to monitor the temperature and fan speed of my intel gpu. However, sensors does not seem to detect it:

Quote:

niko@dell-xps15: ~ $ sudo sensors-detect
Password:
# sensors-detect revision 6284 (2015-05-31 14:00:33 +0200)
# System: Dell Inc. XPS 15 9550 (laptop)
# Board: Dell Inc. 0N7TVV
# Kernel: 4.4.14 x86_64
# Processor: Intel(R) Core(TM) i7-6700HQ CPU @ 2.60GHz (6/94/3)

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 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 15h power sensors... No
AMD Family 16h power 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 0x1d00
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):
Found unknown SMBus adapter 8086:a123 at 0000:00:1f.4.
Sorry, no supported PCI bus adapters found.

Next adapter: Synopsys DesignWare I2C adapter (i2c-0)
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-1)
Do you want to scan it? (YES/no/selectively):
Adapter doesn't support all probing functions.
Some addresses won't be probed.

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

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

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

Next adapter: DPDDC-A (i2c-5)
Do you want to scan it? (yes/NO/selectively): yes
Client found at address 0x5c
Probing for `Analog Devices ADT7462'... No
Probing for `SMSC EMC1072'... No
Probing for `SMSC EMC1073'... No
Probing for `SMSC EMC1074'... No

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

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


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/sysconfig/lm_sensors? (YES/no):
Copy prog/init/lm_sensors.init to /etc/init.d/lm_sensors
for initialization at boot time.
You should now start the lm_sensors service to load the required
kernel modules.

The contents of /etc/sysconfig/lm_sensors:

Quote:

# Generated by sensors-detect on Tue Jul 19 22:27:04 2016
# This file is sourced by /etc/init.d/lm_sensors and defines the modules to
# be loaded/unloaded.
#
# The format of this file is a shell script that simply defines variables:
# HWMON_MODULES for hardware monitoring driver modules, and optionally
# BUS_MODULES for any required bus driver module (for example for I2C or SPI).

HWMON_MODULES="coretemp"
Can this be related to the fact that I also have nvidia gpu and I am using bumblebee to switch between the two GPUs?

The GPUs are Intel(R) HD Graphics 530 and NVIDIA GTX 960M. OS is Slackware 14.2.

Is there a fix or can I monitor the intel gpu sensors using another tool?

ardvark71 07-23-2016 09:18 AM

Quote:

Originally Posted by naikin (Post 5580194)
Is there a fix or can I monitor the intel gpu sensors using another tool?

Hi...

I don't know enough about lm-sensors or Linux to help you dig into this further but you may need additional modules (or libraries) for lm-sensors to display this information. Please see the response from business_kid (post #2) here. However, as to what modules these would be, I have no idea. :(

As examples, please see these threads...

https://ubuntuforums.org/showthread.php?t=2075764

http://askubuntu.com/questions/53646...4-when-using-t

Regards...

273 07-23-2016 11:05 AM

I wasn't aware that it was possible to display the details of the Intel GPU. Thinking about it, I didn't know Intel did discrete GPUs that could be monitored? Surely the GPU is part of the CPU die and the measurements are taken from there? Or am I misunderstanding Intel integrated GPUs?

Emerson 07-23-2016 12:20 PM

Quote:

Originally Posted by 273 (Post 5580254)
I wasn't aware that it was possible to display the details of the Intel GPU. Thinking about it, I didn't know Intel did discrete GPUs that could be monitored? Surely the GPU is part of the CPU die and the measurements are taken from there? Or am I misunderstanding Intel integrated GPUs?

That's what I was thinking ...

naikin 07-23-2016 03:33 PM

Yes, the intel GPU is part of the CPU - it is integrated. Sorry for not being clear before. Nevertheless, should not sensors detect it as a separate component and report some alaytics. Here is my current output:

Quote:

coretemp-isa-0000
Adapter: ISA adapter
Physical id 0: +38.0°C (high = +100.0°C, crit = +100.0°C)
Core 0: +31.0°C (high = +100.0°C, crit = +100.0°C)
Core 1: +33.0°C (high = +100.0°C, crit = +100.0°C)
Core 2: +29.0°C (high = +100.0°C, crit = +100.0°C)
Core 3: +32.0°C (high = +100.0°C, crit = +100.0°C)
There is nothing about the GPU there

273 07-23-2016 03:48 PM

Quote:

Originally Posted by naikin (Post 5580335)
Yes, the intel GPU is part of the CPU - it is integrated. Sorry for not being clear before. Nevertheless, should not sensors detect it as a separate component and report some alaytics.

Does it tell you in the documentation you read that in what the sensor is called?

naikin 07-23-2016 03:54 PM

I did not read any documentation. Just searched the internet and saw that other ppl are able to monitor their intel GPUs using lm-sensors. I think it is supposed to report it as PCI adapter or sth similar.

273 07-23-2016 04:18 PM

Quote:

Originally Posted by naikin (Post 5580346)
I did not read any documentation. Just searched the internet and saw that other ppl are able to monitor their intel GPUs using lm-sensors. I think it is supposed to report it as PCI adapter or sth similar.

I'm not convinced but if that is the case then I think you skipped the scanning of PCI adaptors by pressing enter instead of typing yes (going by what you posted but it's hard to tell).
For the record the machine I'm typing this on has an Intel GPU (only) and I see the following from lm-sensors:
Code:

sensors
 
acpitz-virtual-0
Adapter: Virtual device
temp1:        +63.0°C  (crit = +108.0°C)

coretemp-isa-0000
Adapter: ISA adapter
Physical id 0:  +65.0°C  (high = +87.0°C, crit = +105.0°C)
Core 0:        +65.0°C  (high = +87.0°C, crit = +105.0°C)
Core 1:        +62.0°C  (high = +87.0°C, crit = +105.0°C)

asus-isa-0000
Adapter: ISA adapter
cpu_fan:    3100 RPM
temp1:        +63.0°C

Edit: Sorry, upon further reading I see that you did scan everything. My apologies.

keefaz 07-23-2016 07:34 PM

If GPU is part of CPU, CPU temp = GPU temp, no?

273 07-23-2016 07:38 PM

Quote:

Originally Posted by keefaz (Post 5580410)
If GPU is part of CPU, CPU temp = GPU temp, no?

Without documentation it is hard to tell but, yes, I would expect that to be the case. However, Intel do give a temperature for each core (which if you think about it are fractions of mms apart) so who knows?
My take on it is that somebody saw the "PCI temperature" and thought, for some reason, it was the temperature of the onboard video as they couldn't think what else it could be. I am just guessing though.

keefaz 07-23-2016 08:25 PM

Yes, reading kernel docs for coretemp module (Kernel Source/Documentation/hwmon/coretemp), Intel CPUs have digital temperature sensor per-core with a measurement resolution of 1 degree C.

There is nothing about the GPU part

273 07-23-2016 08:34 PM

Quote:

Originally Posted by keefaz (Post 5580420)
Yes, reading kernel docs for coretemp module (Kernel Source/Documentation/hwmon/coretemp), Intel CPUs have digital temperature sensor per-core with a measurement resolution of 1 degree C.

There is nothing about the GPU part

I find it odd that there could be 1°C between cores which are less than a tenth of a millimetre apart. But, then, what do I know?

keefaz 07-23-2016 09:10 PM

1°C resolution is what the digital temperature sensor (DTS) reports, in real life its accuracy may be much worst than that

About temperature difference between cores, see this paper on page 4 (Die hot spot in dual core workloads)
http://arxiv.org/pdf/0709.1861

naikin 07-25-2016 07:12 AM

So does that mean that intel integrated GPU temperature would not be available?

273 07-25-2016 07:39 AM

Quote:

Originally Posted by naikin (Post 5580958)
So does that mean that intel integrated GPU temperature would not be available?

It seems that way. I couldn't find anything about reading GPU temperature when I googled it.

seasons 07-27-2016 05:43 AM

Quote:

Originally Posted by 273 (Post 5580411)
My take on it is that somebody saw the "PCI temperature" and thought, for some reason, it was the temperature of the onboard video as they couldn't think what else it could be. I am just guessing though.

That would be my guess too. I think OP really needs to give links..

Quote:

Originally Posted by naikin
Just searched the internet and saw that other ppl are able to monitor their intel GPUs using lm-sensors.

Depending on how old the systems in use are, that may make sense as the GPU used to be built into the system chipset (or northbridge on even older systems) rather than the CPU. Again, please give specific links if you really think they are seeing a temp from a GPU integrated into the CPU

Quote:

Originally Posted by 273
Edit: Sorry, upon further reading I see that you did scan everything.

Yes, the OP scanned the PCI bus, but because this is a Skylake (Sunrise Point chipset) system, sensors-detect isn't quite up-to-date enough to handle it completely:
Code:

Found unknown SMBus adapter 8086:a123 at 0000:00:1f.4.
Adding this block of code to the PCI definitions section of /usr/sbin/sensors-detect would probably allow it to scan the bus (though I have no idea whether that would result in additional output from sensors command).
** USE AT OWN RISK **
Code:

}, {
                vendid  => 0x8086,
                devid  => 0xA123,
                procid  => "Intel Sunrise Point (PCH)",
                driver  => "i2c-i801",

sensors-detect also gave this error, but googling didn't give me any clues as to what kind of sensor it is:
Code:

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



All times are GMT -5. The time now is 03:48 AM.