FreeJHack Posted July 24, 2020 Share Posted July 24, 2020 (edited) If you're using FakeSMC v.6.26-357.1800 (RehabMan-kozlek) with OpenCore 0.60 (0.5.9), you're most probably having a FakeSMC backtrace and/or random or repetitive crash during boot. Short story: this is due to an error during properties reading. Look at your boot-log, you could find something like this and if you check with IORegistryExplorer the resource FakeSMCKeyStore, the two properties "manufacturer" and "product-name" are missing. I've patched FakeSMC fixing the backtrace and loading the two needed properties In order to correctly load the two properties, it is mandatory set in the OpenCore config.plist file the ExposeSensitiveData->Expose OEM information as a set of UEFI variables = true, in Misc->Security. Then, replace FakeSMC.kext with the patched version and reboot. Check the boot-log and you'd find the string "Trying OpenCore OEM properties..." and with IORegistryExplorer the resource FakeSMCKeyStore: the two properties "manufacturer" and "product-name" should be now available. which is in my case "Clevo" and "P95_96_97Ex,Rx", yours will be, obviously, different. There's NO need to replace the supporting kexts ACPISensors.kext, CPUSensors.kext, ... It's just enough replace FakeSMC.kext Link if you want to build the kext by yourself (remember first the versioning): https://github.com/FreeJHack/OS-X-FakeSMC-kozlek alternatively, the patched FakeSMC kext has been attached. Tested on Mojave and Catalina. Hoping this could help... FakeSMC.kext.zip Edited July 24, 2020 by Allan Remove Format 3 Link to comment Share on other sites More sharing options...
Planet X Posted August 12, 2020 Share Posted August 12, 2020 So when you load that edited FakeSMC.kext then you can have VirtualSMC both together and have the sensors back in OC? Link to comment Share on other sites More sharing options...
FreeJHack Posted August 22, 2020 Author Share Posted August 22, 2020 On 8/12/2020 at 8:19 PM, Planet X said: you can have VirtualSMC both together No VirtualSMC is an alternative to FakeSMC. You cannot run both contemporary. 1 Link to comment Share on other sites More sharing options...
deeveedee Posted February 15, 2021 Share Posted February 15, 2021 (edited) @FreeJHack - Great stuff! For the newbies like me who don't know what 'Expose OEM information as a set of UEFI variables' means, read this (set Misc>Security>ExposeSensitiveData = 8). EDIT: @FreeJHack - I replaced my 'old' FakeSMC.kext with yours and changed Misc>Security>ExposeSensitiveData from 6 to 8 in my OC 0.6.6 config.plist. I can confirm that I now see the missing KeyStore Properties Spoiler Upon boot with OC 0.6.6, I now see the following error flash briefly before the text bootpicker appears: OCS: Failed to parse real field as value with type integer and <214xxxxxx> contents. context <HaltLevel> EDIT2: I found this explanation for the error. After I edited my config.plist (with XCode) to change Misc>Security>ExposeSensitiveData, XCode did change HaltLevel to real. I changed this back to integer and the OCS error is gone now. Thanks again for your FakeSMC fix! Before: Spoiler After: Spoiler Edited February 15, 2021 by tonyx86 Added fix for HaltLevel Link to comment Share on other sites More sharing options...
chris1111 Posted February 15, 2021 Share Posted February 15, 2021 For Clover ? Link to comment Share on other sites More sharing options...
Planet X Posted February 15, 2021 Share Posted February 15, 2021 15 hours ago, tonyx86 said: @FreeJHack - Great stuff! For the newbies like me who don't know what 'Expose OEM information as a set of UEFI variables' means, read this (set Misc>Security>ExposeSensitiveData = 8). EDIT: @FreeJHack - I replaced my 'old' FakeSMC.kext with yours and changed Misc>Security>ExposeSensitiveData from 6 to 8 in my OC 0.6.6 config.plist. I can confirm that I now see the missing KeyStore Properties Reveal hidden contents Upon boot with OC 0.6.6, I now see the following error flash briefly before the text bootpicker appears: OCS: Failed to parse real field as value with type integer and <214xxxxxx> contents. context <HaltLevel> EDIT2: I found this explanation for the error. After I edited my config.plist (with XCode) to change Misc>Security>ExposeSensitiveData, XCode did change HaltLevel to real. I changed this back to integer and the OCS error is gone now. Thanks again for your FakeSMC fix! Before: Reveal hidden contents After: Reveal hidden contents Is there may be something more to do in my config.plist to be able to use FakeSMC? I did exactly what you have written but I cannot boot as soon when I use FakeSMC. In IStatMenus I see only 4 CPU cores at the moment when I use iMac20,2. I wanted to see if may be VirtualSMC is the cause. Link to comment Share on other sites More sharing options...
deeveedee Posted February 15, 2021 Share Posted February 15, 2021 @Planet X I'd need to see your current EFI (at least your config.plist) to have any chance of helping you. If you don't mind posting your EFI, post it with your sanitized config.plist (remove the PlatformInfo private stuff). Link to comment Share on other sites More sharing options...
deeveedee Posted February 15, 2021 Share Posted February 15, 2021 5 hours ago, chris1111 said: For Clover ? It's not just for Clover anymore Link to comment Share on other sites More sharing options...
chris1111 Posted February 15, 2021 Share Posted February 15, 2021 (edited) 1 hour ago, tonyx86 said: It's not just for Clover anymore Why not @Slice FAKESMC works for BS Edited February 16, 2021 by chris1111 1 Link to comment Share on other sites More sharing options...
deeveedee Posted February 16, 2021 Share Posted February 16, 2021 (edited) @chris1111 - I'm not sure I understand. Sorry I 'laughed' at your previous comment - I thought you were joking. I use FakeSMC v.6.26-357.1800 with its Sensors and HWMonitor.app. Not because I don't like others - it's just that I haven't tried others. After I migrated from CLOVER to OC, I kept FakeSMC v.6.26-357.1800 with CPU Sensor and HWMonitor.app. This updated FakeSMC.kext lets me keep my same Sensor kext and HWMonitor.app with OC. With FakeSMC v.6.26-357.1800 and OC 0.6.6, I was experiencing unexpected system restarts after I upgraded my rig's BIOS from v2.14.01 to v2.15 (latest at this time). With FreeJHack's FakeSMC v.6.26-357.1801, I no longer experience these restarts. Why continue to use FakeSMC v.6.26-357.1800 (and now FakeSMC v.6.26-357.1801)? I'm lazy. Edited February 16, 2021 by tonyx86 Link to comment Share on other sites More sharing options...
Matgen84 Posted February 16, 2021 Share Posted February 16, 2021 7 hours ago, tonyx86 said: @chris1111 - I'm not sure I understand. Sorry I 'laughed' at your previous comment - I thought you were joking. I use FakeSMC v.6.26-357.1800 with its Sensors and HWMonitor.app. Not because I don't like others - it's just that I haven't tried others. After I migrated from CLOVER to OC, I kept FakeSMC v.6.26-357.1800 with CPU Sensor and HWMonitor.app. This updated FakeSMC.kext lets me keep my same Sensor kext and HWMonitor.app with OC. With FakeSMC v.6.26-357.1800 and OC 0.6.6, I was experiencing unexpected system restarts after I upgraded my rig's BIOS from v2.14.01 to v2.15 (latest at this time). With FreeJHack's FakeSMC v.6.26-357.1801, I no longer experience these restarts. Why continue to use FakeSMC v.6.26-357.1800 (and now FakeSMC v.6.26-357.1801)? I'm lazy. @chris1111 talk about @Slice FakeSMC: this kext is different than FakeSMC v.6.26-357.1800. So don't laugh, and try it if you want. Sorry for Off-Topic.https://github.com/CloverHackyColor/FakeSMC3_with_plugins 1 Link to comment Share on other sites More sharing options...
deeveedee Posted February 16, 2021 Share Posted February 16, 2021 (edited) To be honest, I never paid enough attention (or thought I needed to pay enough attention) to know that there were multiple products named FakeSMC that were actually completely different products (and not simply different versions of each other). I have used FakeSMC v.6.26-357.1800 (and maybe different versions of it) for as long as I can remember. This has certainly been enlightening. Imagine how silly I feel for thinking that FakeSMC 6 was newer than FakeSMC 3? (now realizing that it's FakeSMC v .6). Glad I finally learned this after Apple switched to their own silicon Edited February 16, 2021 by tonyx86 1 Link to comment Share on other sites More sharing options...
FreeJHack Posted March 13, 2021 Author Share Posted March 13, 2021 On 2/15/2021 at 5:04 AM, tonyx86 said: I replaced my 'old' FakeSMC.kext with yours and changed Misc>Security>ExposeSensitiveData from 6 to 8 in my OC 0.6.6 config.plist. I can confirm that I now see the missing KeyStore Properties @tonyx86 Good and thanks for sharing. Still correctly working with OC 0.6.7 and Mojave 18G8022 Sorry for delay reply, I was unable before ... Link to comment Share on other sites More sharing options...
Recommended Posts