Jump to content
9 posts in this topic

Recommended Posts

Besides being that they don't appear in Retail and/or GM afaik. The logs would churn out warnings that the kexts are unsigned, though.

I think it did appear in GM 603. At least for my hack.

If you add them to AppeKextExclusion(I forget the exact name), it will eliminate these console messages. However, it doesn't seem to affect anything other than that. This has been documented several times on this forum so it shouldn't be too hard to find. I'm going to bed now (lol... it's 5 in the morning here), but I'll try find a link for you tommorrow.

Who knows how I can avoid this annoying protection system

 

 

Screen%20Shot%202013-11-08%20at%2019.30.

 

Now You can use Kext Utility to install kexts and avoid this annoying protection system.

KU itself adds a records about the installing kexts in the AppleKextExcludeList.kext.

  • Like 1

The main problem was that FakeSMC takes a lot to boot because of this error.

Now by installing manually with Kext Utility problem is solved.

 

Thanks cVaD

Hmm, I might give that a try. The HWSensors installer should've patched the exclude list too, and so should other kexts that are installed via wizards.

×
×
  • Create New...