OpenCore General Discussion

[Styxie]

Hi there, I'm currently using my Z390 Designare with Clover v5099, but I'd like to switch to OC. I've downloaded OC 0.5.3 and started experimenting, trying to replace my working Clover config with OC. I've followed this guide (https://khronokernel-2.gitbook.io/opencore-vanilla-desktop-guide/config.plist/coffee-lake) to the T, even unlocking my CFG MSR and calculating my slide value (171 or 0, both should work, according to my own calculations and Discords'). However, after a few days of trying, experimenting both with AptioMemoryFix.efi and FwRuntimeServices.efi and various Quirks settings, I'm stuck at getting the dreaded "ERROR allocating 0x11c89 pages at .... alloc type 2. Couldn't allocate runtime area" message. I can't seem to get any further, what should I try next?

[Styxie]

10 hours ago, texem said:

 

no, my z390 works _with_  native nvram. Thats about using a patched DSDT.

 

Can you please share how you got native nvram to work?

[texem]

Have a look at @Audiogod's thread about z390pro. You can take one the DSDT's from there and build your EFI for OC. 

 

Persistent (native) NVRAM is working if you put a sample entry via commandline or hackintool . After rebooting , this entry should still be there.

 

If not, bless f.i. no longer works - and thats the case with latest OC 0.53 release and 0.54beta.  

 

I uploaded OC 0.53 (beta) EFI's for GB z390pro earlier here but removed all downloads because of the issues now. Until it's not resolved nothing will be released from me again, sry

 

[karacho]

1 hour ago, Styxie said:

Hi there, I'm currently using my Z390 Designare with Clover v5099, but I'd like to switch to OC. I've downloaded OC 0.5.3 and started experimenting, trying to replace my working Clover config with OC. I've followed this guide (https://khronokernel-2.gitbook.io/opencore-vanilla-desktop-guide/config.plist/coffee-lake) to the T, even unlocking my CFG MSR and calculating my slide value (171 or 0, both should work, according to my own calculations and Discords'). However, after a few days of trying, experimenting both with AptioMemoryFix.efi and FwRuntimeServices.efi and various Quirks settings, I'm stuck at getting the dreaded "ERROR allocating 0x11c89 pages at .... alloc type 2. Couldn't allocate runtime area" message. I can't seem to get any further, what should I try next?

Do you have enabled iGPU? If so, disable iGPU in Bios and try again. Use an iMacPro1,1 smbios. Have a look there -> https://www.hackintosh-forum.de/forum/thread/43866-gigabyte-z390-designare-fertiger-efi-ordner-zum-download/ User JimSalabim and i created a working configuration. It only works when iGPU is disabled. Just ask him. 

[Styxie]

Thanks for the input, but I'm still stuck at the "Couldn't allocate runtime area" message.

 

@texem which SSDT are you referring to? I found @AudioGod thread, but as far as I can tell it's Clover only. I have my own Clover install running, I'm trying to use the same SSDT's I'm using with Clover on OC now.

 

@karacho_ak my German isn't that good, but as far as I can tell they're also using Clover, correct?

[karacho]

@Styxie That's right, but we've created an OC Folder for testing purposes and it works fine. Only thing is, you have to disable iGPU in Bios, because that's the reason for that allocation error.

[SavageAUS]

Hi there, I'm currently using my Z390 Designare with Clover v5099, but I'd like to switch to OC. I've downloaded OC 0.5.3 and started experimenting, trying to replace my working Clover config with OC. I've followed this guide (https://khronokernel-2.gitbook.io/opencore-vanilla-desktop-guide/config.plist/coffee-lake) to the T, even unlocking my CFG MSR and calculating my slide value (171 or 0, both should work, according to my own calculations and Discords'). However, after a few days of trying, experimenting both with AptioMemoryFix.efi and FwRuntimeServices.efi and various Quirks settings, I'm stuck at getting the dreaded "ERROR allocating 0x11c89 pages at .... alloc type 2. Couldn't allocate runtime area" message. I can't seem to get any further, what should I try next?

You should only be using FwRuntimeServices.efi with opencore. Not AptioMemory at all.


Sent from my iPhone using Tapatalk

[Styxie]

1 hour ago, karacho_ak said:

@Styxie That's right, but we've created an OC Folder for testing purposes and it works fine. Only thing is, you have to disable iGPU in Bios, because that's the reason for that allocation error.

Thanks, I just tried that, and it works! However, having iGPU is essential for me, as I plan on using iGPU for helping with video export. On Clover, I have iGPU headless (I think): its enabled in BIOS but doesn't show up in Catalina. My export fps in my video app is great, over 50 fps on 4K H264. However, just now booting OC w/o iGPU I get only 18 fps.... But this did clear the allocation error, that's good news, I'll try and dig a little further to see if I can get iGPU to work in OC somehow. Thanks!

 

UPDATE: Nevermind, if I change to iMacPro1,1 as SMBIOS in OC, booting without iGPU, I get the same 50 fps render speed! I'm continuing with this setup now, iMacPro1,1 and no iGPU. Thanks for the input guys!

Edited December 8, 2019 by Styxie

[arsradu]

Hi guys

 

Ever since I used the last version of OC (0.5.3), I'm not sure what happened but my BIOS resolution dropped to some weird 4:3 aspect ratio. What I don't understand is why, even after removing the USB drive containing OC and resetting the BIOS, issue still occurs... And it occurs even with Clover. Which makes no sense to me, since it hasn't happened before. Any idea what could cause this issue? Can OC corrupt the UEFI BIOS in any way...? I know it probably sounds stupid, but I have no explanation for what's happening now.

Edited December 8, 2019 by arsradu

[texem]

1 hour ago, Styxie said:

Thanks for the input, but I'm still stuck at the "Couldn't allocate runtime area" message.

 

@texem which SSDT are you referring to? I found @AudioGod thread, but as far as I can tell it's Clover only. I have my own Clover install running, I'm trying to use the same SSDT's I'm using with Clover on OC now.

 

 

yes, thats Clover. Just wanted to redirect you to the DSDT source. You must create your own OC EFI

[karacho]

@arsradu Perhaps Nvram Reset helps.

39 minutes ago, Styxie said:

Thanks, I just tried that, and it works! However, having iGPU is essential for me, as I plan on using iGPU for helping with video export. On Clover, I have iGPU headless (I think): its enabled in BIOS but doesn't show up in Catalina. My export fps in my video app is great, over 50 fps on 4K H264. However, just now booting OC w/o iGPU I get only 18 fps.... But this did clear the allocation error, that's good news, I'll try and dig a little further to see if I can get iGPU to work in OC somehow. Thanks!

Thats' the reason why, JimSalabim continue using his Clover EFI. He need iGPU too.

Edited December 8, 2019 by karacho_ak

[kaoskinkae]

PciRoot(0x0)\Pci(0x1F,0x2)\Sata(0x5,0xFFFF,0x0)\HD(2,GPT,EE24B8AA-46F5-4BEA-AFCA-CA417E40E472,0xFA000,0x32000) / \Windows\Boot\EFI\bootmgfw.efi

 

 

[arsradu]

21 minutes ago, karacho_ak said:

@arsradu Perhaps Nvram Reset helps.

 

Yeah, already tried that. Didn't work. And it didn't work cause the issue was not on OC/Clover/NVRAM side. I changed a few settings on my monitor and forgot about them. Setting them back solved the issue.  

 

So...nevermind.  

Edited December 8, 2019 by arsradu

[Styxie]

36 minutes ago, karacho_ak said:

@arsradu Perhaps Nvram Reset helps.

Thats' the reason why, JimSalabim continue using his Clover EFI. He need iGPU too.

 

I just updated my original post: if I change to iMacPro1,1 as SMBIOS in OC, booting without iGPU, I get the same 50 fps render speed! I'm continuing with this setup now, iMacPro1,1 and no iGPU. So that seems like a good alternative!

[SavageAUS]

Hi guys

 

Ever since I used the last version of OC (0.5.3), I'm not sure what happened but my BIOS resolution dropped to some weird 4:3 aspect ratio. What I don't understand is why, even after removing the USB drive containing OC and resetting the BIOS, issue still occurs... And it occurs even with Clover. Which makes no sense to me, since it hasn't happened before. Any idea what could cause this issue? Can OC corrupt the UEFI BIOS in any way...? I know it probably sounds stupid, but I have no explanation for what's happening now.

 

I can’t give you a yes or no if OC corrupts uefi or not but I can say with my skylake rig if I boot (accidentally from USB) with wrong acpi config in OC it noops my uefi bios back to defaults and gives me an acpi error.

 

 

Sent from my iPhone using Tapatalk

[Styxie]

6 hours ago, texem said:

Have a look at @Audiogod's thread about z390pro. You can take one the DSDT's from there and build your EFI for OC. 

 

 

I took a look at @AudioGod DSDT but I cannot find out how I can use his DSDT on my (different) motherboard to enable native NVRAM, can you help me out a bit further?

[nmano]

I update SSDT for RTC device.

This SSDT automatically rename Device RTC to RTC0

SSDT-RTC0.aml

 

[texem]

7 minutes ago, Styxie said:

 

I took a look at @AudioGod DSDT but I cannot find out how I can use his DSDT on my (different) motherboard to enable native NVRAM, can you help me out a bit further?

 

unfortunately not, I am running a Aorus z390 pro. The DSDT is different.

 

btw: OpenCore 0.54 (beta) , latest support drivers together with my modified DSDT is now working again with native NVRAM . Seems someone fixed something  

 

 

 

 

[mhaeuser]

@texem There were no changes that could affect this, either 1) you did not update FwRuntimeServices earlier 2) you didn't notice you fixed a misconfiguration when upgrading 3) whatever 0.5.3 compilation you used was borked, e.g. it could be a build caching issue of some sort

[texem]

34 minutes ago, Styxie said:

16 minutes ago, Download-Fritz said:

@texem There were no changes that could affect this, either 1) you did not update FwRuntimeServices earlier 2) you didn't notice you fixed a misconfiguration when upgrading 3) whatever 0.5.3 compilation you used was borked, e.g. it could be a build caching issue of some sort

 

Could have been only the latter. I removed all folders and downloaded both parts newly from GIT and compiled the sources. 

Based on a working EFI from mid November I replaced OC and FWRS - but didn't modify config.plist. 

 

 

 

[Styxie]

1 hour ago, texem said:

 

unfortunately not, I am running a Aorus z390 pro. The DSDT is different.

 

 

 

Do you perhaps know the DSDT patches you used to get native NVRAM to work on Z390? AFAIK native nvram was a no-go on Z390, so hearing this is very interesting to me! 

[l.monay]

Are there any known issues about booting windows. I use veracrypt on old asus laptop and  this this entry:

                              <key>Arguments</key>
                              <string></string>
                                        <key>Name</key>
                                        <string>Vera</string>
                              <key>Comment</key>
                              <string>Not signed for security reasons</string>
                              <key>Enabled</key>
                              <true/>
                                        <key>Path</key>
                                        <string>PciRoot(0x0)/Pci(0x1F,0x2)/Sata(0x0,0xFFFF,0x0)/HD(1,GPT,8D0AD20F-B2D8-453E-852C-1AA2CCAF639D,0x44,0xFFBC)/\EFI\VeraCrypt\Dcs.efi</string>
                                </dict>
                        </array>

I get blue screen on windows boot using OC but ok boot using laptop bios. OC is overiding the ACPI BGTR logo for the windows too because the ASUS logo is AWOL

 

Also using the UEFI shell from edk2 to get the PciRoot device the result doesn't work because when I add debug I get the correct value Sata(0x0,0xFFFF,0x0) but with edk2 shell (probably buggy UEFI) which is annoying.

[Ellybz]

@l.monay @kaos kinkae
Check out this post:

 NTFS Driver is also needed. @l.monay You might need some arguments for veracrypt but that latter encryption seems problematic even with Clover. 

Edited December 8, 2019 by Ellybz

[l.monay]

19 hours ago, Ellybz said:

@l.monay @kaos kinkae
Check out this post:

 NTFS Driver is also needed. @l.monay You might need some arguments for veracrypt but that latter encryption seems problematic even with Clover. 

 

Why would the NTFS driver be needed? The NTFS partition is encrypted. The problem is after veracrypt has decrypted the drived Windows doesn't work. If you boot windows without OC then the same install boots fine. The windows 10 loader and veracrypt both live on the ESP partition

 

Can you please explain why you think that NTFS is needed? Why would veracrypt need arguments, there are no arguments needed when you boot veracrypt from the shell.

[mhaeuser]

1 hour ago, l.monay said:

Can you please explain why you think that NTFS is needed? Why would veracrypt need arguments, there are no arguments needed when you boot veracrypt from the shell.

What shell? "GUI Shell" as in the boot menu or UEFI Shell?