Jump to content

2,100 posts in this topic

Recommended Posts

6 minutes ago, Sniki said:

Hi Open Core team or anyone else that can help

 

Im trying to do a clean install on my Lenovo ThinkPad X240.

I did create the Catalina USB Installer but it is not showing on the OC Picker.

 

I don't understand this part very well:

  1.  

I attached the EFI folder so maybe someone can point me where the problem is.

Where is tha com.apple.recovery.boot directory supposed to be ?

 

I only see:

1. Mac (currently installed macOS Catalina beta 11 - main boot drive)

2. Recovery (10.15) dmg

3. OpenCore Shell

 

The installer is created with create install media method as requested and the EFI folder is on the EFI partition.

 

CC @vit9696 @Andrey1970 @Download-Fritz @PMheart @vandroiy2012

 

Here is the EFI: EFI.zip

Try this config, you really should not use ACPI > Patches section to rename DSDT devices. You should use SSDTs

config.plist.zip

Share this post


Link to post
Share on other sites
Advertisement
Posted (edited)
19 minutes ago, Pavo said:

Try this config, you really should not use ACPI > Patches section to rename DSDT devices. You should use SSDTs

config.plist.zip

Ok so it was scanpolicy, Thanks @Pavo

 

I have SSDTs for everything, Renames are necessary for Battery Status and Dual Battery Support.

This is the only way "that i currently know" to implement that without patched DSDT, so you can have full hotpatch system.

 

How would you implement it without Renames and (without Patched DSDT because i want full hotpatch) in this case ?

What would be your recommendations ?

Edited by Sniki

Share this post


Link to post
Share on other sites
10 minutes ago, Sniki said:

Ok so it was scanpolicy, Thanks @Pavo

 

I have SSDTs for everything, Renames are necessary for Battery Status and Dual Battery Support.

This is the only way "that i currently know" to implement that without patched DSDT, so you can have full hotpatch system.

 

How would you implement it without Renames and (without Patched DSDT because i want full hotpatch) in this case ?

What would be your recommendations ?

Here is an example of how I do my rename for my ethernet port on-board. BR1B > ETH0

 

Scope (\_SB.PCI0.PEX0)
    {
        If (_OSI ("Darwin"))
        {
            Scope (BR1B)
            {
                Method (_STA, 0, NotSerialized)  // _STA: Status
                {
                    Return (Zero)
                }
            }

            Device (ETH0)
            {
                Name (_ADR, Zero)  // _ADR: Address
                Method (_STA, 0, NotSerialized)  // _STA: Status
                {
                    Return (0x0F)
                }
            }

            Method (_DSM, 4, NotSerialized)  // _DSM: Device-Specific Method
            {
                Return (Package (0x02)
                {
                    "location", 
                    Buffer (0x02)
                    {
                        "1"
                    }
                })
            }
        }
    }

 

Share this post


Link to post
Share on other sites
Posted (edited)

Hi OpenCore Testers

 

I'm trying to do a clean install of High Sierra 10.13.6 on my Ive Bridge laptop to try and switch to OpenCore from Clover, booting through external HFS installers went super smooth and OS installation stage breezed through fine, but then booting into the installed APFS volume post-install the booting process ends up stalling and stopping at this:

kextd stall[0], (240s): 'X86PlatformPlugin' , 'MCHC' , 'GFX0' , "AppleHDAHardwareConfigDriverLoader' , 'IOResources' 

 

Kexts I am using: Lilu, VirtualSMC, WEG, ALC
 

I haven't been able to find a fix for this with the OpenCore bootloader yet, I think  Im missing some ACPI patching/fixes not mentioned anywhere on this forum or elsewhere, if anyone could help out would be greatly appreciated !  
 

Here is the EFI EFI.zip

 

Thanks and happy testing everyone !

 

Edited by aben

Share this post


Link to post
Share on other sites
Posted (edited)
On 9/28/2019 at 1:52 PM, ham4ever said:

I managed to solve a lot fails by looking at the comments and reading the manual.

 

i have one single fail left that i couldn't find anything about it:

 

OCB: Failed to match a default boot option.

 

EDIT: to be clear, the system does boot and all, is just that line appears before booting and is bothering me. 

I have the same issue since updating to OC 0.5.1. Did you find a fix for this? (I tried selecting the startup disk in system preferences)

 

EDIT: the fix is setting RequestBootVarRouting = TRUE

Edited by canyondust

Share this post


Link to post
Share on other sites

Hi all OpenCore testers,

 

I encountered an issue with assigning default boot option and hope if anyone could shed me some light. Assigning default boot option via Startup Disk preference panel doesn't seem to have any effect to the default boot-up option of OpenCore. I changed it to two different disks but the OpenCore default stays still the first one (an EFI). 

 

I can see that efi-boot-device in nvram.plist is able to change according to the selection on Startup Disk preference panel. However that doesn't change what OpenCore brings up as the default. 

 

These are tested with RequestBootVarRouting enabled. When disabled, the default booting option stayed on the second entry of the booting list (another EFI...), regardless of what was chosen on the Startup Disk preference panel. 

 

Other than this issue, OpenCore has been working flawlessly with my hack. Well done guys! 

 

My plist can be found below, and the specs. Thanks. 

 

CPU: i5-8500

GPU: Sapphire RX580 Pulse

RAM: Corsair - Vengeance LPX 2 x 8GB DDR4-3000

Motherboard/Laptop model: Gigabyte B360 AORUS Gaming 3 WIFI

config copy.plist

Share this post


Link to post
Share on other sites
On 10/7/2019 at 8:12 PM, duffs said:

When installing catalina i got error "an error occurred while verifying firmware" it turns out that my FirmwareFeatures ported from clover was wrong. Fixing that, install went thru just fine. Used one from sample.plis.

 

 

Missing some functionality from clover like "lastbootedvolume". When installing Macos on reboot  clover automatically selected "macOS installer" and continue installing. does this work?

 

i have the same problem opencore catalina 5.0.1 install ,  

How did you solve this problem? please

Share this post


Link to post
Share on other sites

The system kernel often broken. Would you please add replacement commands to LogoutHook. command? 

sudo cp -R /Library/Apple/System/Library/PrelinkedKernels/prelinkedkernel /System/Library/PrelinkedKernels

 

Share this post


Link to post
Share on other sites

Hello everyone, was wondering if someone could answer this question. I am on the latest Open core 0.5.2 and have have noticed this issue for the last few builds. When I select OC to boot quickly before the picker menu is shown, I get the following message: "OCS: No schema for DevicePathsSupported at 0 index!"

 

Any ideas as couldn't find this anywhere?

Share this post


Link to post
Share on other sites

The only issue I have with OC is after booting Windows 10 I can no longer boot Catalina. I get " Error loading kernel cache " Mohave boots no problem and Catalina will boot with Clover just fine. I can boot mohave and catalina just fine with OC multiple times as long as I don't boot windows. Still trying to figure this out, will have to stay with clover until I do.

 

Share this post


Link to post
Share on other sites

ok, I am at a loss, I have poured over the configuration documents many times and still can't get my system to boot.I got OC .3 to boot mostly, but that was using AptioMemoryFix which is now been absorbed into OC and other functions. the page in the documents that discuss how to get it working are extremely vague and simply point out what appears to be unrelated Quirks that if you search the documentation on don't say if they need to be on or off. Attached are 2 files, 1 my freshly compiled .5.1 OC folder with a config.plist that I know will not boot, because it gives me the dreaded (ERROR allocating 0x##### pages at 0x000000000######## alloc Type 2, Couldn't allocate runtime area) or worse just fails to do anything after making a selection one a Clover config file that will boot the system correctly.  Can someone please help, or point me in the direction that will allow me to resolve the issues?

 

TLDR: My OC files will boot .3, but when I try to move onto any that don't use AptioMemoryFix I can't get the system to boot, looking for help.  Attached are the OC EFI (not working) and a working Clover config for my system.

System in Question is the Z390 DESIGNARE

HBP

clover_config.plist

EFI.zip

Edited by HBP

Share this post


Link to post
Share on other sites

Hey, so my system instantly reboots after moving fine working build with Clover to OpenCore. I don't have any Macs (VM too) so I can't fix it directly.

Screenshot_2019-10-09-20-26-06-862_com.g
This is what I get before reboot.
This is my config.plist: https://pastebin.com/0vSaVDD1 (without iMessage because I had it working under Clover).
Drivers:
ApfsDriverLoader.efi
FwRuntimeServices.efi
VBoxHfs.efi
VirtualSmc.efi

Kexts:
AppleALC.kext
Lilu.kext
RealtekRTL8111.kext
SMCProcessor.kext
SMCSuperIO.kext
VirtualSMC.kext
WhateverGreen.kext

I suppose it's not working due to EC not being faked/patched, but because I don't have access to macOS to get DSDT and patch them, I need probably to get working old Clover build (I have backup) or wait for OpenCore dev to implement directly EC faking under Catalina?

Share this post


Link to post
Share on other sites
7 minutes ago, HBP said:

ok, I am at a loss, I have poured over the configuration documents many times and still can't get my system to boot.I got OC .3 to boot mostly, but that was using AptioMemoryFix which is now been absorbed into OC and other functions. the page in the documents that discuss how to get it working are extremely vague and simply point out what appears to be unrelated Quirks that if you search the documentation on don't say if they need to be on or off. Attached are 2 files, 1 my freshly compiled .5.1 OC folder with a config.plist that I know will not boot, because it gives me the dreaded (ERROR allocating 0x##### pages at 0x000000000######## alloc Type 2, Couldn't allocate runtime area) or worse just fails to do anything after making a selection one a Clover config file that will boot the system correctly.  Can someone please help, or point me in the direction that will allow me to resolve the issues?

 

TLDR: My OC files will boot .3, but when I try to move onto any that don't use AptioMemoryFix I can't get the system to boot, looking for help.  Attached are the OC EFI (not working) and a working Clover config for my system.

 

HBP

clover_config.plist

EFI.zip

 

1. Try to enable Booter->Quirks->AvoidRuntimeDefrag.

2. Which system is this EFI for? You have three in your signature.

3. Some options seem to be missing from your config.plist. Start fresh with the SampleFull.plist corresponding to your OC 0.5.1 build, or compare with it and add missing options.

4. I see you have DSDT.aml defined in the ACPI->Add section, but the file seems to be missing. And DSDT patching isn't recommended anyway.

5. You have multiple ACPI renames in place, and most of them shouldn't be needed, I would suggest you start with no renames at all and fix them one at a time.

6. The `Fix RTC _STA` should be achieved by using SSDT patch provided in OpenCorePkg->Docs->AcpiSamples

7. Although I'm not sure about the ACPI->Block section, I would suggest you disable them until you're sure that it is absolutely required to boot

8. In OC 0.5.1 you shouldn't use AptioMemoryFix since its functionalities are mostly merged into OC and some separated in FwRuntimeServices. Just include FwRuntimeServices and enable the Booter quirks. You can find detailed information in the Configuration.pdf

 

That's all I can see in a glance for now.. :)

 

Share this post


Link to post
Share on other sites
1 minute ago, maddie said:

 

1. Try to enable Booter->Quirks->AvoidRuntimeDefrag.

2. Which system is this EFI for? You have three in your signature.

3. Some options seem to be missing from your config.plist. Start fresh with the SampleFull.plist corresponding to your OC 0.5.1 build, or compare with it and add missing options.

4. I see you have DSDT.aml defined in the ACPI->Add section, but the file seems to be missing. And DSDT patching isn't recommended anyway.

5. You have multiple ACPI renames in place, and most of them shouldn't be needed, I would suggest you start with no renames at all and fix them one at a time.

6. The `Fix RTC _STA` should be achieved by using SSDT patch provided in OpenCorePkg->Docs->AcpiSamples

7. Although I'm not sure about the ACPI->Block section, I would suggest you disable them until you're sure that it is absolutely required to boot

8. In OC 0.5.1 you shouldn't use AptioMemoryFix since its functionalities are mostly merged into OC and some separated in FwRuntimeServices. Just include FwRuntimeServices and enable the Booter quirks. You can find detailed information in the Configuration.pdf

 

That's all I can see in a glance for now.. :)

 

the system (sry I forgot the add that) is the Z390 DESGINARE.

HBP

Share this post


Link to post
Share on other sites
8 minutes ago, HBP said:

the system (sry I forgot the add that) is the Z390 DESGINARE.

HBP

 

Z370 you mean, I presume?

 

If so, your Z370 machine is quite similar to mine (ASUS Z370-F).

 

Here is my EFI folder, fill in your SMBIOS info and see it helps. You might need some minor changes to make everything work.

 

My OC could be slightly older than yours, 0.5.1 still, but right before the "MinKernel/MaxKernel" commit. So if you're gonna test it out I would suggest you replace the whole thing, and upgrade later if you want.

EFI.zip

 

 

EDIT: It doesn't have the Thunderbolt ACPI patch since my board doesn't have TB. You might have to add it yourself.

Edited by maddie

Share this post


Link to post
Share on other sites
49 minutes ago, maddie said:

 

Z370 you mean, I presume?

 

If so, your Z370 machine is quite similar to mine (ASUS Z370-F).

 

Here is my EFI folder, fill in your SMBIOS info and see it helps. You might need some minor changes to make everything work.

 

My OC could be slightly older than yours, 0.5.1 still, but right before the "MinKernel/MaxKernel" commit. So if you're gonna test it out I would suggest you replace the whole thing, and upgrade later if you want.

EFI.zip

 

 

EDIT: It doesn't have the Thunderbolt ACPI patch since my board doesn't have TB. You might have to add it yourself.

no luck, it might be I am tired, will try it again in the morning

 

hbp

Share this post


Link to post
Share on other sites

got the bright idea to try every boot option (I have 5) and what I can see is that recovery mode on 10.14.6 and 10.15 do nothing, while normal mode gives me this Error (see attached). I have gone into the EFI Shell and tried to launch boot.efi manually and it appears that it is not patching/debugging on boot. 

no luck, it might be I am tired, will try it again in the morning

 

hbp

IMG_1468.jpeg

Share this post


Link to post
Share on other sites
16 hours ago, littlegtplr said:

Hi all OpenCore testers,

 

I encountered an issue with assigning default boot option and hope if anyone could shed me some light. Assigning default boot option via Startup Disk preference panel doesn't seem to have any effect to the default boot-up option of OpenCore. I changed it to two different disks but the OpenCore default stays still the first one (an EFI). 

 

I can see that efi-boot-device in nvram.plist is able to change according to the selection on Startup Disk preference panel. However that doesn't change what OpenCore brings up as the default. 

 

These are tested with RequestBootVarRouting enabled. When disabled, the default booting option stayed on the second entry of the booting list (another EFI...), regardless of what was chosen on the Startup Disk preference panel. 

 

Other than this issue, OpenCore has been working flawlessly with my hack. Well done guys! 

 

My plist can be found below, and the specs. Thanks. 

 

CPU: i5-8500

GPU: Sapphire RX580 Pulse

RAM: Corsair - Vengeance LPX 2 x 8GB DDR4-3000

Motherboard/Laptop model: Gigabyte B360 AORUS Gaming 3 WIFI

config copy.plist

 

It seems like OpenCore default boot option isn't compatible with emulated nvram. When asked about it on the acidanthera bug tracker, one of the devs replied that you should simply go and buy a z370 board instead. It's a shame because all current gen intel motherboards have incompatible nvram.

 

I ended up just setting up ScanPolicy to make sure that my macOS disk was the first boot option.

Edited by yobro

Share this post


Link to post
Share on other sites
3 hours ago, yobro said:

 

It seems like OpenCore default boot option isn't compatible with emulated nvram. When asked about it on the acidanthera bug tracker, one of the devs replied that you should simply go and buy a z370 board instead. It's a shame because all current gen intel motherboards have incompatible nvram.

 

I ended up just setting up ScanPolicy to make sure that my macOS disk was the first boot option.

 

Thanks for the feedback. Good to know that the failure of default bootup assignment is directly linked to the emulated nvram. 

Setting up ScanPolicy sounds like a decent workaround. I've looked up the manual and figured out how to set the number in the plist. Will try this today or tomorrow. Cheers 

Edited by littlegtplr

Share this post


Link to post
Share on other sites

00:000 00:000 OCC: No compatible mode for 1920x1080@0 (max: 0) resolution
00:112 00:112 OC: Changed resolution to 1920x1080@0 (max: 0) from 1920x1080@30 - Not Found

Resolution is not working,how to fix it?

 

Share this post


Link to post
Share on other sites
4 minutes ago, linvers said:

00:000 00:000 OCC: No compatible mode for 1920x1080@0 (max: 0) resolution
00:112 00:112 OC: Changed resolution to 1920x1080@0 (max: 0) from 1920x1080@30 - Not Found

Resolution is not working,how to fix it?

 

I'm not sure but '1920x1080@32' works for me

Share this post


Link to post
Share on other sites

open core has the blessed drive just like a real mac. open core far superior to clover. go into system pref/startup drive choose and blessed just like mac.

Share this post


Link to post
Share on other sites
7 hours ago, HBP said:

ok, I am at a loss, I have poured over the configuration documents many times and still can't get my system to boot.I got OC .3 to boot mostly, but that was using AptioMemoryFix which is now been absorbed into OC and other functions. the page in the documents that discuss how to get it working are extremely vague and simply point out what appears to be unrelated Quirks that if you search the documentation on don't say if they need to be on or off. Attached are 2 files, 1 my freshly compiled .5.1 OC folder with a config.plist that I know will not boot, because it gives me the dreaded (ERROR allocating 0x##### pages at 0x000000000######## alloc Type 2, Couldn't allocate runtime area) or worse just fails to do anything after making a selection one a Clover config file that will boot the system correctly.  Can someone please help, or point me in the direction that will allow me to resolve the issues?

 

TLDR: My OC files will boot .3, but when I try to move onto any that don't use AptioMemoryFix I can't get the system to boot, looking for help.  Attached are the OC EFI (not working) and a working Clover config for my system.

System in Question is the Z370 DESIGNARE

HBP

clover_config.plist

EFI.zip

You are missing a ton of things that have to be in the config. Try this EFI

EFI.zip

Share this post


Link to post
Share on other sites

Hi every one,

I'm using Clover and try to change to OpenCore(0.5.1) but I'm stucking with follow error.

276b966165f048f5bf145519a5763db6.jpg

 

This is some info about my system:

- Running Mojave with Clover

- motherboard Z370

- Chip Coffee Lake i8400

- Using usb bluetooth dongle (BCM20702A0)

- TP-Link Archer T9E for wifi

- Card AMD RX 570

 

I also attach EFI folder here.

Thank you very much for any advise !

EFI.zip

Edited by hoangtuan211

Share this post


Link to post
Share on other sites
19 minutes ago, hoangtuan211 said:

Hi every one,

I'm using Clover and try to change to OpenCore(0.5.1) but I'm stucking with follow error.

276b966165f048f5bf145519a5763db6.jpg

 

This is some info about my system:

- Running Mojave with Clover

- motherboard Z370

- Chip Coffee Lake i8400

- Using usb bluetooth dongle (BCM20702A0)

- TP-Link Archer T9E for wifi

- Card AMD RX 570

 

I also attach EFI folder here.

Thank you very much for any advise !

EFI.zip

Try this EFI, people really need to stop using ACPI > Patches to do ACPI renames, if you need to rename a device use a SSDT. Think of comparing Clover and OpenCore to a Automatic and Manual transmission in a vehicle. Clover is the Automatic and OpenCore is the manual. You can not do things with a manual that you can do in an automatic.

EFI.zip

Edited by Pavo

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Similar Content

    • By clockT
      sono un pò arrugginito ..e volevo chiedere un aiuto su come installare opencore anzichè clover. ho provato ma dopo il post installazione riesco solo a far partire catalina tramite pendrive. quale congifurazione sbaglio?
      EFI.zip

    • By MaLd0n
      ---TUTORIAL---

      https://olarila.com/forum/viewtopic.php?f=50&t=8685
       
      --Original Post--
       
      https://olarila.com/forum/viewtopic.php?f=97&t=11237
       
      --Bios/UEFI Settings--
       
      *Update bios/uefi to F7+*
      1- Go to M.I.T./Advanced Frequency Settings tab
       
      Extreme Memory Profile (X.M.P.) - Profile 1
       
      2- Go to BIOS tab
       
      CSM Support - Disabled
       
      3- Go to Peripherals/Thunderbolt(TM) Configuration tab
       
      Security Level - No Security
      Thunderbolt USB Support - Enabled
      GPIO3 Force Pwr - Enabled
       
      4- Go to Chipset tab
       
      Internal Graphics - Enable
       
      ---CLOVER FOLDER---
      https://olarila.com/files/Clover.Folder/EFI CLOVER Z390 DESIGNARE.zip
      *Use this folder with FULL DSDT PATCHED
       
      ---OPENCORE FOLDER---
      https://olarila.com/forum/download/file.php?id=24376
      *Use this folder with FULL DSDT PATCHED
       
       
      ---Extract one Full dump for DSDT edits, post files---
       
      RunMe.app
       
       
       
      ---HARDWARE---
       
      --MOBO

      GIGABYTE Z390 DESIGNARE
      -Link
      https://www.amazon.com/Z390-DESIGNARE-Gigabyte-Thunderbolt-Motherboard/dp/B07K8RJZRG/ref=sr_1_1?keywords=Z390+DESIGNARE&qid=1565492390&s=electronics&sr=1-1

      --PROCESSOR

      Intel Core i9-9900K
      -Link
      https://www.amazon.com/Intel-i9-9900K-Desktop-Processor-Unlocked/dp/B005404P9I/ref=sr_1_1_sspa?keywords=Intel+Core+i9-9900K&qid=1553358099&s=gateway&sr=8-1-spons&psc=1

      --COOLER

      CORSAIR H100i RGB PLATINUM AIO Liquid CPU Cooler
      -Link
      https://www.amazon.com/CORSAIR-H100i-PLATINUM-Liquid-Cooler/dp/B07JWB5BSN/ref=sr_1_4?keywords=WATER+COOLER+CPU&qid=1565492509&s=gateway&sr=8-4

      --MEMORY

      Corsair CMW32GX4M2C3200C16 Vengeance RGB PRO 32GB (2x16GB) DDR4 3200 (PC4-25600)
      -Link
      https://www.amazon.com/Corsair-CMW32GX4M2C3200C16-Vengeance-PC4-25600-Desktop/dp/B07GTG2T7L/ref=sr_1_15?keywords=memory+ddr4+32&qid=1553358238&s=gateway&sr=8-15

      --GPU

      MSI RX Vega 64 AIR Boost 8G OC
      -Link
      https://www.amazon.com/MSI-RX-64-AIR-8G/dp/B07DH7S1X1/ref=sr_1_2?keywords=vega+64+gigabyte&qid=1565492819&s=electronics&sr=1-2

      --SSD

      Samsung 970 EVO 1TB SSD (MZ-V7E1T0BW) NVMe M.2 V-NAND
      -Link
      https://www.amazon.com/Samsung-970-EVO-1TB-MZ-V7E1T0BW/dp/B07BN217QG/ref=sr_1_1?keywords=s+samsung+970+evo+1tb&qid=1565493002&s=electronics&sr=1-1

      --POWER SUPPLY

      EVGA Supernova 1000 P2 80+ Platinum, 1000W ECO Mode Fully Modular 
      -Link
      https://www.amazon.com/EVGA-Supernova-Platinum-Crossfire-220-P2-1000-XR/dp/B00EKJQM5E/ref=sr_1_3?keywords=power+supply+1000w&qid=1565493196&s=gateway&sr=8-3

      --WIRELESS

      TP-Link Archer T9E
      -Link
      https://www.amazon.com/TP-Link-Archer-T9E-Beamforming-Technology/dp/B00TQEX7AQ/ref=sr_1_1?keywords=TP-Link+Archer+T9E&qid=1553358397&s=gateway&sr=8-1

      --CASE

      Thermaltake Core P5 Tempered Glass Black Edition ATX Open Frame Panoramic Viewing
      -Link
      https://www.amazon.com/Thermaltake-Tempered-Panoramic-Certified-CA-1E7-00M1WN-03/dp/B01N4IGVSC/ref=sr_1_2?keywords=Thermaltake+Core+P5&qid=1565493567&s=gateway&sr=8-2

      --DSDT Patches--
      -FIX ACPI ERRORS -FIX OEM SSDTs to AVOID ERRORS AND WARNINGS -REMOVE UNUSED SCOPES / DEVICES -HIGH PRECISION EVENT TIMER -SATA -DMAC -REMOVE PROBLEMATIC AND UNUSED DEVICES -FIX K.P in REBOOT -SLPB -DARWIN / WINDOWS 2015 -XHCI -PLUGIN TYPE -HDAS to HDEF -HDEF -REAL TIME CLOCK -ARTC -IRQs -SBUS -BUS1 -MCHC -ALS0 -SHUTDOWN -LAN -FWHD -USBX -PMCR -PPMC -XSPI -CNVW -GMM -IMEI -EC -PNLF -ARPT -GFX0 -NVME -DTGP -ACQUIRE MUT0 0XFFFF -MUTEX MUT0 0x00 -EXTERNAL REFERENCES -UNKNOWNOBJ -HDMI / HDAU -FULL RENAMED DEVICES ---SCREENSHOTs---




















      -Credits and thanks to the old and new people in the community who developed patches, kexts and bootloaders!
      Thanks to KGP for SSDT Thunderbolt
      Slice, Kabyl, usr-sse2, jadran, Blackosx, dmazar, STLVNUB, pcj, apianti, JrCs, pene, FrodoKenny, skoczy, ycr.ru, Oscar09, xsmile, SoThOr, RehabMan, Download-Fritz, Zenit432, cecekpawon, Intel, Apple, Oracle, Chameleon Team, crazybirdy, Mieze, Mirone, Oldnapalm, netkas, Elconiglio, artut-pt, ErmaC, Pavo, Toleda, Master Chief and family, bcc9, The King, PMheart, Sherlocks, Micky1979, vit9696, vandroiy2013, Voodoo Team, Pike R. Alpha, lvs1974, Austere.J, CVad, Sampath007, onemanosx, erroruser, Jenny David, Olarila Facebook Community, Hackintosh Facebook Community and many others!
      We're all here to have fun and learn from each other!
    • By rusty-bits
      Command line tool that will build a working EFI folder based on the settings in the config.plist file.
      https://github.com/rusty-bits/OC-tool
       
       
      you can also copy your config.plist to the RELEASE folder and double-click OC-tool  
      this is the same as running
      ./OC-tool -uo build release from the command line  
       
      see the wiki for more info  
       
      https://github.com/rusty-bits/OC-tool/wiki
       
      added functionality to the -T option  (update ver 1.6pt)  

      TUI (Text based User Interface) now has limited functionality  
      kexts, drivers, tools and quirks can be toggled on or off, then by pressing g an EFI folder will be created based on what you set  
       
       
      working:  
      - BOOT/BOOTx64.efi built automatically  
      - OC/OpenCore.efi build automatically
      - OC/ACPI folder built automatically from settings in ACPI/Add section of config.plist  
      - - the tool can compile .dsl to .aml on the fly if iasl is present, but I recommend compiling them to .aml yourself for the tool to move over  
      - OC/Drivers folder built automatically from settings in UEFI/Drivers section of config.plist  
      - OC/kexts folder built automatically from settings in Kernel/Add section of config.plist  
      - OC/Tools/Shell.efi built automatically from setings in Misc/Tools section of config.plist  
      - OC/vault.plist and OC/vault.sig are built automatically from the Misc/Security/RequireVault setting in config.plist  
      - can specify debug or release version of resources to be built  
      - parses plist files internally, no longer needs to call /usr/libexec/PlistBuddy which may not exist on Catalina  
      - kexts, drivers, tools and quirks can be enabled or disabled before building the EFI by using the -T option  
       
×