xpamamadeus Posted April 8, 2014 Author Share Posted April 8, 2014 Still don't work! Yesterday i was speaking with kozlek in (github.com) about transforming FakeSMC.kext to SMCKextEmulator.kext to make it work, and he told me to rename it as SMCKextEmulator.kext and try! "kozlek commented 5 hours ago Oh really, just rename it to SMCEmulatorKext If you get this one from archive you provided, open it's info.plist you'll see it's the same FakeSMC but only file has been renamed to SMCEmulatorKext.kext. Do it FakeSMC.kext - > SMCEmulatorKext.kext. As i already say. u give him wrong info and he told u to rename... This has nothing with name of kexts... It seems thats some bug with latest ozmosis only becouse all fakesmc versions work with previous one. Default one work with Hasswell,and slice version work with haswell,for some users latest kozlek version work with haswell soo its not hasswell or fakesmc problem but latest ozmosis. Some people use this on ivy,sandy systems and latest kozlek version dont work with latest ozmosis but some previous version does. u can read whole thread and u will find out what version work for who. just w8 for ozmosis update and maybe it will be fixed. EDIT:i try to install HWSensors.6.4.1218 to S/L/E and it works just fine with ozmosis. HWmonitor There are also some errors with this now in console 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR TC1H kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR TC1H kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR TC2H kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR TC2H kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR TC3H kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR TC3H kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR TC4D kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR TC4D kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR TC4H kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR TC4H kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR TC5D kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR TC5D kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR TC5H kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR TC5H kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR TC6D kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR TC6D kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR TC6H kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR TC6H kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR TC7D kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR TC7D kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR TC7H kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR TC7H kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR TC8D kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR TC8D kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR TC8H kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR TC8H kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR TC9D kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR TC9D kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR TC9H kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR TC9H kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR TC0P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR TC0P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR Th0H kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR Th0H kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR TN0P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR TN0P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR TG0D kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR TG0D kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR TG0H kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR TG0H kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR TG0P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR TG0P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR TG1D kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR TG1D kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR TG1H kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR TG1H kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR TG1P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR TG1P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR TG2D kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR TG2D kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR TG2H kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR TG2H kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR TG2P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR TG2P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR TG3D kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR TG3D kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR TG3H kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR TG3H kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR TG3P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR TG3P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR TG4D kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR TG4D kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR TG4H kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR TG4H kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR TG4P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR TG4P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR TG5D kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR TG5D kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR TG5H kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR TG5H kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR TG5P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR TG5P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR TG6D kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR TG6D kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR TG6H kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR TG6H kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR TG6P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR TG6P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR TG7D kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR TG7D kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR TG7H kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR TG7H kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR TG7P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR TG7P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR TG8D kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR TG8D kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR TG8H kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR TG8H kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR TG8P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR TG8P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR TG9D kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR TG9D kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR TG9H kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR TG9H kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR TG9P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR TG9P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR FRC0 kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR FRC1 kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR FRC2 kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR FRC3 kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR FRC4 kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR FRC5 kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR FRC6 kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR FRC7 kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR FRC8 kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR FRC9 kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR FRCA kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR FRCB kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR FRCC kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR FRCD kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR FRCE kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR FRCF kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR CG0C kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR CG0S kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR CG1C kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR CG1S kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR CG2C kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR CG2S kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR CG3C kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR CG3S kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR CG4C kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR CG4S kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR CG5C kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR CG5S kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR CG6C kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR CG6S kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR CG7C kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR CG7S kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR CG8C kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR CG8S kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR CG9C kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR CG9S kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR MC0C kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR MC1C kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR MC2C kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR MC3C kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR MC4C kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR MC5C kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR MC6C kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR MC7C kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR MC8C kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR MC9C kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR MPkC kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR VS0C kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR VS0C kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR VP0R kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR VP0R kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR Vp0C kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR Vp0C kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR VBAT kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR VBAT kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR VC0G kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR VC0G kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR VC1G kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR VC1G kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR VC2G kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR VC2G kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR VC3G kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR VC3G kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR VC4G kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR VC4G kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR VC5G kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR VC5G kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR VC6G kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR VC6G kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR VC7G kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR VC7G kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR VC8G kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR VC8G kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR VC9G kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR VC9G kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR F5ID kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR F5Ac kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR F5Ac kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR F6ID kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR F6Ac kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR F6Ac kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR F7ID kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR F7Ac kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR F7Ac kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR F8ID kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR F8Ac kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR F8Ac kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR F9ID kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR F9Ac kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 08/04/14 03:13:24,000 kernel[0]: SMC::smcReadKeyAction ERROR F9Ac kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8018712000 2 Link to comment Share on other sites More sharing options...
ammoune78 Posted April 8, 2014 Share Posted April 8, 2014 Thank's xpamamadeus! I see now, the problem is in latest Ozmosis and not SmcEmulatorKext! I've tested a second time the Slice FakeSMC and it works! Do you know how to rollback the .ffs to .kext? Link to comment Share on other sites More sharing options...
Aigors Posted April 8, 2014 Share Posted April 8, 2014 A good news for me if you use ozmo 828 you can insert ALXEthernet kext in bios with kozlek last version FakeSMC , using a vanilla usb key for mavericks you can restore Time-machine backup if you have it one , i'm happy the only open problem is DSDT we are waiting Fred if he have good news, if he fix the problem, we can integrate everything in bios room permitted Link to comment Share on other sites More sharing options...
Aigors Posted April 8, 2014 Share Posted April 8, 2014 One Question, someone knows if it's possible permit network boot via uefi so pc with ozmosis can install osx via network? cpuld be usefull to have a real mac-efi bios extract netwprk part that acts like network boot and try to integrate in ami bios, but i think i'm dreaming Link to comment Share on other sites More sharing options...
ammoune78 Posted April 8, 2014 Share Posted April 8, 2014 One Question, someone knows if it's possible permit network boot via uefi so pc with ozmosis can install osx via network? cpuld be usefull to have a real mac-efi bios extract netwprk part that acts like network boot and try to integrate in ami bios, but i think i'm dreaming I don't know if it's possible, but you can reinstall OS X via Recovery HD with your AppleID. So you have to integrate your Network Kext into the Bios, like that you can format your OS X partition and redownload the entire OS X to install it! I've tested it and it's working If someone knows how to convert .ffs file to .kext, like SmcEmulatorKext.ffs, because i want to integrate inside it some kexts! Please Please Please Link to comment Share on other sites More sharing options...
Aigors Posted April 8, 2014 Share Posted April 8, 2014 Sorry i was on my cell i say, use a fakesmc do your mod and use kext2ffs to transform and integrate in bios Link to comment Share on other sites More sharing options...
PJALM© Posted April 8, 2014 Share Posted April 8, 2014 The script to convert the kext to ffs dosn't support plugins inside kexts anyhow so why do u want to do that? Link to comment Share on other sites More sharing options...
ammoune78 Posted April 8, 2014 Share Posted April 8, 2014 Sorry i was on my cell i say, use a fakesmc do your mod and use kext2ffs to transform and integrate in bios The latest FakeSMC don't work with this Ozmosis 894M, but with the 828M i've integrate The latest FakeSMC with all my kext IONetworking+ AppleIntele1000e+ IOAHCIfamilly+ IOAHCIblockstorageinjector+ IOAHCIblockstorage The script to convert the kext to ffs dosn't support plugins inside kexts anyhow so why do u want to do that? OK OK PJALM i didn't know it! Because i want to integrate inside SmcEmulatorKext some kexts like: IONetworking+ AppleIntele1000e+ IOAHCIfamilly+ IOAHCIblockstorageinjector+ IOAHCIblockstorage! Link to comment Share on other sites More sharing options...
Aigors Posted April 8, 2014 Share Posted April 8, 2014 Why do you want add all those kexts in FakeSMC? The script to convert the kext to ffs dosn't support plugins inside kexts anyhow so why do u want to do that? But with kext2ffs you can process IONetworking kext that include some others kexts, i'm not so skilled, but it seems tha same thing Link to comment Share on other sites More sharing options...
PJALM© Posted April 8, 2014 Share Posted April 8, 2014 If u check the size of IONetworking with and without those extra kexts the result is exact same thing, those extras are not included. Just do them separately as you really don't gain anything at all even if they did work as plugins. Link to comment Share on other sites More sharing options...
ammoune78 Posted April 8, 2014 Share Posted April 8, 2014 I'm using UEFITools from CodeRush soft does not refuse to integrate bigger dsdt, but it does not boot. Maybe checksum issue or other i must investigate. Fred Hi FredWst! Did you successfully managed to integrate the DSDT in bios with large size? Link to comment Share on other sites More sharing options...
Aigors Posted April 8, 2014 Share Posted April 8, 2014 Hi FredWst! Did you successfully managed to integrate the DSDT in bios with large size? I think no, if he have some news, i think he posted here some result Link to comment Share on other sites More sharing options...
ammoune78 Posted April 8, 2014 Share Posted April 8, 2014 EDIT:i try to install HWSensors.6.4.1218 to S/L/E and it works just fine with ozmosis. There are also some errors with this now in console Thank's it works fine for me to, but i don't have errors! Is it because i tried with original SmcEmulatorKext from the Ozmosis 894M and i have installed on S/L/E: FakeSMC 6.4.1220 with all he's sensors and kexts that i need. I think no, if he have some news, i think he posted here some result Yes he has BlackScreen in the power ON with he's PC, but i don't know if he has switch on the motherboard to Flash the main bios with the BackUp one! And i really hope that he's Board works again!!!! Link to comment Share on other sites More sharing options...
Aigors Posted April 8, 2014 Share Posted April 8, 2014 I hope too I have a spi programmer, so i can program bios chip by myself, but with gigabyte you have double bios but it's' not so safe, if the backup bios can't start the copy process, you have to short pin 5 and 6 of main bios, start main board, and after 2 seconds take off short circuits from pin 5 and 6, the main board restart, and the copy process start Asus have a different recovery procedure, but the mainbiard have a chip in socket, so it's easy remove and reprogram if you have a programmer, it's' cheap from ebay almost 35$ I'm using UEFITools from CodeRush soft does not refuse to integrate bigger dsdt, but it does not boot. Maybe checksum issue or other i must investigate. Fred Can you try with mmtool? if you want we can try for you, i have robust bios recovery tools ( spi programmer) and i can try with different kind of mobo, asus, gigabyte, z77 and z87 i have also and asrock h77m asus and asrock are very easy to unbrick, they have socket with bios chip so i can reprogram, Gigabyte have dual bios but there is a simple procedure to recover if auto recover don't start Link to comment Share on other sites More sharing options...
ammoune78 Posted April 8, 2014 Share Posted April 8, 2014 I think its very easy! The last week i was flashing the bios with corrupted one, after a first reboot BlackScreen! Then it's simple: Step 1: Shut down the computer Step 2: Press the power bouton during 5 second until the system shut down them self Step 3: Release the power bouton Step 4: Now the computer is off, press the power bouton again and release it instantly Step 5: Now the system is powered on, and you can see the main bios recovery being performed. It's for users that didn't have a switch onboard !!! Link to comment Share on other sites More sharing options...
Israel Fernandes Posted April 9, 2014 Share Posted April 9, 2014 Good night, efetuei a test today to try to decrease the size of the DSDT. I extracted it, turned it into dsl, I applied the patches, and compared the sizes, I saw that the files had many comments with / /. I removed all the comments dsdt patched, and even got smaller even than the original dsl. But when compiling the file back to its original size, is there any way to compile without the comments? so could make it less dsdt without losing the patches. Original DSL http://www.sendspace.com/file/ltlanz Patched DSL http://www.sendspace.com/file/oh4b8w Link to comment Share on other sites More sharing options...
PJALM© Posted April 9, 2014 Share Posted April 9, 2014 Comments do not compile into a AML file, they are simply added back when u decompile it to edit again. Link to comment Share on other sites More sharing options...
FredWst Posted April 9, 2014 Share Posted April 9, 2014 I hope too I have a spi programmer, so i can program bios chip by myself, but with gigabyte you have double bios but it's' not so safe, if the backup bios can't start the copy process, you have to short pin 5 and 6 of main bios, start main board, and after 2 seconds take off short circuits from pin 5 and 6, the main board restart, and the copy process start Asus have a different recovery procedure, but the mainbiard have a chip in socket, so it's easy remove and reprogram if you have a programmer, it's' cheap from ebay almost 35$ Can you try with mmtool? if you want we can try for you, i have robust bios recovery tools ( spi programmer) and i can try with different kind of mobo, asus, gigabyte, z77 and z87 i have also and asrock h77m asus and asrock are very easy to unbrick, they have socket with bios chip so i can reprogram, Gigabyte have dual bios but there is a simple procedure to recover if auto recover don't start I've try with MMTOOLS same issue. Gigabyte bios recovery works fine. is there code part in module ? if yes maybe there is hard coded address. i'll check. Edit: If i'm wright, i've found some hard offset witch accessing addresses after DSDT location. i'll try to manually patch this evening. Fred Link to comment Share on other sites More sharing options...
Aigors Posted April 9, 2014 Share Posted April 9, 2014 I've try with MMTOOLS same issue. Gigabyte bios recovery works fine. is there code part in module ? if yes maybe there is hard coded address. i'll check. Edit: If i'm wright, i've found some hard offset witch accessing addresses after DSDT location. i'll try to manually patch this evening. Fred We waith for you news if you need something, ask ;-) Link to comment Share on other sites More sharing options...
Aigors Posted April 9, 2014 Share Posted April 9, 2014 I've try with MMTOOLS same issue. Gigabyte bios recovery works fine. is there code part in module ? if yes maybe there is hard coded address. i'll check. Edit: If i'm wright, i've found some hard offset witch accessing addresses after DSDT location. i'll try to manually patch this evening. Fred Hi Fred, i dont want bother you, have you read this http://forums.mydigitallife.info/threads/48979-UEFITool-UEFI-firmware-image-viewer-and-editor?p=869225&viewfull=1#post869225 master coderush explain how dsdt is inserted into AmiBoardInfo.ffs i dont know if it helps your already great work Link to comment Share on other sites More sharing options...
unexpected_eof Posted April 9, 2014 Share Posted April 9, 2014 So, it's PE32+ - this makes sense, but it won't be easy to rebuild AmiBoardInfo structure with a modified (bigger) DSDT. It seems that DSDT is in the data section and only reloc section is following. 1 Link to comment Share on other sites More sharing options...
Aigors Posted April 9, 2014 Share Posted April 9, 2014 So, it's PE32+ - this makes sense, but it won't be easy to rebuild AmiBoardInfo structure with a modified (bigger) DSDT. It seems that DSDT is in the data section and only reloc section is following. i'm not a programmer, and i dont know deep internal stuff, but could be insert dsdt and move reloc section, but i dont know if we need to recalculate some address, offset and so on, if yes, we have tu know the logic to recalculate and insert in rigth place where they must be If i write some {censored} things, please forgive me Link to comment Share on other sites More sharing options...
ammoune78 Posted April 9, 2014 Share Posted April 9, 2014 So, it's PE32+ - this makes sense, but it won't be easy to rebuild AmiBoardInfo structure with a modified (bigger) DSDT. It seems that DSDT is in the data section and only reloc section is following. Yes it will not be easy to do it, but i don't know how they do it. For exemple my board is Z87X-UD4H, I tried today in morning to flash the bios with beta one. Normally the size of all dsdt in AmiBoardInfo is 48880 bytes but in the beta F9A the size was changed and it's 59850 bytes. I don't know how they do, but there is a tool to do it i think! Link to comment Share on other sites More sharing options...
Aigors Posted April 9, 2014 Share Posted April 9, 2014 Yes it will not be easy to do it, but i don't know how they do it. For exemple my board is Z87X-UD4H, I tried today in morning to flash the bios with beta one. Normally the size of all dsdt in AmiBoardInfo is 48880 bytes but in the beta F9A the size was changed and it's 59850 bytes. I don't know how they do, but there is a tool to do it i think! For Gigabyte's Guys it's' simple, they have source file of bios and they can make all the modification they want but i think 59850 it's' enough for our DSDT mod, with Fred's tools we can add DSDT in AmiboardInfo 1 Link to comment Share on other sites More sharing options...
ammoune78 Posted April 9, 2014 Share Posted April 9, 2014 For Gigabyte's Guys it's' simple, they have source file of bios and they can make all the modification they want but i think 59850 it's' enough for our DSDT mod, with Fred's tools we can add DSDT in AmiboardInfo Yes suuuuuuuuuure! And we all hope this, it can really make a change in our Hackintosh life!!! Hello FredWst tools, if you accept to integrate an biggest size of DSDT in AmiBoardInfo without any problem, i can give you a lots of chocolate and candy! Just kidding! Any way, i really wish you the best Fred! Link to comment Share on other sites More sharing options...
Recommended Posts