Jump to content
Slice

RadeonMonitor problems

128 posts in this topic

Recommended Posts

The thread splitted from HWSensors3.
 
Tools to testing Radeon state.
Load RadeonPCI.kext  
RadeonPCI.kext.zip
 
How to load

sudo chown -R root:wheel ~/Downloads/RadeonPCI.kext
sudo chmod -R 755 ~/Downloads/RadeonPCI.kext
sudo kextutil -v ~/Downloads/RadeonPCI.kext

and use RadeonDump utility
RadeonDump1.zip
 
Commands to see temperature
Polaris
./RadeonDump1 -n 6b0,c0300014

SeaIsaland

./RadeonDump1 -n 200,c0300014
 
Old families
./RadeonDump1 -r 714,7f4
 
Other possible methods to find a register for temperature
./RadeonDump1 -n 6b0,c0300e0c
./RadeonDump1 -n 6b0,1c5
./RadeonDump -n 6b0,d8200ca4
./RadeonDump -r 59800,59810
./RadeonDump -r 678,680


 
 
 
01.12.2017
Latest solution RadeonMonitor.kext here
works for RX 460,480,580
not works for HD7790, R9 290X?

 

06.12.2017

Here works also with HD7790, R9 290X

 

14.12.2017

Support VEGA here

 

13.12.2017

Version for test modern cards

RadeonPCI5.kext.zip

Share this post


Link to post
Share on other sites
Advertisement

MSI X79 + E5 2650 v2

2X Asus matrix 290x

El Capitan 10.11.4

 

https://www.dropbox.com/s/yqpdsal9gg36yp1/Zrzut%20ekranu%202016-03-25%20o%2019.15.32.png?dl=0

 

in Clover kext 10.11 folder instaled FakeSMC ver 6.18-313-g671f31c.1707 and ACPI CPU LPC plug in. 

And your RadeonMonitor.kext. 

This is the reason. My RadeonMonitor is incompatible with FakeSMC 6.***. It must be used with FakeSMC 3.4.1. Link to HWSensors3 in my signature.

Share this post


Link to post
Share on other sites

OK. I will try. 


This is the reason. My RadeonMonitor is incompatible with FakeSMC 6.***. It must be used with FakeSMC 3.4.1. Link to HWSensors3 in my signature.

i have black screen after boot with your version of FakeSMC

Share this post


Link to post
Share on other sites

If you boot in verbose mode you can see mesages on the screen telling what is happen with you set of kexts. Not black screen.

Photo this screen when stop.

I can propose that black screen means "FakeSMC was not properly installed"

Share this post


Link to post
Share on other sites

If you boot in verbose mode you can see mesages on the screen telling what is happen with you set of kexts. Not black screen.

Photo this screen when stop.

I can propose that black screen means "FakeSMC was not properly installed"

 

I was booting in verbs mode. It boot from SSD and is very fast. At the end of boot is black screen. (sorry for my english)

Share this post


Link to post
Share on other sites

I was booting in verbs mode. It boot from SSD and is very fast. At the end of boot is black screen. (sorry for my english)

It means "FakeSMC is not properly installed"

Share this post


Link to post
Share on other sites

Hi Slice!

 

Thank you for your work!

 

@all

 

Has anyone gotten the RadeonMonitor.kext to play nice with a R9 390 - 0x67B11002 in AMD8000 and in AMDRadeonX4000 under Hawaii -and HWMonitoSMC?

 

If I put it in SLE - chmod -R 755 & chown -R 0:0 & touch SLE- 10.11 starts up fine, kextstat lists it as loaded and kextutility -v also checks out.

 

But as soon as I start HWMonitor it crashes while showing the beginning of the icon animation, looks like its exploding ;)

 

btw, HWInfo leads to a direct KP with console output in the upper left corner.

 

If I remove the kexts and restart, HWMonitor loads fine. I was mostly interested in using it to control the fans of my R9 390 and system fans.

Share this post


Link to post
Share on other sites

Update:

 

yep, gpurestart. For anyone interested in R9 390s gpurestarts I will link to my post in Hardware/Graphics Cards/ATI in a bit.

 

could be something else but I guess it the R9 390 is the culprit.

 

edit:

here is my post http://www.insanelymac.com/forum/topic/312607-r9-390-black-screen-gpurestart/

Test please this version of RadeonMonitor             #220            

sudo -s

chown -R root:wheel ~/Downloads/RadeonMonitor.kext

chmod -R 755 ~/Downloads/RadeonMonitor.kext

kextutil -v ~/Downloads/RadeonMonitor.kext

and show the terminal output

Share this post


Link to post
Share on other sites

Test please this version of RadeonMonitor             #220            

sudo -s

chown -R root:wheel ~/Downloads/RadeonMonitor.kext

chmod -R 755 ~/Downloads/RadeonMonitor.kext

kextutil -v ~/Downloads/RadeonMonitor.kext

and show the terminal output

Password:

bash-3.2# chown -R root:wheel ~/Downloads/RadeonMonitor.kext

bash-3.2# chmod -R 755 ~/Downloads/RadeonMonitor.kext

bash-3.2# kextutil -v ~/Downloads/RadeonMonitor.kext

Defaulting to kernel file '/System/Library/Kernels/kernel'

/Users/mateuszjachym/Downloads/RadeonMonitor.kext - dependency 'org.netkas.FakeSMC' not found.

/Users/mateuszjachym/Downloads/RadeonMonitor.kext - dependency 'org.netkas.FakeSMC' not found.

/Users/mateuszjachym/Downloads/RadeonMonitor.kext - dependency 'org.netkas.FakeSMC' not found.

Diagnostics for /Users/mateuszjachym/Downloads/RadeonMonitor.kext:

Dependency Resolution Failures: 

    No kexts found for these libraries: 

        org.netkas.FakeSMC

 

Code Signing Failure: not code signed

bash-3.2# 

 

Share this post


Link to post
Share on other sites

My RadeonMonitor must be used with my FakeSMC which is "not found"

Mateuszs-Mac-Pro:~ mateuszjachym$ sudo -s

bash-3.2# chown -R root:wheel ~/Downloads/RadeonMonitor.kext

bash-3.2# chmod -R 755 ~/Downloads/RadeonMonitor.kext

bash-3.2# kextutil -v ~/Downloads/RadeonMonitor.kext

Defaulting to kernel file '/System/Library/Kernels/kernel'

Diagnostics for /Users/mateuszjachym/Downloads/RadeonMonitor.kext:

Code Signing Failure: not code signed

/Users/mateuszjachym/Downloads/RadeonMonitor.kext appears to be loadable (not including linkage for on-disk libraries).

kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext "/Users/mateuszjachym/Downloads/RadeonMonitor.kext"

kext signature failure override allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext "/System/Library/Extensions/FakeSMC.kext"

kext signature failure override allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext "/Users/mateuszjachym/Downloads/RadeonMonitor.kext"

Loading /Users/mateuszjachym/Downloads/RadeonMonitor.kext.

/Users/mateuszjachym/Downloads/RadeonMonitor.kext successfully loaded (or already loaded).

 

bash-3.2#

Share this post


Link to post
Share on other sites

 

Mateuszs-Mac-Pro:~ mateuszjachym$ sudo -s

bash-3.2# chown -R root:wheel ~/Downloads/RadeonMonitor.kext

bash-3.2# chmod -R 755 ~/Downloads/RadeonMonitor.kext

bash-3.2# kextutil -v ~/Downloads/RadeonMonitor.kext

Defaulting to kernel file '/System/Library/Kernels/kernel'

Diagnostics for /Users/mateuszjachym/Downloads/RadeonMonitor.kext:

Code Signing Failure: not code signed

/Users/mateuszjachym/Downloads/RadeonMonitor.kext appears to be loadable (not including linkage for on-disk libraries).

kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext "/Users/mateuszjachym/Downloads/RadeonMonitor.kext"

kext signature failure override allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext "/System/Library/Extensions/FakeSMC.kext"

kext signature failure override allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext "/Users/mateuszjachym/Downloads/RadeonMonitor.kext"

Loading /Users/mateuszjachym/Downloads/RadeonMonitor.kext.

/Users/mateuszjachym/Downloads/RadeonMonitor.kext successfully loaded (or already loaded).

 

bash-3.2#

 

Successfully loaded. Now look to system.log about RadeonMonitor. There should be messages from it.

Or just make full DarwinDumper report (without BIOS to reduce the space).

Share this post


Link to post
Share on other sites

Jun 21 11:26:26 Mateuszs-Mac-Pro kernel[0]: RadeonMonitor: found Radeon chip id=67b0 

Jun 21 11:26:26 Mateuszs-Mac-Pro kernel[0]: Found ATI Radeon 67b0
Jun 21 11:26:37 Mateuszs-Mac-Pro loginwindow[98]: -[sFLListManager(ServiceReplyProtocol) notifyChanges:toListWithIdentifier:] Notified of item changes to list with identifier com.apple.LSSharedFileList.RecentApplications
Jun 21 11:26:46 --- last message repeated 1 time ---
Jun 21 11:26:46 Mateuszs-Mac-Pro Console[608]: Failed to connect (_consoleX) outlet from (NSApplication) to (ConsoleX): missing setter or instance variable
 
And DarwinDumper raport: 
 

Share this post


Link to post
Share on other sites

 

Jun 21 11:26:26 Mateuszs-Mac-Pro kernel[0]: RadeonMonitor: found Radeon chip id=67b0 

Jun 21 11:26:26 Mateuszs-Mac-Pro kernel[0]: Found ATI Radeon 67b0
Jun 21 11:26:37 Mateuszs-Mac-Pro loginwindow[98]: -[sFLListManager(ServiceReplyProtocol) notifyChanges:toListWithIdentifier:] Notified of item changes to list with identifier com.apple.LSSharedFileList.RecentApplications
Jun 21 11:26:46 --- last message repeated 1 time ---
Jun 21 11:26:46 Mateuszs-Mac-Pro Console[608]: Failed to connect (_consoleX) outlet from (NSApplication) to (ConsoleX): missing setter or instance variable
 
And DarwinDumper raport: 
 

 

Please remove BIOS and already compressed report, don't make HTML report and your file will be 100kb instead of your 248Mb

Share this post


Link to post
Share on other sites

OK, it is better while... I was asking to do this after loading RadeonMonitor to see it works.

Anyway i see one problem, you have two cards and I am not sure how RadeonMonitor will work with them.

Share this post


Link to post
Share on other sites

Link KP

 

my card is Sapphire Radeon RX 460 OC 

1002:67ef Subsystem: 174b:e348

 

$ log show --predicate "processID == 0" --start 2017-03-26 --debug | grep RadeonMonitor

2017-03-23 22:14:09.946236+0100 0x72       Default     0x0                  0      kernel: (kernel) RadeonMonitor: found Radeon chip id=67ef

2017-03-24 21:58:05.966024+0100 0x72       Default     0x0                  0      kernel: (kernel) RadeonMonitor: found Radeon chip id=67ef

2017-03-26 07:42:03.925394+0200 0x72       Default     0x0                  0      kernel: (kernel) RadeonMonitor: found Radeon chip id=67ef

2017-03-26 07:42:56.239864+0200 0x72       Default     0x0                  0      kernel: (kernel) RadeonMonitor: found Radeon chip id=67ef


2017-03-26 07:42:56.177283+0200 0x72       Default     0x0                  0      kernel: (kernel) HWInfo: SMC Platform: j95

2017-03-26 07:42:56.181681+0200 0x72       Default     0x0                  0      kernel: (kernel) HWInfo: SMC Branch: j95j95a

2017-03-26 07:42:56.186129+0200 0x72       Default     0x0                  0      kernel: (kernel) HWInfo: SMC Revision set to: 2.33f10

2017-03-26 07:42:56.190771+0200 0x72       Default     0x0                  0      kernel: (kernel) HWInfo: SMC ConfigID set to: 08 c0 f0 00

2017-03-26 07:42:56.195485+0200 0x72       Default     0x0                  0      kernel: (kernel) IntelCPUMonitor: CPU family 0x6, model 0x9e, stepping 0x9, cores 4, threads 8

2017-03-26 07:42:56.201013+0200 0x72       Default     0x0                  0      kernel: (kernel) IntelCPUMonitor: Using efi

2017-03-26 07:42:56.205466+0200 0x72       Default     0x0                  0      kernel: (kernel) IntelCPUMonitor: BusClock=100MHz FSB=400MHz

2017-03-26 07:42:56.212608+0200 0x72       Default     0x0                  0      kernel: (kernel) IntelCPUMonitor: CPU0 Tjmax 100

2017-03-26 07:42:56.217249+0200 0x72       Default     0x0                  0      kernel: (kernel) IntelCPUMonitor: CPU1 Tjmax 100

2017-03-26 07:42:56.221753+0200 0x72       Default     0x0                  0      kernel: (kernel) IntelCPUMonitor: CPU2 Tjmax 100

2017-03-26 07:42:56.226208+0200 0x72       Default     0x0                  0      kernel: (kernel) IntelCPUMonitor: CPU3 Tjmax 100

2017-03-26 07:42:56.230625+0200 0x72       Default     0x0                  0      kernel: (kernel) W836x: found NCT6791D

2017-03-26 07:42:56.234794+0200 0x72       Default     0x0                  0      kernel: (kernel) W836x:  mother vendor=ASRock product=Z270 Gaming K4

2017-03-26 07:42:56.239864+0200 0x72       Default     0x0                  0      kernel: (kernel) RadeonMonitor: found Radeon chip id=67ef

2017-03-26 07:42:56.246835+0200 0x72       Default     0x0                  0      kernel: (kernel)  Common ATI Radeon like HAWAII DID=67ef

2017-03

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 Slice
      Guys,
      Don't mix 6.18 and 3.41.
       
      There are three different projects for monitoring temperatures, voltages, fans speed and other hardware parameters:
      Initially it was FakeSMC with plugins for producing SMC keys for hardware parameters for different hardware. But sometimes ago Kozlek separated own version of FakeSMC and producing new set of plugins while I stay with good working version 3. So..
      1. FakeSMC v3 with Hardware Sensors3  which I still supported.
      2. FakeSMC v6 (rev1800) by Kozlek and supported by Rehabman. AFAIK both are abandoned and the project is not supported. Or may be maintained by coauthors.
      3. New VirtualSMC by vit9696 with own set of sensors kexts. It depends on Lilu.kext. The project is in active development.
      All three project have incompatible interfaces sensors<->SMC so they are incompatible with each other.
       
      There are applications for monitoring hardware parameters and they commonly depends on these projects.
      1. iStat, iStatMenu, iStatPro compatible with real Macs because they use SMC keys just like those presents in real Macs.
      2. HWMonitorSMC by Navi (initial codes from Kozlek)  used in my HWSensors3.
      3. HWMonitor by Kozlek with graphics like in IntelPowerGadget used in his HWSensors version.
      4. HWMonitorSMC2 by Vector_Sigma tends to be universal supporting all project. It also may use sensors information produces by Apple graphics and by IntelPowerGadget.
       
      Let us discuss here differences and common ideas for this projects.
       
    • By Slice
      This thread devoted to share information about different SMC keys found or investigated anywhere.
       
      What are they?
      SMC keys is a somehow language to speak between macOS and hardware microcontroller presented in real Mac and absent in Hackintosh.
      They inform macOS about Hardware ID and current status. Moreover macOS can write something through SMC protocol to control hardware.
      FakeSMC ( ©Netkas) is the driver to emulate this microcontroller on PC having no such device which is necessary to boot macOS here.
      But FakeSMC contain only ~20 keys while real Mac answers ~200 keys.
      Some keys we added by HWSensors project reporting temperatures, FAN speeds, voltages etc.
      Some keys are model dependent was added by Clover to be sure if user changed model in GUI then corresponding keys will be changed automatically.
      Clover sets
      LogDataHub(&gEfiMiscSubClassGuid, L"RPlt", &gSettings.RPlt, 8);
      LogDataHub(&gEfiMiscSubClassGuid, L"RBr", &gSettings.RBr, 8);
      LogDataHub(&gEfiMiscSubClassGuid, L"EPCI", &gSettings.EPCI, 4);
      LogDataHub(&gEfiMiscSubClassGuid, L"REV", &gSettings.REV, 6);
      LogDataHub(&gEfiMiscSubClassGuid, L"BEMB", &gSettings.Mobile, 1);
      BEMB - is a mobility sign. =0 -desktop, =1 - mobile.
      REV - SMC hardware revision, changes sometimes with Apple updates.
      RPlt, RBr and EPCI is hardware capabilities, noticed used in Intel HD drivers.
       
      Structure.
      All SMC keys consists of name 4 ascii chars as 32bit integer, type and value.
      Types:
       "flag", len 1
       "ui8 ", len 1
       "ui16", len 2
       "sp78", len 2
       "ui32", len 4
      "fp2e", len 2
      "fpe2", len 2
      "{rev", and others...
       
      List of known keys
      SMC_list.plist.zip
      More keys will be discussed in the thread
       
       
      Feel free to share you knowledge and ask about noticed keys.
    • By Slice
      As I see many novices in the forum ask "How to make my Radeon working? I have bad resolution, no QE/CI...." and so on. They come to the section and have no find an answer here because all Radeons are different and they don't know where else they read about this.
      I want to explain all steps needed for launching the Radeon family of videocards.
       
      Bootloader.
      I will speak about Clover because I maintain this bootloader to know recent hardware and modern OSX. Not sure if you will have the same result with other bootloaders. I am carefully checking the injecting of ATI card and correcting it times to times. I am also accessible for bug reports.
       
      OSX version.
      Older card require older system, newer cards require new system.
      ATIRadeon9000 is possible to launch under Tiger.
      ATIRadeonMobilityX1400 requires 10.5-10.6. See RadeonHD topic.
      As I see RadeonHD3xxx was successful only in 10.5
      For new AMDRadeonHD7xxx there must be 10.8.3+ system.
       
      DeviceID.
      This must be the first question before asking about the card.
      You may know the device-id from Windows->DeviceManger->VideoCard.properties->compatibleIDs
      You may boot into system in safe mode (key -x) and see system profiler
       
      And you may boot into Clover GUI, press F2 and get preboot.log. Find here something like
      2:709 0:000 PCI (00|01:00.00) : 1002 6758 class=030000 2:709 0:000 Found Radeon model=AMD Radeon HD 6670 Series It means my DeviceID=6758 (these are hex numbers)
      Then you must check that Apple's drivers support your DeviceID. If not then add it!
      For example HD7850 has DeviceID=6819. If we look into ATI7000Controller (AMD7000... in new systems) we find 6818 here but no 6819!
       
       
      I show you how to do this with terminal commands. Launch /Application/Utilities/Terminal.app. Type in opened window:
       
      cp /System/Library/Extensions/ATI7000Controller.kext/Contents/Info.plist ~/Desktop So you get a copy of the Info.plist on Desktop. Edit it with TextEdit. Change 68181002 -> 68191002.
      Don't edit this file directly in the system folder! 
      Then copy back by terminal. Don't use finder to copy kexts! They will have wrong permissions in this case.
      sudo cp ~/Desktop/Info.plist /System/Library/Extensions/ATI7000Controller.kext/Contents/ sudo rm -r -v /System/Library/Caches/com.apple.kext.caches/* Second command make sure next reboot the kext will use your edited info.plist.
      The same operation you must do with a kext AMDRadeonAccelerator or ATIRadeonX2000 or other one. Check all candidates if they contain such list of possible IDs and choose closest to you.
       
      FakeID
      Since Clover revision 1971+ you may just inject new DeviceID into DSDT instead of correcting kexts. See instruction here.
       
      GraphicsEnabler or Injector
      OSX needs to know some properties (Model name, Family, etc...) that must be somehow injected at boot time. Yes, also real Macs got DeviceProperties string from firmware.
      Alternatives:
      1. Set InjectATI=Yes in Clover (same as GE=y in Chameleon).
      2. Use custom string made with gfxutil. For whom who knows.
      3. Write _DSM into DSDT. You should know what to write.
      4. Use some kext like ATY_init.kext or Natit.kext. If you are sure that the kext is for your card namely.
      I want to say that all this methods make the same thing. Differencies in their tuning.
      The Clover do this automatically for most known cards at this moment.
       
      Connectors.
      As you may see to start HD5000-7000 some strange names used: Pithecia, Orangutan, Elodea... What are they?
      They are configs for framebuffer. Predefined configs how connectors are solded for cards used in real Macs. Strange but these configs rear coincide with PC card. Usually gurus make advice "choose a framebuffer that most appropriate for your card". The chances 1:10. In most cases you may find a FB name that gives you main monitor working. Or nothing at all.
      Great respect to bcc9 who gives us a method to correct one of config to be exactly for you. See here.
      My retelling for Clover is here
      Success example in the thread in posts 44-52
       
      Radeon Mobility
      I tested Clover's methods with two users having Mobility Radeon HD5470 and HD5650M. We found that full memory and QE/CI will be achieved if we set in Clover's config
      LoadVBios=Yes
      even thou no file with bios is provided. This is the key to make Radeon Mobility working!
      Other problem is bad gradients or artifacts. For this case Clover accept the key
      InjectEDID=Yes
      and sometimes you also need to inject CustomEDID.
      See Clover instructions for details.
       
      And my results.
      Gigabyte Radeon HD6670
      <key>Graphics</key> <dict> <key>GraphicsInjector</key> <true/> <key>InjectEDID</key> <true/> <key>FBName</key> <string>Ipomoea</string> <key>LoadVBios</key> <false/> <key>VideoPorts</key> <integer>3</integer> <key>PatchVBios</key> <true/> </dict> <key>KernelAndKextPatches</key> <dict> <key>KernelCpu</key> <false/> <key>ATIConnectorsController</key> <string>6000</string> <key>ATIConnectorsData</key> <string>000400000403000000010000120401050008000004020000000100001102040310000000100000000001000000000002</string> <key>ATIConnectorsPatch</key> <string>040000000403000000010000100001061000000010000000000100000000000100080000040200000001000012040403</string> VTX Radeon HD5570
      <key>Graphics</key> <dict> <key>PatchVBios</key> <false/> <key>FBName</key> <string>Baboon</string> <key>VideoPorts</key> <string>3</string> <key>GraphicsInjector</key> <string>Yes</string> <key>LoadVBios</key> <string>No</string> </dict> <key>KernelAndKextPatches</key> <dict> <key>Debug</key> <false/> <key>KernelCpu</key> <false/> <key>ATIConnectorsController</key> <string>5000</string> <key>ATIConnectorsData</key> <string>040000001400000000010000010201030008000000020000007100002205020110000000100000000001000000100002</string> <key>AppleRTC</key> <true/> <key>ATIConnectorsPatch</key> <string>040000001400000000010000010001040008000000020000007100002200020510000000100000000001000000000002</string> <key>AsusAICPUPM</key> <false/> <key>KextsToPatch</key> <array> <dict> <key>Name</key> <string>AppleAHCIPort</string> <key>Find</key> <data>RXh0ZXJuYWw=</data> <key>Replace</key> <data>SW50ZXJuYWw=</data> </dict> </array> </dict> See PatchVBios=No
      for this card "yes" leads to black screen. Use with precautions.
       
      A sample for Radeon R7 240
       
      UPDATE for ElCapitan.
      It seems has more problems. My HD6670 is not working in ElCapitan OOB unlike Mavericks.
      I had to set FakeID=0x67401002 as correspond to real iMac12,2 and set this model in SMBIOS section.
      It related to GraphicsPM or GraphicsControl.
      Look these kexts to decide what you can do for your configuration.
       
      HighSierra requires change these kexts by version from Sierra 10.12.6
      for Radeon HD6xxx
      AMDRadeonX3000.kext AMDRadeonX3000GLDriver.bundle IOAccelerator2D.plugin IOAcceleratorFamily2.kext .  for Radeon HD7xxx and up AMDRadeonX4000.kext AMDRadeonX4000GLDriver.bundle IOAccelerator2D.plugin IOAcceleratorFamily2.kext .    Black screen after wake problem resolved by follow method radeon_bios_decode.0.2.zip
      ati-personality.pl.0.15.zip
      ati-personality.pl.0.15a.zip
    • By Slice
      Hi all,
       
      I created an installer for my version of FakeSMC with plugins and applications latest revision.
       
      Compatibility from 10.6 up to 10.15.
      Test, please.

      Download here: HWSensors.pkg.zip
      See my signature
       
      02.11.2019
      New project home
      https://github.com/CloverHackyColor/FakeSMC3_with_plugins
      FakeSMC v3.5.3 and plugins
       
      HWMonitorSMC2 at
      https://github.com/CloverHackyColor/HWMonitorSMC2
       
       
      FakeSMC 3.4.0 revision 751
      HWSensors.pkg-751.zip
       
      New project home is
      https://sourceforge.net/projects/hwsensors3.hwsensors.p/
      where you can download most recent versions.
      Now it is FakeSMC 3.4.1
       
      Explanations about the difference between versions 3 and 6
        #137 
       
      20.05.2016
      Revision 32 with explanation at    #220 
       
      10.10.2017
      FakeSMC is 3.5.0 compatible with High Sierra.
      New plugin VoodooBatterySMC created on the base of VoodooBattery by Superhai but with SMC keys generating to show Battery voltage and amperage. As well it created key BATP needed for right speedstep and FileVault2.
      Other kexts revised.
×