Jump to content

OpenCore General Discussion


dgsga
8,888 posts in this topic

Recommended Posts

10 minutes ago, Muntashir said:

It's clearly present in the Configurations.pdf file (in the Booter section). Set `ForceExitBootServices=YES`.

didnt help. Still getting same error;

 

IMG_0032.JPG.9ecefe40baf587dbf8546757f22cb2c9.JPG

 

Another question; Recommended BIOS settings says use Windows8.1/10 for boot. But I dont have this options; I have just two options Other OS and Windows UEFI which one I must choose?

 

IMG_0030.jpg.5a1b2d316d93103e0f52f05b8f7de2a6.jpg

Link to comment
Share on other sites

34 minutes ago, jinbingmao said:

Windows UEFI

Thanks. I thought maybe this affect but still getting the same error. Another question should I need virtualsmc.efi as far as I know its implemented in the latest FwRuntimeServices.efi. am I right? 

Link to comment
Share on other sites

7 hours ago, telepati said:

didnt help. Still getting same error;

If you've read the configuration.pdf, you'll find that there are several reason for this freeze. For instance, you may have to set `ReleaseUsbOwnership=YES` in the `UEFI` section, `DisableVariableWrite=YES` and `ForceExitBootServices=YES` in `Booter` or a combination of them (including `SetupVirtualMap`, `EnableWriteUnprotector`, `ShrinkMemoryMap`).

Link to comment
Share on other sites

48 minutes ago, gengik84 said:

Add SSDT: AWAC and EC

I disable DSDT.aml and added all necessary SSDT's now I am getting panic.

 

IMG_0043.thumb.JPG.1cea6c6ddb903c46f0417d790d3be1ca.JPG

 

I am not set to DisableVariableWrite=YES cause I am already using SSDT-PMC.aml which is also implemented in my DSDT.aml. 

 

When I set to ShrinkMemoryMap 'YES' I am getting the halting critical error;

 

IMG_0033.jpeg.d1b2301dc51d8ec446e9cb64a780bd08.jpeg

 

This is my latest EFI;

 

EFI.zip

  • Sad 1
Link to comment
Share on other sites

2 hours ago, telepati said:

I disable DSDT.aml and added all necessary SSDT's now I am getting panic.

 

IMG_0043.thumb.JPG.1cea6c6ddb903c46f0417d790d3be1ca.JPG

 

I am not set to DisableVariableWrite=YES cause I am already using SSDT-PMC.aml which is also implemented in my DSDT.aml. 

 

When I set to ShrinkMemoryMap 'YES' I am getting the halting critical error;

 

IMG_0033.jpeg.d1b2301dc51d8ec446e9cb64a780bd08.jpeg

 

This is my latest EFI;

 

EFI.zip

Try this config, used on GiGabyte z390 w/9600k.. look to also setting up device properties with hackintool . If it boots can fine tune. 

config.plist

  • Like 1
Link to comment
Share on other sites

49 minutes ago, Andrey1970 said:

Delete it:

372314449_2020-01-2410_33_39.png.c80160d10a16dbd69fb6287b5410ee4d.png

 

And add HfsPlus.efi

HfsPlus.efi.zip

thanks Andrey1970 worked Recovery partition with HfsPlus.efi

I have second issue that when I play 60fps video 1080p with QuickTime player then little screen flickering black 

nothing issue with 30fps only issue is 60fps

I think this is Shiki related bug 

how can I solve this? any idea

  • Like 1
Link to comment
Share on other sites

When you update OpenCore please make sure turnon KeySupport =Yes

 

 

1057976923_ScreenShot2020-01-24at7_03_41AM.png.64efff399c43316d303eb8d62144b62b.png

 

1516546508_ScreenShot2020-01-24at7_11_17AM.thumb.png.932083f1adf6978c673ac2cc50195ca4.png

 

 

PMCR update for X299 WU8

SSDT-PMC1.aml

 

1219603178_ScreenShot2020-01-24at8_16_31AM.png.a8d1ac84d9dc6da427d1fa519942dfca.png

 

Edited by nmano
Link to comment
Share on other sites

Hi

I have a problem I have tried this in Mojave and Catalina but both macOS the result is same. the issue is when I use Bootcamp to install Windows 10 it starts and complete the installation in macOS. but when it restarts some how BOOT folder DELETES itself from EFI folder which render non bootable and system goes into BIOS setup screen. OC folder remains intact.

Any help appreciated,

Thank you,

Link to comment
Share on other sites

35 minutes ago, mathew2019 said:

@Andrey1970 do you have any idea why BOOT folder in EFI folder deletes itself when using BootCamp? tried several times but result is same.

 

Thank you,

Because Winblows installs it own EFI, which will delete any existing EFI currently on the ESP. It’s best to completely disconnect the drive that you have your opencore EFI on when installing Winblows.

Link to comment
Share on other sites

×
×
  • Create New...