indiekiduk Posted June 2, 2021 Share Posted June 2, 2021 Upgraded to 0.6.9, latest Lilu, latest VirtualSMC inc plugins, noticed can't read CPU temp, did some investigation and noticed the SMCProcessor is not loading. Unfortunately the OC log doesn't output what the name of the invalid parameter is so I'm stuck! 00:849 00:561 OC: Prelinked injection SMCProcessor.kext () - Invalid Parameter 00:858 00:008 OC: Prelinked injection SMCSuperIO.kext () - Invalid Parameter m@imac ~ % /Volumes/EFI/Utilities/acdtinfo/acdtinfo Installed kexts: - Lilu : Yes (1.5.3, published 03.05.2021, RELEASE) - AppleALC : Yes (1.6.0, published 03.05.2021, RELEASE) - AirportBrcmFixup : No - BrightnessKeys : No - CPUFriend : No - CpuTscSync : No - DebugEnhancer : No - HibernationFixup : No - NVMeFix : No - RestrictEvents : No - RTCMemoryFixup : No - SMCBatteryManager : No - SMCProcessor : No - SMCDellSensors : No - SMCLightSensor : No - SMCSuperIO : No - VirtualSMC : Yes (1.2.3, published 03.05.2021, RELEASE) - WhateverGreen : Yes (1.4.9, published 05.04.2021, RELEASE) <dict> <key>Arch</key> <string>x86_64</string> <key>BundlePath</key> <string>SMCProcessor.kext</string> <key>Comment</key> <string></string> <key>Enabled</key> <true/> <key>ExecutablePath</key> <string>Contents/MacOS/SMCProcessor</string> <key>MaxKernel</key> <string></string> <key>MinKernel</key> <string>12.0.0</string> <key>PlistPath</key> <string>Contents/Info.plist</string> </dict> <dict> <key>Arch</key> <string>x86_64</string> <key>BundlePath</key> <string>SMCSuperIO.kext</string> <key>Comment</key> <string></string> <key>Enabled</key> <true/> <key>ExecutablePath</key> <string>Contents/MacOS/SMCSuperIO</string> <key>MaxKernel</key> <string></string> <key>MinKernel</key> <string>12.0.0</string> <key>PlistPath</key> <string>Contents/Info.plist</string> </dict> Link to comment Share on other sites More sharing options...
1Revenger1 Posted June 2, 2021 Share Posted June 2, 2021 (edited) Invalid parameter usually means that either one of the entries in your config.plist are wrong, or you have the order wrong and VirtualSMC isn't there to link against. SMCProcessor/SMCSuperIO both depend on VirtualSMC, so VirtualSMC needs to be before those two kexts in your config.plist. I'm not seeing anything else wrong with your entries taking a quick glance at them Edited June 2, 2021 by 1Revenger1 2 Link to comment Share on other sites More sharing options...
indiekiduk Posted June 2, 2021 Author Share Posted June 2, 2021 Thanks for your prompt reply, you were exactly right! I moved VirtualSMC above and that fixed it. I had no idea the order mattered but it seems obvious now. Thanks again. Link to comment Share on other sites More sharing options...
Andrey1970 Posted June 2, 2021 Share Posted June 2, 2021 Use ocvalidate utilitie. Link to comment Share on other sites More sharing options...
indiekiduk Posted June 6, 2021 Author Share Posted June 6, 2021 On 6/2/2021 at 6:56 PM, Andrey1970 said: Use ocvalidate utilitie. Thanks yep that does detect this problem m@xmac ~ % /Volumes/EFI/Utilities/ocvalidate/ocvalidate /Volumes/EFI/EFI/OC/config.plist Kernel->Add[2] discovers SMCProcessor.kext, but its Parent (VirtualSMC.kext) is either placed after it or is missing! Kernel->Add[3] discovers SMCSuperIO.kext, but its Parent (VirtualSMC.kext) is either placed after it or is missing! CheckKernel returns 2 errors! Completed validating /Volumes/EFI/EFI/OC/config.plist in 1 ms. Found 2 issues requiring attention. Link to comment Share on other sites More sharing options...
Recommended Posts