Jump to content

1,960 posts in this topic

Recommended Posts

Advertisement

Well, but my laptop's GF119M actually.. has no GPU Fan, or am I wrong with installed monitoring kexts? Also not sure if NVClockX is for my GPU since it gives error message on verbose logs.. There's another AppleSMC.kext on downloaded package but I already got it on 10.11's SLE.. ah, I think I need to learn more about my HW..  :rofl:

 

 

zAyN7hq.jpg

 

You should not use NVClockX and GeforceSensors simultaneously. Use one of them

In my case Dell NVS5200M (GF108) is monitored by Geforce sensors very good.

Share this post


Link to post
Share on other sites

Hi @Slice

 

I have a question. My EVGA's (1070 SuperClocked) fan speed is at it's minimal speed, how can I fix that? I'm concerned about the well being of the GPU, the GPU Die is 63 Degrees Celsius   while idle and it reaches up to 80 under load.

Is there anything that can be done?

Share this post


Link to post
Share on other sites

Hi @Slice

 

I have a question. My EVGA's (1070 SuperClocked) fan speed is at it's minimal speed, how can I fix that? I'm concerned about the well being of the GPU, the GPU Die is 63 Degrees Celsius   while idle and it reaches up to 80 under load.

Is there anything that can be done?

Sorry,

I know nothing how to control this kind of videocard.

Share this post


Link to post
Share on other sites

Revision 51 available on sf.net. Link in my signature.

There is no package, just dmg image. 

Don't install all kexts! Choose only those you needed!

For the desktop in my signature I would only need FakeSMC, IntelCPUMonitor and GeforceSensor? Is this correct?

Are these kexts ok in CLOVER/kexts/other or install to S/L/E?

And Laptop: FakeSMC, IntelCPUMonitor and VoodooBatterySMC?

 

And another question, what is AppleSMC for?

Share this post


Link to post
Share on other sites

For the desktop in my signature I would only need FakeSMC, IntelCPUMonitor and GeforceSensor? Is this correct?

Are these kexts ok in CLOVER/kexts/other or install to S/L/E?

And Laptop: FakeSMC, IntelCPUMonitor and VoodooBatterySMC?

 

And another question, what is AppleSMC for?

For desktop you may add ITE87x.kext for System Fan monitoring.

 

For laptop you may add ACPIMonitor.kext and SSDT as you can find here.

 

AppleSMC is just a version from stable system to replace beta kext with large messages count.

Share this post


Link to post
Share on other sites

What means with "new geforce" here? I have no problem with it

I guess what it mean is that the "GeforceSensor.kext" which is a new version of Kozlek's previous sensor is still causing the kernel panic on Pascal GPUs. The only version of the GPUSensors.kext that I was able to use is the one I attached here. It's also by kozlek but I guess it's been updated and I have no problem using it.

 

But the thing is I wasn't able to get it to work with the new FakeSMC.kext v. 3.5.0 yet.

GPUSensors.kext.zip

Share this post


Link to post
Share on other sites

This kext is fake working. It shows a value having no relation to real temperature.

As well compare frequencies if any.

Yes I know about the fake/inaccurate readings. but when I use your version of the GeForeceSensor.kext it gives me the kernel panic. Is there anything that can be done?

 

Can you please tell me which of these sensors I should use on my SkyLake machine? I tried using the ACPIMonitor, GeforeceSensor, ITEIT87x and it either reboots the system or it will end up in kernel panic.

Share this post


Link to post
Share on other sites

Yes I know about the fake/inaccurate readings. but when I use your version of the GeForeceSensor.kext it gives me the kernel panic. Is there anything that can be done?

 

Can you please tell me which of these sensors I should use on my SkyLake machine? I tried using the ACPIMonitor, GeforeceSensor, ITEIT87x and it either reboots the system or it will end up in kernel panic.

My Skylake machine works with HWSensors3.

But GeforceSensors seems unsupported Pascal cards. Remove this kext.

I have the Skylake Asus H170I-PLUS desktop. Unfortunately, my dsdt doesn't have an embedded controller, or a method TACH for the fan speed.

 

My SuperIO chip is the Nuvoton NCT6793D.

 

I tried the latest revision 51 of HWSensor3, FakeSMC.kext, ACPIMonitor.kext, IntelCPUMonitor.kext, and W836x.kext. But, I get 0 rpm for the CPU Fan speed.

 

I'm trying to get the fan rpm, but either my dsdt is missing the proper code for the fan speed, or the W836x.kext doesn't support my Nuvoton NCT6793D.

The kext supports NCT6793D

        case 0xD1:
            model = NCT6793D;
            break;

Did you see any kernel messages like this?

DebugLog("found unsupported chip ID=0x%x REVISION=0x%x", id, revision);

Share this post


Link to post
Share on other sites

What is the differences with the FakeSMC RehabMan ➤ 6.25-333-g05e0f4be.1759

 

the FakeSMC 3.5.0 does not boot Snow Leopard 10.6.8

Share this post


Link to post
Share on other sites

What is the differences with the FakeSMC RehabMan ➤ 6.25-333-g05e0f4be.1759

 

the FakeSMC 3.5.0 does not boot Snow Leopard 10.6.8

I compile it for 64bit only and set minimum OS 10.8.

3.5.0 contains compatibility with High Sierra.

For Snow you may use older 3.4.1 with HWInfo.kext. 

Share this post


Link to post
Share on other sites

I compile it for 64bit only and set minimum OS 10.8.

3.5.0 contains compatibility with High Sierra.

For Snow you may use older 3.4.1 with HWInfo.kext. 

ok thanks Slice

Share this post


Link to post
Share on other sites

I compile it for 64bit only and set minimum OS 10.8.

3.5.0 contains compatibility with High Sierra.

For Snow you may use older 3.4.1 with HWInfo.kext. 

 

i tested 10.6~10.13 on my sandy laptop

 

i checked 10.8 mountain lion. failed load fakesmc.

10.9~10.13 no problem.

 

For Snow you may use older 3.4.1 with HWInfo.kext. 

-checked.

 

 

what is 3.4.1 latest version? HWSensors3-rev43.pkg.zip right?

 

thanks in advance.

 

EDIT1.

also i wonder one

if has FakeSMC.kext in other folder and 10.6 folder, what is happen?

other fakesmc 3.5.0

10.6  fakesmc 3.4.1

 

loaded fake 3.4.1 right if boot 10.6?

Share this post


Link to post
Share on other sites

I just updated my X79 to the latest rev51 from the rev33 that I've been using for the past year or so.

 

GeforceSensors is showing 10x the speeds for Core and Shaders (should be 405 and 810). Rolling back to the older kext fixed this.

 

Also, is there any way to have the Batteries section in HWMonitorSMC not show up while running on a desktop? Again, rolling back to the older version fixed this for me.

post-267996-0-88050300-1507388475_thumb.png

Share this post


Link to post
Share on other sites

I just updated my X79 to the latest rev51 from the rev33 that I've been using for the past year or so.

 

GeforceSensors is showing 10x the speeds for Core and Shaders (should be 405 and 810). Rolling back to the older kext fixed this.

 

Also, is there any way to have the Batteries section in HWMonitorSMC not show up while running on a desktop? Again, rolling back to the older version fixed this for me.

GeforceSensors is wrong. For my case it shows 2050MHz while it must be 625MHz as Windows said.

I know about Battery section but I very poor know Objective-C and can't correct this.

There is no problem to use on desktop older version. This version has a difference only for laptops.

Share this post


Link to post
Share on other sites

PS. Using VoodooBatterySMC assumes you need no double it by ACPIBatteryManager.

So, If I'll use your kext, I need to delete the RehabMan's kext?

i reworked the app, now show voltage and amperage using rehabman's kext by just reading kIOPMPSVoltageKey and kIOPMPSCurrentCapacityKey.

If I use the HWMonitorSMC.app after extractin it, I've got this error message:

Screen Shot 2017-10-14 at 22.47.58.png

Share this post


Link to post
Share on other sites

So, If I'll use your kext, I need to delete the RehabMan's kext?

If I use the HWMonitorSMC.app after extractin it, I've got this error message:

attachicon.gifScreen Shot 2017-10-14 at 22.47.58.png

don't know, it tells you is damaged, but redownloading it is fine here.

No, mA means current in units "milliAmpers".

mAh means capacity in units mA * hours.

How many hours the laptop can work with battery can be calculated from capacity and current

Hours = mAh/mA 

ok got it. So the one attached is now perfect, tested with VoodooBatterySMC.kext and ACPIBatteryManager.kext.

P.S. I introduced I little bug and by clicking voltage it may be always displayed in the top bar. Don't panic I'll fix it.... now I'v to go. please let me know

Have to correct myself, this bug was already there: fixed.

Also, is there any way to have the Batteries section in HWMonitorSMC not show up while running on a desktop? Again, rolling back to the older version fixed this for me.

Well, I think should be easy, but no time today. I'll looking into this later.

hwmonitor.zip

HWMonitorSMC.app.zip

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

  • Recently Browsing   0 members

    No registered users viewing this page.

  • 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 Slice
      Dell laptops and desktop can be monitored by SMM methods as mentioned is the old topic
       
      I made a plugin SMIMonitor for FakeSMC in 2014 but it was 32bits and was not working. Only now I made it to be 64bits (as darkvoid did with kozleks branch) and got positive results
        
      and after heating 
      So I have monitoring of 4 additional temperature sensors (CPU Proximity, GPU, DIMM, and Motherboard) and a CPU fan which initially stay at 0 rpm and start rotating after heating with 2882rpm.
       
      Moreover I implemented a function for brave people to control fans
      sudo SMC_util3 -kF0As -w2 The last digit 2 is a FAN speed you want to set
      0 = Off
      1 = Low
      2 = High
      If you have more then 1 fan then you can manage other one by choosing next key F1As, F2As etc.
       
      Precaution! Writing the fan speed is dangerous and may cause a computer damage. Do this at your own risk!
      Note. SMIMonitor.kext will work only with FakeSMC v3 provided with HWSensors3 in my signature.
      Official release at sf.net contains SMIMonitor without write possibility.
       
      Please test and report your successes and fails.
       
       
      SMIMonitor.kext-110.zip
      SMC_util3.zip
      smcwrite.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
×