Jump to content

1,868 posts in this topic

Recommended Posts

Hi,

I had this kp as part of an installation on my X299 hack. CPU is i9-7900x

The install was successful after I removed the plugins from fakeSMC kext.

But of course now I don't have HWMon. Which with this chip makes me nervous given that I haven't got speedstep working yet and it's running at full noise (and heat).

 

Is there a way this can be fixed?

 

attachicon.gif20170806_083556.jpg

this is FakeSMC v6 on the screenshot. Use my version or ask Kozlek for update his version.

Share this post


Link to post
Share on other sites
Advertisement

seems smc version problem on some osx or some system. not sure and clear.

i replaced fakesmc files with plugins files. then got result

 

kozlek's kext shown corrected smc version

post-980913-0-92559100-1504886644_thumb.png

 

slice's kext shown incorrected smc version

post-980913-0-49539900-1504886652_thumb.png

 

i just report problem. thanks in advance.

Share this post


Link to post
Share on other sites

seems smc version problem on some osx or some system. not sure and clear.

i replaced fakesmc files with plugins files. then got result

 

kozlek's kext shown corrected smc version

attachicon.gifkozlek.png

 

slice's kext shown incorrected smc version

attachicon.gifslice.png

 

i just report problem. thanks in advance.

Test, please,

Release350.zip

Share this post


Link to post
Share on other sites

Test, please,

attachicon.gifRelease350.zip

post-980913-0-25188000-1505335607_thumb.png

 

it works. :)

 

dell laptop(skylake and kabylake) needs ALS0 dsdt part to load saved brightness when booting. It was confirmed by rehabman and dell laptop users.

https://bitbucket.org/RehabMan/os-x-fakesmc-kozlek/commits/05e0f4bee72461128c461c32eb4f235e48825eaf

 

if enable ALS0, shown smc key received error on High Sierra. on Sierra, i don't see this smcreadkey error.

kozlek's fakesmc has MSLD key.

 

2017-09-14 05:55:57.425535+0900 localhost kernel[0]: (AppleSMCLMU) <AppleSMCLMU`AppleLMUController::smcReadKey(unsigned int, unsigned long long, void*)> AppleLMUController::smcReadKey Error: received error 0x84 when reading key 'MSLD'

 

thanks

 

EDIT.

Seems fixes osinstall.mpkg issue related EmuVariableUefi-64.efi on HS

Share this post


Link to post
Share on other sites

As far as I remember the key MSLD preventing hibernation by LID. So I prefer to exclude it.

More investigations needed.


dell laptop(skylake and kabylake) needs ALS0 dsdt part to load saved brightness when booting. It was confirmed by rehabman and dell laptop users.
https://bitbucket.org/RehabMan/os-x-fakesmc-kozlek/commits/05e0f4bee72461128c461c32eb4f235e48825eaf

 

Show me this DSDT part.

 

 

I have Dell laptop.

Share this post


Link to post
Share on other sites

As far as I remember the key MSLD preventing hibernation by LID. So I prefer to exclude it.

More investigations needed.

 

Show me this DSDT part.

 

 

I have Dell laptop.

Here. I can't link for detail info of dell saved brightness. Because there is info in Toxxxxx site.

 

https://github.com/RehabMan/OS-X-Clover-Laptop-Config/blob/master/hotpatch/SSDT-ALS0.dsl

 

SSDT-ALS0+rehabman's commit keys(5keys)+rc script can use saved brightness when reboot.

 

Thanks

 

EDIT1.

This is only dell xps laptop(skylake and kabylake). I tested xps 12 2in1 on sierra.

My lg laptop need only rc script without ALS0 for saved brightness

 

 

 

나의 LG-F800S 의 Tapatalk에서 보냄

Share this post


Link to post
Share on other sites

Not very good, but normal.

 

This new version compatible with 10.13 and works without HWInfo. Also in nearest future it may support new features if I will make them.

Share this post


Link to post
Share on other sites

Confirmed. Removing key MSLD make hibernation with LID close possible.

Real Mac expected the key=1 when LID is closed and =0 when Open. But we can't produce such behaviour. We can only remove the key.

Okay. Slice like you said, seems better default removed MSLD for LID close. Only dell xps users consider what i mentioned.

 

I saw 350.zip file. I can't see hwinfo.kext and other app. Since 350, does it exclude some kext and apps(monitor, etc)? I used your fakesmc. Because your driver support all osx. I just want to know clear file. Because shown difference of previous pkg.

 

Thanks

 

 

나의 LG-F800S 의 Tapatalk에서 보냄

Share this post


Link to post
Share on other sites

HWInfo excluded. Apps can be used from previous package until I make new one.

The work is not finished, I expected more updates and proposed new installer.

 

PS. Nothing bad if old HWInfo is still present. It just no more needed.

Share this post


Link to post
Share on other sites

HWInfo excluded. Apps can be used from previous package until I make new one.

The work is not finished, I expected more updates and proposed new installer.

 

PS. Nothing bad if old HWInfo is still present. It just no more needed.

Thank you

 

나의 LG-F800S 의 Tapatalk에서 보냄

Share this post


Link to post
Share on other sites

Is there any chance to make support for RX and Vega gpu in RadeonMonitor.kext ?

 

@Slice What about the Pascal GPU support?

To make new hardware support I need specifications/datasheets or code snippets (from linux

If you can find this tell me.

Share this post


Link to post
Share on other sites

Test, please.

Show me kernel messages about the kext.

attachicon.gifGeforceSensor.kext.zip

 

Sorry but I'm travelling and  I won't have access to my computer until Tuesday or so. Hopefully someone else can report kernel messages before.

Thanks!!

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!

Thanks for the updated sensors, just a quick question. Is the GeforceSensor.kext compatible with the Pascal GPUs? 

Share this post


Link to post
Share on other sites

Thanks for the updated sensors, just a quick question. Is the GeforceSensor.kext compatible with the Pascal GPUs? 

I make this, but only temperature. No fan and frequency.

Share this post


Link to post
Share on other sites

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

 

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