Jump to content

[possible solution][X99] OsxAptioFixDrv: requested memory exceeds our allocated relocation block


xeye
 Share

79 posts in this topic

Recommended Posts

I had been having this issue for a long time that it seemed randomly hits OsxAptioFixDrv: requested memory exceeds our allocated relocation block

After retried many times, I found that adding any additional kext will cause this issue on my system at a certain point. 

 

before you try this possible solution, please make sure you tried:

 

1) kernel flag: slide=0

2) OsxAptinFix2Test3 solution.

 

cuz on mamy mobos, those can just fix the issue.

 

if you tried them and they don't solve your problem, please try this Clover build and let me know if it fixed your issue. 

 

 

My build is:

 

MSI x99s SLI Plus mobo

gtx 970

DDR4 memory 16gb

nvidia web driver is installed.

 

 

DOWNLOAD:

https://www.dropbox.com/s/dugpjh7vx6xr0w8/Clover_v2.3k_r3168%20_0x4400.pkg?dl=0

 

Make sure to upgrade OsxAptioFixDrv when install.

Link to comment
Share on other sites

I had been having this issue for a long time that it seemed randomly hits OsxAptioFixDrv: requested memory exceeds our allocated relocation block

After retried many times, I found that adding any additional kext will cause this issue on my system at a certain point. 

 

before you try this possible solution, please make sure you tried:

 

1) kernel flag: slide=0

2) OsxAptinFix2Test3 solution.

 

cuz on mamy mobos, those can just fix the issue.

 

if you tried them and they don't solve your problem, please try this Clover build and let me know if it fixed your issue. 

 

 

My build is:

 

MSI x99s SLI Plus mobo

gtx 970

DDR4 memory 16gb

nvidia web driver is installed.

 

 

DOWNLOAD:

https://www.dropbox.com/s/dugpjh7vx6xr0w8/Clover_v2.3k_r3168%20_0x4400.pkg?dl=0

 

Make sure to upgrade OsxAptioFixDrv when install.

This modified version of clover worked for me on Asus X99 Deluxe and EVGA GTX 780 with 10.10.2 Yosemite.

 

That said may I ask what modification you did on the OsxAptioFixDrv ? 

 

A fix is a always great but it's always better with the explanation. Others may be able to accommodate the fix to their build :-)

 

Thank's so much

 

PM!

Link to comment
Share on other sites

This modified version of clover worked for me on Asus X99 Deluxe and EVGA GTX 780 with 10.10.2 Yosemite.

 

That said may I ask what modification you did on the OsxAptioFixDrv ? 

 

A fix is a always great but it's always better with the explanation. Others may be able to accommodate the fix to their build :-)

 

Thank's so much

 

PM!

 

it is actually quite easy. All I did is increasing the memory block size from 0x4000 to 0x4400.  AptioDrv2Test3 seems using a different way to apply the overrides which I think is a better way to go. But that doesn't work for x99s at this moment. This is just a temp solution. 

Link to comment
Share on other sites

it is actually quite easy. All I did is increasing the memory block size from 0x4000 to 0x4400. AptioDrv2Test3 seems using a different way to apply the overrides which I think is a better way to go. But that doesn't work for x99s at this moment. This is just a temp solution.

does this require using the entire clover version that you posted or can just the aptiofix be used? Also will this work with boards that only have this problem because of nvidia cards? My z68 did this a few times.

it is actually quite easy. All I did is increasing the memory block size from 0x4000 to 0x4400. AptioDrv2Test3 seems using a different way to apply the overrides which I think is a better way to go. But that doesn't work for x99s at this moment. This is just a temp solution.

does this require using the entire clover version that you posted or can just the aptiofix be used? Also will this work with boards that only have this problem because of nvidia cards? My z68 did this a few times.
Link to comment
Share on other sites

This seems to help a bit, but will hit a memmap error 100% of the time when attempting to use the BTFirmwareUploader. It will occasionally hit an error when making other system changes.

 

How did you increase the memory block size? If I am reading the error properly, increasing the size will not help here unless that also changes where it will be allocated. 

 

Can we instead compress or delete things to attempt to stay below 4608000?

 

Contents of drivers64UEFI:

FSInject-64.efi

HFSPlus-64.efi

OsxAptioFixDrv-64.efi

OsxFatBinaryDrv-64.efi (I tried deleting this one as well)

 

This is my error:

Slightly_different_error.jpg

Link to comment
Share on other sites

does this require using the entire clover version that you posted or can just the aptiofix be used? Also will this work with boards that only have this problem because of nvidia cards? My z68 did this a few times.

does this require using the entire clover version that you posted or can just the aptiofix be used? Also will this work with boards that only have this problem because of nvidia cards? My z68 did this a few times.

 

not. it does not require a whole update I guess. also this hack can help a little on any this type of errors. But it just adding very small amount of memory to load the kexts (which loads me 3 additional kexts without problem). This build was made to fix my own issue, so it might not that universal. I am reading through the code of a2t3 these days. :)

Link to comment
Share on other sites

not. it does not require a whole update I guess. also this hack can help a little on any this type of errors. But it just adding very small amount of memory to load the kexts (which loads me 3 additional kexts without problem). This build was made to fix my own issue, so it might not that universal. I am reading through the code of a2t3 these days. :)

are you aware of any drawbacks of doing this? What happen if we just used a really large number? And are you saying that this has to do with the amount of kexts loaded?
Link to comment
Share on other sites

are you aware of any drawbacks of doing this? What happen if we just used a really large number? And are you saying that this has to do with the amount of kexts loaded?

 

64mb is already hard to allocate. It will not work just putting a huge number (and yes I tried). And sorry I really have limited knowledge about bootloader dev, I cannot answer the question about if there is any drawback. :(

  • Like 1
Link to comment
Share on other sites

I attached my memmap--looks like there is a great deal of space. Am I reading this wrong, or is this not the type of space that we need?

 

So my AptioFix error says it is having difficulties allocating 1258f pages. That is 74,639 pages, right? Each page is 4096 Bytes, so that amounts to 305,721,344 Bytes, or just over 305MBs. 

 

I guess my question is whether that difficulty is because I am actually using more than 305MBs of files, drivers, firmware with Clover, or if it is trying to use an address that is simply not available. I am assuming the latter, but have no idea how to see what addresses AptioFix is using.

 

Xeye, could you make an AptioFix that relocates to the large space I have starting at 0000000100000000-00000008BFFFFFFF? That is an uninterrupted chunk of ~30GBs of RAM.

 

 

 

 

edit again: Looking at my error, the first thing AptioFix does is attempt to use blocks 47F500-16D83FFF. However, the initial block is only partially available, up to block 268,435,455, while Clover requests up to block 306,769,920. (then the first BS_Code interrupts it in my memmap).

 

It then relocates it to: 90850000, but my next available block in the high high range is not until 0000000100000000. Can that 90850000 just be changed to block 100000000?

 

If that range works then you could double the size to up to 600MBs allowed even, just in case I really am running out of space.

memmap.txt

Link to comment
Share on other sites

I'm sure it is not the matter of the total memory. 

 

Not the amount of total memory per se, but the buggy dynamic relocation would have a hell of a large target if you have 62GBs of available addresses. I could certainly see it not making a difference, but might order another 32GBs to check.

Link to comment
Share on other sites

@xeye I just helped someone with the same problem on an X99 Deluxe after installing logitech control center (which I am assuming installs a kernel extension). This solution seems to have solved it. I'm posting the driver by itself in case anyone wants to use it without the Clover installer. I renamed it to avoid confusion.

 

https://www.dropbox.com/s/1x1h2tzpnwt40gk/OsxAptioFixDrv-X99.efi?dl=0

Link to comment
Share on other sites

@xeye I just helped someone with the same problem on an X99 Deluxe after installing logitech control center (which I am assuming installs a kernel extension). This solution seems to have solved it. I'm posting the driver by itself in case anyone wants to use it without the Clover installer. I renamed it to avoid confusion.

 

Glad that helped. and thanks for doing this. 

Link to comment
Share on other sites

Am I blind? Not seeing that .efi driver in the clover package, nor a pre-compiled version of it online.

The precompiled version was on projectosx site.

We not include it into package because it is for developers who able to compile Clover by itself.

  • Like 1
Link to comment
Share on other sites

I would love to be able to compile Clover. If only! ;)

 

I hit another error doing the manual compiling you linked me to in the general thread.

i believe there is a precompiled version here: http://www.insanelymac.com/forum/topic/301229-clover-2941-updated-and-signed-xcode-51-clang-and-gcc-491-built/ I think it's old though. I'll try to build it myself later.

Link to comment
Share on other sites

tried building it with clovergrowerpro and got this:

 

- gcc-4.9.2 extracting...
- gcc-4.9.2 extracted
- gcc-4.9.2 (native) configure...
Error configuring GCC-4.9.2 ! Check the log /Users/jamiethemorris/**WORKSPACE**/CloverGrowerPro/src/logs/gcc-native.x64.configure.log.txt
 
- Ejecting RAM disk
"disk2" unmounted.
"disk2" ejected.
Toolchain build  ERROR!!

configure: error: Unable to find a usable CLooG.  See config.log for details.

Link to comment
Share on other sites

tried building it with clovergrowerpro and got this:

- gcc-4.9.2 extracting...
- gcc-4.9.2 extracted
- gcc-4.9.2 (native) configure...
Error configuring GCC-4.9.2 ! Check the log /Users/jamiethemorris/**WORKSPACE**/CloverGrowerPro/src/logs/gcc-native.x64.configure.log.txt
 
- Ejecting RAM disk
"disk2" unmounted.
"disk2" ejected.
Toolchain build  ERROR!!

configure: error: Unable to find a usable CLooG.  See config.log for details.

 

Yes, CloverGrower, CGP, and the manual instructions all give me the same error. No doubt it is something I installed (or did not install), but I can't compile Clover at this time =/

Link to comment
Share on other sites

Yes, CloverGrower, CGP, and the manual instructions all give me the same error. No doubt it is something I installed (or did not install), but I can't compile Clover at this time =/

This is the one from Andy's build I linked above, like I said, it's probably old I think (this build is from October), but it's something.

DumpUefiCalls-64.zip

  • Like 1
Link to comment
Share on other sites

 Share

×
×
  • Create New...