Jump to content
dgsga

OpenCore Discussion

2,966 posts in this topic

Recommended Posts

5 minutes ago, aben said:

Hi OpenCore testers,

 

Unable to get XCPM and X86PlatformPlugin to work with plugin-type, how does one patch KernelXCPM like Clover on OC for i5 Ivy-Bridge, should I be using FakeCPUID and xcpm_bootstrap patches from @PMheart ? Where can I find these kernel patches 

Ivy-Bridge doesn't support XCPM

Share this post


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

Ivy-Bridge doesn't support XCPM

 

Sorry I mean't XCPM patches for Ivy-Bridge to get X86PlatformPlugin and PM to work on 10.13.6 using OC.

I hope @PMheart can help me find Ivy bootstrap patches for 10.13.6 since Clover spoiled me with KernelXCPM auto patches 

 

Edit: Finally fixed XCPM kernel panic by using @PMheart's AppleX86PlatformPluginInjector with patched MAC-BoardID, Ivy-Bridge now running flawless on OC 0.5.1 with full Power Management. Thanks to all developers and OpenCore Team for this amazing bootloader. Goodbye Clover, you were good to me. Cant wait to experience the future OpenCore development in action.

Edited by aben

Share this post


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

 

Sorry I mean't XCPM patches for Ivy-Bridge to get X86PlatformPlugin and PM to work on 10.13.6 using OC.

I hope @PMheart can help me find Ivy bootstrap patches for 10.13.6 since Clover spoiled me with KernelXCPM auto patches 

 

Edit: Finally fixed XCPM kernel panic by using @PMheart's AppleX86PlatformPluginInjector with patched MAC-BoardID, Ivy-Bridge now running flawless on OC 0.5.1 with full Power Management. Thanks to all developers and OpenCore Team for this amazing bootloader. Goodbye Clover, you were good to me. Cant wait to experience the future OpenCore development in action.

Hey can you share your OpenCore folder?

 

Thanks

Share this post


Link to post
Share on other sites
14 hours ago, Download-Fritz said:

@obus It is a bug in the current DEBUG build documented in the Changelog, this error happens when an "Arguments" field is empty. It does not affect RELEASE or master DEBUG builds

Tested with the Release version 0.5.1 with "FailSafe empty Arguments string" and got the same result as previous test, stuck at boot menu.

OpenCore is loading but can't find any APFS/recovery volume  to boot on. If I put in my USB recovery pen drive I use for my other two (fully working) rigs when I want to do a recovery, the RecoveryImage.dmg pops up in boot menu and start loading but fail before boot into recovery.

 

Is this a problem with my firmware in my HP laptop or with my config.plist, or could it be a problem with OC or maybe a bug in OC?

I feel Iv'e get no serious response in this matter. People just more and less telling me that this is a "noob" problem with my config.plist (read the manual and so on.) It might be a part of the problem but even if I should have some problem with my configuration my rig should at least boot up and then crash. I'm not an expert but I'm not a noob neither. I have two fully working rigs with OpenCore but I never had experienced a problem like this. Clover is working flawlessly on this laptop and I'm quite sure that that should be the case with OpenCore too, if I can solve this boot problem.

 

I attach the last log with Debug version and my used config.plist.

 

Is there any of you devs how could try to shed some lights over my problem?

config.plist

opencore-2019-10-15-155211.txt

Share this post


Link to post
Share on other sites

@obus I'm not spending much time to read user reports right now because I want to use my time off on the OC crypto stack

"FailSafe empty Arguments string", what is this supposed to be? it must *not* be empty in DEBUG, currently

Try with non-empty "Arguments" and current DEBUG, or leave the field alone and compile master DEBUG (bug fixed there)

Edited by Download-Fritz

Share this post


Link to post
Share on other sites
5 hours ago, Download-Fritz said:

@obus I'm not spending much time to read user reports right now because I want to use my time off on the OC crypto stack

"FailSafe empty Arguments string", what is this supposed to be? it must *not* be empty in DEBUG, currently

Try with non-empty "Arguments" and current DEBUG, or leave the field alone and compile master DEBUG (bug fixed there)

8.6 Entry Properties

  1. Arguments
    Type: plist string
    Failsafe: Empty string
    Description: Arbitrary ASCII string used as boot arguments (load options) of the specified entry.

This is what I mean with "FailSafe empty Arguments string".

Try to read what I men instead of treat me like an idiot!

 

Secondely above is not my problem. The problem is that I can't boot with OpenCore if you care to read what I've wrote previously . 

Edited by obus

Share this post


Link to post
Share on other sites

@obus Let me clarify. You are asking me for help, and I am on limited time to dedicate for this kind of request, so I will read, think and respond as long or short as I see fit to suit my available resources, not more and not less. I have explained the bug, you have not avoided the bug with obvious and explained ways, but instead re-provide the same kind of useless log in every post. Yet, I had been patient, I told you the possible ways again, and yet I do not see the log in the fashion it had been requested. I'm not sure what you are expecting from me, but whatever it is, you are not going to get it. I will not dedicate a single second more to this until we have an actually useful log.

Share this post


Link to post
Share on other sites

@obus, the configuration document is correct, but there is a bug in 0.5.1-DEBUG release.

 

to work around the bug either add some dummy value into each of your <Arguments> entries such as "Bypass" as this will prevent the ASSERT stop you are seeing.

 

or you can build the source from the repo as the bug has been fixed.

 

easiest for you is to add dummy values into each of the Argument entries as indicated above.

Share this post


Link to post
Share on other sites

Sorry Iv'e already tested that but the ASSERT stop is still coming up. 

I will compile a new master Debug version and test.

 

Cheers anyway

Edited by obus

Share this post


Link to post
Share on other sites
16 minutes ago, UefiBooter said:

its a different problem if you have added dummy value. but yeah better to wait for a 1.x.x release in your circumstance.

Ok here is the log from a new compiled 0.5.2 OC version.

It is telling me exactly the same as the old one or?

opencore-2019-10-16-101413.txt

Edited by obus

Share this post


Link to post
Share on other sites
On 10/12/2019 at 10:32 AM, jsl2000 said:

Big thanks to Shaneee & darc without their help I can not get OC 0.5.0 working.

Booting with OC 0.5.0 in Ryzen 1700X hackintosh got instant reboot at 10.15 (19A583), but working well at 10.13.6, 10.14.5, & 10.14.6.

My config.plist & OC.zip were attached

How to fix it ?

[Solved]

There's no error in my OC folder.

It got reboot because it tried to update from 19A583 to 19A602 by itself.

Allowed completing update by Clover, it can work by OC again !

 

 

 

 

config.plist

OC.zip

Edited by jsl2000

Share this post


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

Ok here is the log from a new compiled 0.5.2 OC version.

It is telling me exactly the same as the old one or?

opencore-2019-10-16-101413.txt

 

OC finds only the ESP it itself is installed on, tries to boot itself, detects nested boot and aborts, that's it.

Make sure ConnectDrivers is on and HFSPlus/ApfsDriverLoader are current and working

Share this post


Link to post
Share on other sites
2 hours ago, Download-Fritz said:

 

OC finds only the ESP it itself is installed on, tries to boot itself, detects nested boot and aborts, that's it.

Make sure ConnectDrivers is on and HFSPlus/ApfsDriverLoader are current and working

All my drivers and kext are up to date, downloaded today from official site. I swapped the HFSPlus.efi to VBoxHfs.efi and tested again with the same result.

My latest HP firmware works perfect with "native" NVRAM in Clover so problems with HP firmware shouldn't be the culprit.

So I put the question again. Is it something wrong with my config.plist or is it something with OpenCore?

Can I do some further reserch myself or is the problem unresolvable with OpenCore and My laptop?

Edited by obus

Share this post


Link to post
Share on other sites

Infact, it is a "problem" with the HP firmware. If it's not a literal bug, it's an unexpected state, because the only other person to ever report similar behaviour experienced it on a HP laptop as well. It's not impossible it's a problem with OC, if you want to test further, load the drivers from Shell and run "reconnect -r" before launching OC... it might work if you exit Shell again from within OC too, but not sure

Edited by Download-Fritz

Share this post


Link to post
Share on other sites
9 minutes ago, Download-Fritz said:

Infact, it is a "problem" with the HP firmware. If it's not a literal bug, it's an unexpected state, because the only other person to ever report similar behaviour experienced it on a HP laptop as well. It's not impossible it's a problem with OC, if you want to test further, load the drivers from Shell and run "reconnect -r" before launching OC... it might work if you exit Shell again too, but not sure

Tested without success.

Giving up for the moment.

Share this post


Link to post
Share on other sites

Hey friends,

 

I've been up and running for a few months now. Im loving the simplicity of this since getting my head around most of it. Im about to enter a busy season of work and wanted to do a little check up to see if there's anything I should be doing differently. Does anyone care to look these over and see if "I done good" for me? No sweat if not. I feel like I've checked all the boxes.

 

Archive 2.zip

Share this post


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

You should upload EFI folder (Include BOOT and OC Folder).

Not only config.plist

Thank's for showing interest. Can you help me solving this problem you will be my hero of the year:)

Here is my complete EFI-folder.

EFI_OC_0.5.2_Debug.zip

Share this post


Link to post
Share on other sites
On 10/17/2019 at 2:17 AM, obus said:

Thank's for showing interest. Can you help me solving this problem you will be my hero of the year:)

Here is my complete EFI-folder.

EFI_OC_0.5.2_Debug.zip

Try this.. replace OC and BOOT folder with this

 

 

Edited by Andres ZeroCross

Share this post


Link to post
Share on other sites

Hi everyone,

 

What are the necessary Quirks to fix Big Apple boot logo, in short words here is my explained problem:

Disabling CSM does show correct size of Apple Boot Logo and OC display scaling correctly but as soon as Apple Logo reaches 60% when it blinks, screen get's garbled like this:

CSM_OFF.thumb.jpg.9fc8bbd046aeeddff248fed7de02dbe2.jpg

 

However if i close and open the lid (without waiting for sleep, the screen comes back to normal

 

The second option is leaving CSM enabled shows Massive Apple Logo progress bar like this:

1.thumb.jpg.32d0243d1596ae7b88dbfa22466368c5.jpg

 

And when it reaches 60% of the apple boot logo bar (when screen blinks), it goes back to normal and glitches don't occur:

2.thumb.jpg.bf57ea6cddfc95e3b9e7dc2fc600498d.jpg

 

So with CSM disabled i get glitchy screen, how to fix that (closing and opening lid is a workaround but it's pain in the a..)

CSM enabled Huge OC text (small resolution) and huge apple logo but no glitch (possibly a fix for this if none for glitchy screen with csm disabled)

 

Here is my EFI.zip

Share this post


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

Hi everyone,

 

What are the necessary Quirks to fix Big Apple boot logo, in short words here is my explained problem:

Disabling CSM does show correct size of Apple Boot Logo and OC display scaling correctly but as soon as Apple Logo reaches 60% when it blinks, screen get's garbled like this:

CSM_OFF.thumb.jpg.9fc8bbd046aeeddff248fed7de02dbe2.jpg

 

However if i close and open the lid (without waiting for sleep, the screen comes back to normal

 

The second option is leaving CSM enabled shows Massive Apple Logo progress bar like this:

1.thumb.jpg.32d0243d1596ae7b88dbfa22466368c5.jpg

 

And when it reaches 60% of the apple boot logo bar (when screen blinks), it goes back to normal and glitches don't occur:

2.thumb.jpg.bf57ea6cddfc95e3b9e7dc2fc600498d.jpg

 

So with CSM disabled i get glitchy screen, how to fix that (closing and opening lid is a workaround but it's pain in the a..)

CSM enabled Huge OC text (small resolution) and huge apple logo but no glitch (possibly a fix for this if none for glitchy screen with csm disabled)

 

Here is my EFI.zip

 

Try ProvideConsoleGop=Yes

Share this post


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

Try this.. replace OC and BOOT folder with this

 

EFI.zip

Sorry but that EFI dosen't work. Stuck at boot menu. Stuck at:StartImage failed- Not Found. 

It was no debug version so I can't provide any logs.

Any other suggestions?

Edited by obus
still stuck at:StartImage failed- Not Found

Share this post


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

 

Try ProvideConsoleGop=Yes

Thanks @Andrey1970

With CSM disabled that didn't fix the glitch, so it's a firmware issue,

 

However i managed to fix with CSM enabled, i set ConsoleMode and Resolution to Max, that fixed the big Apple logo and with CSM enabled the glitch doesn't occur so problem is solved.

Share this post


Link to post
Share on other sites

Hello.

ASUS K501UQ laptop, trying to run it with OpenCore 0.5.1. Getting
 

...
55:905 00:054 OCABC: MMIO devirt end
65:961 10:056 OC: Boot failed - Aborted
66:201 00:240 OCC: Configuring behaviour 0
66:256 00:054 OCB: StartImage failed - Aborted

OC folder and log are attached.

 

Also a couple things that I'm not sure about.

I'm using patched DSDT due to extensive battery and eGPU patches. I'm not sure in what order OC goes about patching/inserting/dropping tables. Specifically, I see in log

Patching DSDT of 156035 bytes with 0000000000000000 ID replaced 1 of 0

and then 

Replaced DSDT of 157634 bytes into ACPI

Does that mean that if I provide custom DSDT, I must apply all patches manually?

 

OC.zip

opencore-2019-10-17-110303.txt

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 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:
       - Hotkey W to boot directly to first available Windows boot entry from either auto scanner or custom entries. (Hold down W to boot Windows OS directly).
       - Auto boot to last booted OS entry (if Misc->Security->AllowSetDefault is NO/false).
       - No verbose apfs.efi driver loading (if using apfs.efi instead of ApfsDriverLoader.efi).
       - Avoid duplicated entry in boot menu, cusstom entry will not be added to boot menu if the same entry already found by auto scanner.
       - Ability to change entry name found by auto scanner by adding custom entry with the exact same device path.
       - Compile with latest edk2.
       - NvmExpressDxe driver build script are also available for system without native nvme support. (Compatible with OC and Clover).
       - ACPI patches is now optional for non macOS with setting ACPI->Quirks->EnableForAll to yes (default is no).
       - *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).
       - macOS Recovery/Tools Entries are hidden by default, use Spacebar in Boot Menu as a toggle on/off to show/hide hidden entries.
       - Individual custom entry can now be set hidden using Misc->Entries->Item 0->Hidden. (Boolean).
       - Booter Quirks only apply to macOS.
       - Custom entries are now listed first in picker menu and by the orders they are appeared in Misc->Boot->Entries, before all other entries.
       - Improved Hotkeys successful rate.
       - SMBIOS and Device Properties patches are now only applied to macOS.
       - Boot Entry Index key 1- 9 can be used as a Hotkey in addition to previous hotkeys implementation to boot directly to that entry and skip the picker menu showing process
       
      For best multi boot experience, turn off ShowPicker and use hotkeys w and x to switch between Windows and macOS, and option key to bring up the boot menu if needed.
       
      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
    • By DarkAlex97
      Hi guys i just installed Catalina using Open Core. Everything is working except audio. I tried to install the os multiple times chaning some parameters but nothing.
      I followed this guide: https://khronokernel-2.gitbook.io/opencore-vanilla-desktop-guide/
      I'm pretty sure the problem is here:
      Maybe i'm setting a wrong layout-id? Am i missing something?
      I tried different layouts (1 and 11) (the one in the picture above is 11) https://github.com/acidanthera/applealc/wiki/supported-codecs
      Here's the content of the USB:
      And here's the config.plist i'm using https://pastebin.com/2QBpqafb
      My hardware:
      CPU: intel i7 8700k
      GPU: integrated intel hd630
      RAM: Corsair ddr4 16GB (2x8)
      Motherboard: ASUS ROG Strix Z370-E -> Audio: Realtek S1220A
      Any help is much appreciated :3
    • By kylon
      Cloud Clover Editor is an open source application that allows you to manage the configuration of various Hackintosh Bootloaders.

      Open Cloud Clover Editor
       
      Cloud Clover Editor Wiki
      Cloud Clover Editor Sources
       
       
      Features
      Supports Clover EFI, Ozmosis, Chameleon, OpenCore GUI and Text Editor Mode CCE Bank Mobile friendly and more...  
      Officially supported browsers
      Chrome 42+ Microsoft Edge 14+ Firefox 39+ Safari 10+ Opera 29+ Opera Mobile 12+ Chrome for Android 75+ Firefox for Android 67+  
       
      Credits
      mackie100 - took some ideas from his app Clover EFI dev team Eric Slivka - new serial number Virtual1 - new serial number cecekpawon - PHP 5.3.3 patch, , help with the ACPI Loader Mode flag and more Micky1979 - Clover flying editor  (Discontinued) crusher. - Help with the ACPI Loader Mode flag Download-Fritz - Help with the ACPI Loader Mode flag Pavo - Ozmosis fields and values stehor - Ozmosis fields and values Sherlocks - General help and support gujiangjiang - General help and support  
      Please let me know if i forgot you!
×