Jump to content

6,300 posts in this topic

Recommended Posts

23 minutes ago, Sniki said:

Have you found a way to call just the XQ** method without pasting the entire code of the original method ?

 

I really need this as well so i can use all Operating Systems using OpenCore without having something broken (FN Buttons).

Check this repository.

Share this post


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

Thank you @hardcorehenry managed to get everything working with _OSI ("Darwin"):

Starting from Fn Keys to Battery Status & Dual Battery support.

It also has English version just recently released. The same repo just translate into English.

 

https://github.com/jsassu20/OpenCore-HotPatching-Guide

Edited by telepati

Share this post


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

It also has English version just recently released. The same repo just translate into English.

 

https://github.com/jsassu20/OpenCore-HotPatching-Guide

First thanks go to both you @telepati and @hardcorehenry for providing me these links

Second thanks to them for providing such educational repositories.

 

Just completed checking all of the patches, it's amazing how many new things i learned and improved upon.

The more you learn, the more you realize that you know nothing... 

 

I believe now all my hacks should reach perfection in a couple of days (at the very least the ACPI side).

 

Thank you all !

 

Respect,

Sniki

Share this post


Link to post
Share on other sites

OC Boot menu does not display properly on Gigabyte GA-Z77P-D3 Rev1.1

It should appear in the top left corner of the screen!But now it's in the middle:(

 

My Hardware:

Motherboard: Giabyte GA-Z77P-D3 Rev1.1

CPU: Intel Xeon E3 1230 V2

Graphics Card: Sapphire Radeon RX560D

Display: View Sonic VX2478-4K-HD (4K 23.6") DP 1.2

 

IMAG0818.jpg

Z77P-D3 OC EFI.zip

Config.plist

Share this post


Link to post
Share on other sites
6 minutes ago, Cloverkit said:

OC Boot menu does not display properly on Gigabyte GA-Z77P-D3 Rev1.1

 It should appear in the top left corner of the screen!But now it's in the middle:(

 

My Hardware:

Motherboard: Giabyte GA-Z77P-D3 Rev1.1

CPU: Intel Xeon E3 1230 V2

Graphics Card: Sapphire Radeon RX560D

Display: View Sonic VX2478-4K-HD (4K 23.6") DP 1.2

 

IMAG0818.jpg

Z77P-D3 OC EFI.zip

Config.plist

But Press F12 boot into BIOS Boot Menu and Select OC Boot Option is right

Share this post


Link to post
Share on other sites

Hi, today I've just updated to OpenCore 0.5.5, no issues so far. Excellent Bootloader. 

 

My hardware is down below (see signature) and while I was reading though the UEFI section of the Configuration.pdf file I found something familiar with my ASUS motherboard:

 

As @vit9696 described here, he mentions double boot entry problems when dealing with namespaces.

 

"However, some firmwares do their own boot option scanning upon startup by checking file presence on the
available disks. Quite often this scanning includes non-standard locations, such as Windows Bootloader paths.
Normally it is not an issue, but some firmwares, ASUS firmwares on APTIO V in particular, have bugs. For them
scanning is implemented improperly, and firmware preferences may get accidentally corrupted due to BootOrder
entry duplication
(each option will be added twice) making it impossible to boot without cleaning NVRAM"

 

Now, I would like to have some clarification on the topic, I'm currently using these Quirks under UEFI > Quirks:

 

•RequestBootVarFallback ON 

I suppose that this quirk enhances security as described here:

 

"By redirecting Boot prefixed variables to a separate GUID namespace we achieve multiple goals (goals_list_after)"

 

I need confirmation that this happens when RequestBootVarFallback is enabled. Thanks

 

Also, this quirks implements security fixes by doing this, is it?

 

 "redirects some Boot prefixed variables to EFI_GLOBAL_VARIABLE_GUID (and requires the other quirk down below to be enabled)"

 

The other quirk I need to have more clarification on, is this:

 

•RequestBootVarRouting ON 

 

"To trigger the bug one should have some valid boot options (e.g. OpenCore) and then install Windows with
RequestBootVarRouting enabled."

 

My question is: if my scope is Not to trigger the bug, I should reboot my pc at least once with both quirks disabled (RequestBootVarFallback OFF +RequestBootVarRouting OFF)?

 

Thanks in advance. 

 

Share this post


Link to post
Share on other sites

Regarding picker issues, newly added BuiltinTextRenderer may improve the situation (it also supports HiDPI).

 

@1Ale1RequestBootVarFallback reduces the chance to run into the entry duplication bug. I.e. you may likely not face the bug when you have RequestBootVarFallback enabled if your motherboard is faulty. The bug may still happen even when RequestBootVarFallback is enabled, however.

 

Even if you have both quirks (RequestBootVarRouting and RequestBootVarFallback) disabled you may still trigger the bug, but indeed with both of them off there is little chance it will happen. However, disabling RequestBootVarRouting will break functionality like switching between operating systems, remembering the default operating system, authenticated restart, unattended update installation, and several others.

Share this post


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

Command-R still doesn't work with TakeoffDelay.

 

These are my settings;

 

I also set TakeoffDelay 0 but nothing change. After Asus Logo, I am pressing Command-R but system boot directly Default boot Drive.  Which part or setting I am doing wrong?

 

1765696715_ScreenShot2020-02-04at00_06_18.thumb.png.c56ce6ef9795cf519f61cb6a61cb8584.png

 

 

On Asus Logo press and hold without releasing. To release when you will see Apple Logo.

Show screenshot Input and Drivers sections in config.plist

Edited by Andrey1970

Share this post


Link to post
Share on other sites

hello 

need some help here with my efi ,reg stalls on " still waiting root device " 

 

EFI.zip

 

Note: my reg is working good catalina 10.15.3 and mojave 10.14.6 with clover 

this is not installtion 

Edited by eng_redaesm
add specs

Share this post


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

spces i7 6700k ,mb gigabyte h270-hd3p ,vga amd rx580 8bg,hdd toshiba m2 ssd 512 ,16 gb ram ddr4

This thread is related to OpenCore, please post your issue in the installation section, and attach your specs to your signature. Thanks

Share this post


Link to post
Share on other sites
53 minutes ago, 1Ale1 said:

This thread is related to OpenCore, please post your issue in the installation section, and attach your specs to your signature. Thanks

dear i know this is opencore topic and my reg is working  good catalina 10.15.3 with clover 

but this efi folder is for opencore 

have a nice day

Share this post


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

dear i know this is opencore topic and my reg is working  good catalina 10.15.3 with clover 

but this efi folder is for opencore 

have a nice day

Yes, but you must ask your question under NDK thread, cause you are using it.

 

 

Share this post


Link to post
Share on other sites
11 minutes ago, telepati said:

Yes, but you must ask your question under NDK thread, cause you are using it.

 

 

ok thanks, done ased the n.d.k topic,  but i have the same issue with standard opencore

Edited by eng_redaesm
add specs

Share this post


Link to post
Share on other sites

The new BuiltInTextRenderer is fantastic, I can finally see it on my 4K screen :)

 

I understand it is Work-In-Progress, but if it helps devs, it seems that some shell commands do not get formatted properly (Particularly with -b formatting)

 

fantastic work!

 

IMG_3606.thumb.JPG.af20826317e86150b8d82b06b20520c5.JPGIMG_3607.thumb.JPG.204307766f7b58b51c7e6011d9520a94.JPG

Share this post


Link to post
Share on other sites

@telepati

 

I have the same problem .

Before, everything was fine.

Share this post


Link to post
Share on other sites
On 2/3/2020 at 10:04 PM, Cloverkit said:

But Press F12 boot into BIOS Boot Menu and Select OC Boot Option is right

The new experimental options  `BuiltinTextRenderer` solved my problem:D

Screen Shot 2020-02-05 at 9.58.44 AM.png

IMAG0819.jpg

IMAG0820.jpg

Share this post


Link to post
Share on other sites
On 12/19/2019 at 2:03 AM, termi said:

my opencore is not booting stuck on boot screen help me out i have also uploded efi folder 

EFI.zip

WhatsApp Image 2019-12-20 at 1.53.44 AM.jpeg

Check message. Your kext are not loaded properly. See if you have deleted any kext and its entry is still there in config.plist.

Share this post


Link to post
Share on other sites
On 1/31/2020 at 11:36 PM, Download-Fritz said:

@Slice @Matgen84 @telepati @dani77zg MemoryAllocation.efi is just renamed free2000, please don't recommend this junk. For memory allocation errors, upgrade the firmware, follow the recommended firmware settings (e.g. Above 4G decoding), use DevirtualiseMmio and ProvideCustomSlide.


I’m currently running an Aorus Master Z390, 9900K, RX 580, IGPU enabled, and I can’t get OC 0.5.5 to boot without MemoryAllocation.efi. 

 

Any tips you can recommend? Slide values don’t help. Changing memory settings for IGPU doesn’t either. I’ve probably tried everything there is to try, including various OC quirks and settings.

Edited by M0r1d1n

Share this post


Link to post
Share on other sites

Hello guys, i need some help. I just upgraded OC to version 0.5.6 , everything works except that OC did not detect my windows bootloader. Then when i try to rollback OC with version 0.5.5 from backup my windows bootloader still not detected. 

on my config:

AdviseWindows > Enabled

RequestBootVarFallback > Enabled

RequestBootVarRouting > Enabled

 

Any tips will be appreciated.... :)

Share this post


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


I’m currently running an Aorus Master Z390, 9900K, RX 580, IGPU enabled, and I can’t get OC 0.5.5 to boot without MemoryAllocation.efi. 

 

Any tips you can recommend? Slide values don’t help. Changing memory settings for IGPU doesn’t either. I’ve probably tried everything there is to try, including various OC quirks and settings.


Disconnect all power from the system and then remove the battery from the motherboard for a few minutes, put it all back and load your bios profile back in and it should boot up first go after that.

Share this post


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


Disconnect all power from the system and then remove the battery from the motherboard for a few minutes, put it all back and load your bios profile back in and it should boot up first go after that.


I unlocked CFGLOCK in my BIOS earlier and saved it as a profile I can load from memory. I assume it will get wiped along with the BIOS settings? Should I try to save it to a pendrive?

Edited by M0r1d1n

Share this post


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


I unlocked CFGLOCK in my BIOS earlier and saved it as a profile I can load from memory. I assume it will get wiped along with the BIOS settings? Should I try to save it to a pendrive?

 

if you save your bios as a profile before you do what I said it will still be there to load back in after you put the battery and power back.

Edited by AudioGod

Share this post


Link to post
Share on other sites
5 minutes ago, AudioGod said:

 

if you save your bios as a profile before you do what I said it will still be there to load back in after you put the battery and power back.


Thanks. I’ll try to copy it over to a spare pen drive as a backup just I case (if that’s even possible). Will share results in a week after I get back from my travels. 

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

Announcements

  • Similar Content

    • By chris1111
      Here my theme of OC 

      How to create are own Theme with Icnspack-Builder
       

       
       
      You can also have the themes on ➤ Github
       
      You can also have the themes on ➤ HTML Page
       
    • By Schlachtbank
      Hi. I need help if possible.
      I tried installing Big Sur on my Hackintosh with OC and Catalina working. Every time I try to boot it I receive a kernel panic relative to ACPI. The strange thing is that this kernel panic occurs only with Big Sur and High Sierra. Every other macOS version boots (I tried from 10.9 to 11).
       
      My build is:
      Motherboard: Gigabyte X79-UD3 CPU: Intel Core I7 4820K GPU: XFX Radeon RX570 I'm attaching the kernel panic and my EFI configuration (I still need to map the USBs 'cause I switched to OpenCore yesterday).
      PS. In the OC folder there's not a resources folder because I deleted it to upload it
      Kernel panic Big Sur.rtf
      OC configuration.zip
    • By dsener
      Hi All,
       
      Need some advice.
       
      I have setup Catalina using opencore 0.6.1, works fine, except max resolution and audio on a Dell Optiplex 7050 micro with 6600T CPU and Q270 mobo 
       
      WHen I plug into a 4K monitor I get 2560x1440 max resolution and when plugging into a 2560x1440 monitor I get 1920x1080 max resolution. ANy help is much appreciated.
       
      I only have
      - AppleALC
      -IntelMausi
      - Lilu
      - NVMEFix
      - SMCDellSensors
      - USBInjectAll
      -VirtualSMC
      - WhateverGreen and
      - SHCI-unsupported in my kexts folder
       
      config.plist
    • By IronManJFF
      Z77MX-QUO-AOS Migrating from OZ to OpenCore (based on OpenCore 0.5.7-2020-03-08)
       
      0) Disclaimer : This a Guide for the QUO motherboard, 100% to fail on any other. I have not tested it with iGPU only so take note. I have not tested it with any other SMBIOS than iMac13,2. I have not tested 'FileVault' drives or Fusion drives.
      1) Backup your current firmware and settings  use Q-Flash  Save BIOS to ROM... if you don't and end up with a brick you deserve what is happening to you
       
      2) Backup your data, only fools don't take backups
       
      Follow these steps ..don't come bitching if you don't do them in the correct order (and don't be creative, well you can be after you make it work with this recipe)
       
      3) Retrieving info, you will need using HackinTool 
      Board Serial Number  ROM ModelIdentifier Serial Number System ID 4) Download "OC to OC Migration.zip" (to come) and extract it 
      5) Now Open this file using XCode or your favorite Plist Editor
        

       
      6) Fill in the info from Step 3 in the Generic Section (don't touch anything else)
       

       
      7) Save as config.plist
       
      8) Open your EFI folder from your boot drive (the one that has the OZ folder), time to copy the stuff over
       

       
      9) Time to flash the OC-friendly firmware, put the firmware on a USB stick and flash it
       

       
      10) If all goes well when it reboots , you will see the original QUO Boot Logo and then it will greet you with a Bootpicker screen .. kinda like when you hold Option on a real Mac. something like (to see reset NVRAM, Recovery HD and access to UEFI Shell from this screen .. press Spacebar)

       
      11) Choose which OS to Boot and enjoy!
       
       
      Special Topics:
       
      The OC-friendly firmware basically it is :
             The H20-XMASS firmware
      stripped of Ozmosis, FakeSMC, HFS, APFSDriverLoader,VoodooHDA and anything Oz specific while retaining the DSDT that made it special snapped back the QUO Boot Logo from the original firmware (F3A) was the only way I found to fix black screen on cold boot Optimized Defaults values to be OC-friendly       
       
      To get into UEFI Shell before invoking OC ---> Hold F12 at startup (nothing new)
      Setting Default Boot Drive ---> OC honors Startup Disk Control Panel
      Windows (UEFI) ---> Two ways , pick one and stick with it
      From OC Boot Picker (that is what I do) From the mobo native boot picker (Holding F12 at startup and choosing Windows) HD4000 headless ---> In firmware setting .. iGPU enabled, Init Display first PEG (that's it --will not work with SMBIOS MacMini), make sure you have a working setup before enabling this feature.
      Parrallels Desktop, VMWare Fusion, Virtual Box --> In firmware setttings, Intel Virtualization Technology  Enabled (i left it off by default because there might be people with Sandy Bridge or Pentium CPU)
       
      To remove the BootPicker at startup (you can still make it show by holding Option at boot) --> Set ShowPicker key to false in config.plist
      To disable the BootChime et startup --> Set AudioSupport key to false in config.plist
       
      Troubleshooting:
       

       
      To retrieve Debug log from Terminal
      nvram 4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:boot-log | awk '{gsub(/%0d%0a%00/,"");gsub(/%0d%0a/,"\n")}1'  
      Get the migration kit (0.5.8)
       
      Updated Kit for 0.5.9
       
      Updated Kit for 0.6.0
       
      *** WARNING I am having issues with 0.6.1 don't apply unless you can revert to 0.6.0 ***
      *** Issue is : Get prohibited sign on cold boot ...under investigation ***
      Updated Kit for 0.6.1
      *** WARNING I am having issues with 0.6.1 don't apply unless you can revert to 0.6.0 ***
      *** Issue is : Get prohibited sign on cold boot ...under investigation ***
       
    • By MacLover1984
      I am installing MacOS Catalina by OpenCore version 0.6.1 with following configuration:
      ·         Ryzen 7 3700X,
      ·         Sapphire Nitro RX 5500XT,
      ·         MSI x570 tomahawk wifi with Realtek® 8125B 2.5G LAN controller
      I have gathered all required files and doable with LucyRTL8125Ethernet.kext[V1.0.0d6] according to installation guide. But when I am going to install Catalina, a message “An internet connection is required to install MacOS” is showing. Please guide me to resolve the issue.

      config.plist
      Info.plist
×