OpenCore General Discussion

[Matgen84]

2 hours ago, dani77zg said:

Hi all! Has anyone encontered a problem where he/she cannot boot into Recovery partition? I am using latest version of opencore on an AMD Ryzen build. Everything else is working perfectly with no issues whatsoever.

I have OSX Ctatalina 10.5.3 installed on an SSD with Recovery partition created by the installer on the same drive. 10.5.3 was an upgrade over originaly installed 10.5.2. I couldn't boot to recovery prior nor after the 10.5.3 update and update itself went without a hitch also upgarding Recovery partition to 10.5.3. I am using iMacPro 1,1 profile. Since I saw on the AMD OSX discord channel that there are quite a few people having the same issue but not getting any answers I thought in asking here. Appreciate any help I can get.

 

The message I get is:

Error allocating 0x7b40 pages at 0x000000005859000 alloc type 2 

Couldn't allocate runtime area.

 

Hardware configuration is (if it matters):

Asrock B450M

Ryzen 3500X

Radeon RX580

RAM 16GB 2600 MHz

Samsung Evo 850

 

Try what @telepati says. Insure you're using hfsplus.efi installed instead of vbox

 

Memoryallocation--> Here

 

 

17 minutes ago, telepati said:

Use memoryallocation.kext. Google it.

 

Hi @telepati I's memoryallocation.efi instead of kext. 

 

 

5 minutes ago, Slice said:

Sorry but google keep silence. There are many keywords like memory, allocation and kext on different sites.

 

Take a look to the link in my post @Slice

Edited January 31, 2020 by Matgen84

[syn909]

7 hours ago, nmano said:

Add System peripheral Detail   for X99 and X299 System

 

X299.zip

 

THANK YOU @nmano! This fixed my issue, Vmware not giving me any problems after resuming from sleep!

 

Are you able to boot from the recovery partition? I have HfsPlus.efi but I just get a black screen and it reboots back to the OC picker.

Edited January 31, 2020 by syn909

[mhaeuser]

@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.

[telepati]

2 minutes ago, 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.

Thanks to warning Post deleted.

Edited January 31, 2020 by telepati

[NoEnd]

7 hours ago, telepati said:

Check this post it can help you.

 

 

 

Thanks for the advice, however it didn't work. I tried the kernel patch before and now tested the kext (while disabling the patch) however no luck. I can boot successfully however Sleep/restart/shutdown will only fail into safe bios.

 

Thanks 

[dani77zg]

15 hours ago, 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.

Hi!

I am using Above 4G decoding.

I am using HFSPlus.efi.

MemoryAllocation.efi did nothing as did ProvideCustomSlide.

DevirtualiseMmio prevents system from booting and I had to shange back.

[mhaeuser]

@dani77zg Then yo have to put some effort into it and play around with the whitelist... dump the ranges via log and try out which causes the crash

[canyondust]

Now that TakeOffDelay has been implemented, is it possible to implement a logic where Timeout can be set to a value if ShowPicker is false, but is cancelled (reverts to 0/Off) if the ShowPicker hot key (opt/esc) is detected?

 

fantastic work BTW

[Andrey1970]

37 minutes ago, canyondust said:

Now that TakeOffDelay has been implemented, is it possible to implement a logic where Timeout can be set to a value if ShowPicker is false, but is cancelled (reverts to 0/Off) if the ShowPicker hot key (opt/esc) is detected?

 

fantastic work BTW 

Set Timeout 0

[telepati]

1 hour ago, Andrey1970 said:

Set Timeout 0

But Command+R hotkey doesn't work. I set to ShowPicker NO Timeout 0 when I boot press to Command+R its always boot in default drive.

[canyondust]

1 hour ago, telepati said:

But Command+R hotkey doesn't work. I set to ShowPicker NO Timeout 0 when I boot press to Command+R its always boot in default drive.

I think you might need the changes pushed by vit9696 last night, to add TakeOffDelay so you can set 1-2sec to allow OC to accept the hot keys with timeout=0?

 

(someone correct me if I’m wrong on this?)

[canyondust]

On 1/31/2020 at 5:05 AM, nmano said:

Add System peripheral Detail   for X99 and X299 System

X99.zip

X299.zip

Out of curiosity, (devs) how important is this step in configuration? I assumed this was entirely cosmetic, but these posts suggest otherwise?

[Andrey1970]

4 hours ago, telepati said:

But Command+R hotkey doesn't work. I set to ShowPicker NO Timeout 0 when I boot press to Command+R its always boot in default drive.

timeout=0 not guilty.

Value a timeout applied only for menu.

 

[Sniki]

On 11/11/2019 at 7:00 PM, jl4c said:

Not sure what you suggest. The purpose of this is to use ACPI hotpatch.

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).

[hardcorehenry]

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.

[Sniki]

13 hours ago, hardcorehenry said:

Check this repository.

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

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

[hardcorehenry]

49 minutes ago, Sniki said:

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

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

All credits go to @daliansky for his awesome repository

[telepati]

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 February 2, 2020 by telepati

[Sniki]

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

[Cloverkit]

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

 

Z77P-D3 OC EFI.zip

Config.plist

[Cloverkit]

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

 

Z77P-D3 OC EFI.zip

Config.plist

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

[1Ale1]

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. 

 

[vit9696]

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

 

@1Ale1, RequestBootVarFallback 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.

[Andrey1970]

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?

 

 

 

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 February 3, 2020 by Andrey1970

[eng_redaesm]

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 February 4, 2020 by eng_redaesm
add specs