Jump to content

2,524 posts in this topic

Recommended Posts

19 minutes ago, Pavo said:

Use Device Properties

Hi Pavo!

 

Many thanks for the tip. This is the first time doing this. Could you, please, share a bit more details on how to achieve that?

 

I took a look in the IOreg, and I'm guessing i need to add a new property for IODisplayEDID, right...?

If that's correct, the only thing I got stuck at, is the actual Device. It needs to be the PCI address, right? So...how do I get the PCI address of my display...?

1579459341_Screenshot2019-11-08at19_10_15.thumb.png.a711db766297ff4491836b520ef4b163.png

 

1834587669_Screenshot2019-11-08at19_10_26.thumb.png.5ca5630b11a54a13f30ef11184354ed0.png

 

Edited by arsradu

Share this post


Link to post
Share on other sites
Advertisement

Have anyone installed windows 10 with OpenCore using bootcamp? 

is here any guide and toturials about using bootcamp

Share this post


Link to post
Share on other sites
35 minutes ago, anmool said:

Have anyone installed windows 10 with OpenCore using bootcamp? 

is here any guide and toturials about using bootcamp

 

Why using BootCamp on a PC in the first place? You don't need to emulate anything.

 

BootCamp creates the environment necessary for real Macs to run Windows. A PC will run Windows natively. So no need for BootCamp.

Edited by arsradu

Share this post


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

 

Why using BootCamp on a PC in the first place? You don't need to emulate anything.

 

BootCamp creates the environment necessary for real Macs to run Windows. A PC will run Windows natively. So no need for BootCamp.

@anmool

If You had only 1 single drive formatted for your OSX ( APFS or HFS+ ), you would need to use bootcamp to allow the installation of Windows alongside OSX. Unless you prefer the use of a virtual Machine.

I choose to have a dedicated drive with Windows that you "bless" thru OpenCore, via ENTRIES. Safer & simpler. You'd only need to find the path of your dedicated windows drive & voila:
Everything works.

 

Screen Shot 2019-11-08 at 10.52.32 AM.png

Screen ShoT.png

Edited by Ellybz

Share this post


Link to post
Share on other sites

Hi,

I have been trying to get my first hackintosh working for over 30 hours now and I am loosing my sanity.
I spent most of my time with Clover but always had errors. I finally tried OpenCore and quickly got into the install but then got the 5700 visual glitches during install.
I managed to "guess" where the buttons are on screen and managed to install Catalina !

I must have missed some Kext as I got no ethernet. I went into the libraries and I can't see the Intel Ethernet. 
I read a guide to use Hackintool to install Kext, but there don't seem to get installed.
Apparently this is due needed to enable SIP and I need to "CsrActiveConfig to 0x0 "

-I am currently stuck on this part as all the solutions I saw require Clover to enable SIP.

-I am also confused on how to install an Opencore bootloader so that I don't need the USB key anymore.


Thanks a ton for any help !

 

Share this post


Link to post
Share on other sites
On 10/28/2019 at 6:53 AM, n.d.k said:

try copy this config.plist setting for ivybridge board.

OK, this worked!  I didn't use the whole file but I copied over a number of the flags.  I also noticed that I had "vanderpool technology" (the good kind of virtualization) turned off in UEFI.  However, I think the flags relating to "slide", i.e. osxaptiofix2 or whatever, are what I needed.  

 

This got me booted but sound isn't working.  Also, I continue to have an issue with the OpenCore menu taking a very very long time (multiple minutes) to appear.  I tried setting a more restrictive  ScanPolicy (SATA, USB, APFS, HFS, 0x2010303 or something like that) and while it accepts the flags as valid, this did not reduce how long it takes to get to the menu.

 

Help is, as always, appreciated.

 

EDIT: Between turning off Windows 8 Secure Boot and having OC reset NVRAM, either that or disabling nearly all the various drives I had attached, I got it to go very quickly to the boot menu.  However now it's not showing the installer... trying 0.53 and the new 10.15.1 install APP...

Edited by birdbird
progress!

Share this post


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

You'd only need to find the path of your dedicated windows drive

Mind sharing how you figured out the path? Thanks.

Share this post


Link to post
Share on other sites
2 hours ago, onemanOSX said:

Mind sharing how you figured out the path? Thanks.

There are several ways to do this. You can use
1- the shell Method proposed by @DaGr8Gatzby. It will save the path in a "maps.text" inside your ESP Partition. 

.

2 - Thru Clover Bootloader, selecting the drive , hitting spacebar for the path infos ( Some dashes might be reversed & need to be corrected; see my ex. below ), or booting thru Clover,  using CloverConfig -> Bootlog

3 - Via OC Bootlog, ( you'll need the debug version not the release ); however only the second part of the path appears in the log. in my case OC log only showed this part:

HD(1,GPT,4C15DB92-F532-11E9-AF6E-E172391D34E9,0x800,0xFA000)/\EFI\Microsoft\Boot\bootmgfw.efi

This is the full path for my SSD Drive allocated to Windows:

PciRoot(0x0)/Pci(0x17,0x0)/Sata(0x1,0xFFFF,0x0)/HD(1,GPT,4C15DB92-F532-11E9-AF6E-E172391D34E9,0x800,0xFA000)/\EFI\Microsoft\Boot\bootmgfw.efi

 

PS: OC Scan needs to allow NTFS. Unless you're using"0" .

 

 

Edited by Ellybz

Share this post


Link to post
Share on other sites
13 hours ago, Andrey1970 said:

 

Few questions here:

 

1. Is this for dedicated GPUs, as well? So...basically, all I have to add is key=APPL00,override-no-connect with value=[my custom EDID] to PciRoot(0x0)/Pci(0x1,0x0)/Pci(0x0,0x0) which is my dedicated GPU?

2. Does OC come with drivers built-in? Or...how is someone supposed to get those?

 

Thing is, after upgrading to OC 0.5.3 I can't boot anymore. Get stuck at the Apple logo. It used to work perfectly fine before (I think I had version 0.5.0 or something). I'm assuming it could be a driver issue... but if you have a better idea, please, let me know.

 

3. How can I test if the custom EDID has actually been injected?

4. Assuming this is not a driver issue and it's my mistake, could you, please, let me know if these errors are intended?

 

Ran 280 tests in 1.374s

OK
Error in sitecustomize; set PYTHONVERBOSE for traceback:
ValueError: unknown locale: UTF-8
Build environment: Darwin-19.0.0-x86_64-i386-64bit
Build start time: 09:58:10, Nov.09 2019

WORKSPACE        = /Users/jimmy/Desktop/OpenCorePkg-master/UDK
EDK_TOOLS_PATH   = /Users/jimmy/Desktop/OpenCorePkg-master/UDK/BaseTools
CONF_PATH        = /Users/jimmy/Desktop/OpenCorePkg-master/UDK/Conf
PYTHON_COMMAND   = /usr/bin/python3

Error in sitecustomize; set PYTHONVERBOSE for traceback:
ValueError: unknown locale: UTF-8
Error in sitecustomize; set PYTHONVERBOSE for traceback:
ValueError: unknown locale: UTF-8

Architecture(s)  = X64
Build target     = DEBUG

Processing meta-data Toolchain        = XCODE5
.
Active Platform          = /Users/jimmy/Desktop/OpenCorePkg-master/UDK/OpenCorePkg/OpenCorePkg.dsc
Error in sitecustomize; set PYTHONVERBOSE for traceback:
ValueError: unknown locale: UTF-8
Error in sitecustomize; set PYTHONVERBOSE for traceback:
ValueError: unknown locale: UTF-8
Error in sitecustomize; set PYTHONVERBOSE for traceback:
ValueError: unknown locale: UTF-8
Error in sitecustomize; set PYTHONVERBOSE for traceback:
ValueError: unknown locale: UTF-8
. done!

I kept getting these when building OC.

Edited by arsradu

Share this post


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

@anmool

If You had only 1 single drive formatted for your OSX ( APFS or HFS+ ), you would need to use bootcamp to allow the installation of Windows alongside OSX. Unless you prefer the use of a virtual Machine.

I choose to have a dedicated drive with Windows that you "bless" thru OpenCore, via ENTRIES. Safer & simpler. You'd only need to find the path of your dedicated windows drive & voila:
Everything works.

 

Screen Shot 2019-11-08 at 10.52.32 AM.png

Screen ShoT.png

 

looks great.

 

may i know your scanpolicy?  is it 2689795 ?

also seems you disable Entries for OSX right? and deleted REC for both osx ?

 

thanks

 

Edited by iTTT

Share this post


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

 

Few questions here:

 

1. Is this for dedicated GPUs, as well? So...basically, all I have to add is key=APPL00,override-no-connect with value=[my custom EDID] to PciRoot(0x0)/Pci(0x1,0x0)/Pci(0x0,0x0) which is my dedicated GPU?

2. Does OC come with drivers built-in? Or...how is someone supposed to get those?

 

Thing is, after upgrading to OC 0.5.3 I can't boot anymore. Get stuck at the Apple logo. It used to work perfectly fine before (I think I had version 0.5.0 or something). I'm assuming it could be a driver issue... but if you have a better idea, please, let me know.

 

3. How can I test if the custom EDID has actually been injected?

4. Assuming this is not a driver issue and it's my mistake, could you, please, let me know if these errors are intended?

 


Ran 280 tests in 1.374s

OK
Error in sitecustomize; set PYTHONVERBOSE for traceback:
ValueError: unknown locale: UTF-8
Build environment: Darwin-19.0.0-x86_64-i386-64bit
Build start time: 09:58:10, Nov.09 2019

WORKSPACE        = /Users/jimmy/Desktop/OpenCorePkg-master/UDK
EDK_TOOLS_PATH   = /Users/jimmy/Desktop/OpenCorePkg-master/UDK/BaseTools
CONF_PATH        = /Users/jimmy/Desktop/OpenCorePkg-master/UDK/Conf
PYTHON_COMMAND   = /usr/bin/python3

Error in sitecustomize; set PYTHONVERBOSE for traceback:
ValueError: unknown locale: UTF-8
Error in sitecustomize; set PYTHONVERBOSE for traceback:
ValueError: unknown locale: UTF-8

Architecture(s)  = X64
Build target     = DEBUG

Processing meta-data Toolchain        = XCODE5
.
Active Platform          = /Users/jimmy/Desktop/OpenCorePkg-master/UDK/OpenCorePkg/OpenCorePkg.dsc
Error in sitecustomize; set PYTHONVERBOSE for traceback:
ValueError: unknown locale: UTF-8
Error in sitecustomize; set PYTHONVERBOSE for traceback:
ValueError: unknown locale: UTF-8
Error in sitecustomize; set PYTHONVERBOSE for traceback:
ValueError: unknown locale: UTF-8
Error in sitecustomize; set PYTHONVERBOSE for traceback:
ValueError: unknown locale: UTF-8
. done!

I kept getting these when building OC.

 Those error are caused by using Python 3, you can just ignore them, it will go away when OC update their edk2.

 

If you get stuck at Apple Logo right after updating your OC version, a hard reboot would get it going again. 

Share this post


Link to post
Share on other sites
On 10/30/2019 at 8:39 PM, Andrey1970 said:

@Elende

Don't use UsbKbDxe.efi and KeySupport=yes at the same time.

Delete UsbKbDxe.efi or set all NO in Input section. (Decide as works for you better.)


Replace VBoxHfs.efi on HfsPlus.efi

VBoxHfs.efi it is license it is pure, but it is very slow therefore problems with boot RecoveryHD (dmg).

 

good day Andrey1970,

 

i use apple wired keyboard and must need to UsbKbDxe.efi to make AppleHotKeys (like CMD + V ....) available during PC is turned on.

 

but i have one issue , if i select SHELL, then keyboard will auto input the same keys in command line or its hard to input the correct key in command line.

 

any solution to prevent keyboard to auto input in shell command line?

 

thanks.

 

 

Share this post


Link to post
Share on other sites

@iTTT, I am afraid we did not understand you. Could you be more descriptive on what happens, perhaps make a video or something…

 

Is it the following?

1. You hold CMD+V before starting OpenCore

2. You release it

3. You launch OpenCore Shell

4. A number of v keys appears in shell input, i.e. you see:

Shell> vvvvvvvvvvvv

 

If so, I cannot imagine why would you do that, and it feels kind of expected to me?

Share this post


Link to post
Share on other sites
5 hours ago, arsradu said:

4. Assuming this is not a driver issue and it's my mistake, could you, please, let me know if these errors are intended?


Error in sitecustomize; set PYTHONVERBOSE for traceback:
ValueError: unknown locale: UTF-8
. done!

I kept getting these when building OC.

 

https://coderwall.com/p/-k_93g/mac-os-x-valueerror-unknown-locale-utf-8-in-python

(Would be different with ZSH)

Edited by Badruzeus

Share this post


Link to post
Share on other sites

@vit9696, Thank you for your efforts with the Configuration PDF and the Docs.

 

If I could make a suggestion regarding sample.plist:

 

Have it defaulting to logging to screen and to file. Nothing hidden in the sample version booting up.  Cutting back on the logging after you get things up and running is easier for a newbie than searching through all the nuances to get things turned on at the start.

 

It would also help if you could just install the EFI folder to the hidden EFI partition on a USB Flash and you try to boot that.  If there is nothing for OpenCore to then boot, fine, you get to see the OpenCore log and fix away.

 

I am really impressed with the development protocol being used with OpenCore.  You folks are more top down than bottom up.  Concurrently generated documentation is really helpful.

 

Thank you again from a newbie.

Share this post


Link to post
Share on other sites

Ooook... So, I couldn't get it to boot with OC, and however I try to inject another EDID, doesn't seem to work. Also using the plist from edid-gen.sh from WhateverGreen, under Catalina, doesn't seem to work either since /System/Library/Displays/Contents/Resources/Overrides/DisplayVendorID-xxxx/ seems to be read-only with no option to authenticate.

 

So, I don't know if anyone tried to inject a different EDID recently, but using AAPL00,override-no-connect doesn't seem to work anymore. Ooor...maybe I'm doing something wrong.

 

In short, what I'm trying to achieve here is to force the OS into 8-bit color mode (since the monitor doesn't support full 10-bit; the specs say "10 bit (8-bit + FRC)") in an attempt to fix the infamous screen flashing on boot time with AMD cards. Looks like the issue happens when switching from ARGB8888 (from bios) to ARGB210101010 from the OS. Not sure why it doesn't happen on Windows, or Linux, or any other OS outside of MacOS, but that's beside the point. And even with MacOS, it doesn't always happen. But it does happen 99% of the time.

 

And since MacOS doesn't have an option to set ARGB8888 from the OS itself...I'm trying to do it from the EDID. Problem is...I can't seem to get the EDID to inject. Either with Clover or OC. And right now, with OC I can't even boot anymore. But I guess I can revert to an older version just to test this part.

 

Anyway, I just installed High Sierra on a spare HDD, for testing. Just to see if there are any differences. But if you have any clues here, please, let me know. This is an oooold issue. :))

Edited by arsradu

Share this post


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

Also using the plist from edid-gen.sh from WhateverGreen, under Catalina, doesn't seem to work either since /System/Library/Displays/Contents/Resources/Overrides/DisplayVendorID-xxxx/ seems to be read-only with no option to authenticate.

 

Uhmmmb... guessing, OC does nothing with this APFS read-only system, but Catalina.

Though, we've discussed about this one many times:

sudo mount -uw / && killall Finder

 

Share this post


Link to post
Share on other sites
2 minutes ago, Badruzeus said:

 

Uhmmmb... guessing, OC does nothing with this APFS read-only system, but Catalina.

Though, we've discussed about this one many times:


sudo mount -uw / && killall Finder

 

Yeah, it's not OC's fault. But because of that, I also couldn't inject edid into Displays/Overrides...

 

Right now I'm on HS. :D Where I can add that DisplayProductID-xxxx.plist after authentication.

 

Will try the command above when I'm coming back to Catalina. I don't expect it to make any difference. But we'll see. :) At least I don't need to boot into an HDD to test this anymore. So thank you! :) 

Share this post


Link to post
Share on other sites
52 minutes ago, BiggestCookie said:

@vit9696, Thank you for your efforts with the Configuration PDF and the Docs.

 

If I could make a suggestion regarding sample.plist:

 

Have it defaulting to logging to screen and to file. Nothing hidden in the sample version booting up.  Cutting back on the logging after you get things up and running is easier for a newbie than searching through all the nuances to get things turned on at the start.

 

It would also help if you could just install the EFI folder to the hidden EFI partition on a USB Flash and you try to boot that.  If there is nothing for OpenCore to then boot, fine, you get to see the OpenCore log and fix away.

 

I am really impressed with the development protocol being used with OpenCore.  You folks are more top down than bottom up.  Concurrently generated documentation is really helpful.

 

Thank you again from a newbie.

Unfortunately logging to file is slow (way over 5 minutes) on many firmwares when logging to USB flash, so we prefer to keep it off by default.

Share this post


Link to post
Share on other sites
57 minutes ago, arsradu said:

In short, what I'm trying to achieve here is to force the OS into 8-bit color mode (since the monitor doesn't support full 10-bit; the specs say "10 bit (8-bit + FRC)") in an attempt to fix the infamous screen flashing on boot time with AMD cards.

 

-rad24

https://github.com/acidanthera/WhateverGreen/blob/master/Manual/FAQ.Radeon.en.md

Share this post


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

 

Thank you! :)

 

While that did (finally!!) make the OS use 24-bit colors (8-bit per channel), the flashing was still there... :( Either I'm doing something wrong, or there's something else I'm missing.

 

1434804863_Screenshot2019-11-09at16_45_14.thumb.png.53931f7221bff4ff02f4f0176f559b6d.png

Edited by arsradu

Share this post


Link to post
Share on other sites
34 minutes ago, arsradu said:

 

Thank you! :)

 

While that did (finally!!) make the OS use 24-bit colors (8-bit per channel), the flashing was still there... :( Either I'm doing something wrong, or there's something else I'm missing.

 

1434804863_Screenshot2019-11-09at16_45_14.thumb.png.53931f7221bff4ff02f4f0176f559b6d.png

 

How do you  to make RX580 in your signature become Radeon Pro 580, flashing? Please tell me. :)

Share this post


Link to post
Share on other sites
4 hours ago, iTTT said:

 

good day Andrey1970,

 

i use apple wired keyboard and must need to UsbKbDxe.efi to make AppleHotKeys (like CMD + V ....) available during PC is turned on.

 

but i have one issue , if i select SHELL, then keyboard will auto input the same keys in command line or its hard to input the correct key in command line.

 

any solution to prevent keyboard to auto input in shell command line?

 

thanks.

 

 

 

I too use apple wired keyboard. Without UsbKbDxe.efi, with Input section:

1253274725_2019-11-0918_19_31.png.262da33de899346b9f1b4634f18b356d.png

And with PollAppleHotKeys Yes

 

Check the last version OpenCore from master, there were many improvings for keys.

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