Jump to content
8755 posts in this topic

Recommended Posts

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
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
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

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

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,

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.

Hi Pavo

 

Thank you for the reply but it wont delete the entire EFI folder. The OC folder in EFI folder / partition is still there..only BOOT folder which contains BOOTX64.efi deletes. so is it a bug or some settings need to be added in Config.plist? Please see the screen shot of EFI folder attached here with.

 

 

OC-EFI-FOlder.png

Edited by mathew2019

The BootX64.efi is basically a re-directing module. That is what UEFI looks for in drives in order to add it to the boot menu entry for your mobo. If you are installing Windows it "could" potentially replace that file for its own which will make the BootX64.efi file direct it to the Winblows boot.efi (windows bootloader) location. Again I suggest you disconnect the drive completely that has OpenCore EFI on it and install Windows on its own.

 

4 minutes ago, mathew2019 said:

Pavo

 

But then how do you dual boot with Windows on single drive? because I am partitioning it and there is no other drive..

You install Winblows first and then install macOS second and add your OpenCore EFI after.

1 hour ago, mathew2019 said:

Pavo

 

But then how do you dual boot with Windows on single drive? because I am partitioning it and there is no other drive..

 

You have to deploy Windows manually using DISM tool. Here is manual. It's in russian. Use Google translate. 

https://applelife.ru/threads/manual-ustanovka-macos-i-windows-na-odin-xard-poshagovo.38295/page-30#post-548639

 

4 hours ago, Pavo said:

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.

umm no it doesnt. it removes BOOTX64.efi and the /EFI/BOOT folder as part of the boot camp installation, when OS X and Windows are shared on the same disk.

 

so much misinformation in this thread these days, reminds me more of a clover thread.

 

 

Just install OS X first as then use the boot camp assistant to install Windows.

 

note more recent versions of boot camp assistant may create the modified windows installer on a ExFat usb drive instead of Fat32.

 

either copy the files onto a Fat32 or add a ExFat uefi driver to OpenCore.

Edited by UefiBooter
spelling
×
×
  • Create New...