HWSensors3

[vector sigma]

9 hours ago, jinbingmao said:

Existence before sleep, loss after awakening.

Try this: ITEIT87x.kext.zip and let me know.

[jinbingmao]

2小时前，矢量西格玛说：

试试这个：  ITEIT87x.kext.zip  并告诉我。

Should be my own problem, I upgraded the development version, now normal.

Edited June 17, 2019 by jinbingmao

[vector sigma]

On 6/17/2019 at 9:53 PM, jinbingmao said:

Should be my own problem, I upgraded the development version, now normal.

Is it ok also with the standard version at sourceforge?

[vector sigma]

On 6/17/2019 at 11:04 AM, Slice said:

Suppose you have this controller with an input pin where you expected to see an ambient temperature value.

To do this you have to be sure there is an thermodiod which actually measures the temperature of environment and is connected to this input pin. I am not sure if the thermodiod exists.

Can be any, I cannot not be sure is it the "Ambient" sensor, but I guess @jinbingmao already ensure this...  anyway for sure some thing is connected at ITE_TEMPERATURE_BASE_REG + index 2.

[MacKonsti]

Hi everyone, thanks to you also @Slice for your work all this time, I am considering using HWSensors3 on my new hack and wanted your kind support for adding my chipset so I can monitor fans.

 

Computer = Intel NUC8i7BEH2
Chipset Model = ITE IT8987E-VG. (per Linux device information tools)
Chipset ID = 0x8987
SMBIOS Used = Macmini8,1

 

I can imagine that recent Clover should be used and that the SMC keys used are the usual ones. But please if you need further info or dump or anything, let me know, my old hacks worked out of the box, it's the first time I am requesting assistance on such thing.

 

Anyone already using this NUC? Many thanks.

Edited June 19, 2019 by MacKonsti

[Slice]

Quote

Chipset Model = ITE IT8987E-VG. (per Linux device information tools)
Chipset ID = 0x8987

I can add this ID to ITE plugin consuming it works same as other ITE chip. But for sure I need a datasheet for this chip.

[jinbingmao]

16小时前，矢量西格玛说：

可以是任何，我不能肯定它是“环境”传感器，但我想@jinbingmao  已经确保了这一点......无论如何 肯定有一些东西在ITE_TEMPERATURE_BASE_REG +索引2连接。

Platform Controller Hub( South Bridge)

Edited June 20, 2019 by jinbingmao

[jinbingmao]

[MacKonsti]

10 hours ago, Slice said:

I can add this ID to ITE plugin consuming it works same as other ITE chip. But for sure I need a datasheet for this chip.

 

Hi @Slice and thank you for responding. I found these:

 

ITE Official Product Description = http://www.ite.com.tw/en/product/view?mid=121

 

Quote

IT8987 is a highly integrated embedded controller with system functions suitable for mobile system applications. The IT8987 directly interfaces to the LPC bus and provides ACPI embedded controller function, keyboard controller (KBC) and matrix scan, PWM and ADC for hardware monitor, PS/2 interface for external keyboard/mouse devices, BRAM, CIR, and system wakeup functions for system power management.

 

Differences between IT8987E and IT8987E-VG are, per ITE:

 

PART NUMBER    PACKAGE TYPE                     DESCRIPTION

IT8987E               128-pin LQFP 14mm x 14mm    128KB e-Flash
IT8987VG             128-ball VFBGA 7mm x 7mm    128KB e-Flash
 

I suppose both are the same, so you could include both in the FakeSMC plugin.

 

However, the official site did not have downloads. I could only find a PDF for the datasheet only of IT8987E, despite being in the market for some time:

 

Source = http://www.datasheetcafe.com/it8987e-datasheet-pdf-controller/
Datasheet = http://datasheetcafe.databank.netdna-cdn.com/wp-content/uploads/2019/04/IT8987E.pdf

 

Are these good enough? It's a schematic rather than a datasheet

 

Finally, Intel's NUC mainboard description writes:

 

Quote

The hardware monitoring and fan control subsystem is based on an ITE Tech. IT8987E-VG embedded controller, which supports the following:
• Processor and system ambient temperature monitoring
• Chassis fan speed monitoring
• Voltage monitoring of CPU IO Vcc (+Vccio), Memory Vcc (V_SM), CPU IN Vcc (+Vccp)
• SMBus interface

 

Hardware monitoring subsystem: based on a ITE Tech. IT8987E-VG embedded controller, including:
• Voltage sense to detect out of range power supply voltages
• Thermal sense to detect out of range thermal values
• One processor fan header
• Fan sense input used to monitor fan activity
• Fan speed control

 

Thank you.

Edited June 20, 2019 by MacKonsti

[Slice]

@MacKonsti,

Thanks for electric schemes although it is not datasheet.

Anyway I created a version to test

Hope it will work somehow.

ITEIT87x.kext.zip

[MacKonsti]

On 6/20/2019 at 9:10 PM, Slice said:

Thanks for electric schemes although it is not datasheet.

Anyway I created a version to test

Hope it will work somehow.

 

Sorry I could not provide a proper product sheet, can't be found anywhere. Thanks for getting the chipset into the kext, unfortunately it does not show any reading at all, despite loading OK (checked it on Terminal, result was org.mozodojo.ITEIT87x (1.0.4) etc.)

 

a) I installed in stages in /L/E/ step-by-step on my NUC (10.14.5) FakeSMC r206, then IntelCPUMonitor, then ACPIMonitor and finally the modified ITEIT87x. Does this ITE kext depend on anything i.e. any kext? Running Clover r4961

 

b) What can I do to provide you with SMC keys reported or detected? How can I help you on this? Do you want me to provide smcread output? Any special instructions?

 

c) Do I need to create a device per your old thread/guide here or do you want me to disassemble the DSDT and look for about thermal devices? I am no ACPI expert but all these years I've done some DSDT improvements...

 

d) Does IntelCPUMonitor support officially the NUC's CPU which is in this case Coffee Lake (Bean Canyon) generation? It's Intel Core i7-8559U / Intel Iris Plus Graphics 655

 

Thank you! (спасибо)

 

UPDATE: I found your SMC_util3 tool from here (says v0.01 hopefully it's the latest?) and I attach the keys detected via SMC_util3 -l >> NUC8-Keys.txt hope they help. Does it make sense to write some fake FAN value to see if it appears on your monitoring tool? Not sure what value that would be for a motherboard fan.

 

I am a little concerned because the output of SMC_Read3 has no visual indication of a FAN being reported, FNum shows 0 and I only get to recognise FRC0-FRC3 [freq] and TC0D-TC3D [sp78] could this be that Intel made the BIOS/ACPI to not report fans at all? For example, no clear indication of keys for CPU proximity or Ambient temperature etc. Not sure if these are CPU-platform dependent or machine/BIOS dependent... Can an SSDT-xxx device retrieve that FAN data?

 

NUC8-Keys.txt

Edited June 22, 2019 by MacKonsti

[Andrey1970]

@vector sigma

Intel updated IPG.

Attention, version number 3.5.5 did not change, but it is the new program.

https://software.intel.com/en-us/articles/intel-power-gadget

Good news: Now there is a IGPU Power.

I use VirtualSMC and now I see duplicating.

I think that now there is no need to receive CPU/IGPU Power from smc keys.

[vector sigma]

4 minutes ago, Andrey1970 said:

Intel updated IPG.

Attention, version number 3.5.5 did not change, but it is the new program.

https://software.intel.com/en-us/articles/intel-power-gadget

Good news: Now there is a IGPU Power.

I use VirtualSMC and now I see duplicating.

I think that now there is no need to receive CPU/IGPU Power from smc keys.

Tomorrow I'll handle this by looking at the new public header. Thanks for the info!

[Slice]

HWMonitor2 works with updated IPG.

[vector sigma]

1 hour ago, Slice said:

HWMonitor2 works with updated IPG.

Just adjusting the translation for "GT". More I want to see if isGTAvailable() now works .. as in the old framework wasn't

..and avoid scanning for sensors when is not necessary. a smcopen() in less.

[Pavo]

What is needed in order to get HWMonitorSMC to work with dual CPU systems? IPG does not work with dual CPU systems, so that is out of the question.

[vector sigma]

13 minutes ago, Pavo said:

IPG does not work with dual CPU systems, so that is out of the question

tried?

[Pavo]

14 minutes ago, vector sigma said:

tried?

Yes

 

[vector sigma]

9 minutes ago, Pavo said:

Yes

 

This is not HWMonitorSMC2.app! Try to decompress the package and manual install the kext and the framework.

[Slice]

Hi @vector sigma,

is it possible to make somehow HWMonitorSMC2 to NOT autostarted at system launch?

I checkout its preferences.

I exclude in from Login Items.

I checked Luach Daemons.

Anyway after restart the monitor is started again...

 

I need this to debug SMC keys without monitor.

[vector sigma]

4 hours ago, Slice said:

Hi @vector sigma,

is it possible to make somehow HWMonitorSMC2 to NOT autostarted at system launch?

I checkout its preferences.

I exclude in from Login Items.

I checked Luach Daemons.

Anyway after restart the monitor is started again...

 

I need this to debug SMC keys without monitor.

Hi Slice, that already happened to me... but later I've realize that I hade more the one HWMonitorSMC2.app that wanted to load at login (due to some tests with various copies of the source code), and since at app initialization each app unload itself if another HWMonitorSMC2.app is already running ..at next reboot, again, another app was showing up. Please ensure this is not the problem, anyway I'll revise the code.

 

EDIT

For the moment, a simple way to ensure no smc calls are made, just go to the settings and uncheck each sensor group that reads smc keys:

media, ram and battery groups doesn't use the smc. Settings are shared between each app, so this way we can ensure smc doesn't get  opened.

On 7/7/2019 at 9:40 AM, zkingtut said:

Thank you all

Please I got this result but I am not sure !!!

Please see my GPU Sensors ; is it correct ?

looks ok to me

Edited July 19, 2019 by vector sigma

[Slice]

3 hours ago, vector sigma said:

Hi Slice, that already happened to me... but later I've realize that I hade more the one HWMonitorSMC2.app that wanted to load at login (due to some tests with various copies of the source code), and since at app initialization each app unload itself if another HWMonitorSMC2.app is already running ..at next reboot, again, another app was showing up. Please ensure this is not the problem, anyway I'll revise the code.

 

EDIT

For the moment, a simple way to ensure no smc calls are made, just go to the settings and uncheck each sensor group that reads smc keys:

 

media, ram and battery groups doesn't use the smc. Settings are shared between each app, so this way we can ensure smc doesn't get  opened.

looks ok to me

This moment I am sure having only one app. But I don't know if macOS remembered it twice.

I resolved the problem deleting the app. Next time I will restore it from archive.

 

I have many news about using SMC keys so FakeSMC and plugins will be updated.

[vector sigma]

2 hours ago, Slice said:

I have many news about using SMC keys so FakeSMC and plugins will be updated.

sounds cool

[MacKonsti]

Hi @Slice per my earlier message, were I tried your plugin for the ITE IT8987VG, I suspect that I have too few SMC keys reported by your SMC_util3 as its output has no visual indication of a FAN being reported, FNum shows 0...!

 

Could this mean that the Intel NUC8's DSDT is reporting no fans, despite visible in the BIOS page? Can we help this situation by creating an SSDT-xxx.AML to retrieve that FAN data or recreate it from the disassembled DSDT? This is very curious, why would Intel block these keys...

 

Also, can you confirm that IntelCPUMonitor supports officially the Coffee Lake (Bean Canyon) generation? It's Intel Core i7-8559U / Intel Iris Plus Graphics 655.

 

Any ideas/help are welcome. Thanks again.

[Slice]

Yes, IntelCPUMonitor supported CoffeeLake processores model 0x9E. See dmesg->kernel.log to find any messages about CPU.

Give me your DSDT and I will look if there is something to do with it. And all SSDT as well!