Jump to content

1,165 posts in this topic

Recommended Posts

hello

you need to used the dsdt patched in efi / clover/ acpi /patched folder of clover and configure with clover configurator

Share this post


Link to post
Share on other sites
Advertisement

Oh sorry for that man, I was using my normal DSDT not the one you sent me. Let me post ioreg and config plist witht that


I can find this SMCD device you say but only when I use your DSDT

 

post-1517295-0-39544800-1456484639_thumb.png

 

Here goes the ioreg and the config plist

 

Archive.zip


THANKS TO @legot28 fan reading works very nice now! Thanks so much  :w00t:

 

post-1517295-0-99951200-1456484976_thumb.png

Share this post


Link to post
Share on other sites

Well, after a reboot, it doesnt work.. I have tried with and without caches to no result. I have other versions of OSX installed and I tried and it also didnt work....

I dont understand.. Here goes the screenshot as proof:

 

post-1517295-0-25935900-1456506840_thumb.png

 

I attach here my current IOREG

 

kosakgroove IOREG.zip

 

By looking at current IOREG, compared to the one I submitted when it was working, the SMCD device seems unchanged.... :(

 

 

post-1517295-0-00623700-1456506976_thumb.png

 

Could you guys give me some help?

Share this post


Link to post
Share on other sites

OMG! Thanks so much @legot28 thanks to your modification of the Info plist of my FakeSMC, more precisely the FNum key, and some other little tweaks in my DSDT, fan readings work great in my Asus Laptop hehe

 

post-1517295-0-67608400-1456602242_thumb.png

 

I got no other words than Thank you thank you thank you! :D

 

Share this post


Link to post
Share on other sites

Not working for me. Only disk is showing. Oo

Have you extracted with Pacifist the HWmonitor app and installed FakeSMC that came with it + Acpi , Cpu, Gpu and LPC sensors kexts?

 

Enviado desde mi XT1068 mediante Tapatalk

Share this post


Link to post
Share on other sites

JuniorGump must have forgotten to install the FakeSMC plugins (the ACPI/CPU/GPU/LPC sensors kexts). They either go alongside FakeSMC in its directory (/E/E or /L/E or /S/L/E depending on your own installation) or within a subfolder called PlugIns of the FakeSMC kext itself.

Share this post


Link to post
Share on other sites

Have you extracted with Pacifist the HWmonitor app and installed FakeSMC that came with it + Acpi , Cpu, Gpu and LPC sensors kexts?

 

Enviado desde mi XT1068 mediante Tapatalk

 

 

JuniorGump must have forgotten to install the FakeSMC plugins (the ACPI/CPU/GPU/LPC sensors kexts). They either go alongside FakeSMC in its directory (/E/E or /L/E or /S/L/E depending on your own installation) or within a subfolder called PlugIns of the FakeSMC kext itself.

 

Fakesmc on EFI and the rest on /S/L/E = Not work

All on EFI = Not work

Share this post


Link to post
Share on other sites

In all my hacks i haave Fake SMC and Sensor kexts in the same folder which is /System/Library/Extensions i believe that is the right way.. Only older versions of HWMonitor required the plugins to be inside fakesmc..

 

Enviado desde mi XT1068 mediante Tapatalk

Share this post


Link to post
Share on other sites

FakeSMC and its associated sensors will of course work/load/get cached from /S/L/E but the same will apply if they're placed in /L/E and/or if the sensors are manually placed in a created PlugIns subfolder of FakeSMC itself. That's how I use and run FakeSMC on all my Hacks.

 

@JuniorGump: what version of FakeSMc are you using? Did you try to integrate the sensors (of same FakeSMC release) to a PlugIns subfolder?

Share this post


Link to post
Share on other sites

FakeSMC and its associated sensors will of course work/load/get cached from /S/L/E but the same will apply if they're placed in /L/E and/or if the sensors are manually placed in a created PlugIns subfolder of FakeSMC itself. That's how I use and run FakeSMC on all my Hacks.

 

@JuniorGump: what version of FakeSMc are you using? Did you try to integrate the sensors (of same FakeSMC release) to a PlugIns subfolder?

please which version use you of clover?

Share this post


Link to post
Share on other sites

FakeSMC and its associated sensors will of course work/load/get cached from /S/L/E but the same will apply if they're placed in /L/E and/or if the sensors are manually placed in a created PlugIns subfolder of FakeSMC itself. That's how I use and run FakeSMC on all my Hacks.

 

@JuniorGump: what version of FakeSMc are you using? Did you try to integrate the sensors (of same FakeSMC release) to a PlugIns subfolder?

 

>what version of FakeSMc are you using?

 

R: 3.4.1

 

6.16.1372

 

>Did you try to integrate the sensors (of same FakeSMC release) to a PlugIns subfolder

 

Nops.

 

please which version use you of clover?

 

3424

 

@

@

 

I created the folder "PlugIns" within the Fakesmc kext and now worked. Thank you so much guys! :thumbsup_anim:

Share this post


Link to post
Share on other sites

Hello PPL

 

i have a skylake Asus notebook > http://www.insanelymac.com/forum/topic/312181-el-capitan-on-asus-x556ub-unresolved-problems/

 

and i can't to take working cpu sensors. everytime goes on kernel panic.

i have see other skylake notebooks and working,and i try these Fakesmc and sensors. all other sensors "working"

the cpu always goes on kernel panic... Any Idea about ?

Share this post


Link to post
Share on other sites

Hello PPL

 

i have a skylake Asus notebook > http://www.insanelymac.com/forum/topic/312181-el-capitan-on-asus-x556ub-unresolved-problems/

 

and i can't to take working cpu sensors. everytime goes on kernel panic.

i have see other skylake notebooks and working,and i try these Fakesmc and sensors. all other sensors "working"

the cpu always goes on kernel panic... Any Idea about ?

Might be lacking native power management as well as an adequate SkyLake SMBIOS. Without that you are doomed to crashes and instability.

Share this post


Link to post
Share on other sites

I hate to double-post, but I think this thread is more appropriate for my questions:

 

How to tell if ACPISensors is installed?  I installed it using the pkg, but it doesn't show in kextstat.  I do see LPCSensors and GPUSensors there.

 

Four out of five fans show the wrong speed, and CPU heatsink temp never changes.  Maybe this would be fixed by using ACPISensors?

 

Should I report this issue on GitHub?

Share this post


Link to post
Share on other sites

Since few versions back I can no longer auto update. It gives message thast new version exists, downloads & on install instantly gives error:

 

"An error occurred while relaunching HWMonitor, but the new version will be available next time you run HWMonitor."

 

New version is NOT available on next restart, as the same happens again

 

Manual upgrade works fine.

Share this post


Link to post
Share on other sites

All on EFI = Not work

 

Absolutely NOT the case. I have all kext in 10.10 folder on EFI next to FakeSMC & loads/works fine (with Clover)

FakeSMC and its associated sensors will of course work/load/get cached from /S/L/E but the same will apply if they're placed in /L/E and/or if the sensors are manually placed in a created PlugIns subfolder of FakeSMC itself. That's how I use and run FakeSMC on all my Hacks.

 

@JuniorGump: what version of FakeSMc are you using? Did you try to integrate the sensors (of same FakeSMC release) to a PlugIns subfolder?

 

Plugin subfolder must be created inside Contents folder

Share this post


Link to post
Share on other sites

HWmonitor.app ,FAKESMC.kext and plugins  version 6.23.1417 is out !

 

http://www.hwsensors.com/content/01-releases/43-release-1417/HWSensors.6.23.1417.pkg

 

·  CPUSensors: Support for more Skylake models

·  Feature  GPUSensors: Initial Pascal support

·  Feature  HWMonitor: Use monospaced font in status bar (Thanks to MrMage for suggestion)

·  Bug Fix  Fixed installer issues

 

:thumbsup_anim:

Share this post


Link to post
Share on other sites

How is there Pascal support?  I still haven't seen any OS X Nvidia drivers for Pascal.

All I found is here from the author Natan Zalkin  : ( the word "initial" has a sense though ...) perhaps he took the preliminary information from LINUX/FREEBSD drivers ?

 

https://github.com/kozlek/HWSensors/commit/51937f7234c8e20c037326f7c4afe8ded5a10489

Share this post


Link to post
Share on other sites

@ROBASEFR, don't waste your time. Obviously Llamafilm cannot make the difference between graphics support for a dGPU at OS level and support for a piece of hardware for monitoring purposes at a sensor/driver level. Not quite the same thing... But I guess he has not understood yet that Kozlek's FakeSMC PlugIns play no part in graphics acceleration/support for GPUs. And as you quite rightly highlighted, the word "initial" was not used for nothing.

Share this post


Link to post
Share on other sites

Sorry I have a really dumb question.

 

How do I install this program?

 

I've run the .pkg installer, rebooted, and all I get the HWMonitor app is disk temp.

 

I have a Gigabyte GA-Z170X-UD3 and a i7-6700K. I used clover to make the install

 

Thanks

Share this post


Link to post
Share on other sites

Sorry I have a really dumb question.

 

How do I install this program?

 

I've run the .pkg installer, rebooted, and all I get the HWMonitor app is disk temp.

 

I have a Gigabyte GA-Z170X-UD3 and a i7-6700K. I used clover to make the install

 

Thanks

 

As already else where explained in this topic: For Clover use

 

First : Uninstall all the kexts (FakeSMC+ 4 sensors kexts)  from S/L/E !

 

  1. Extract the .pkg with Pacifist in a new folder ( Then you get: HWMonitor.app;FakeSMC.kext and 4 sensors kexts (Acpi, Cpu, Gpu and LPC) )
  2. Create a  "PlugIns" subfolder inside FakeSMC.kext/Contents
  3. Copy the 4 sensors.kexts inside that folder
  4. Copy the "New" FakeSMC.kext inside the EFI/CLOVER/KEXTS/10.12
  5. reboot

Good luck

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)
       
    • By amin321
      hello everyones 
      I think i have a problem with my power management i feels like temperature is coming so hot and so on 
      lenovo ideapad 500 
      i7 6500U 2.50 gz
      any help please 
      Send me macbook-pro.zip
    • 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
×