Jump to content



Member Since 17 May 2010
Offline Last Active Yesterday, 07:36 PM

Posts I've Made

In Topic: Clover General discussion

Yesterday, 03:33 AM

only is broken in 10.11

Dummy kexts/Info.plists work

Kext w/executable code do not (even with SIP completely disabled)

Aug  1 19:44:41 localhost kernel[0]: Not entitled to link kext 'org.netkas.driver.FakeSMC'
Aug  1 19:44:41 localhost kernel[0]: Failed to load executable for kext org.netkas.driver.FakeSMC.
Aug  1 19:37:59 localhost kernel[0]: Not entitled to link kext 'com.insanelymac.IntelMausiEthernet'
Aug  1 19:37:59 localhost kernel[0]: Failed to load executable for kext com.insanelymac.IntelMausiEthernet.

In Topic: Bench and tested 4790k on Z97 with different SMBIOS

Yesterday, 02:53 AM

So Piker's AICPUPMI is inaccurate?

Some people said Intel Power Gadget is not accurate b/c it's averaging the frequency of all cores. 

No AICPUPMI presented in Post #1

Power Gadget, most accurate tool available for OS X.

Attach IOReg, AICPUPMI output and config.plist.

In Topic: OS X El Capitan DP's builds!

01 August 2015 - 10:14 PM

I'm just curious if I got this right. Please, correct me if I'm wrong.

You are correct, post updated. Tables above combined last 2 lines.

In Topic: OS X El Capitan DP's builds!

01 August 2015 - 08:42 PM

I think I'm gonna choose to lower access permission to 0x3,


2. UNRESTRICTED FS (I assume that stands for FileSystem)


The reason why I wouldn't go for full SIP enabled is that I might forget to turn it off before the next EC update.


0x1 is all the protection you need for the next EC update.  That can be set with the restart initiated by Software Update.

Other choices from the list above:

1&2 = 0x3

1&3 = 0x41

1-3 = 0x43


edit: 8/1/15

In Topic: OS X El Capitan DP's builds!

01 August 2015 - 08:04 PM

Did I get this right? Or should it be 0x03? Or it doesn't matter since it's the same thing?


For as far as I could see, the latest versions of Clover will disable SIP even without adding that in RtVariables. Not sure how it's doing it...

So, my questions are:
1. is my assumption above correct in order to have working audio and SIP enabled? It's working just fine with 0x67, as well. So it's not a problem of working vs not working audio.

2. how would you even enable SIP after reboot if Clover disables it by default?

3. assuming you will be able to reenable SIP (not sure enabling it form Recovery will actually work, since, as I said, somehow, Clover seems to disable it anyway), will you be able to boot with SIP enabled and kexts (FakeSMC in particular) in Library/Extensions?


got endless reboots if I just change 0x67 to 0x0. I saw someone saying 0x00. Haven't tried that yet. But does it even make any difference?

Yes, the 0x3 property is a string, no difference for 0x03.  It the property was data, the hex values are different. 

Once kernel cache is built with unsigned kexts, SIP (0) can be enabled and restarted.  Audio will work with every boot until something causes a kernel cache rebuild with SIP enabled. 

My opinion, Clover should boot with SIP enabled. User controls when to disable SIP and how long.

Most kexts work from EFI.  FakeSMC can be installed in L/E or S/L/E with 0x3.

Auto reboot with 0x0 is a different problem.


csr config


0x67 does not look right, last line is 2 lines (edited above) 0x47 (hex) for the bits noted.

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