Jump to content

1,598 posts in this topic

Recommended Posts

What is changed except the kext? Something else? 

The main difference is reporting SMC keys, but it is not influencing on system.

May be broken permissions?

 

Nothing else has changed. I have tried your latest HWSensor automatic installation package as well as extracting the package with Pacifist and then installing the resulting appropriate kexts via Chameleon Wizard. I have installed both versions several times using the same installation methods, and rolled them back to the previous version several times even running Disk Utility each time for good measure.

 

In both instances, there are no permission errors and kextstat and System Information both show the FakeSMC.kext and its plugins installed correctly. Each time, the latest FakeSMC.kext version 3.4.0 causes a black screen upon system Wake while FakeSMC.kext 3.3.1 presents no such issue.

 

In the past several years, I have never experienced any issues with your branch of FakeSMC HWSensors, and I have also never experienced black screen upon system Wake for any reason.

FakeSMC:

  Version: 3.3.1
  Last Modified: 12/11/14 4:16 PM
  Kind: Intel
  Architectures: i386, x86_64
  64-Bit (Intel): Yes
  Location: /System/Library/Extensions/FakeSMC.kext
  Kext Version: 3.3.1
  Load Address: 0xffffff7f81a04000
  Valid: Yes
  Authentic: Yes
  Dependencies: Satisfied

Share this post


Link to post
Share on other sites
Advertisement

 

Nothing else has changed. I have tried your latest HWSensor automatic installation package as well as extracting the package with Pacifist and then installing the resulting appropriate kexts via Chameleon Wizard. I have installed both versions several times using the same installation methods, and rolled them back to the previous version several times even running Disk Utility each time for good measure.

 

In both instances, there are no permission errors and kextstat and System Information both show the FakeSMC.kext and its plugins installed correctly. Each time, the latest FakeSMC.kext version 3.4.0 causes a black screen upon system Wake while FakeSMC.kext 3.3.1 presents no such issue.

 

In the past several years, I have never experienced any issues with your branch of FakeSMC HWSensors, and I have also never experienced black screen upon system Wake for any reason.

FakeSMC:

  Version: 3.3.1
  Last Modified: 12/11/14 4:16 PM
  Kind: Intel
  Architectures: i386, x86_64
  64-Bit (Intel): Yes
  Location: /System/Library/Extensions/FakeSMC.kext
  Kext Version: 3.3.1
  Load Address: 0xffffff7f81a04000
  Valid: Yes
  Authentic: Yes
  Dependencies: Satisfied

Compare, please, Info.plist's of these two versions of FakeSMC.kext.

I see no reason for different behavior other then different info.plist.

The version changed because of new output but system can't see it.

Share this post


Link to post
Share on other sites

Compare, please, Info.plist's of these two versions of FakeSMC.kext.

I see no reason for different behavior other then different info.plist.

The version changed because of new output but system can't see it.

 

Both FakeSMC.kext versions Info.plists appear to be identical short of the version number and yet the problem persists.

For now, I will simply continue using the older FakeSMC.kext version 3.3.1.

 

Thank You for your work!

Share this post


Link to post
Share on other sites

Hey

 

thanks for your great work. I have a question. Do you have any idea when and/or if the gm204 chipsets might be supported in the future?

Jan  3 15:39:14 localhost kernel[0]: GeForceSensors (pci1): [Fatal] GM204 not supported yet
Jan  3 15:39:14 localhost kernel[0]: GeForceSensors (pci1): [Fatal] unsupported chipset, 0x124020a1

Cheers

Share this post


Link to post
Share on other sites

Hey

 

thanks for your great work. I have a question. Do you have any idea when and/or if the gm204 chipsets might be supported in the future?

Jan  3 15:39:14 localhost kernel[0]: GeForceSensors (pci1): [Fatal] GM204 not supported yet
Jan  3 15:39:14 localhost kernel[0]: GeForceSensors (pci1): [Fatal] unsupported chipset, 0x124020a1

Cheers

Yes, I think it may be supported in future... but I see these messages not from my project...

Share this post


Link to post
Share on other sites

Revision 11.

Yes, I change project home and begin numeration from zero. Link is in the topic.

 

Change log:

- support more hardware, more NVidia cards, more SMBus chips;

- installer has more options to install. Silent AppleSMC included to not spam in system.log;

- corrected numerous bugs existing here from initial.

Share this post


Link to post
Share on other sites

Can anybody test debug version of new plugin DIMMSensor? It should monitor temperature on DIMM sensors.

SMC keys will be TM0P, TM1P, ...

sudo chown -R root:wheel DIMMSensor.kext
sudo kextutil -v DIMMSensor.kext

There will be many messages in kernel.log

 

Share this post


Link to post
Share on other sites

It doesn't work for me and  I think you mean this messages.

 

 

Jan 30 21:32:23 localhost kernel[0] <Notice>: ARPT cannot assert wake from D3cold
Jan 30 21:32:23 localhost kernel[0] <Notice>: [iCHSMBus] init
Jan 30 21:32:23 localhost kernel[0] <Notice>: [iCHSMBus] probe
Jan 30 21:32:23 localhost kernel[0] <Notice>: [iCHSMBus] start
Jan 30 21:32:23 localhost kernel[0] <Notice>: [iCHSMBus] conf: 0x1
Jan 30 21:32:23 localhost kernel[0] <Notice>: [iCHSMBus] IRQ: 19
Jan 30 21:32:23 localhost kernel[0] <Notice>: Controller: Intel 82801H (vendor ID: 8086, device ID: 284b)
Jan 30 21:32:23 localhost kernel[0] <Notice>: FakeSMC: opensource SMC device emulator by netkas © 2009
Jan 30 21:32:23 localhost kernel[0] <Notice>: FakeSMC: plugins & plugins support modifications by mozodojo, usr-sse2, slice © 2010
Jan 30 21:32:23 localhost kernel[0] <Notice>: FakeSMCDevice: 21 preconfigured key(s) added
Jan 30 21:32:23 localhost kernel[0] <Notice>: FakeSMCDevice: successfully initialized
Jan 30 21:32:23 localhost kernel[0] <Notice>: IntelCPUMonitor: CPU family 0x6, model 0xf, stepping 0xd, cores 2, threads 2
Jan 30 21:32:23 localhost kernel[0] <Notice>: FireWire runtime power conservation disabled. (3)
Jan 30 21:32:23 localhost kernel[0] <Notice>: IntelCPUMonitor: Using efi
Jan 30 21:32:23 localhost kernel[0] <Notice>: IntelCPUMonitor: BusClock=166MHz FSB=665MHz
Jan 30 21:32:23 localhost kernel[0] <Notice>: [iCHSMBus] exec: op 1, addr 0x18, cmdlen 1, len 1
Jan 30 21:32:23 localhost kernel[0] <Notice>: [iCHSMBus] exec: St 0x40
Jan 30 21:32:23 localhost kernel[0] <Notice>: IntelCPUMonitor: CPU Tjmax 100
Jan 30 21:32:23 localhost kernel[0] <Notice>: HWInfo: SMC Platform: M75
Jan 30 21:32:23 localhost kernel[0] <Notice>: [iCHSMBus] exec: Ctl 0x49
Jan 30 21:32:23 localhost kernel[0] <Notice>: VoodooPS2SynapticsTouchPad Version 1.8.12 loaded...
Jan 30 21:32:23 localhost kernel[0] <Notice>: [iCHSMBus] Register decoded: 0x44<BUSY=0,INTR=0,DEVERR=1,BUSERR=0,FAILED=0,SMBAL=0,INUSE=1,BDONE=0>
Jan 30 21:32:23 localhost kernel[0] <Notice>: [iCHSMBus] marker = 1
Jan 30 21:32:23 localhost kernel[0] <Notice>: [iCHSMBus] exec: op 1, addr 0x19, cmdlen 1, len 1
Jan 30 21:32:23 localhost kernel[0] <Notice>: [iCHSMBus] exec: St 0x0
Jan 30 21:32:23 localhost kernel[0] <Notice>: [iCHSMBus] exec: Ctl 0x49
Jan 30 21:32:23 localhost kernel[0] <Notice>: [iCHSMBus] Register decoded: 0x44<BUSY=0,INTR=0,DEVERR=1,BUSERR=0,FAILED=0,SMBAL=0,INUSE=1,BDONE=0>
Jan 30 21:32:23 localhost kernel[0] <Notice>: [iCHSMBus] marker = 1
Jan 30 21:32:23 localhost kernel[0] <Notice>: [iCHSMBus] exec: op 1, addr 0x1a, cmdlen 1, len 1
Jan 30 21:32:23 localhost kernel[0] <Notice>: [iCHSMBus] exec: St 0x0
Jan 30 21:32:23 localhost kernel[0] <Notice>: [iCHSMBus] exec: Ctl 0x49
Jan 30 21:32:23 localhost kernel[0] <Notice>: [iCHSMBus] Register decoded: 0x44<BUSY=0,INTR=0,DEVERR=1,BUSERR=0,FAILED=0,SMBAL=0,INUSE=1,BDONE=0>
Jan 30 21:32:23 localhost kernel[0] <Notice>: [iCHSMBus] marker = 1
Jan 30 21:32:23 localhost kernel[0] <Notice>: [iCHSMBus] exec: op 1, addr 0x1b, cmdlen 1, len 1
Jan 30 21:32:23 localhost kernel[0] <Notice>: [iCHSMBus] exec: St 0x0
Jan 30 21:32:23 localhost kernel[0] <Notice>: [iCHSMBus] exec: Ctl 0x49
Jan 30 21:32:23 localhost kernel[0] <Notice>: [iCHSMBus] Register decoded: 0x44<BUSY=0,INTR=0,DEVERR=1,BUSERR=0,FAILED=0,SMBAL=0,INUSE=1,BDONE=0>
Jan 30 21:32:23 localhost kernel[0] <Notice>: [iCHSMBus] marker = 1
Jan 30 21:32:23 localhost kernel[0] <Notice>: [iCHSMBus] exec: op 1, addr 0x1c, cmdlen 1, len 1
Jan 30 21:32:23 localhost kernel[0] <Notice>: [iCHSMBus] exec: St 0x0
Jan 30 21:32:23 localhost kernel[0] <Notice>: [iCHSMBus] exec: Ctl 0x49
Jan 30 21:32:23 localhost kernel[0] <Notice>: [iCHSMBus] Register decoded: 0x44<BUSY=0,INTR=0,DEVERR=1,BUSERR=0,FAILED=0,SMBAL=0,INUSE=1,BDONE=0>
Jan 30 21:32:23 localhost kernel[0] <Notice>: [iCHSMBus] marker = 1
Jan 30 21:32:23 localhost kernel[0] <Notice>: [iCHSMBus] exec: op 1, addr 0x1d, cmdlen 1, len 1
Jan 30 21:32:23 localhost kernel[0] <Notice>: [iCHSMBus] exec: St 0x0
Jan 30 21:32:23 localhost kernel[0] <Notice>: [iCHSMBus] exec: Ctl 0x49
Jan 30 21:32:23 localhost kernel[0] <Notice>: [iCHSMBus] Register decoded: 0x44<BUSY=0,INTR=0,DEVERR=1,BUSERR=0,FAILED=0,SMBAL=0,INUSE=1,BDONE=0>
Jan 30 21:32:23 localhost kernel[0] <Notice>: [iCHSMBus] marker = 1
Jan 30 21:32:23 localhost kernel[0] <Notice>: [iCHSMBus] exec: op 1, addr 0x1e, cmdlen 1, len 1
Jan 30 21:32:23 localhost kernel[0] <Notice>: [iCHSMBus] exec: St 0x0
Jan 30 21:32:23 localhost kernel[0] <Notice>: [iCHSMBus] exec: Ctl 0x49
Jan 30 21:32:23 localhost kernel[0] <Notice>: [iCHSMBus] Register decoded: 0x44<BUSY=0,INTR=0,DEVERR=1,BUSERR=0,FAILED=0,SMBAL=0,INUSE=1,BDONE=0>
Jan 30 21:32:23 localhost kernel[0] <Notice>: [iCHSMBus] marker = 1
Jan 30 21:32:23 localhost kernel[0] <Notice>: [iCHSMBus] exec: op 1, addr 0x1f, cmdlen 1, len 1
Jan 30 21:32:23 localhost kernel[0] <Notice>: [iCHSMBus] exec: St 0x0
Jan 30 21:32:23 localhost kernel[0] <Notice>: [iCHSMBus] exec: Ctl 0x49
Jan 30 21:32:23 localhost kernel[0] <Notice>: [iCHSMBus] Register decoded: 0x44<BUSY=0,INTR=0,DEVERR=1,BUSERR=0,FAILED=0,SMBAL=0,INUSE=1,BDONE=0>
Jan 30 21:32:23 localhost kernel[0] <Notice>: [iCHSMBus] marker = 1
Jan 30 21:32:23 localhost kernel[0] <Notice>: FireWire (OHCI) VendorID 1180 ID 832 PCI now active, GUID 00241b002fd83c00; max speed s400.
Jan 30 21:32:23 localhost kernel[0] <Notice>: [DIMM] Device matching failed.
 

Share this post


Link to post
Share on other sites

46395098.png

 

Apparently it doesn't work with my GTX 970.

 

 

I installed it like this:

 

CPU -> Intel CPU

LPC chip type -> winbond

GPU type -> Nvidia -> New Geforce

FakeSMC

SMBus chip type

Share this post


Link to post
Share on other sites

46395098.png

 

Apparently it doesn't work with my GTX 970.

 

 

I installed it like this:

 

CPU -> Intel CPU

LPC chip type -> winbond

GPU type -> Nvidia -> New Geforce

FakeSMC

SMBus chip type

It is a conflict with Kozlek's HWMonitor application.

There is another one HWMonitor in the package.

Share this post


Link to post
Share on other sites

Hi Slice,

Does this application works if FakeSMC is an injected kext (Clover and 10.10 folder routine) via clover on USB pen?

Yes, as usual.

These kexts will work if injected by a bootloader.

I prefer place all kexts into SLE because injection requires additional time while SLE will be cached.

Share this post


Link to post
Share on other sites

Ok its working now but I only see one GPU in the list I have three. I have 2 x 970 and one 570.

 

How do one change fan speed with this version?

 

post-36193-0-26568000-1423227130_thumb.png

Share this post


Link to post
Share on other sites

i cant get my cpu fan reading in fake smc 

pls help me 

my dump and screenshot is added

OK.

You are using kexts and HWMonitor application v6.x from Kozlek while the thread about HWSensors3 by me.

There is a difference.

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 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 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)
       
    • 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
×