OpenCore General Discussion

[Matgen84]

On 8/9/2019 at 9:06 AM, Andres ZeroCross said:

Remember this, typo 1 character, wrong class plist (string, bolean, data, dictionary or other) can make error parsing of config.plist.

You must learn / know for every enable / disable options in your config.plist.

There is no similar "Clover Configurator.app" for OpenCore yet, so manual edit of config.plist must be very carefully

 

 

Very strange issue: yesterday all works fine (thanks for your OC Config.plist). Today, I can't boot: stuck at OpenCore Boot Menu 

Edited August 10, 2019 by Matgen84

[Andres ZeroCross]

58 minutes ago, Matgen84 said:

 

Very strange issue: yesterday all works fine (thanks for your OC Config.plist). Today, I can't boot: stuck at OpenCore Boot Menu 

It mean you have changed configuration or BIOS setting

[Matgen84]

34 minutes ago, Andres ZeroCross said:

It mean you have changed configuration or BIOS setting

 

No change at all. The same USB Drive for test

 

EDIT: reinstall Catalina Beta 5 on Volumes/Catalina. July update on Windows 10 HDD.

Edited August 10, 2019 by Matgen84

[HmO]

2 hours ago, Matgen84 said:

 

Very strange issue: yesterday all works fine (thanks for your OC Config.plist). Today, I can't boot: stuck at OpenCore Boot Menu 

 

[iTTT]

hello , i find one issue related to "About this Mac" -> Memory tab missing...

 

Asus X299 Deluxe II

i9-9920X

iMacPro 1,1

 

if PlatformInfo - Automatic set to "NO", then Memory tab will disappear from "About this Mac".

 

not sure what caused this issue.

 

 

 

 

 

Edited August 10, 2019 by iTTT

[NorthAmTrans]

15 hours ago, dracoflar said:

Well there's a couple issues:

- Your ACPI patches are all using Count = 1, this is very bad as it'll only apply to the first instance and your shouldn't be doing ACPI patches regardless with OpenCore. Look at the sample AcpiSamples folder

- EHC1 to EH01, EHC2 to EH02 are not needed for Skylake+ systems

- GFX0 to IGPU is handled by WhateverGreen already

- Most if not all your ACPI patches are irrelevant, I'm not going to continue critiquing them 

- csr-active-config is a Data value, NOT STRING

- Why are you using Booter quirks if you're not using FwRuntimeServices.efi?

 

Critiques are welcome. It looks like I needed to update my knowledge on what I was using and why in Clover first. This was actually quite helpful so thank you.

 

I'm starting back with a cleaned up build. If you've got the time to double check these below I'd be most grateful!

 

My only patches are: EC0 to EC and _DSM to XDSM. In the thought of not having any patches at all, how would you recommend implementing these? This might seem elementary to you so forgive me in advance.

 

I also have 2 boot args: nvdisable_1 dart=0.

 

Im guessing with dart=0 it's unnecessary. I have VTD enabled in bios so it's redundant to kill it with that, correct? If not I could just turn if off in bios. Not even sure why I have it on. Parallels maybe?

 

With nvdisable_1, if I'm reading it right, it disables Nvidia drivers. Do you know if those are killed anyways by Whatevergreen?

 

I've also filled in device properties as well while adding my audio device and layout ID to simplify things when moving to Opencore.

 

Thanks in advance

 

 

 

 

[dracoflar]

20 minutes ago, NorthAmTrans said:

 

Critiques are welcome. It looks like I needed to update my knowledge on what I was using and why in Clover first. This was actually quite helpful so thank you.

 

I'm starting back with a cleaned up build. If you've got the time to double check these below I'd be most grateful!

 

My only patches are: EC0 to EC and _DSM to XDSM. In the thought of not having any patches at all, how would you recommend implementing these? This might seem elementary to you so forgive me in advance.

 

I also have 2 boot args: nvdisable_1 dart=0.

 

Im guessing with dart=0 it's unnecessary. I have VTD enabled in bios so it's redundant to kill it with that, correct? If not I could just turn if off in bios. Not even sure why I have it on. Parallels maybe?

 

With nvdisable_1, if I'm reading it right, it disables Nvidia drivers. Do you know if those are killed anyways by Whatevergreen?

 

I've also filled in device properties as well while adding my audio device and layout ID to simplify things when moving to Opencore.

 

Thanks in advance

 

 

 

 

So I'll be basing the following off this hardware: Asus Prime z370a 1, 8700, rx580, Mojave 10.14.6

 

EC0 to EC:

This can be implemented with the SSDT-EC-USBX.dsl

 

_DSM to XDSM:

Your hardware shouldn't need this

 

nvdisable_1:

Remove entirely, not needed as you're running an AMD GPU

 

dart=0:

You can keep this and set the quirk DisableIOmapper to YES, this will allow you to use VT-D and run VMs

 

If you're wanting a more step by step guide, you can look at this guide: OpenCore vanilla Desktop Guide

 

[Pavo]

Anyone know if there is away to set cpu-type in OpenCore?

[iTTT]

10 minutes ago, Pavo said:

Anyone know if there is away to set cpu-type in OpenCore?

 

PlatformInfo -> SMBIOS -> ProcessorType

[matgeo]

11 hours ago, matgeo said:

Anyone can help?

 

I'm on a Dell 5570 and I cannot boot on High Sierra and Catalina.

 

It just hangs on boot picker.

 

Thanks in advance.

OC.zip

Anyone?

[Guest]

@dracoflar

Thanks for linking open core detailed guide

 

[stinga11]

How can I create a log with opencore to see if I have any errors?

[Guest]

2 minutes ago, stinga11 said:

How can I create a log with opencore to see if I have any errors?

use debug version

 

[NorthAmTrans]

2 hours ago, dracoflar said:

So I'll be basing the following off this hardware: Asus Prime z370a 1, 8700, rx580, Mojave 10.14.6

 

EC0 to EC:

This can be implemented with the SSDT-EC-USBX.dsl

 

_DSM to XDSM:

Your hardware shouldn't need this

 

nvdisable_1:

Remove entirely, not needed as you're running an AMD GPU

 

dart=0:

You can keep this and set the quirk DisableIOmapper to YES, this will allow you to use VT-D and run VMs

 

If you're wanting a more step by step guide, you can look at this guide: OpenCore vanilla Desktop Guide

 

 

Thank you very much.

 

I'll get on figuring out the SSDT-EC-USBX.dsl. I currently have a SSDT-EC.aml that works if I have EC0>EC patched. Looking forward to simplifying that.

 

Without _DSM>XDSM I lose my X86 platform and AGPM power management. Im wondering if there's another way I'm unaware of.

 

Disabled nvdisable_1.

 

Once I figure out these loose ends I'll go back to the guide you sent and will DEFINITELY have some questions about "schema" and SMBIOS. 

[Pavo]

25 minutes ago, NorthAmTrans said:

Without _DSM>XDSM I lose my X86 platform and AGPM power management. Im wondering if there's another way I'm unaware of.

SSDT-PLUG

[stinga11]

1 hour ago, fabiosun said:

use debug version

 

Ok, If I want to save the log on the early booting screen to .txt on mac os x or efi folder, How can do this

[Erroruser]

2 minutes ago, stinga11 said:

Ok, If I want to save the log on the early booting screen to .txt on mac os x or efi folder, How can do this

set like so then a log will be place on the ESP along side of the efi folder

 

any idea how to remove as i see it just before the picker

[NorthAmTrans]

46 minutes ago, Pavo said:

SSDT-PLUG

 

Not sure if it's because I haven't moved to OC yet but I can't get that one to work. This still requires DSM as well.

 

Perhaps I'm saving it wrong. I have extension ".aml"

 

Side note, without EC0>EC I can you use SSDT-EC.aml to get EC to show up, however in IOreg I have both EC and EC0 loaded. I don't have a 19,2 IOreg to compare to but if memory serves it's supposed to only be EC, right?

Edited August 10, 2019 by NorthAmTrans
new info

[justin]

13 minutes ago, NorthAmTrans said:

 

Not sure if it's because I haven't moved to OC yet but I can't get that one to work. This still requires DSM as well.

 

Side note, without EC0>EC I can you use SSDT-EC.aml to get EC to show up, however in IOreg I have both EC and EC0 loaded. I don't have a 19,2 IOreg to compare to but if memory serves it's supposed to only be EC, right?

 

 

When using SSDT-PLUG, you need to  know where your CPU is located in DSDT, is it PR00 or something else? Check it with MaciAsl.app. 

 

When using SSDT-EC.aml, it means you are going to Fake a EC device or Rename EC0 to EC, but not both, check the content of that aml. 

 

 

[gengik84]

 

25 minutes ago, NorthAmTrans said:

Side note, without EC0>EC I can you use SSDT-EC.aml to get EC to show up, however in IOreg I have both EC and EC0 loaded. I don't have a 19,2 IOreg to compare to but if memory serves it's supposed to only be EC, right?

it's not really good to have AppleacpiEC and AppleBusPowerController in in the same device and when we can its better to disable AppleAcpiEC 

Rename EC0 to EC does this in many cases

Device EC

             |- AppleACPIEC

             |- AppleBusPowerController

https://github.com/acidanthera/OpenCorePkg/blob/master/Docs/AcpiSamples/SSDT-EC.dsl

[NorthAmTrans]

16 minutes ago, justin said:

 

 

When using SSDT-PLUG, you need to  know where your CPU is located in DSDT, is it PR00 or something else? Check it with MaciAsl.app. 

 

When using SSDT-EC.aml, it means you are going to Fake a EC device or Rename EC0 to EC, but not both, check the content of that aml. 

 

 

Thanks for the help. Focusing on SSDT-Plug x86 platform. When I look at it in I0reg it's "PR00" and perhaps im renaming wrong.

 

DefinitionBlock ("", "SSDT", 2, "CpuRef", "CpuPlug", 0x00003000)
{
    External (_PR_.CPU0, ProcessorObj)    // (from opcode)

    Scope (\_PR.CPU0)
    

 

[justin]

4 minutes ago, NorthAmTrans said:

Thanks for the help. Focusing on SSDT-Plug x86 platform. When I look at it in I0reg it's "PR00" and perhaps im renaming wrong.

 

DefinitionBlock ("", "SSDT", 2, "CpuRef", "CpuPlug", 0x00003000)
{
    External (_PR_.CPU0, ProcessorObj)    // (from opcode)

    Scope (\_PR.CPU0)
    

 

 

https://raw.githubusercontent.com/cattyhouse/oc-guide/master/EFI/OC/ACPI/SSDT-PLUG.aml

[AlGrey]

On 8/9/2019 at 10:19 AM, Andres ZeroCross said:

I have installed AMD hackintosh before,, if something wrong about kernel patcher can make stuck in "random seed".

Can you check again your kernel patch?? Boot with clover with disable all kernel patch,, check if you can bypass random seed error. just to make sure your issue is not about "kernel patch"

I can confirm that fully working AMD kernel patches are not anymore since Aptiomemoryfix is embedded in OC - stuck at End randomseed. What am I missing?

 

EDIT : FIXED WITH NEW DOCUMENTATION. Below still valid. 

 

Also, the first patch  [0]:

<dict>
                <key>Comment</key>
                <string>algrey - commpage_populate -remove rdmsr</string>
                <key>Count</key>
                <integer>0</integer>
                <key>Enabled</key>
                <true/>
                <key>Find</key>
                <data>
                uaABAAAPMg==
                </data>
                <key>Identifier</key>
                <string>kernel</string>
                <key>Limit</key>
                <integer>0</integer>
                <key>Mask</key>
                <data>
                </data>
                <key>MatchKernel</key>
                <string></string>
                <key>Replace</key>
                <data>
                Dx+AAAAAAA==
                </data>
                <key>ReplaceMask</key>
                <data>
                </data>
                <key>Skip</key>
                <integer>0</integer>
            </dict>

this patch which is universal across any XNU version (10.13.6 and above)  is replaced 15 times, but if you open the kernel in a decompiler your clearly see that B9A00100000F32 is found once. So I don't know what is patched 15 times to be honest.

 

@vit9696 maybe you could help me with that ?

21:208 00:064 OCC: Configuring behaviour 0
21:462 00:254 Trying XNU hook on System\Library\PrelinkedKernels\prelinkedkernel
21:627 00:165 Kext reservation size 7860224
22:522 00:895 Result of XNU hook on System\Library\PrelinkedKernels\prelinkedkernel is Success
22:590 00:067 OC: Read kernel version 18.2.0
22:761 00:171 ReplaceCount - 15
22:793 00:031 OC: Kernel patcher result 0 for kernel - Success
22:965 00:172 ReplaceCount - 1
22:998 00:032 OC: Kernel patcher result 1 for kernel - Success
23:175 00:177 ReplaceCount - 1
23:206 00:031 OC: Kernel patcher result 2 for kernel - Success
23:380 00:173 ReplaceCount - 1
23:409 00:029 OC: Kernel patcher result 3 for kernel - Success
23:579 00:169 ReplaceCount - 1
23:609 00:030 OC: Kernel patcher result 4 for kernel - Success
23:778 00:169 ReplaceCount - 1
23:809 00:031 OC: Kernel patcher result 5 for kernel - Success
23:982 00:172 ReplaceCount - 1
24:015 00:032 OC: Kernel patcher result 6 for kernel - Success
24:186 00:171 ReplaceCount - 1
24:217 00:031 OC: Kernel patcher result 7 for kernel - Success
24:451 00:233 ReplaceCount - 1
24:481 00:030 OC: Kernel patcher result 8 for kernel - Success
24:653 00:172 ReplaceCount - 2
24:684 00:031 OC: Kernel patcher result 9 for kernel - Success
24:857 00:173 ReplaceCount - 1
24:889 00:031 OC: Kernel patcher result 10 for kernel - Success
25:063 00:173 ReplaceCount - 1
25:093 00:030 OC: Kernel patcher result 11 for kernel - Success
25:131 00:038 ReplaceCount - 3
25:164 00:033 OC: Kernel patcher result 12 for kernel - Success
25:339 00:174 ReplaceCount - 1
25:372 00:033 OC: Kernel patcher result 13 for kernel - Success
25:546 00:173 ReplaceCount - 1
25:576 00:030 OC: Kernel patcher result 14 for kernel - Success
25:748 00:172 ReplaceCount - 1
25:781 00:033 OC: Kernel patcher result 15 for kernel - Success
25:964 00:183 ReplaceCount - 1
26:005 00:041 OC: Kernel patcher result 16 for kernel - Success
26:065 00:059 ReplaceCount - 1
26:097 00:032 Patch success com.apple.iokit.IOUSBHostFamily
26:139 00:042 ReplaceCount - 1
26:173 00:033 Patch success com.apple.driver.usb.AppleUSBXHCI
26:228 00:055 OC: Prelink injection Lilu.kext - Success
26:278 00:050 OC: Prelink injection FakeSMC.kext - Success
26:323 00:045 OC: Prelink injection WhateverGreen.kext - Success
26:367 00:044 OC: Prelink injection AppleALC.kext - Success
26:404 00:037 OC: Prelink injection NullCPUPowerManagement.kext - Success
26:451 00:046 OC: Prelink injection RealtekRTL8111.kext - Success
26:514 00:062 Prelinked status - Success

 

Edited August 11, 2019 by AlGrey

[NorthAmTrans]

27 minutes ago, gengik84 said:

 

it's not really good to have AppleacpiEC and AppleBusPowerController in in the same device and when we can its better to disable AppleAcpiEC 

Rename EC0 to EC does this in many cases

Device EC

             |- AppleACPIEC

             |- AppleBusPowerController

https://github.com/acidanthera/OpenCorePkg/blob/master/Docs/AcpiSamples/SSDT-EC.dsl

 

Giant help. The only patch left is DSM>XDSM. Thank you.

[NorthAmTrans]

27 minutes ago, justin said:

 

https://raw.githubusercontent.com/cattyhouse/oc-guide/master/EFI/OC/ACPI/SSDT-PLUG.aml

 

Man, still didn't work. Thanks for the effort here. I'll keep digging.