Jump to content



Member Since 17 Jan 2009
Offline Last Active Yesterday, 09:11 PM

Posts I've Made

In Topic: [possible solution][X99] OsxAptioFixDrv: requested memory exceeds our allocat...

18 March 2015 - 03:06 AM

Can you provide debug.log?

Yes, you do something wrong.


I would like to. When I set Debug=YES I am not getting anything generated in misc.


Can you take a look at this config.plist and see why I have no debug log?

In Topic: [possible solution][X99] OsxAptioFixDrv: requested memory exceeds our allocat...

16 March 2015 - 08:38 PM

Did you see black screen with 5_ at the start?


You also can choose Clover BiosBlockIO. It sometimes works better. 


I do not see a 5_, but I am still having problems. Here is what I have tried:

1. Don't Update, ESP, 64-bit SATA: see attached runtime allocation error picture.


2. Don't Update, ESP, BiosBlockIO: black screen after Clover home screen. Nothing else happens.


3. Boot0af, ESP, BiosBlockIO: runtime allocation error (I was able to boot once, then not again even after clearing kernelcache)


4. Boot0af, ESP, 64-bit SATA: runtime allocation error.


Am I doing something wrong? Just left everything else on default, including the config.plist as the actual OS is not the problem. Anyone else on Legacy Clover?



In other news, BIOS 1502 on my X99 Deluxe no longer needs the 10.9.5 rollback kexts. Xeon CPU's do not need the kernel patch, so this is officially a very very easy Chameleon installation these days. I do prefer kext autopatching, true UEFI, and a superior SMBIOS generator though =/


Oh, and VoodooTSCSync is only necessary for wake from sleep (been like that for several BIOS updates now). Can that be addressed via SSDT? or MADT?

In Topic: [possible solution][X99] OsxAptioFixDrv: requested memory exceeds our allocat...

15 March 2015 - 07:26 PM

Well, I guess I'll be the guinea pig for this board then. If worse comes to worse I'll just use CloverEFI.

BTW I've heard Linux runs terribly on X99, is that still true?


What exactly is necessary to boot legacy? I am getting an "error allocating runtime" when attempting to boot with legacy clover.


I installed with the following options:

1. Install Clover in the ESP

2. Bootloader: Install boot0af in MBR (also tried Don't update)

3. CloverEFI: 64-bit SATA

4. HFS+ 64-bit driver, filesystemdrv, nothing else.

In Topic: [possible solution][X99] OsxAptioFixDrv: requested memory exceeds our allocat...

10 March 2015 - 08:04 PM

OK, posted in Coderush's topic. I am sure what I am asking is impossible (or at least impractical), but I had to check!

Thanks for your information Dmazar!

In Topic: [UEFIPatch] UEFI patching utility

10 March 2015 - 07:58 PM

Hello Coderush,


Thank you for all that you do for this community. I have used your PM fix long ago for one of my old builds. 


I have a questions that is no doubt ignorant, but I hope you can answer it for me  ;) I apologize if this is off-topic, not sure where to post this.



Those of us with X99 motherboards have a memory map that does not leave enough space for UEFI Clover to load the proper kernelcache, which leads to a boot error. Would any of your tools allow me to modify my memorymap?


What I hope is that it is possible to clear up more space by relocating a small BS_Code to a different available address. The address I want to relocate is: BS_Code    0000000010000000-000000001000AFFF to anywhere in the 0000000000000000-000000000003EFFF range instead.



1. Is it possible to modify the BIOS in such a way to alter the memmap?

2. Can you help me do it, if so?

3. Is there another way around this problem that you can think of?


Thank you!



I have attached my memmap and memdump from shell.


Thread with the problem several of us have, Dmazar's response: http://www.insanelym...on-block/page-3



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