justin Posted July 29, 2019 Share Posted July 29, 2019 2 minutes ago, obus said: Can't boot into recovery partition "Recovery 10.14.6 (dmg). The funny thing is that if I boot from my "Backup" disk I get straight into the Recovery environment. ScanPolicy set to 0. Last version OC build compiled from scratch. Nothing in the Configuration.pdf about recovery partition more than chapter 11.2.3 "What is the simplest way to install macOS?". Glad for help! 2 minutes ago, obus said: Use HFSPlus.efi instead of vboxHFS.efi and set AvoidHighAlloc = YES 1 Link to comment https://www.insanelymac.com/forum/topic/350754-opencore-general-discussion/page/41/#findComment-2683329 Share on other sites More sharing options...
Guest Posted July 29, 2019 Share Posted July 29, 2019 (edited) @all Some of you are using in his rig 2 nvme driver on m2 slot with an Asus WS Sage 10G? With a minimal config.plist and no Acpi patch I have only a regular boot on first boot or if I start clearing nvram after first working boot If I do not clear system reboot itself before login or about 10 second after. In this 10 second I can't see untitled (nvme windows icon) icon and system reboots After reboot I have this apple report: panic(cpu 0 caller 0xffffff7f941a913e): nvme: "Fatal error occurred. CSTS=0x3 . FW Revision=2B6QCXP7\n"@/BuildRoot/Library/Caches/com.apple.xbs/Sources/IONVMeFamily/IONVMeFamily-356.71.1/ Using debug version does not help because no particular debug is shown Anyone? Edited July 29, 2019 by Guest Link to comment https://www.insanelymac.com/forum/topic/350754-opencore-general-discussion/page/41/#findComment-2683333 Share on other sites More sharing options...
obus Posted July 29, 2019 Share Posted July 29, 2019 (edited) Hi @justin Sorry but that doesn't work. If I use HFSPlus and setting AvoidHighAlloc to YES doesn't change anything more than that my Backup disk disappears from boot menu. config.plist Edited July 29, 2019 by obus Link to comment https://www.insanelymac.com/forum/topic/350754-opencore-general-discussion/page/41/#findComment-2683334 Share on other sites More sharing options...
justin Posted July 29, 2019 Share Posted July 29, 2019 34 minutes ago, obus said: Hi @justin Sorry but that doesn't work. If I use HFSPlus and setting AvoidHighAlloc to YES doesn't change anything more than that my Backup disk disappears from boot menu. config.plist then set AvoidHighAlloc = NO. i don't see HFSPlus.efi in your config.plist Link to comment https://www.insanelymac.com/forum/topic/350754-opencore-general-discussion/page/41/#findComment-2683338 Share on other sites More sharing options...
obus Posted July 29, 2019 Share Posted July 29, 2019 11 minutes ago, justin said: then set AvoidHighAlloc = NO. i don't see HFSPlus.efi in your config.plist I reverted back to vboxHFS.efi when it didn't work. Tested again with HFSPlus.efi and AvoidHighAlloc to NO and everything is working fine. Thank's for your help. Link to comment https://www.insanelymac.com/forum/topic/350754-opencore-general-discussion/page/41/#findComment-2683341 Share on other sites More sharing options...
justin Posted July 29, 2019 Share Posted July 29, 2019 2 minutes ago, obus said: I reverted back to vboxHFS.efi when it didn't work. Tested again with HFSPlus.efi and AvoidHighAlloc to NO and everything is working fine. Thank's for your help. This is because vboxHFS.efi sometimes is extremely slow, if you wait for few minutes it will finally boot your recovery. HFSPlus.efi is much faster. AvoidHighAlloc to Yes could also fix recovery boot failure on some motherboard, that’s why i suggested both, but it seems you don’t need this option for your motherboard. See vboxHFS.efi issue here: https://github.com/acidanthera/bugtracker/issues/399 Link to comment https://www.insanelymac.com/forum/topic/350754-opencore-general-discussion/page/41/#findComment-2683342 Share on other sites More sharing options...
obus Posted July 29, 2019 Share Posted July 29, 2019 9 minutes ago, justin said: This is because vboxHFS.efi sometimes is extremely slow, if you wait for few minutes it will finally boot your recovery. HFSPlus.efi is much faster. AvoidHighAlloc to Yes could also fix recovery boot failure on some motherboard, that’s why i suggested both, but it seems you don’t need this option for your motherboard. See vboxHFS.efi issue here: https://github.com/acidanthera/bugtracker/issues/399 Is there a "dedicated" HFSPlus.efi driver for OC or can I use the one I used in Clover without issue? Link to comment https://www.insanelymac.com/forum/topic/350754-opencore-general-discussion/page/41/#findComment-2683345 Share on other sites More sharing options...
justin Posted July 29, 2019 Share Posted July 29, 2019 2 hours ago, Enrize said: Hmm, but it doesn't work. I've set it to =true and i still see those messages... This brings another question: what are valid Bool options? Can we use YES, yes, true, TRUE for positive bool and NO, no, false, FALSE for negative bool? No such mentions in docs. @vit9696 @Download-Fritz 3 minutes ago, obus said: Is there a "dedicated" HFSPlus.efi driver for OC or can I use the one I used in Clover without issue? The HFSPlus.efi is from Apple, there is one and only one, just like apfs.efi. Link to comment https://www.insanelymac.com/forum/topic/350754-opencore-general-discussion/page/41/#findComment-2683346 Share on other sites More sharing options...
vandroiy2012 Posted July 29, 2019 Share Posted July 29, 2019 3 minutes ago, justin said: This brings another question: what are valid Bool options? Can we use YES, yes, true, TRUE for positive bool and NO, no, false, FALSE for negative bool? No such mentions in docs. All specs are discribed in manual. Read carefully 1.2 Generic terms and use approved plist editors. Link to comment https://www.insanelymac.com/forum/topic/350754-opencore-general-discussion/page/41/#findComment-2683350 Share on other sites More sharing options...
justin Posted July 29, 2019 Share Posted July 29, 2019 4 minutes ago, vandroiy2012 said: All specs are discribed in manual. Read carefully 1.2 Generic terms and use approved plist editors. Thanks, Vscode shows true/false while Plistedit pro shows YES/NO, i get it, it depends on "approved editors". Link to comment https://www.insanelymac.com/forum/topic/350754-opencore-general-discussion/page/41/#findComment-2683352 Share on other sites More sharing options...
mhaeuser Posted July 29, 2019 Share Posted July 29, 2019 @justin That is just UI cosmetics, important is the boolean type is used in file, which only allows "true" and "false". I think Xcode displays them as "YES" and "NO" as well, but they all save to the same format (hopefully). Funny stuff like "true"/"false"/"YES"/"NO" as *strings* are not supported. 1 1 Link to comment https://www.insanelymac.com/forum/topic/350754-opencore-general-discussion/page/41/#findComment-2683355 Share on other sites More sharing options...
Guest Posted July 29, 2019 Share Posted July 29, 2019 (edited) 2 hours ago, fabiosun said: @all Some of you are using in his rig 2 nvme driver on m2 slot with an Asus WS Sage 10G? With a minimal config.plist and no Acpi patch I have only a regular boot on first boot or if I start clearing nvram after first working boot If I do not clear system reboot itself before login or about 10 second after. In this 10 second I can't see untitled (nvme windows icon) icon and system reboots After reboot I have this apple report: panic(cpu 0 caller 0xffffff7f941a913e): nvme: "Fatal error occurred. CSTS=0x3 . FW Revision=2B6QCXP7\n"@/BuildRoot/Library/Caches/com.apple.xbs/Sources/IONVMeFamily/IONVMeFamily-356.71.1/ Using debug version does not help because no particular debug is shown Anyone? @devs attached opecore debug log By the way on M2 connector there is a 960 pro drive with Windows 10 Os in ntfs I have no problem with other boot loaders but I would like to understand if I can have again OC as my daily preferred boot loader TY opencore.log.zip added some infos Using Asus F8 key to choose oSX drive in bios drives scan (with OC EFI) system starts well always Edited July 29, 2019 by Guest added others info Link to comment https://www.insanelymac.com/forum/topic/350754-opencore-general-discussion/page/41/#findComment-2683369 Share on other sites More sharing options...
MacPato Posted July 29, 2019 Share Posted July 29, 2019 (edited) 4 hours ago, justin said: Yes. see attached example. bootercfg log=0 debug=0 ConsoleControl=Yes Under UEFI/Protocols will disable those message's along with IgnoreTextInGraphics=YES Under UEFI/Quirks Edited July 29, 2019 by MacFriedIntel Link to comment https://www.insanelymac.com/forum/topic/350754-opencore-general-discussion/page/41/#findComment-2683375 Share on other sites More sharing options...
Enrize Posted July 29, 2019 Share Posted July 29, 2019 I can't get emulated NVRAM to work...I run "sudo defaults write...etc..." LogoutHook.command as described but i can't see generated nvram.plist anywhere, am i doing something wrong? Link to comment https://www.insanelymac.com/forum/topic/350754-opencore-general-discussion/page/41/#findComment-2683377 Share on other sites More sharing options...
dracoflar Posted July 29, 2019 Share Posted July 29, 2019 @Enrize For emulated NVRAM, make sure you run: sudo defaults write com.apple.loginwindow LogoutHook /Users/(your username)/LogoutHook/LogoutHook.command And when you restart, the nvram.plist will be added to your EFI. No extra work is necessary besides having LegacyEnable: set to YES and NVRAM variables set in LegacySchema. For more info, check this page: https://khronokernel-2.gitbook.io/opencore-vanilla-desktop-guide/post-install/nvram Link to comment https://www.insanelymac.com/forum/topic/350754-opencore-general-discussion/page/41/#findComment-2683379 Share on other sites More sharing options...
Enrize Posted July 29, 2019 Share Posted July 29, 2019 Hmm, i did exactly like you said but there is still no nvram.plist in my EFI folder...any ideas what might prevent it to work? I use 0.4 build. Link to comment https://www.insanelymac.com/forum/topic/350754-opencore-general-discussion/page/41/#findComment-2683383 Share on other sites More sharing options...
Erroruser Posted July 29, 2019 Share Posted July 29, 2019 1 minute ago, Enrize said: Hmm, i did exactly like you said but there is still no nvram.plist in my EFI folder...any ideas what might prevent it to work? I use 0.4 build. if you happen to have a 390 board then that will cause an issue with the NVRAM not working Link to comment https://www.insanelymac.com/forum/topic/350754-opencore-general-discussion/page/41/#findComment-2683384 Share on other sites More sharing options...
Enrize Posted July 29, 2019 Share Posted July 29, 2019 (edited) I have B360, but that’s why we need emulated NVRAM, is it not? Edited July 29, 2019 by Enrize Link to comment https://www.insanelymac.com/forum/topic/350754-opencore-general-discussion/page/41/#findComment-2683385 Share on other sites More sharing options...
MacPato Posted July 29, 2019 Share Posted July 29, 2019 2 minutes ago, Enrize said: Hmm, i did exactly like you said but there is still no nvram.plist in my EFI folder...any ideas what might prevent it to work? I use 0.4 build. I have B360, but that’s why we need emulated NVRAM, is it not? Goodluck Gigabyte Aurous Z390, Asus Z390 and so many others have this issue and still can't get it to work. Link to comment https://www.insanelymac.com/forum/topic/350754-opencore-general-discussion/page/41/#findComment-2683386 Share on other sites More sharing options...
justin Posted July 29, 2019 Share Posted July 29, 2019 (edited) 1 hour ago, Enrize said: Hmm, i did exactly like you said but there is still no nvram.plist in my EFI folder...any ideas what might prevent it to work? I use 0.4 build. Oh... my. Please DO NOT say these fuzzy words when you’re reporting something. No body know what you’ve actually done. Did you copy the LogoutHook folder to your HOME dir? Did you use Tab on your keyboard to fill the path while trying to run the ‘sudo defaults write’ command? Here are the steps to debug your issue: 1. Run ‘sudo defaults read com.apple.loginwindow LogoutHook’ 2. You will see the path of LogoutHook.command, does the path exist? 3.You can always dry run the command like this in your Terminal.app first: ~/LogoutHook/LogoutHook.command, did you see any error? Did you make sure it is executable by running chmod +x LogoutHook.command? If no error, you should be able to see some generated files, including nvram.plist (but not in EFI, why not in EFI? Because in this case the command is run by a user, a user is not able to mount EFI with out sudo command, but it is enough to test this command to see if it generates nvram.plist correctly. ) if you see it, you can them run the command as mentioned in README( in this case, the command will be tun by macOS hook, and it is able to mount your EFI partition) Finally, please always provide screenshots. Edited July 29, 2019 by justin Link to comment https://www.insanelymac.com/forum/topic/350754-opencore-general-discussion/page/41/#findComment-2683396 Share on other sites More sharing options...
Enrize Posted July 29, 2019 Share Posted July 29, 2019 (edited) Ok, thanks for help, ill try to debug it. Edited July 29, 2019 by Enrize Link to comment https://www.insanelymac.com/forum/topic/350754-opencore-general-discussion/page/41/#findComment-2683397 Share on other sites More sharing options...
justin Posted July 29, 2019 Share Posted July 29, 2019 LogoutHook has nothing to do with Emulated NVRAM, if you look inside into the code, the only thing this command does is to save your custom nvram items to nvram.plist, so opencore can restore your custom nvram items next boot. For Emulated NVRAM, you need VariableRuntimeDxe.efi compiled from audk. Please search this thread for how to do that (my post) 1 Link to comment https://www.insanelymac.com/forum/topic/350754-opencore-general-discussion/page/41/#findComment-2683400 Share on other sites More sharing options...
Slice Posted July 30, 2019 Share Posted July 30, 2019 10 hours ago, justin said: This is because vboxHFS.efi sometimes is extremely slow, if you wait for few minutes it will finally boot your recovery. HFSPlus.efi is much faster. AvoidHighAlloc to Yes could also fix recovery boot failure on some motherboard, that’s why i suggested both, but it seems you don’t need this option for your motherboard. See vboxHFS.efi issue here: https://github.com/acidanthera/bugtracker/issues/399 The issue closed as not a bug. Link to comment https://www.insanelymac.com/forum/topic/350754-opencore-general-discussion/page/41/#findComment-2683413 Share on other sites More sharing options...
Enrize Posted July 30, 2019 Share Posted July 30, 2019 1. This is where my LogoutHook folder located. 2. This is what i typed in the Terminal to install it. 3. This is what i've got to debug. Link to comment https://www.insanelymac.com/forum/topic/350754-opencore-general-discussion/page/41/#findComment-2683433 Share on other sites More sharing options...
cecekpawon Posted July 30, 2019 Share Posted July 30, 2019 Im successfully adding a project page for my forked OpenCore project. Hope ppl can start to embed the direct link(s) from pdf doc with this way. Ex: https://cecekpawon.github.io/OpenCorePkg/Docs/Configuration.pdf#section.11 1 Link to comment https://www.insanelymac.com/forum/topic/350754-opencore-general-discussion/page/41/#findComment-2683447 Share on other sites More sharing options...
Recommended Posts