Jump to content

1,881 posts in this topic

Recommended Posts

14 hours ago, jinbingmao said:

"target speed"= "目标速度"

 

Sorry, next time, yesterday my son wanted me with him almost all the day ;).

7 hours ago, Slice said:

Done!

Thanks!

Share this post


Link to post
Share on other sites
Advertisement
Posted (edited)
On 2019/6/10 at PM7点10分, vector sigma said:

对不起,下一次,昨天我的儿子几乎整天都想和  他在一起;)

谢谢!

 

Loss of key after awakening。 The computer restarted and returned to normal。2.png

3.png

1.png

1.png

Edited by jinbingmao

Share this post


Link to post
Share on other sites

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.

Share this post


Link to post
Share on other sites
Posted (edited)
40 minutes ago, 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.

Existence before sleep, loss after awakening.

 

There were no problems in earlier versions.

Edited by jinbingmao

Share this post


Link to post
Share on other sites
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?

Share this post


Link to post
Share on other sites
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.

Share this post


Link to post
Share on other sites
Posted (edited)

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 by MacKonsti

Share this post


Link to post
Share on other sites
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.

Share this post


Link to post
Share on other sites
Posted (edited)
16小时前,矢量西格玛说:

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

Platform Controller Hub( South Bridge)2.png

Edited by jinbingmao

Share this post


Link to post
Share on other sites
Posted (edited)
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 by MacKonsti

Share this post


Link to post
Share on other sites
Posted (edited)
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 by MacKonsti

Share this post


Link to post
Share on other sites

@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.1384291117_2019-07-061_22_39.thumb.png.80a8f8f6c81a2e5d6c79a5713efb0cf1.png

Share this post


Link to post
Share on other sites
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!

Share this post


Link to post
Share on other sites
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.

Share this post


Link to post
Share on other sites

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.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Similar Content

    • By fusion71au
      This is a brief guide on how to create a vanilla El Capitan (also same process for Sierra) OS X Installer USB with an updated prelinked kernel containing FakeSMC.

      It is tailored for those users who want to understand the “nuts and bolts” of how to create an installer and also to help brush up on their terminal skills (rather than have one made for them with the numerous automated “tools” available or even Apple’s createinstallmedia) :
       
       
      Specifically, it is also a “Proof of Concept” which shows that installation is possible without even having to rely on boot loader kext injection.

      Prerequisites
      Existing Yosemite installation (or Mavericks - see post#4 for steps 7,8) “Install OS X El Capitan.app" downloaded to the Applications folder Pacifist FakeSMC.kext - Slice or Kozlek branch Bootloader - Clover or Chameleon 8GB or larger USB drive (16GB recommended), formatted HFS+ (MBR or GUID) named “Installer”  
      Procedure
      1.  Boot into Yosemite with the kext-dev-mode=1 boot flag
      2.  Open OS X terminal and type the following lines, followed by <Enter> after each line.
          The image restore and file copying may take a while to complete, and at the end of the process, the Installer volume is renamed to “OS X Base System"....
       
      sudo -s hdiutil attach /Applications/Install\ OS\ X\ El\ Capitan.app/Contents/SharedSupport/InstallESD.dmg asr restore -source /Volumes/OS\ X\ Install\ ESD/BaseSystem.dmg  -target /Volumes/Installer -erase -format HFS+ -noprompt -noverify rm /Volumes/OS\ X\ Base\ System/System/Installation/Packages cp -av /Volumes/OS\ X\ Install\ ESD/Packages /Volumes/OS\ X\ Base\ System/System/Installation cp -av /Volumes/OS\ X\ Install\ ESD/BaseSystem.dmg /Volumes/OS\ X\ Install\ ESD/BaseSystem.chunklist /Volumes/OS\ X\ Base\ System diskutil unmount /Volumes/OS\ X\ Install\ ESD exit 3.  Right click on the “OS X Base System” Volume and click “Get Info”
       

      4.  Click on the lock icon and untick “Ignore ownership on this volume”
       

      5.  Extract/Copy the El Capitan Kernels folder into /System/Library/ of the USB with Pacifist.  NB It is found in the "Essentials.pkg" in /System/Installation/Packages
       

      6.  Delete or Rename the original /System/Library/PrelinkedKernels/prelinkedkernel —> OG.prelinkedkernel
       

      7.  Copy FakeSMC.kext and other necessary kexts (e.g. VoodooPS2Controller.kext for laptops) into the /Library/Extensions folder of the installer USB using Finder.
       

      8.  Back in terminal, type the following lines, followed by <Enter> after each line to rebuild the prelinkedkernel…..
       
      sudo -s chmod -R 755 /Volumes/OS\ X\ Base\ System/Library/Extensions chown -R 0:0 /Volumes/OS\ X\ Base\ System/Library/Extensions touch /Volumes/OS\ X\ Base\ System/System/Library/Extensions kextcache -u /Volumes/OS\ X\ Base\ System exit Any errors should be noted but the output below is normal e.g.


      9. Install your Bootloader targeting the OS X Base System volume
       
       
       
       
      10.  Boot your system with the USB without injected kexts into the OS X Installer GUI....
       
       
       
       
       
      Post Install
      The original prelinked kernel in a fresh install of El Capitan will also lack FakeSMC ie it will only be linked to Apple signed kexts.  In order to boot into El Capitan the first time around without boot loader kext injection, the PLK needs to be rebuilt for the El Capitan volume like we did for the installer:
       
      1.  Boot into Yosemite with the kext-dev-mode=1 boot flag
      2.  Delete or Rename the original /System/Library/PrelinkedKernels/prelinkedkernel for the El Capitan volume —> OG.prelinkedkernel
      3.  Copy FakeSMC.kext and other necessary kexts (e.g. VoodooPS2Controller.kext for laptops) into the /Library/Extensions folder of El Capitan using Finder
      4.  Back in terminal, type the following lines, followed by <Enter> after each line to rebuild the prelinkedkernel.  In this example, the El Capitan volume is named "El_Capitan" - change if you have named it something else...
      sudo -s chmod -R 755 /Volumes/El_Capitan/Library/Extensions chown -R 0:0 /Volumes/El_Capitan/Library/Extensions touch /Volumes/El_Capitan/System/Library/Extensions kextcache -u /Volumes/El_Capitan exit 5. Install your Bootloader targeting the El Capitan volume.  This step is only necessary if you are installing El Capitan on a new drive without existing boot loader (not required if installing on a disk with existing boot loader beside Yosemite).
      6. Reboot your system without injected kexts into El Capitan!
       
       
      Other links
      The All-In-One Guide to Vanilla OS X for beginners
       
      Updates for Sierra and High Sierra   Custom Prelinkedkernel Generator Tool I have made a custom prelinkedkernel generator "PLK.tool" for Sierra + El Capitan.  Instructions:   1.  Download and extract the attached BaseSystem_PLK.tool.zip into your ~/Downloads folder.   2.  Copy any extra kexts necessary for booting your hack to ~/Downloads/BaseSystem/ExtraKexts (e.g. FakeSMC, VoodooPS2Controller), making sure SIP is disabled. 3.  Copy BaseSystem.dmg to ~/Downloads/BaseSystem  4.  Open terminal and run the following commands... cd ~/Downloads/BaseSystem chmod +x PLK.tool ./PLK.tool ---> supply your admin password ---> will place your new custom prelinkedkernel on the desktop.       macOS High Sierra bypass Firmware and MBR checks in post#13.
      BaseSystem_PLK.tool_ElCap.zip
      BaseSystem_PLK.tool_Sierra.zip
      BaseSystem_PLK.tool_Mojave.zip (need to run in Mojave to avoid dependency errors)
      BaseSystem_PLK.tool_Catalina.zip
       
    • By DaHarry
      I have installed Hackintosh on to my System, but the CPU cooler is obviously louder then on Windows.
      I am using right now VirtualSMC.kext, but since FakeSMC provides temperature measurement tools, and VirtualSMC not, I asked my self if that might be a hint for my loud cooler?
      My question, has somebody tried maybe both and even compared them? And is FakeSMC maybe less noisy?
      Is it enough to just mount EFI partition, and delete the VirtualSMC.kext and put instead FakeSMC.kexts ? Without any fancy kext installation tool or terminal commands, just replace files and restart in enough?
      My System:
      Mainboard: Gigabyte Aorus Z390 Ultra
      CPU: Intel i9 9900k
      CPU Cooler: BeQuiet! Dark Rock 4
      GPU: Vega 64
      Ram: 2x16GB Corsair 3200
      SSD: 1TB Adata M.2
       
      The Tutorial i have used - https://github.com/cmer/gigabyte-z390-aorus-master-hackintosh/blob/master/STEP_BY_STEP.md
       
      Really works like a charm besides, the more noisy cooler, which i bought because it is extra quietly.
      I asked first at tonymac's forum, but they deleted the post because I haven't used their tool, really disgustig.. I really hope to never use their tools, and I hope here the information freedom is more respected.
      #f. tonyhoremacs
    • By vector sigma
      HWSensor Features
      Control temperature of Intel and AMD CPU Control temperature of AMD, Intel and NVidia cards Control temperature of motherboard Control FANS Control Voltages Control HDD/SSD state (SATA & NVMe) with S.M.A.R.T. monitoring  Control frequencies Laptop Battery Monitoring Different applications support High Sierra compatible Installation to /S/L/E or in the ESP (Clover only)  
      Supported languages:
      English (base), Russian, Italian, Korean and semplified Chinese
       
      Source code: at https://sourceforge.net/p/hwsensors/hwsensors3/code3/HEAD/tree/
      Bugs report at https://sourceforge.net/p/hwsensors/hwsensors3/tickets/
      Topic for discussion at: https://www.insanelymac.com/forum/topic/299861-hwsensors3/
       
      Chief Developer @Slice, new HWMonitorSMC2.app and package by @vector sigma
    • By Slice
      Laptop battery monitoring

       
       
       
      Using this driver you have to exclude other battery drivers: ACPIBatteryManager, AppleSmartBattery and so on.
      This driver assumes to using HWSensors3 with FakeSMC 3.5 as being part of it.
       
      19.01.2018
      Updated version of VoodooBatterySMC will get extended battery information and so it will be more exact.
      VoodooBatterySMC.kext.zip
       
      Updated HWMonitorSMC by vector-sigma
      HWMonitorSMC.app.zip
       
      HWMonitor2 by vector-sigma
      https://sourceforge.net/projects/hwsensors3.hwsensors.p/files/latest/download
×