hardcorehenry Posted March 3, 2021 Share Posted March 3, 2021 (edited) 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 1 Link to comment https://www.insanelymac.com/forum/topic/350754-opencore-general-discussion/page/264/#findComment-2752338 Share on other sites More sharing options...
deeveedee Posted March 4, 2021 Share Posted March 4, 2021 @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! 1 Link to comment https://www.insanelymac.com/forum/topic/350754-opencore-general-discussion/page/264/#findComment-2752378 Share on other sites More sharing options...
oSxFr33k Posted March 5, 2021 Share Posted March 5, 2021 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! Link to comment https://www.insanelymac.com/forum/topic/350754-opencore-general-discussion/page/264/#findComment-2752466 Share on other sites More sharing options...
tluck Posted March 5, 2021 Share Posted March 5, 2021 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. Link to comment https://www.insanelymac.com/forum/topic/350754-opencore-general-discussion/page/264/#findComment-2752467 Share on other sites More sharing options...
mhaeuser Posted March 5, 2021 Share Posted March 5, 2021 @tluck Try resetting NVRAM and then booting into a "broken" version *without* booting the old version (prior to the commit) Link to comment https://www.insanelymac.com/forum/topic/350754-opencore-general-discussion/page/264/#findComment-2752477 Share on other sites More sharing options...
tluck Posted March 5, 2021 Share Posted March 5, 2021 (edited) 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 Link to comment https://www.insanelymac.com/forum/topic/350754-opencore-general-discussion/page/264/#findComment-2752513 Share on other sites More sharing options...
macgirl Posted March 7, 2021 Share Posted March 7, 2021 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. Link to comment https://www.insanelymac.com/forum/topic/350754-opencore-general-discussion/page/264/#findComment-2752641 Share on other sites More sharing options...
Taruga Posted March 7, 2021 Share Posted March 7, 2021 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 Link to comment https://www.insanelymac.com/forum/topic/350754-opencore-general-discussion/page/264/#findComment-2752675 Share on other sites More sharing options...
Taruga Posted March 7, 2021 Share Posted March 7, 2021 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 Link to comment https://www.insanelymac.com/forum/topic/350754-opencore-general-discussion/page/264/#findComment-2752680 Share on other sites More sharing options...
deeveedee Posted March 8, 2021 Share Posted March 8, 2021 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? Link to comment https://www.insanelymac.com/forum/topic/350754-opencore-general-discussion/page/264/#findComment-2752740 Share on other sites More sharing options...
deeveedee Posted March 8, 2021 Share Posted March 8, 2021 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. 1 1 Link to comment https://www.insanelymac.com/forum/topic/350754-opencore-general-discussion/page/264/#findComment-2752748 Share on other sites More sharing options...
HenryV Posted March 8, 2021 Share Posted March 8, 2021 (edited) 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 1 Link to comment https://www.insanelymac.com/forum/topic/350754-opencore-general-discussion/page/264/#findComment-2752760 Share on other sites More sharing options...
Taruga Posted March 8, 2021 Share Posted March 8, 2021 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. 2 Link to comment https://www.insanelymac.com/forum/topic/350754-opencore-general-discussion/page/264/#findComment-2752761 Share on other sites More sharing options...
crusher Posted March 8, 2021 Share Posted March 8, 2021 I just used reset NVRAM and work normally Link to comment https://www.insanelymac.com/forum/topic/350754-opencore-general-discussion/page/264/#findComment-2752762 Share on other sites More sharing options...
deeveedee Posted March 9, 2021 Share Posted March 9, 2021 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! 1 Link to comment https://www.insanelymac.com/forum/topic/350754-opencore-general-discussion/page/264/#findComment-2752780 Share on other sites More sharing options...
davidm71 Posted March 10, 2021 Share Posted March 10, 2021 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 Link to comment https://www.insanelymac.com/forum/topic/350754-opencore-general-discussion/page/264/#findComment-2752844 Share on other sites More sharing options...
HenryV Posted March 15, 2021 Share Posted March 15, 2021 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: 1 Link to comment https://www.insanelymac.com/forum/topic/350754-opencore-general-discussion/page/264/#findComment-2753190 Share on other sites More sharing options...
Andrey1970 Posted March 16, 2021 Share Posted March 16, 2021 In most cases isn't required to disable SIP. Use 00000000. 3 Link to comment https://www.insanelymac.com/forum/topic/350754-opencore-general-discussion/page/264/#findComment-2753217 Share on other sites More sharing options...
Andrey1970 Posted March 16, 2021 Share Posted March 16, 2021 Bit 0x10 breaks system updates. 2 Link to comment https://www.insanelymac.com/forum/topic/350754-opencore-general-discussion/page/264/#findComment-2753221 Share on other sites More sharing options...
hardcorehenry Posted March 16, 2021 Share Posted March 16, 2021 With latest commits no more problems(for those who have them) with ACPI renames(_STA, _CRS, skip etc.), now it’s much easier. I needed to rework 14 renames, but surprisingly everything went well. 1 Link to comment https://www.insanelymac.com/forum/topic/350754-opencore-general-discussion/page/264/#findComment-2753225 Share on other sites More sharing options...
Andrey1970 Posted March 16, 2021 Share Posted March 16, 2021 27 minutes ago, Hervé said: Which bit do you mean by 0x10? CSR_ALLOW_APPLE_INTERNAL 2 Link to comment https://www.insanelymac.com/forum/topic/350754-opencore-general-discussion/page/264/#findComment-2753234 Share on other sites More sharing options...
iamprabhuantony Posted March 17, 2021 Share Posted March 17, 2021 0.6.8 nightly show this errors /Users/prabhuantonystudios/Downloads/OpenCorePkg-R0.6.8-DevBuild-03172021_015627\ 2/Utilities/ocvalidate/ocvalidate /Volumes/EFI/EFI/OC/config.plist OCS: Missing key Base, context <Patch>! OCS: Missing key BaseSkip, context <Patch>! OCS: Missing key Base, context <Patch>! OCS: Missing key BaseSkip, context <Patch>! OCS: Missing key Base, context <Patch>! OCS: Missing key BaseSkip, context <Patch>! OCS: Missing key Base, context <Patch>! OCS: Missing key BaseSkip, context <Patch>! OCS: Missing key Base, context <Patch>! OCS: Missing key BaseSkip, context <Patch>! OCS: Missing key Base, context <Patch>! OCS: Missing key BaseSkip, context <Patch>! OCS: Missing key Base, context <Patch>! OCS: Missing key BaseSkip, context <Patch>! OCS: Missing key Base, context <Patch>! OCS: Missing key BaseSkip, context <Patch>! OCS: Missing key Base, context <Patch>! OCS: Missing key BaseSkip, context <Patch>! Serialisation returns 18 errors! Completed validating /Volumes/EFI/EFI/OC/config.plist in 3 ms. Found 18 issues requiring attention. Link to comment https://www.insanelymac.com/forum/topic/350754-opencore-general-discussion/page/264/#findComment-2753279 Share on other sites More sharing options...
Avery B Posted March 17, 2021 Share Posted March 17, 2021 (edited) patching based off of a Base method/device was just added - that's where the new keys come from. Read the Differences.pdf, that usually gets updated for all the commits when needed Edited March 17, 2021 by 1Revenger1 3 Link to comment https://www.insanelymac.com/forum/topic/350754-opencore-general-discussion/page/264/#findComment-2753280 Share on other sites More sharing options...
iamprabhuantony Posted March 17, 2021 Share Posted March 17, 2021 34 minutes ago, 5T33Z0 said: @iamprabhuantony Open Sample.plist > ACPI > Patch > 0 Copy Base and BaseSkip Paste them in every of the 18 patches in your config. Thanks a Lot. prabhuantonystudios@Prabhus-iMac ~ % /Users/prabhuantonystudios/Downloads/OpenCorePkg-R0.6.8-DevBuild-03172021_015627/Utilities/ocvalidate/ocvalidate /Volumes/EFI/EFI/OC/config.plist Completed validating /Volumes/EFI/EFI/OC/config.plist in 4 ms. No issues found. 2 Link to comment https://www.insanelymac.com/forum/topic/350754-opencore-general-discussion/page/264/#findComment-2753295 Share on other sites More sharing options...
deeveedee Posted March 17, 2021 Share Posted March 17, 2021 When I switched from CLOVER to OC, I also switched from the CLOVER/Slice preferred Fix RTC (which sets RTC memory length = 0x02) to Acidanthera's rtcmemoryfixup.kext with a custom rtcfx_exclude range. I'm finding that with my rig, the required rtcfx_exclude range changes with a new BIOS update and/or a new macOS update - not exactly sure which factors cause the change). I'm thinking of abandoning rtcmemoryfixup.kext and switching back to a patched RTC with memory length = 0x02. Is anyone else running OC with a patched RTC (SSDT patch changing RTC memory length to 0x02) instead of using rtcmemoryfixup.kext and if so, how is that working for you? Link to comment https://www.insanelymac.com/forum/topic/350754-opencore-general-discussion/page/264/#findComment-2753296 Share on other sites More sharing options...
Recommended Posts