OpenCore General Discussion

[Sander Spilleman]

Hi,

 

I've just upgraded to OC 0.5.8. I'm on macOS 10.15.4 on a Asus Prime Z390-A. Over time I've collected some stuff in my config related to RTC patching, which is needed as otherwise I have that F1 POST / Safe mode {censored}. I might have some stuff in my config that may not be needed anymore. I'd like to get some support to get confirmed what is still needed and want I can remove by now.

 

My config contains the following

Kernel --> Quirks --> DisableRtcChecksum set to TRUE (added in update to OC 0.5.8)

UEFI --> ProtocolOverrides --> AppleRtcRam set to TRUE  (added in update to OC 0.5.8)

NVRAM --> Add --> 7C436110-AB2A-4BBB-A880-FE41995C9F82 --> wake-failure set to 5 bytes 0 (added after 10.15.4: https://github.com/acidanthera/bugtracker/issues/765)

ACPI --> Add --> SSDT-AWAC.aml (per vanilla desktop guide)

 

ACPI --> Patch as follows: (I believe this was generated by SSDTTime)

 

And Kernel --> Add --> Patch the following 2: (found these in here... somewhere)

 

Is there something I can get rid of??

 

Thank you so much!

 

Sander

Edited May 4, 2020 by Sander Spilleman

[kiu777]

1 hour ago, bexem said:

Fair enough, I will try and clean it, I understand that and thank you for pointing it out. But it must be said, I had no issues with the previous release (this doesn't mean I'm not going to skim it). I'm just trying to figure that out. 

 

PS: I'll do my signature right away!

 

EDIT: Sorted out, cleaned it up and re-downloaded, now it works! Thank you anyway! Stay safe!

cool!

[kiu777]

1 hour ago, eSaF said:

@ kiu777 - I've done some corrections to the Patch and removed some unnecessary entries and it is clean as possible (See Pic). This Patch allows me to hot swop disks on the fly as I have a case with an X-DOCK feature which I use to load programs from external disks and do backups also disks shows as external (Orange Icon).

Tried even your stripped version of the patch. And it did not work either. Not really astonishing for me because it is not so different from the version I tried before.
I suspect that there must be another problem in my configuration.
Nevertheless thank you for your effort!

[kiu777]

@eSaF
Thank you for posting. I compared it with mine and found several smaller differences but none seems to be responsible for my problem.

[markl18]

hi can someone help this is a kp

OC.zip

Edited May 5, 2020 by markl18

[ltooz_audis]

On 5/2/2020 at 4:12 AM, MacNB said:

 

Those patches will not work because you have not specified in the Identifier field which binary this patch applies to (e.g. driver, kernel, etc).

You have to look at your Clover patches (which you did not post here) and use them as the basis for OC patch

Besides, if you use Whatevergreen kext, those patches you are trying should not be necessary.

 

If you want timeout on the boot picker to work, you have to build the latest version of OC 0.5.8.

If you do, be warned that the certain fields on the Config files have changed to reflect the changes in the OC features.

You have to read the Differences.pdf file to find what has changed and look at the new Samples.plist file.

 

 

Thanks, I've downloaded the 0.5.8 and yes, it's autoboot after 5 seconds. I've tested the booting time of the OC 0.5.8 and Clover 5113 on the same volume and OC = 36 sec and Clover 51 secs. Now, there's one thing that really bother me is that in the EFI folder, there are tons of text files from OC which eventually will fill up the EFI partition. How do I move the default folder or stop OC from reporting.

Thanks,

Louis 

[topolino1]

What exactly is it for.
I don't understand this description.

1. BootProtect
   Type: plist string
   Failsafe: None
   Description: Attempt to provide bootloader persistence.

   Valid values:

   • None — do nothing.

   • Bootstrap — create or update top-priority \EFI\OC\Bootstrap\Bootstrap.efi boot option (Boot9696)

     in UEFI variable storage at bootloader startup. For this option to work RequestBootVarRouting is required to be enabled.

     This option provides integration with third-party operating system installation and upgrade at the times they overwrite \EFI\BOOT\BOOTx64.efi file. By creating a custom option in Bootstrap mode this file path becomes no longer used for bootstraping OpenCore.

     Note 1: Some firmewares may have broken NVRAM, no boot option support, or various other incompatibilities of any kind. While unlikely, the use of this option may even cause boot failure. Use at your own risk on boards known to be compatible.

     Note 2: Be warned that NVRAM reset will also erase the boot option created in Bootstrap mode.

[Tiem]

1 hour ago, topolino1 said:

What exactly is it for.
I don't understand this description.

1. BootProtect
   Type: plist string
   Failsafe: None
   Description: Attempt to provide bootloader persistence.

   Valid values:

   • None — do nothing.

   • Bootstrap — create or update top-priority \EFI\OC\Bootstrap\Bootstrap.efi boot option (Boot9696)

     in UEFI variable storage at bootloader startup. For this option to work RequestBootVarRouting is required to be enabled.

     This option provides integration with third-party operating system installation and upgrade at the times they overwrite \EFI\BOOT\BOOTx64.efi file. By creating a custom option in Bootstrap mode this file path becomes no longer used for bootstraping OpenCore.

     Note 1: Some firmewares may have broken NVRAM, no boot option support, or various other incompatibilities of any kind. While unlikely, the use of this option may even cause boot failure. Use at your own risk on boards known to be compatible.

     Note 2: Be warned that NVRAM reset will also erase the boot option created in Bootstrap mode.

It means fooking around with NVRAM variables, given their nature of being chaotic at best, is something you really shouldn't be doing if you don't precisely know what you're doing. NVRAM stores quite a bit of data, not just macOS-only entries. This setting is stored there. It has to be to jump ahead of anything aside from the BIOS.

[familygw]

Hi everyone!
I recently updated my boot loader to OC 0.5.8 and I noticed the new configuration section related to APFS. Everything is working fine but now the default boot device doesn't work.
I'm using Windows 10 and macOS in separated SSD disks, so I configured the Security > ScanPolicy option to 0 in order to see all my drives and until the version 0.5.7 (using ApfsDriverLoader.efi driver) everything went fine, now with the new option the order of appearance in OC Picker changed and the Windows drive is the first option and OC start automatically in Windows and not in macOS. No matter if I choose the startup disk (the only option in macOS is the macOS drive).
NVRAM are ok, I've reseted several times but nothing.

My idea is to boot in macOS by default and only choose Windows pressing the hotkey during the boot (or, show the Windows drive at Preferences > Startup Disk, which will be great).

Any clue?

 

Thanks in advance.

PS: attached are my EFI disk's content.

EFI (OC 0.5.8).zip

[polkaholga]

On 4/26/2020 at 5:32 PM, polkaholga said:

I just noticed that my hack immediately restarts when I try to use search in Finder.

 

Doesn't make any difference if I use BLT or wired keyboard, when I go to the search bar click into it all ok.

But as son as I hit the first letter... black screen and restart !

Keyboards work flawless in any other application though !

Anyone experiencing the same ?

 

I still can't figure it out what is wrong here.

This error does not happen with CLOVER

 

My actual config added... if someone could take a look i really would appreciate it.

Thanks

config.plist

[obus]

2 hours ago, familygw said:

Hi everyone!
I recently updated my boot loader to OC 0.5.8 and I noticed the new configuration section related to APFS. Everything is working fine but now the default boot device doesn't work.
I'm using Windows 10 and macOS in separated SSD disks, so I configured the Security > ScanPolicy option to 0 in order to see all my drives and until the version 0.5.7 (using ApfsDriverLoader.efi driver) everything went fine, now with the new option the order of appearance in OC Picker changed and the Windows drive is the first option and OC start automatically in Windows and not in macOS. No matter if I choose the startup disk (the only option in macOS is the macOS drive).
NVRAM are ok, I've reseted several times but nothing.

My idea is to boot in macOS by default and only choose Windows pressing the hotkey during the boot (or, show the Windows drive at Preferences > Startup Disk, which will be great).

Any clue?

 

Thanks in advance.

PS: attached are my EFI disk's content.

EFI (OC 0.5.8).zip

After NVRAM reseat Windows will be the default startup disk automatically. To change default startup disk you need to use the bless tool in System Preferences --> Startup Disk. 

[Tiem]

1 hour ago, obus said:

After NVRAM reseat Windows will be the default startup disk automatically. To change default startup disk you need to use the bless tool in System Preferences --> Startup Disk. 

There are many ways to do this. You can set this in OC directly. You can also set this in the BIOS. And of course in Windows using something like BOOTICE.

AllowSetDefault
Type: plist boolean
Failsafe: false
Description: Allow CTRL+Enter and CTRL+Index handling to set the default boot option in boot picker.

 

[Andres ZeroCross]

@vit9696 i just compiled latest OpenCorePkg and AppleSupportPkg, and i can't hear audio assist anymore.

[obus]

1 hour ago, Tiem said:

There are many ways to do this. You can set this in OC directly. You can also set this in the BIOS. And of course in Windows using something like BOOTICE.

AllowSetDefault
Type: plist boolean
Failsafe: false
Description: Allow CTRL+Enter and CTRL+Index handling to set the default boot option in boot picker.

 

Sure man but this is maybe the recommended and most vanilla way.

 

"How to choose the default boot entry?

OpenCore uses the primary UEFI boot option to select the default entry. This choice can be altered from UEFI Setup, with the macOS Startup Disk preference, or the Windows Boot Camp Control Panel."

Edited May 5, 2020 by obus

[MacNB]

9 hours ago, ltooz_audis said:

Thanks, I've downloaded the 0.5.8 and yes, it's autoboot after 5 seconds. I've tested the booting time of the OC 0.5.8 and Clover 5113 on the same volume and OC = 36 sec and Clover 51 secs. Now, there's one thing that really bother me is that in the EFI folder, there are tons of text files from OC which eventually will fill up the EFI partition. How do I move the default folder or stop OC from reporting.

Thanks,

Louis 

 

You're welcome.

RTFM...Section 8.4 of Configuration.pdf (your boot speed might increase a bit more as well).

You cannot change the folder.

[Paksman]

@vit9696 Please correct me if I'm wrong, if I understood correctly, the purpose of adding the fake EC device in SSDT-EC-USBX.dsl is for AppleBusPowerController to load correctly so we have proper USB power property injection. I think it is not needed at least in Catalina, because ApplebusPowerController is now attached to IORessources instead of EC.

Edited May 5, 2020 by Paksman

[ghost8282]

37 minutes ago, topolino1 said:

I also can't hear

Without additional info it's impossible to understand what's going wrong, attach opencore logs.

[familygw]

3 hours ago, Tiem said:

There are many ways to do this. You can set this in OC directly. You can also set this in the BIOS. And of course in Windows using something like BOOTICE.

AllowSetDefault
Type: plist boolean
Failsafe: false
Description: Allow CTRL+Enter and CTRL+Index handling to set the default boot option in boot picker.

 

Hi! thanks for your response. I already did all these options but still booting in windows as first option.

From Windows I‘m able to modify the boot order or the default boot device (in this case the BOOTx64.efi from the EFI partition in the macOS disk), which is basically the same thing that I can do from BIOS Setup. That’s ok, but from the moment that OC boots the computer, the default OS that starts is Windows, no matter if I press Ctrl+Enter or select the macOS disk in Startup Disk.

 

Thanks!

 

[ghost8282]

8 minutes ago, topolino1 said:

opencore-2014-05-05-103808.txt

Can you hear the chime or you can't hear nothing?

[ghost8282]

1 minute ago, topolino1 said:

I can't hear the ringtone and I can't hear PickerAudioAssist.
I have normal sound in the system.

Your config could be wrong then, especially look at the audioout, look at configuration.pdf

[ghost8282]

12 minutes ago, topolino1 said:

I looked at configuration.pdf
I tried values 0, 1, 2, 3, 4, 5. And nothing.
What am I doing wrong. I don't know where to look.

Please help.

 

Is it onboard audio you are trying to make it work or..?Take into account that Hdmi or digital outputs are not supported (by AudioDXE).

Attach a copy of the config.plist too.

Edited May 5, 2020 by ghost8282

[mhaeuser]

3 hours ago, obus said:

Sure man but this is maybe the recommended and most vanilla way.

 

There is no "most vanilla way", this sets the option the exact same way as Startup Disk of course, and it's also available on Macs

[vit9696]

Two things:

- Do you realise that audio assistance is not yet implemented in OpenCanopy? 

- Does audio assistance work with the previous release of AudioDxe?

[Andres ZeroCross]

Two things:
- Do you realise that audio assistance is not yet implemented in OpenCanopy? 
- Does audio assistance work with the previous release of AudioDxe?

Yes, it work before. No problem.

I tried with picker built-in and no audio, ndk-bootpicker (latest commit), same no audio.


It's happened after latest commit of OpenCorePkg and AppleSupportPkg.


Sent from my iPhone using Tapatalk

[Andres ZeroCross]

7 minutes ago, vit9696 said:

Two things:

- Do you realise that audio assistance is not yet implemented in OpenCanopy? 

- Does audio assistance work with the previous release of AudioDxe?

I just tried using my latest working AudioDxe.efi from AppleSupportPkg but with latest OpenCorePkg,, but still no audio. After reach OC GUI, i got the countdown time,,

With working audio then countdown time should be appeared after audio picker finish,, but currently not so it's not about wrong audio setup output.

Sorry for bad english