Jump to content

macOS Sierra only boots with CsrActiveConfig 0x67


ahmedbilal
 Share

11 posts in this topic

Recommended Posts

I am running Mac OS Sierra on Dell e5430 with 4 GB Ram and Intel HD 4000.

Whenever i try to run it on CstActiveConfig 0x3 (only allowing unsigned kext) it shows some memory error and restarts.

I want to run it on 0x3 to avoid permission corruption that usually occurs on 0x67 due to some softwares.

I use OsxAptioFixDrv-64.efi because OsxAptioFixDrv2-64.efi does not work at all.

Link to comment
Share on other sites

This may be because your kernel block pages is too small due to the default settings is 0x8000 (128Mb). Try to increase it. (By editing src/edk2/Clover/OsxAptioFixDrv/OsxAptioFixDrv.c)

 

Search for

#define KERNEL_BLOCK_NO_RT_SIZE_PAGES	0x8000

And replace with (for example)

#define KERNEL_BLOCK_NO_RT_SIZE_PAGES	0x16000

Which means 256 Mb. Then compile it, you will get a proper OsxAptioFixDrv-64.efi.

 

If you are too lazy to do so, then there is a pre-compiled one.

 

Edit: Confusing content removed.

 

For more information, please check here

Link to comment
Share on other sites

This may be because your kernel block pages is too small due to the default settings is 0x8000 (128Mb). Try to increase it. (By editing src/edk2/Clover/OsxAptioFixDrv/OsxAptioFixDrv.c)

 

Search for

#define KERNEL_BLOCK_NO_RT_SIZE_PAGES	0x8000

And replace with (for example)

#define KERNEL_BLOCK_NO_RT_SIZE_PAGES	0x16000

Which means 256 Mb. Then compile it, you will get a proper OsxAptioFixDrv-64.efi.

 

If you are too lazy to do so, then there is a pre-compiled one.

 

attachicon.gif512_OsxAptioFixDrv-64.efi.zip

 

For more information, please check here

 

I still got errorc7YzXbh.jpg

Link to comment
Share on other sites

Thank you PMheart. Is there any other way to prevent permission corruption?

Sorry for delaying replying. Recent days I have to prepare to be about to return to school.

IMHO. This may be not related to permission.

Try this one. And feedback. I've increased it to 0x20000.

 

20000_OsxAptioFixDrv-64.efi.zip

 

Some tips:

1 - Test the attachment above.

2 - If it still not work, then refer to this article and use its OsxAptioFix2Drv-free2000.efi.

Note: You must delete my OsxAptioFixDrv-64.efi before using OsxAptioFix2Drv-free2000.efi.

3 - If still not work, then try OsxAptioFix2Drv-free2000.efi + Test2-2016.efi (Also from above), TBH I don't suggest using Test2-2016.efi alongside OsxAptioFixDrv-64.efi.

4 - If none of above works, then try legacy boot.

Link to comment
Share on other sites

Sorry for delaying replying. Recent days I have to prepare to be about to return to school.

IMHO. This may be not related to permission.

Try this one. And feedback. I've increased it to 0x20000.

 

attachicon.gif20000_OsxAptioFixDrv-64.efi.zip

 

Some tips:

1 - Test the attachment above.

2 - If it still not work, then refer to this article and use its OsxAptioFix2Drv-free2000.efi.

Note: You must delete my OsxAptioFixDrv-64.efi before using OsxAptioFix2Drv-free2000.efi.

3 - If still not work, then try OsxAptioFix2Drv-free2000.efi + Test2-2016.efi (Also from above), TBH I don't suggest using Test2-2016.efi alongside OsxAptioFixDrv-64.efi.

4 - If none of above works, then try legacy boot.

Nothing works. 20000_OsxAptioFixDrv-64.efi just don't let the boot process to progress. It just holds on saying freeing 0x20000000, result = 0.

OsxAptionFix + Test2-2016 does not work at all.

  • Like 1
Link to comment
Share on other sites

Nothing works. 20000_OsxAptioFixDrv-64.efi just don't let the boot process to progress. It just holds on saying freeing 0x20000000, result = 0.

OsxAptionFix + Test2-2016 does not work at all.

Sorry to hear that. In this case I think you have to use legacy Clover... Yes. AptioFix may be not compatible with very few cases.

  • Like 1
Link to comment
Share on other sites

 Share

×
×
  • Create New...