OpenCore General Discussion

[deeveedee]

Still running OC 0.6.6 and I started experiencing this again (OC text boot picker not visible and Apple Logo not visible during startup).  I'm not experiencing this any more after a couple of changes and I think that the solution ended up being to set Booter > Quirks > ProtectUefiServices = 1 (true) (was zero/false).  Does it make sense that changing this setting would resolve the strange startup behavior that I was observing with OC 0.6.6 (again, system would boot, but during startup, OC text boot picker was not displayed and Apple Logo was not visible during startup).

 

My rig (documented here) is CoffeeLake i7 / UHD630 Graphics.

Edited March 1, 2021 by tonyx86
Added true/false if that's easier for people to understand

[Matgen84]

26 minutes ago, tonyx86 said:

Still running OC 0.6.6 and I started experiencing this again (OC text boot picker not visible and Apple Logo not visible during startup).  I'm not experiencing this any more after a couple of changes and I think that the solution ended up being to set Booter > Quirks > ProtectUefiServices = 1 (was zero).  Does it make sense that changing this setting would resolve the strange startup behavior that I was observing with OC 0.6.6 (again, system would boot, but during startup, OC text boot picker was not displayed and Apple Logo was not visible during startup).

 

My rig (documented here) is CoffeeLake i7 / UHD630 Graphics.

 

The correct setting for ProtectUefiServices is false or true (not 0 or 1). I use it for my Z390 config. 

[deeveedee]

11 minutes ago, Matgen84 said:

 

The correct setting for ProtectUefiServices is false or true (not 0 or 1). I use it for my Z390 config. 

 

Thanks.  When using XCode to edit config.plist, bit values of 0 and 1 correspond to false and true respectively.  I've edited my original post if it makes it easier to understand.  Question remains the same.

 

EDIT: According to OC Sanity Checker, correct values are Yes and No

 

Spoiler

 

Edited March 1, 2021 by tonyx86
Added OC Sanity Checker screen shot

[Matgen84]

15 hours ago, tonyx86 said:

 

Thanks.  When using XCode to edit config.plist, bit values of 0 and 1 correspond to false and true respectively.  I've edited my original post if it makes it easier to understand.  Question remains the same.

 

EDIT: According to OC Sanity Checker, correct values are Yes and No

 

  Reveal hidden contents

 

 

For PlistEdit Pro, Yes for Boolean corresponding to True in sample-config.plist. I use PlistEDPlus (by @ic005k): there are no confusion with this app: directly True or False for Boolean. 

 

Spoiler

 

As PlisEdit Pro, Xcode show YES/NO for Boolean

 

Spoiler

 

[deeveedee]

@Matgen84 All good info.  Thank you.  For those who are confused about the meaning of 0/1, False/True, No/Yes, this is very helpful.

 

@Matgen84 Here's my XCode 12.4 configuration for ProtectUefiServices.  Hopefully we've thoroughly addressed the confusion over Yes/No, True/False and 1/0 so that someone knows the answer to my ProtectUefiServices question.

 

Spoiler

Edited March 2, 2021 by tonyx86
Added XCode Screenshot

[hardcorehenry]

On 3/2/2021 at 12:20 PM, tonyx86 said:

someone knows the answer to my ProtectUefiServices question.

 

Maybe this post clarifies if ProtectUefiServices quirk is applicable to your firmware.

Edited March 3, 2021 by hardcorehenry

[deeveedee]

@hardcorehenry Thank you for your post.  Looks like I will need to enable OC logging and look for the OCABC: Recovering trashed GetMemoryMap pointer message in the log to determine that setting's relevance to my build.  Thank you!

[oSxFr33k]

I know I asked this already but my post was clouded with a lot of text.  Is there a way to inject an EFI string in the OC config and if so how and where?  Thanks!

[tluck]

it took me a awhile to track downt where OC stopped working for me. but it is this commit: 

OpenCoreNvram: Never store 'opencore-version' as NV

•  
  Marvin Häuser
• 40cdc48c

     gRT->SetVariable (
      OC_VERSION_VARIABLE_NAME,
      &gOcVendorVariableGuid,

was
     Config->Nvram.WriteFlash ? OPEN_CORE_NVRAM_NV_ATTR : OPEN_CORE_NVRAM_ATTR,

proposed
      OPEN_CORE_NVRAM_ATTR,

      AsciiStrLen (Version),
      (VOID *) Version
      );

 

problem is that it seems I need to set WriteFlash = true, otherwise it doesnt work.

[mhaeuser]

@tluck Try resetting NVRAM and then booting into a "broken" version *without* booting the old version (prior to the commit)

[tluck]

16 hours ago, Download-Fritz said:

@tluck Try resetting NVRAM and then booting into a "broken" version *without* booting the old version (prior to the commit)

hmm i built the latest version and reset nvram. but unless i add this Config->Nvram.WriteFlash ? OPEN_CORE_NVRAM_NV_ATTR : OPEN_CORE_NVRAM_ATTR back into the code - boot just stops after loading kexts.

 

Edited March 6, 2021 by tluck

[macgirl]

Guys I got an old Gigabyte motherboard H55M that I cant make to shutdown or restart properly or make all the USB ports work with non HUB, it is running Big Sur, Originay I installed Catalina with Clover and shutdown/restart and USB ports were good but GUI was very sluggish, if I boot with Opencore sluggishness disappears but I cannot make it shutdown/restart or USB work properly

Then I upgraded to Big Sur so clover now doesn't boot properly
 

I researched several forums but sinces this is an old motherboard I cant find anything to make proper SSDTs to modify the behaviour

I found an old modified DSDT that makes the USB works fine but cannot boot windows with it because it shows an ACPI error but again Shutdown and Restart does not work properly

BTW, hello again.

[Taruga]

Not sure if I did something wrong, I updated Open Core from 0.6.5 to 0.6.7 but it looks like I'm still on 0.6.5 version.
Hackintool also says the Current Booted Version is 0.6.5
Is there any bug with 0.67 ?!

Open Core 0.6.7 ocvalidade has the following output:

Completed validating /Volumes/EFI/EFI/OC/config.plist in 1 ms. No issues found.

nvram 4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:opencore-version

4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:opencore-version REL-065-2021-01-04

 

[eSaF]

3 minutes ago, Taruga said:

Not sure if I did something wrong, I updated Open Core from 0.6.5 to 0.6.7 but it looks like I'm still on 0.6.5 version.
Hackintool also says the Current Booted Version is 0.6.5
Is there any bug with 0.67 ?!

Open Core 0.6.7 ocvalidade has the following output:

Completed validating /Volumes/EFI/EFI/OC/config.plist in 1 ms. No issues found.

nvram 4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:opencore-version

4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:opencore-version REL-065-2021-01-04

 

Reboot and clean NvRAM, see what the result is.

[Taruga]

Cleared NVRAM, rebooted and I have the same result. This is weird ... 

Just tested updating open core on another PC to 0.6.7 and I have the same result.

I don't understand what's happening....
 

 

MD5 is a match

[deeveedee]

On 3/7/2021 at 3:23 AM, macgirl said:

 

Guys I got an old Gigabyte motherboard H55M that I cant make to shutdown or restart properly or make all the USB ports work with non HUB, it is running Big Sur, Originay I installed Catalina with Clover and shutdown/restart and USB ports were good but GUI was very sluggish, if I boot with Opencore sluggishness disappears but I cannot make it shutdown/restart or USB work properly

Then I upgraded to Big Sur so clover now doesn't boot properly
 

I researched several forums but sinces this is an old motherboard I cant find anything to make proper SSDTs to modify the behaviour

I found an old modified DSDT that makes the USB works fine but cannot boot windows with it because it shows an ACPI error but again Shutdown and Restart does not work properly

BTW, hello again.

Can't tell much without your EFI (at least config.plist).  Have you enabled ACPI > Quirks > FadtEnableReset?

[deeveedee]

20 hours ago, Taruga said:

Cleared NVRAM, rebooted and I have the same result. This is weird ... 

Just tested updating open core on another PC to 0.6.7 and I have the same result.

I don't understand what's happening....

Hackintool 3.5.3 reports correct 0.6.7 version for me...

Spoiler

 

When I "upgrade" from one version of OC to the next, I completely clear my EFI, copy the new (in this case 0.6.7) EFI from github (both BOOT and OC) to my clean EFI and then replace config.plist, Kexts, ACPI.  Then I reboot, clear NVRAM and boot with my new OC.

 

Without seeing your EFI, I'd guess that you've accidentally mixed OC file versions in your EFI or you're not booting from the EFI that you think you are.

[HenryV]

Is anyone having a problem chainloading OpenCore.efi  0.6.5 or later from Grub2?

 

Up until 0.6.4 chainloading worked fine from the Grub.cfg but no boot list appears when updating to 0.6.5 or later.

 

using:

 

menuentry "Open Core"{
    insmod part_gpt
    # insmod chain
    search --no-floppy --set=root --fs-uuid xxxx-xxxx
    chainloader /EFI/OC/OpenCore.efi
}

 

Any specific pointers to resolve this?

Edited March 8, 2021 by HenryV
add info

[Taruga]

3 hours ago, tonyx86 said:

Without seeing your EFI, I'd guess that you've accidentally mixed OC file versions in your EFI or you're not booting from the EFI that you think you are.

I've just solved my issue and I figured out what I was doing wrong.

It was because I was clearing nvram with: sudo nvram -c
As soon as I used the OC ClearNvram.efi from the Tools, the problem went away

Now I see the correct version (also on Hackintool):
 

❯ nvram 4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:opencore-version

4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:opencore-version REL-067-2021-03-01

Thank you for your comment, It gave me the push I needed to try one more time.
All the EFI files were correct, I didn't change anything. 

[crusher]

I just used reset NVRAM and work normally 

[deeveedee]

8 hours ago, Taruga said:

I've just solved my issue and I figured out what I was doing wrong.

It was because I was clearing nvram with: sudo nvram -c
As soon as I used the OC ClearNvram.efi from the Tools, the problem went away

Now I see the correct version (also on Hackintool):
 

❯ nvram 4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:opencore-version

4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:opencore-version REL-067-2021-03-01

Thank you for your comment, It gave me the push I needed to try one more time.
All the EFI files were correct, I didn't change anything. 

 

You deserve all the credit for finding your error and correcting it - not me.  The best we can say about my post is that I guessed incorrectly and you found the solution anyway.  Way to persist without giving up!

[davidm71]

Hi guys,

 

Long time since last post. Have issue with black screen after switching from HDMI to DP on a Sapphire 5700 XT Nitro card. HDMI works beautifully.

 

On Catalina 10.15.4. Feel no urgency in upgrading to anything else as works great except for DP support.

 

Any help be appreciated.

 

PS: Running natively. No Whatevergreen or anything like that being loaded I don't think.

 

They exist in my efi kext folder but not referenced in config.plist so I don't suppose they are being loaded.

 

Thanks

[HenryV]

Thanks to 5T33Z0

 

This post solved the missing Big Sur updates issue:

 

EDIT: *According to Dortania's OpenCore install Guide, the csr-value for Big Sur is FF0F0000. But in my and a lot of other people's experiences in the german hackintosh-forum, this value doesn't work correctly, because you won't get any system updates if you use it. According to this discussion, 67080000 is the correct value for Big Sur:

[Andrey1970]

In most cases isn't required to disable SIP. Use 00000000.

[Andrey1970]

Bit 0x10 breaks system updates.