[Solved] Couldn't allocate runtime area error during clover boot install Mojave

[ConcreteBong]

in clover activate inject usb and usb ownership, it worked for me.

 

[psr]

Hello,
Please I have similar problem.
I successfully installed Mojave. But I have issues with boot every time. I tried different types of memoryFixes but I am not lucky.
After many restarts can I boot thanks to trying different boot options.
Mostly helps combination of slide=0 and different ones.

In verbose I see mostly: Couldn’t allocate runtime area alloc 2.
Or: Error loading kernel cache (0x9)
Or sometimes post ends: ++++++++++++++
Sometimes everything seems fine but PC restarts.

Please. Don’t you know what should I do ?

 

[JessicaSinclair]

i have the exact same problem when ever i reboot i get this error "couldn't allocate runtime area" could someone please help me with how to change the driver in a folder? I am new to hackingtosh sorry

 

[pastrychef]

This is a common problem on Z390. It's a sign that whichever Aptio fix you are using doesn't work well with your motherboard.

Some general tips for Z390 users:

• Try different Aptio fixes until you find one that works with your motherboard.
• Try without any of the FileVault and as few Clover drivers as possible until you are able to boot. You can add them later on once you've found a combination of Aptio fix + EmuVariableUefi that works for you.
• Try to avoid OsxAptioFix2Drv-free2000. The original developer of this Aptio fix has warned that it may cause permanent damage to your motherboard.
• The only way I am aware to find which Aptio fix works well with your motherboard is through a lot of trial-and-error.
• Different hardware configurations can affect the Aptio fixes. Therefore, when first trying to get macOS installed, try to do so with as few extraneous PCI-e cards as possible. You can add them after you have macOS up and running.
• The "slide=0" may or may not help. Try with and without.
• Sometimes, even with a working Aptio fix, you may still get stuck during the boot process at "+++++++++++". When this happens press the reset button and try again. Sometimes, it requires multiple resets.

 

[JessicaSinclair]

This is a common problem on Z390. It's a sign that whichever Aptio fix you are using doesn't work well with your motherboard.

Some general tips for Z390 users:

• Try different Aptio fixes until you find one that works with your motherboard.
• Try without any of the FileVault and as few Clover drivers as possible until you are able to boot. You can add them later on once you've found a combination of Aptio fix + EmuVariableUefi that works for you.
• Try to avoid OsxAptioFix2Drv-free2000. The original developer of this Aptio fix has warned that it may cause permanent damage to your motherboard.
• The only way I am aware to find which Aptio fix works well with your motherboard is through a lot of trial-and-error.
• Different hardware configurations can affect the Aptio fixes. Therefore, when first trying to get macOS installed, try to do so with as few extraneous PCI-e cards as possible. You can add them after you have macOS up and running.
• The "slide=0" may or may not help. Try with and without.
• Sometimes, even with a working Aptio fix, you may still get stuck during the boot process at "+++++++++++". When this happens press the reset button and try again. Sometimes, it requires multiple resets.

that's the problem there i dont know how to add or remove files? where do i do that in clover?

 

[timcharper]

On my new z390 build, I just started getting this error after one reboot; I'm not sure what I did or what I changed. I had a fully working build for a few days, and one day, I rebooted, and it started to consistently fail with this error (Couldn't allocate runtime area).

I tried a few different things, changing the slide parameter, using a different Aptio, reset the bios and reconfigured, but ultimately what ended up working is I disabled the iGPU. Apparently, the iGPU can mess with the initial allocation?

Kexts:

kexts/Other/AppleALC.kext
kexts/Other/FakeSMC.kext
kexts/Other/IntelMausiEthernet.kext
kexts/Other/Lilu.kext
kexts/Other/USBInjectAll.kext

Clover drivers:

drivers/UEFI/VBoxHfs.efi
drivers/UEFI/ApfsDriverLoader.efi
drivers/UEFI/AptioMemoryFix.efi
drivers/UEFI/EmuVariableUefi.efi
drivers/BIOS/ApfsDriverLoader.efi

Boot args (config.plist)

slide=4 ...

For me, slide=4 was required to get the EmuVariableUefi driver working, which was required to install Mac OS (I had an infinite reboot loop in the middle of install without it). Dropping bread crumbs in case anyone else is having similar issues.

 

[pastrychef]

that's the problem there i dont know how to add or remove files? where do i do that in clover?

Sorry, I didn't see your post until just now... Anyway, the Aptio drivers are in /EFI/CLOVER/drivers/UEFI/.

 

[pastrychef]

Apparently, the iGPU can mess with the initial allocation?

I think I saw someone else make this claim so you are not alone.

On my Z390, I use iMacPro1,1 system definition with IGPU disabled.

 

[JessicaSinclair]

• Try to avoid OsxAptioFix2Drv-free2000. The original developer of this Aptio fix has warned that it may cause permanent damage to your motherboard.

My motherboard is damaged because of this and it wont boot to menu it will not boot to menu no matter which ports i use - it will go into a looping black screen of death.

Luckily my motherboard is under warranty and will get replaced.

 

[CaseySJ]

My motherboard is damaged because of this and it wont boot to menu it will not boot to menu no matter which ports i use - it will go into a looping black screen of death.

Luckily my motherboard is under warranty and will get replaced.

Have you tried CMOS Reset by shorting 2 pins on the motherboard as described in the Gigabyte user's manual? This will also reset BIOS parameters to their factory-default values, so it will necessary to set them again.