Jump to content

Unsigned kexts issue (I believe)


  • Please log in to reply
3 replies to this topic

#1
Buckeyes1995

Buckeyes1995

    InsanelyMac Protégé

  • Members
  • Pip
  • 41 posts

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.



#2
artur-pt

artur-pt

    InsanelyMacaholic

  • Local Moderators
  • 4,493 posts
  • Gender:Male
  • Location:Portugal
  • Interests:TechManiaco

hello

 

if u rebuild the cache .. if any kext with problems u see which one in terminal

 

sudo kexcache -prelinked-kernel

 

good hack



#3
Yoann

Yoann

    InsanelyMac Protégé

  • Members
  • Pip
  • 9 posts
  • Gender:Male
  • Location:Paris

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"...



#4
aphex6b

aphex6b

    InsanelyMac Protégé

  • Members
  • PipPip
  • 85 posts
  • Gender:Male

Try rebuilding the cache in single user mode.







0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

© 2014 InsanelyMac  |   News  |   Forum  |   Downloads  |   OSx86 Wiki  |   Mac Netbook  |   PHP hosting by CatN  |   Designed by Ed Gain  |   Logo by irfan  |   Privacy Policy