Jump to content
dgsga

OpenCore Discussion

3,032 posts in this topic

Recommended Posts

Advertisement
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
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
8 minutes ago, Matgen84 said:

 

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

 

While I think this is mostly cosmetic, you can do this with Device Properties, by adding to your GPU (mine is located at PciRoot(0x0)/Pci(0x1,0x0)/Pci(0x0,0x0) ) the following combination of key + value:

key: model
value: 52616465 6F6E2050 726F2035 3830
type: data

 

Edited by arsradu

Share this post


Link to post
Share on other sites

@Andrey1970 just for reference, this is the issue I'm trying to fix: 

 

So...since switching to 24-bit didn't seem to do anything to fix this, I'm guessing there's probably something else causing it...or there's something else I'm missing.

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 bufferoverflow
      I've a working Hackintosh but I'm trying to migrate to Opencore. I'm following Vanilla Guide to configure Opencore. I'm able to boot but it fails after entering password for FileVault. Here is the error message and list of file in my Opencore EFI folder. Link to my EFI folder. Help to fix it is appreciated.

       
    • By ChrisWayg
      In Clover there is ForceKextsToLoad. What is the equivalent method in OpenCore?
      I want to force /System/Library/Extensions/IO80211Family.kext to load from S/L/E as it is required by AirPortAtheros40.kext which I am loading via OpenCore, without copying IO80211Family.kext to EFI/OC/Kexts/

      Relevant Specs: Opencore 0.5.4, macOS Mojave 10.14.6, Wifi: TP-Link WDN4800 (AR9380)
    • By n.d.k
      After several weeks of testing OC bootloader,  disecting its source code and also Clover's source code as well, I finally switch from Clover to OC as my main bootloader. Wait! don't get the wrong idea that OpenCore is better than Clover. They both work equally well, producing a bootable macOS as an end result with simliar boot time. OC design direction is different with Clover, I believe it's not intended as a Clover replacement, but more narrowing down to macOS specifically. However, macOS is not the only OS that i am using, so, i decided to add some minimal necessary source code modification to the OC to get some of the features I need. I like to share my customized OC forked https://github.com/n-d-k/OpenCorePkg , you have to compile it yourself if you want, i will not provide pre build binary.    
       
      Additional features/changes:
      ============
       
      [ Multi-Boot ]
        - ACPI patches are optional for non macOS with setting ACPI->Quirks->EnableForAll to yes (default is no).
        - Booter Quirtks, SMBIOS and Device Properties patches will only applied to macOS.
          
      [ Hotkeys ]
        - Full functional Hotkeys [1-9] corresponding to Boot Entry's Index number and dedicated W (Windows) / X (macOS) keys can be used without seeing Boot Picker.
                
      [ Boot Picker ]
        - Bios Date/time, auto boot to the same OS or manual set to always boot one OS mode, and OC version are displayed in boot picker.
        - Auto boot to previous booted OS (if Misc->Security->AllowSetDefault is NO/false).
        - macOS Recovery/Tools Entries are hidden by default, use Spacebar in Boot Menu as a toggle on/off to show/hide hidden entries.
                
      [ Custom Entries ]
         - Custom entries are now listed first in picker menu and by the orders they are appeared in Misc->Boot->Entries, before all other entries.
         - Individual custom entry can be set hidden using Misc->Entries->Item 0->Hidden (Boolean).
         - Ability to change entry name found by auto scanner by adding custom entry with the exact same device path,
           this will give users the option to complete change how all boot entries listed in Boot Picker.
          
      [ Others ]
         - No verbose apfs.efi driver loading (if using apfs.efi instead of ApfsDriverLoader.efi).
         - Fixed the unmatched 1st and 2nd stages boot Apple logo (* To ensure a match, set Misc->Boot->Resolution to match with one in macOS preferences,
           and to better boot menu text visibility for 4k+ display, set Misc->Boot->ConsoleMode to Max).
          - ndk-macbuild.tool script are set to compile with latest edk2 (One can easily set to stable edk2 if prefer).
          - NvmExpressDxe driver build script are also available for system without native nvme support. (Compatible with OC and Clover).
       
      Usage:
       - To build OpenCore, run "./ndk-macbuild.tool" at Terminal (require Xcode and Xcode Command Line Tool installed, and open xcode to accept license agreement before compiling).
       - To build NvmExpressDxe driver, run "./buildnvme.sh".
       
      * The fix is by setting the screen resolution before starting the apple boot.efi image back to the setting of the Misc->Boot->Resolution, where the setting of Misc->Boot->ConsoleMode doesn't have the same resolution as screen resolution setting.
       
       
       
       
       
       

    • By valueimagery
      Hello,
      I have almost succesfully converted from Clover to OpenCore 0.5.4 following this Vanilla Guide by khronokernel
      https://khronokernel-2.gitbook.io/opencore-vanilla-desktop-guide/
       
      Just an issue with the ethernet intelmausiethernet.kext injecting...
      SOLVED - the sample plist default kernel entry for Ethernet BOOLEAN is NO.  I changed to the kext name correctly, but oversaw to make the simple change to YES!
       
      OC 0.5.4
      OSX 10.15.2
      ASUS Rog Maximus X Code Bios v2203 (uses Intel® I219V)
      i7 8700k w/ AMD RX 580 Sapphire Nitro+ SE
       
      The latest kext is in my EFI/OC/Kexts folder with the other latest kexts that have loaded properly.  It seems to be entered correctly in the config.plist like the other latest kexts.  But the service is inactive and there is no Ethernet connection.  Airport works fine.
       
      I ran kextstat in terminal and could confirm that the kext was not loaded. Nor did en0 report anything with IoRegistryExplorer
      The only way I was able to get ethernet to work was by manually installing the kext into the L/E/ folder via ##### and after reboot.
      I can confirm ethernet is now working and reports as loaded with kextstat, and the device populates in IoRegistryExplorer.
      I know ##### sn't the proper way to install kexts so reaching out for some advice if I've done anything wrong with my config.plist
      Possibly an issue with OC version 0.5.4? I know everything is still BETA.
      Attached is my EFI folder with serial removed
      EFI.zip
×