Buckeyes1995 Posted June 10, 2014 Share Posted June 10, 2014 When I boot my system WITH the 'kext-dev-mode=1' flag, it won't boot. It stops after it forces the load of AppleMobileDevice.kext. I'm assuming that one of the kexts that Apple has not signed yet is causing the issue. So.. how do I find which one? Does anyone have a list (or a log) booting with the dev mode flag set that lists all of the kexts that are forced to load that fail signing verification?.. Maybe I could determine it by process of elimination. That list appears during boot in verbose mode. It could be the kext after AppleMobileDevice, but doubtful and I have no way of seeing which one that is. Thanks. Link to comment https://www.insanelymac.com/forum/topic/298710-unsigned-kexts-issue-i-believe/ Share on other sites More sharing options...
artur_pt Posted June 10, 2014 Share Posted June 10, 2014 hello if u rebuild the cache .. if any kext with problems u see which one in terminal sudo kexcache -prelinked-kernel good hack Link to comment https://www.insanelymac.com/forum/topic/298710-unsigned-kexts-issue-i-believe/#findComment-2028162 Share on other sites More sharing options...
Yoann Posted June 11, 2014 Share Posted June 11, 2014 Same problem here When I try to put a new kext in Extension Folder, I have error message about Unsigned kexts despite "kext-dev-mode=1"... Link to comment https://www.insanelymac.com/forum/topic/298710-unsigned-kexts-issue-i-believe/#findComment-2028567 Share on other sites More sharing options...
aphex6b Posted June 11, 2014 Share Posted June 11, 2014 Try rebuilding the cache in single user mode. Link to comment https://www.insanelymac.com/forum/topic/298710-unsigned-kexts-issue-i-believe/#findComment-2028600 Share on other sites More sharing options...
Recommended Posts