jdk Posted May 24, 2020 Share Posted May 24, 2020 (edited) Hi, I successfully installed Catalina following the first of these guides (hardware purchase, initial setup) then the second (Clover configuration). I'm not a gamer so wanted to use the onboard HDMI video and found some posts that gave me the needed settings. There were some small issues that might be video related but overall I was very pleased and grateful to the guides' authors for their amazing work! https://github.com/cmer/gigabyte-z390-aorus-master-hackintosh https://hackintosh.gitbook.io/-r-hackintosh-vanilla-desktop-guide/ My hardware List Gigabyte Z390 AORUS Elite Motherboard Intel Core i9-9900KS 4.0GHz 16M Phanteks 140mm PWM CPU Cooler Black Corsair Vengeance LPX D4 2x16G Samsung 970 EVO Plus PCIe SSD 1TB I also boot Linux on other disks, wanted to do some work with VMware and added another 32Gb maxing out the MB at 64Gb. Linux was fine with the additional memory but Catalina was not and now gives this error. Error allocating 0x..... pages at 0x0000000.... alloc type 2 Couldn't allocate runtime area I've tried the following all with the same result and am now reaching out for help. downgrade 64Gb to the original 32Gb tried variety of memory fixes (and even started looking at the latest's source) OsxAptioFix3Drv.efi AptioMemoryFix.efi OsxAptioFix2Drv-64.efi OsxAptioFix3Drv-64.efi tried more closely matching the above guides' Clover configs read 'Understanding and fixing "Couldn't allocate runtime area" errors"' and tried fixes www.reddit.com/r/hackintosh/comments/d524ip/understanding_and_fixing_couldnt_allocate_runtime/ enable/disable XMP and removed memory did the memmap excercise only to decide that "slide=0" is the answer (slide=0 was already a kernel parameter) verified that the model of iMac19,1 that I selected support 64Gb RAM The USB flash that I used for the install no longer boots with the same error. I believe that the memory map is kept on the MB and was hopeful that XMP settings or changing the DIMMS would cause it to recalculate a new map. The KASLR post suggests disabling on board components and a different post explicitly states to disable the iGPU. I'm a little nervous about the iGPU since I have no video card and don't know what will happen if I do. Does anyone have any thoughts on this? List of questions; Am I correct to think that the memory map is on the MB and possibly in one of DSDT, SSDT, SRAT or other tables? Should I try to fix the problem by focusing on the MB memmap or try to get a working memory fix? Is there any point trying different slide= values? Can I, should I switch to OpenCore? Without reinstalling? Are there any other suggestions? Thanks, JDK Edited May 24, 2020 by jdk Link to comment https://www.insanelymac.com/forum/topic/343953-error-allocating-0x-pages-at-0x-after-memory-upgrade/ Share on other sites More sharing options...
STLVNUB Posted May 25, 2020 Share Posted May 25, 2020 (edited) OsxAptioFix2Drv-free2000.efi.zip Edited May 25, 2020 by STLVNUB Try This one Link to comment https://www.insanelymac.com/forum/topic/343953-error-allocating-0x-pages-at-0x-after-memory-upgrade/#findComment-2723683 Share on other sites More sharing options...
jdk Posted May 25, 2020 Author Share Posted May 25, 2020 8 hours ago, STLVNUB said: OsxAptioFix2Drv-free2000.efi.zip I specifically skipped this driver after reading the warning posted by its developer. I'll read the comments/feedback received and reconsider if there are no other suggestions. i_unleashed_a_plague_upon_you_guys_and_i_am_sorry/ Link to comment https://www.insanelymac.com/forum/topic/343953-error-allocating-0x-pages-at-0x-after-memory-upgrade/#findComment-2723721 Share on other sites More sharing options...
STLVNUB Posted May 26, 2020 Share Posted May 26, 2020 What I'm using here., no adverse consequences Link to comment https://www.insanelymac.com/forum/topic/343953-error-allocating-0x-pages-at-0x-after-memory-upgrade/#findComment-2723791 Share on other sites More sharing options...
mhaeuser Posted May 26, 2020 Share Posted May 26, 2020 @STLVNUB As someone weaing the "developer" badge you should not recommend garbage. @jdk Use OcQuirks with DevirtualiseMmio enabled Link to comment https://www.insanelymac.com/forum/topic/343953-error-allocating-0x-pages-at-0x-after-memory-upgrade/#findComment-2723809 Share on other sites More sharing options...
jdk Posted May 26, 2020 Author Share Posted May 26, 2020 @Download-FritzThank you for the suggestion. Unfortunately, it did not work w/ or without the recommended setting. I was curious about the allocation error and looked into it some more (spaces added for readability) "Error allocating 0x0001 1994 pages at 0x000 0000 03d9 2000" According to memmap the starting address falls within this range where there are enough pages "Available 0000000000100000-000000001529EFFF 000000000001519F 000000000000000F" if only I could get the allocation to start closer to 0x0010 0000 rather than 0x03d9 2000. I'm pretty sure that "slide=0" and the starting address is always the same on every attempted boot. I believe that the Clover drivers are trying to find a place to load the kernel. Can I try to manually set the memory address to use? Is that foolish/ridiculous to suggest? Should I try switching to OpenCore? My previous build was years ago and I just started with the Vanilla Clover build so I don't want to go to the OpenCore beta just yet after putting effort into Clover (at least not without a reasonable chance of success). Thanks, JDK Link to comment https://www.insanelymac.com/forum/topic/343953-error-allocating-0x-pages-at-0x-after-memory-upgrade/#findComment-2723839 Share on other sites More sharing options...
jdk Posted May 30, 2020 Author Share Posted May 30, 2020 @Download-Fritz thank you again for your suggestion and pointing me in the right direction. I got your port working but needed another setting (for z390) related to the one you specifically mentioned. Use OcQuirks with DevirtualiseMmio and ProtectUefiServices enabled Link to comment https://www.insanelymac.com/forum/topic/343953-error-allocating-0x-pages-at-0x-after-memory-upgrade/#findComment-2724324 Share on other sites More sharing options...
Recommended Posts