Jump to content

OpenCore General Discussion

dgsga

By dgsga,
in OpenCore

 Share
8,805 posts in this topic

Recommended Posts

gengik84
gengik84
Posted
Posted

 

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

  • Like 2
Link to comment
Share on other sites
NorthAmTrans
NorthAmTrans
Posted
Posted
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)

 

Link to comment
Share on other sites
justin
justin
Posted
Posted
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

  • Like 1
Link to comment
Share on other sites
AlGrey
AlGrey
Posted
Posted (edited)
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 by AlGrey
  • Like 1
Link to comment
Share on other sites
NorthAmTrans
NorthAmTrans
Posted
Posted
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.

  • Like 1
Link to comment
Share on other sites
Pavo
Pavo
Posted
Posted

@vit9696 

Above 4G Decoding or similar enabled in firmware settings if present. Note, that on some motherboards (notably
ASUS WS-X299-PRO) this option causes adverse effects, and must be disabled. While no other motherboards
with the same issue are known, consider this option to be first to check if you have erratic boot failures.

ASUS Z9PE-D8 WS also requires this setting to be disabled in firmware or you lose audio device.

Link to comment
Share on other sites
Badruzeus
Badruzeus
Posted
Posted (edited)

Still unable booting macOS after AptioMemoryFix.efi has been embedded into OpenCore.efi on my 2nd Gen. laptop (sig). OC DEBUG (or RELEASE) version is loaded, but once I select OS entry it got reboot immediately after `End randomseed` appears. My mach has AMI Aptio UEFI 2.0, it has no EFI GOP support, nor CSM option on BIOS, nor VT-d. With Clover I use AptioMemoryFix.efi plus slide=128 boot-arg (otherwise having KASLR warning), no need EmuVariableUefi.efi and my NVRAM was run natively (with or w/o FwRuntimeServices.efi doesn't make any difference). macOS 10.13.6 & 10.15 Beta are installed on HFS+ so I don't use ApfsDriverLoader.efi.

 

Previous OC 2019-07-27 run really well #BTW. Probably I made some mistakes on config.plist?

So, here I attached my complete EFI (with _MASKED_ some sensitive datas on PlatformInfo). Thanks.

EFI-Oc-A43SJ-20190811.zip

Edited by Badruzeus
  • Like 1
Link to comment
Share on other sites
dracoflar
dracoflar
Posted
Posted
5 hours ago, Badruzeus said:

Still unable booting macOS after AptioMemoryFix.efi has been embedded into OpenCore.efi on my 2nd Gen. laptop (sig). OC DEBUG (or RELEASE) version is loaded, but once I select OS entry it got reboot immediately after `End randomseed` appears. My mach has AMI Aptio UEFI 2.0, it has no EFI GOP support, nor CSM option on BIOS, nor VT-d. With Clover I use AptioMemoryFix.efi plus slide=128 boot-arg (otherwise having KASLR warning), no need EmuVariableUefi.efi and my NVRAM was run natively (with or w/o FwRuntimeServices.efi doesn't make any difference). macOS 10.13.6 & 10.15 Beta are installed on HFS+ so I don't use ApfsDriverLoader.efi.

 

Previous OC 2019-07-27 run really well #BTW. Probably I made some mistakes on config.plist?

So, here I attached my complete EFI (with _MASKED_ some sensitive datas on PlatformInfo). Thanks.

EFI-Oc-A43SJ-20190811.zip

ProvideConsoleGop is required as this was handled by AptioMemoryFix before

Link to comment
Share on other sites
tiger511
tiger511
Posted
Posted
On 5/7/2019 at 11:57 PM, Andres ZeroCross said:

OpenCore Bootloader with macOS Mojave 10.14.5 Beta 4 Build 18F127a

 

Specifications :
- Processor : Intel Core i7 6700
- iGPU : Intel HD 530
- eGPU : MSI Armor RX580 4GB
- Motherboard : Gigabyte Z170X Gaming 7
- Storage : 1x MSata WD 240GB + 2x SSD @120GB + 5 HDD Storage (2x 2TB + 2x 500GB)
- Wifi + Bluetooth : Broadcom BCM943602CS
- Audio Codec : Creative CA0132 (5.1 Audio work)
- RAM : 8GB (2x4GB) PC24000 (3000Mhz)
- OpenCore version : rev 0.0.2
- Boot Mode : UEFI


What's work??
- Sleep, Shutdown, and Restart
- Good Cpu Power Management
- HEVC and H264 for IGPU and eGPU
- All USB Port 
- Unlock limit patch USB from config.plist of OpenCore (Built-in, just enable it)
- QE/CI for RX580
- Faster boot time than clover
- All kext in OC/Kexts is loaded perfectly
- HDMI Audio 
- Audio Onboard (CA0132)

All ACPI patch is in DSDT only,, no patch / binary DSDT patch from config.plist of OpenCore.

I can say, all device work like using Clover but better boot time and Cpu Power management (my opinion)
 

 

Can you share your OC folder please? Im trying to make Opencore work on XPS 9550 but the resources are very limited compared to clover.

Link to comment
Share on other sites
Badruzeus
Badruzeus
Posted
Posted (edited)
7 hours ago, dracoflar said:

ProvideConsoleGop is required as this was handled by AptioMemoryFix before

It doesn't help unfortunately, I never use ProvideConsoleGop upto OC 2019-07-27 and it was working, now it' s not.

 

#EDIT: But thanks for suggestion anyway.

Edited by Badruzeus
  • Like 1
Link to comment
Share on other sites
gengik84
gengik84
Posted
Posted

@matgeoMaybe ssdt does not load

did you add it on the config/ACPI?

remove this from your ssdt 

    External (_SB_.PCI0.LPCB.ECDV, DeviceObj)    // (from opcode)

    Scope (\_SB.PCI0.LPCB.ECDV)
    {
        Method (_STA, 0, NotSerialized)  // _STA: Status
        {
            If (_OSI ("Darwin"))
            {
                Return (Zero)
            }
            Else
            {
                Return (0x0F)
            }
        }
    }

Because in laptop you lose battery

  • Haha 1
Link to comment
Share on other sites
vandroiy2012
vandroiy2012
Posted
Posted (edited)
11 minutes ago, matgeo said:

I don't understand.

Should I have the native ECDV in my ioreg or disable it and add a fake EC ?

 

Is this a notebook? If yes you have to rename it in order to not brake battery statistics. If it is desktop you must disable it an add new EC device. 

Edited by vandroiy2012
  • Like 1
Link to comment
Share on other sites
chris1111
chris1111
Posted
Posted (edited)

The problem with OC bootloader is that there will be no installation program like all the others that have had success on the Hackintosh scene, like Chameleon or Clover. people want things to be easier and faster, and when it's too much complicated to do and not fast, they move on to other things.

You should have provided a generic installation program that would work for the majority and could have been manually configured later or with an application.

This is my opinion.

 

EDIT ****

Do you think there were so many people to install macOS on the old mac if dosdude1 did not create a program to do it

Answer NO

Edited by chris1111
  • Thanks 1
Link to comment
Share on other sites
NorthAmTrans
NorthAmTrans
Posted
Posted
8 hours ago, matgeo said:

Did you manage to disable eco and fake a ec device?

 

Could you upload the ec.aml you made ?

 

Thanks in advance.

Yes. The SSDT-EC.aml file had a section that needed to be enabled. Here's where I landed and it works. For learning, you should compare to the original one a page or two back.

SSDT-EC.aml

Link to comment
Share on other sites
matgeo
matgeo
Posted
Posted
18 minutes ago, vandroiy2012 said:

 

Is this a notebook? If yes you have to rename it in order to not brake battery statistics. If it is desktop you must disable it an add new EC device. 

Yes , it is a notebook.

 

I would suggest add this note to first page guide.

Link to comment
Share on other sites
NorthAmTrans
NorthAmTrans
Posted
Posted (edited)

2 items left for me: XCPM and an SSDT to rename DSM>XDSM. It's time I learn how to make my own SSDT.

 

EDIT: XCPM is taken care of. 

 

This is as far as I've gotten. I definitely do not know what Im doing so bare with.

  


    Scope (DSM)
    {
        Name (_STA, Zero) // _STA: Status
    }
    Device (XDSM)
    {
        Name (_ADR, Zero) // _ADR: Address

 

Edited by NorthAmTrans
resolved issue
Link to comment
Share on other sites
LAbyOne
LAbyOne
Posted
Posted
3 hours ago, chris1111 said:

The problem with OC bootloader is that there will be no installation program like all the others that have had success on the Hackintosh scene, like Chameleon or Clover. people want things to be easier and faster, and when it's too much complicated to do and not fast, they move on to other things.

You should have provided a generic installation program that would work for the majority and could have been manually configured later or with an application.

This is my opinion.

 

EDIT ****

Do you think there were so many people to install macOS on the old mac if dosdude1 did not create a program to do it

Answer NO

I maybe have misunderstood your point, 

but, hackintosh is not a brand, just a choice anyone make for its own purpose

hence the unavoidable need to understand what they are doing, its something you take on yourself first, then using places like insanelymac you can find help to solve issues, but the base is you have to learn first

Sure Clover simplified the installation providing an installer.... but if you then have to modify your config or any other file you will mount your EFI and make the changes... 

its only a bootloader nothing similar to what dosdude1 did

So i can't really see what would make this one so uncomfortable to set up.

then again I maybe have misunderstood your point...

 

The real problem in my opinion 

is that there are also many people now too *miseducated to be able to give real contribution, quoting what you said " people want things to be easier and faster", well people must understand also that sometimes things are different and require a different spirit.

 

PS

*miseducated = people who just want to find the supper ready, and can't even make a sandwich by themselves :)

  • Like 1
Link to comment
Share on other sites
UefiBooter
UefiBooter
Posted
Posted
3 hours ago, chris1111 said:

The problem with OC bootloader is that there will be no installation program like all the others that have had success on the Hackintosh scene, like Chameleon or Clover. people want things to be easier and faster, and when it's too much complicated to do and not fast, they move on to other things.

You should have provided a generic installation program that would work for the majority and could have been manually configured later or with an application.

This is my opinion.

 

EDIT ****

Do you think there were so many people to install macOS on the old mac if dosdude1 did not create a program to do it

Answer NO

Chris, may i draw your attention to the following disclaimer from the OpenCore git page

 

WARNING: This release is a developer preview, i.e. it targets experienced engineers and developers. Configuration and feature set are under works, i.e. refinements are expected to happen .....

 

  • Like 2
Link to comment
Share on other sites
Sniki
Sniki
Posted
Posted

@vit9696 Thanks for all the suggestions and help into the issues we discussed.

You were correct !,

For now TgtBridge function may not be needed as thanks to @ben9923 solution after analysing my DSDT, we dropped the old way of patching the TPD0 device with a better and simpler solution thanks to the template/idea of your SSDT-AWAC.dsl on ACPI Samples.

Previously i had to patch TPD0 _CRS to XCRS and TPD0 _DSM to XDSM and add the patched code into a SSDT which we required the TgtBridge to specify which "device" CRS and DSM method to rename.

Now we removed all Renames needed for Touchpad from config.plist and simply use this SSDT based on your SSDT-AWAC.dsl template: 

// Touchpad fix for Lenovo V330-15IKB

DefinitionBlock ("", "SSDT", 2, "V330", "_TPD0", 0)
{
    External (SDM0, IntObj)

    Scope (_SB)
    {
        Method (_INI, 0, NotSerialized)  // _INI: Initialize
        {
            If (_OSI ("Darwin"))
            {
                SDM0 = Zero
            }
        }
    }
}

And TouchPad now works like charm.

 

About the InfoPlistPatch to disable AppleI2C kext from loading, i first solved the problem by blocking the kext from loading with OpenCore config.plist/Kernel/Block and by listing com.apple.driver.AppleIntelLpssI2C

 

However after @ben9923 told that he found the solution to load VoodooI2C without disabling the AppleIntelI2C kext with your help by just adding: 

<key>OSBundleRequired</key>
<string>Root</string>

Into VoodooI2C.kext, Plugins and Satellite kexts, VoodooI2C kexts work excellent on OpenCore.

 

Thanks a lot to all of you.

Now my Lenovo V330-15IKB works perfect.

 

Laptops should not be a problem anymore and can use Open Core as default Bootloader.

I will soon start working on the project i mentioned on the Sep. Release schedule on Bugtracker which i think should make it easier for everyone else to have laptop templates for each generation.

 

Sincerely,

Sniki

  • Like 2
Link to comment
Share on other sites
FredWst
FredWst
Posted
Posted

@vit9696

 

Hi,

 

Since some build, I'm not able to get verbose mode on all my hacks and no Apple logo in first stage boot.

it began just after using FwRuntimeServices.efi. (Don't remember which build it began and not sure it's OC issue)

 

Somebody else got the same issue ?

 

Fred

 

Link to comment
Share on other sites
 Share
Go to topic listing
×
×
  • Create New...