Jump to content

2,463 posts in this topic

Recommended Posts

Posted (edited)

 

 

 

10 hours ago, arsradu said:
Drivers, drivers, drivers.
 
Try to use AptioMemoryFix.efi or OsXAptioFix3Drv.efi from Clover.
 
As a matter of fact, I can't boot with default OC drivers (AppleSupportPkg). Getting stuck just like you do (including with the new FWRuntimeServices.efi). But I can boot no problem with my old Clover drivers.
 
If it helps, here's what I'm currently using with OpenCore.
Drivers.zip

 

 


It's not about drivers, his problem is solved. I have sent him new configuration. Check post above


Sent from my iPhone using Tapatalk

 

 

Edited by Andres ZeroCross

Share this post


Link to post
Share on other sites
Advertisement

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

Share this post


Link to post
Share on other sites
6 hours ago, maxb2000 said:

On my configuration the VooDooI2C kexts aren't loading or working with Open Core, the rest of the kexts are fine except for these two: 

 

VooDooI2C and VooDooI2CHID

 

Anybody knows how can I debug this? 

Order of kext matters.

Screenshot 2019-08-10 at 1.40.49 PM.png

Share this post


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

It's not about drivers, his problem is solved. I have sent him new configuration. Check post above

 

 

 

Oh, yeah. I've missed that. :) 

Share this post


Link to post
Share on other sites
1 hour ago, onemanOSX said:

Order of kext matters.

Screenshot 2019-08-10 at 1.40.49 PM.png

 

I did know that but I forgot to put the plugins ! Thanks !

Share this post


Link to post
Share on other sites
Posted (edited)
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 :cry:

Edited by Matgen84

Share this post


Link to post
Share on other sites
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 :cry:


It mean you have changed configuration or BIOS setting

Share this post


Link to post
Share on other sites
Posted (edited)
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 by Matgen84

Share this post


Link to post
Share on other sites
Posted (edited)

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.

 

 

111.thumb.png.e2cd017e6a26f6268167551d2c59bf09.png

 

 

 

Edited by iTTT

Share this post


Link to post
Share on other sites
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

 

 

 

 

Share this post


Link to post
Share on other sites
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

 

Share this post


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

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

 

PlatformInfo -> SMBIOS -> ProcessorType

Share this post


Link to post
Share on other sites
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?

Share this post


Link to post
Share on other sites

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

Share this post


Link to post
Share on other sites
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. 

Share this post


Link to post
Share on other sites
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

Share this post


Link to post
Share on other sites
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

Share this post


Link to post
Share on other sites
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

 

image.thumb.png.7f504bd1a9f092f5853d88d930f61087.png


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

image.png.a7fcabd9f6b7201e01c94eb398e5d73f.png

Share this post


Link to post
Share on other sites
Posted (edited)
46 minutes ago, Pavo 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.

 

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 by NorthAmTrans
new info

Share this post


Link to post
Share on other sites
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. 

 

 

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

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • 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://www.mediafire.com/file/wp52azi4dtr0uby/EFI_CLOVER_Z390_DESIGNARE.zip/file
      *Use this folder with FULL DSDT PATCHED
       
      ---OPENCORE FOLDER---
      https://olarila.com/forum/viewtopic.php?f=28&t=10578
      *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 notiflux
      Unfortunately, this project has come to a halt, at least for now. I don't have enough time to work on the project and it's lacking behind, so please don't use it for configuring OpenCore, it will produce broken configuration files.
      I will leave the source code on GitHub, so in case someone wants to take over the project, they can.
       
      original post:
      OpenCore Configurator Source
    • 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 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  
       
×