Erroruser Posted February 21, 2020 Share Posted February 21, 2020 (edited) 6 hours ago, telepati said: You must also update your config.plist. Many parametre places changed on v0.5.6. Update BOOT folder Update OpenCore.efi Update Drivers If you are using any Tools Update those too also update ethe opencore.efi Edited February 21, 2020 by Erroruser 1 1 Link to comment Share on other sites More sharing options...
nmano Posted February 21, 2020 Share Posted February 21, 2020 7 hours ago, Erroruser said: also update ethe opencore.efi 0.5.6 oc configuration requires vault but no vault provided Can you check my config Thanks. config.plist Link to comment Share on other sites More sharing options...
vandroiy2012 Posted February 21, 2020 Share Posted February 21, 2020 5 minutes ago, nmano said: 0.5.6 oc configuration requires vault but no vault provided Can you check my config Thanks. config.plist Read manual: VaultType: plist stringFailsafe: SecureDescription: Enables vaulting mechanism in OpenCore. Valid values: Optional — require nothing, no vault is enforced, insecure. Basic — require vault.plist file present in OC directory. This provides basic filesystem integrity verification and may protect from unintentional filesystem corruption. Secure — require vault.sig signature file for vault.plist in OC directory. This includes Basic integrity checking but also attempts to build a trusted bootchain. 2 Link to comment Share on other sites More sharing options...
nmano Posted February 21, 2020 Share Posted February 21, 2020 25 minutes ago, vandroiy2012 said: Read manual: VaultType: plist stringFailsafe: SecureDescription: Enables vaulting mechanism in OpenCore. Valid values: Optional — require nothing, no vault is enforced, insecure. Basic — require vault.plist file present in OC directory. This provides basic filesystem integrity verification and may protect from unintentional filesystem corruption. Secure — require vault.sig signature file for vault.plist in OC directory. This includes Basic integrity checking but also attempts to build a trusted bootchain. Thanks @vandroiy2012 Secure to Optional - Pass Link to comment Share on other sites More sharing options...
Flyinace2000 Posted February 21, 2020 Share Posted February 21, 2020 On 2/19/2020 at 4:38 PM, Flyinace2000 said: I'm running a GA-z87-UD5h Haswell machine. I've got it mostly working now on OpenCore except sleep. I've tried toggling ProtectCsmRegion to YES, but that works even less. Basically if my machine timeouts to sleep or manually sleeps it sometimes doesn't wake up and needs a hard reset (power button). config.plist william@Williams-iMac ~ % sudo pmset -g Password: System-wide power settings: Currently in use: standby 1 Sleep On Power Button 1 womp 0 autorestart 0 hibernatefile /var/vm/sleepimage powernap 1 networkoversleep 0 disksleep 0 standbydelayhigh 86400 sleep 30 autopoweroffdelay 28800 hibernatemode 0 autopoweroff 1 ttyskeepawake 1 displaysleep 15 highstandbythreshold 50 standbydelaylow 86400 william@Williams-iMac ~ % Any help with this? latest kernal panic is below. Found the machine booted to Windows (which is entry #1 in OpenCore) panic(cpu 6 caller 0xffffff7f9b9de306): NVRM[0/1:0:0]: Read Error 0x00070000: CFG 0x100410de 0x00100000 0x00000000, BAR0 0xf5000000 0xffffff8211aeb000 0x0f0040a1, D3, P0/4 Backtrace (CPU 6), Frame : Return Address 0xffffff92215e2ea0 : 0xffffff801ab3bb2b mach_kernel : _handle_debugger_trap + 0x47b 0xffffff92215e2ef0 : 0xffffff801ac734d5 mach_kernel : _kdp_i386_trap + 0x155 0xffffff92215e2f30 : 0xffffff801ac64f4e mach_kernel : _kernel_trap + 0x4ee 0xffffff92215e2f80 : 0xffffff801aae2a40 mach_kernel : _return_from_trap + 0xe0 0xffffff92215e2fa0 : 0xffffff801ab3b217 mach_kernel : _DebuggerTrapWithState + 0x17 0xffffff92215e30a0 : 0xffffff801ab3b5fb mach_kernel : _panic_trap_to_debugger + 0x21b 0xffffff92215e30f0 : 0xffffff801b2d2aa9 mach_kernel : _panic + 0x61 0xffffff92215e3160 : 0xffffff7f9b9de306 com.apple.nvidia.driver.NVDAResman : _osReadRegistryBinary + 0x470 0xffffff92215e31e0 : 0xffffff7f9baab11b com.apple.nvidia.driver.NVDAResman : _gpuExecRegOps + 0xd386 0xffffff92215e3240 : 0xffffff7f9dd15dea com.apple.nvidia.driver.NVDAGK100Hal : __ZN12NVDAGK100HAL5probeEP9IOServicePi + 0x1d880 0xffffff92215e3290 : 0xffffff7f9dd15d13 com.apple.nvidia.driver.NVDAGK100Hal : __ZN12NVDAGK100HAL5probeEP9IOServicePi + 0x1d7a9 0xffffff92215e32d0 : 0xffffff7f9b9c4e11 com.apple.nvidia.driver.NVDAResman : _rmGenerateSha256Gid + 0x72c5 0xffffff92215e3370 : 0xffffff7f9bac5280 com.apple.nvidia.driver.NVDAResman : _vpHalIfacesSetup_VGPUSTUB + 0x51cd 0xffffff92215e33d0 : 0xffffff7f9b9ad4b7 com.apple.nvidia.driver.NVDAResman : _nvErrorLog_va + 0x6c2d 0xffffff92215e3470 : 0xffffff7f9b9a5370 com.apple.nvidia.driver.NVDAResman : _rmFreeInternal + 0x12c 0xffffff92215e34d0 : 0xffffff7f9b9a53df com.apple.nvidia.driver.NVDAResman : _rmFreeInternal + 0x19b 0xffffff92215e3500 : 0xffffff7f9b9a2b72 com.apple.nvidia.driver.NVDAResman : _osReadRegistryString + 0x75f 0xffffff92215e35a0 : 0xffffff7f9b9e2b1c com.apple.nvidia.driver.NVDAResman : _insert_registration_func + 0x1308 0xffffff92215e3720 : 0xffffff7f9b9e358d com.apple.nvidia.driver.NVDAResman : _NvRmFree + 0x66 0xffffff92215e3810 : 0xffffff7f9be8898e com.apple.GeForce : __ZN8nvMemory14DestroySurfaceEP16__GLNVsurfaceRec + 0x70 0xffffff92215e3860 : 0xffffff7f9be569ab com.apple.GeForce : __ZN15nvBaseAllocator24DestroySingleEmptyBufferEP19__GLNVallocatorHeapP28__GLNVallocatorBufferListRech + 0xf3 0xffffff92215e3890 : 0xffffff7f9be580c2 com.apple.GeForce : __ZN15nvBaseAllocator4FreeEP21nvAllocatorAllocation + 0x56 0xffffff92215e38c0 : 0xffffff7f9be58d0c com.apple.GeForce : __ZN11nvAllocator11FreeVirtualEP21nvAllocatorAllocation + 0x4a 0xffffff92215e38e0 : 0xffffff7f9bead473 com.apple.GeForce : __ZN16nvVirtualAddress4freeEv + 0x3d 0xffffff92215e3900 : 0xffffff7f9be4e0a0 com.apple.GeForce : __ZN11nvMemoryMap21freeGPUVirtualAddressEv + 0x66 0xffffff92215e3920 : 0xffffff7f9bdbdf18 com.apple.iokit.IOAcceleratorFamily2 : __ZNK16IOAccelMemoryMap7releaseEv + 0x8e 0xffffff92215e3940 : 0xffffff7f9bda6218 com.apple.iokit.IOAcceleratorFamily2 : __ZN11IOAccelTask23prune_orphaned_mappingsEv + 0x6c 0xffffff92215e3980 : 0xffffff7f9bd713e5 com.apple.iokit.IOAcceleratorFamily2 : __ZN13IOAccelMemory19createMappingInTaskEP11IOAccelTaskj + 0x1bb 0xffffff92215e39c0 : 0xffffff7f9bea11fa com.apple.GeForce : __ZN11nvSysMemory19createMappingInTaskEP11IOAccelTaskj + 0x1a 0xffffff92215e39f0 : 0xffffff7f9bd949bb com.apple.iokit.IOAcceleratorFamily2 : __ZN16IOAccelResource23mapEv + 0x183 0xffffff92215e3a30 : 0xffffff7f9bd996fa com.apple.iokit.IOAcceleratorFamily2 : __ZN24IOAccelSharedUserClient212new_resourceEP22IOAccelNewResourceArgsP28IOAccelNewResourceReturnDatayPj + 0x904 0xffffff92215e3a80 : 0xffffff7f9bd9aee9 com.apple.iokit.IOAcceleratorFamily2 : __ZN24IOAccelSharedUserClient214s_new_resourceEPS_PvP25IOExternalMethodArguments + 0x97 0xffffff92215e3ac0 : 0xffffff801b26739b mach_kernel : __ZN12IOUserClient14externalMethodEjP25IOExternalMethodArgumentsP24IOExternalMethodDispatchP8OSObjectPv + 0x1db 0xffffff92215e3b10 : 0xffffff7f9bd9b0e2 com.apple.iokit.IOAcceleratorFamily2 : __ZN24IOAccelSharedUserClient214externalMethodEjP25IOExternalMethodArgumentsP24IOExternalMethodDispatchP8OSObjectPv + 0x80 0xffffff92215e3b60 : 0xffffff801b270443 mach_kernel : _is_io_connect_method + 0x223 0xffffff92215e3ca0 : 0xffffff801ac22d12 mach_kernel : _iokit_server_routine + 0x4e62 0xffffff92215e3db0 : 0xffffff801ab419d8 mach_kernel : _ipc_kobject_server + 0x238 0xffffff92215e3e10 : 0xffffff801ab18635 mach_kernel : _ipc_kmsg_send + 0x135 0xffffff92215e3e70 : 0xffffff801ab2f0e5 mach_kernel : _mach_msg_overwrite_trap + 0x2e5 0xffffff92215e3f00 : 0xffffff801ac4b575 mach_kernel : _mach_call_munger64 + 0x205 0xffffff92215e3fa0 : 0xffffff801aae3226 mach_kernel : _hndl_mach_scall64 + 0x16 Kernel Extensions in backtrace: com.apple.nvidia.driver.NVDAResman(14.0)[ECB33CB3-2FE3-3E99-A4E6-ED7C5DA6D543]@0xffffff7f9b971000->0xffffff7f9bc48fff dependency: com.apple.iokit.IOPCIFamily(2.9)[ADD485B5-3EF8-37C4-B3C5-F86326E497A4]@0xffffff7f9b52f000 dependency: com.apple.iokit.IONDRVSupport(569.4)[EACCC42A-9D18-383E-BF13-51910962371C]@0xffffff7f9b955000 dependency: com.apple.iokit.IOGraphicsFamily(569.4)[1F9B5D88-52DB-3A16-8373-4F608A3CB2D8]@0xffffff7f9b8f6000 dependency: com.apple.AppleGraphicsDeviceControl(4.7.2)[2F63196D-03C6-3E49-BE5D-574F4AADED1A]@0xffffff7f9b965000 com.apple.nvidia.driver.NVDAGK100Hal(14.0)[D9BD5415-852D-3F99-B5D9-9E4FD7CABEEC]@0xffffff7f9dcf7000->0xffffff7f9dea2fff dependency: com.apple.nvidia.driver.NVDAResman(14.0.0)[ECB33CB3-2FE3-3E99-A4E6-ED7C5DA6D543]@0xffffff7f9b971000 dependency: com.apple.iokit.IOPCIFamily(2.9)[ADD485B5-3EF8-37C4-B3C5-F86326E497A4]@0xffffff7f9b52f000 com.apple.iokit.IOAcceleratorFamily2(438.3.1)[66992525-3204-3CB0-8F03-4B70031B1CF2]@0xffffff7f9bd6f000->0xffffff7f9be32fff dependency: com.apple.driver.AppleMobileFileIntegrity(1.0.5)[A243D030-19AC-30AA-AC70-6C786DF9E6CE]@0xffffff7f9bd45000 dependency: com.apple.iokit.IOPCIFamily(2.9)[ADD485B5-3EF8-37C4-B3C5-F86326E497A4]@0xffffff7f9b52f000 dependency: com.apple.iokit.IOSurface(269.6)[42377B3B-D14A-368E-820F-07E7EA666198]@0xffffff7f9b8c5000 dependency: com.apple.iokit.IOGraphicsFamily(569.4)[1F9B5D88-52DB-3A16-8373-4F608A3CB2D8]@0xffffff7f9b8f6000 dependency: com.apple.iokit.IOReportFamily(47)[988360A2-2E10-3014-A119-BE81BC045A10]@0xffffff7f9bd68000 com.apple.GeForce(14.0)[4CC8D53A-2090-3437-99E7-AA7D85AB765C]@0xffffff7f9be47000->0xffffff7f9bf23fff dependency: com.apple.iokit.IOPCIFamily(2.9)[ADD485B5-3EF8-37C4-B3C5-F86326E497A4]@0xffffff7f9b52f000 dependency: com.apple.iokit.IOSurface(269.6)[42377B3B-D14A-368E-820F-07E7EA666198]@0xffffff7f9b8c5000 dependency: com.apple.iokit.IONDRVSupport(569.4)[EACCC42A-9D18-383E-BF13-51910962371C]@0xffffff7f9b955000 dependency: com.apple.nvidia.driver.NVDAResman(14.0.0)[ECB33CB3-2FE3-3E99-A4E6-ED7C5DA6D543]@0xffffff7f9b971000 dependency: com.apple.iokit.IOGraphicsFamily(569.4)[1F9B5D88-52DB-3A16-8373-4F608A3CB2D8]@0xffffff7f9b8f6000 dependency: com.apple.iokit.IOAcceleratorFamily2(438.3.1)[66992525-3204-3CB0-8F03-4B70031B1CF2]@0xffffff7f9bd6f000 BSD process name corresponding to current thread: WindowServer Boot args: keepsyms=1 Link to comment Share on other sites More sharing options...
Alpha22 Posted February 22, 2020 Share Posted February 22, 2020 (edited) Hi everyone, some advice thanks Quote OCS: No schema for MatchKernel at 4 index! 1.EFIschema for MatchKernel at 4 index! 2.macOS Catalina MatchKernel at 4 index! 3.Recovery 10.5.3 (dmg)nel at 4 index! 4. Reset NVRAMor MatchKernel at 4 index! OCS: No schema for MatchKernel at 4 index! Choose boot entry: BudlePatch at 0 index! OCS: No schema for Enable at 2 index! OCS: No schema for MatchKernel at 4 index! OCS: No match for LegacySchema at 3 index! Asus Z97 config.plist.zip Edited February 22, 2020 by Alpha22 Link to comment Share on other sites More sharing options...
bayard Posted February 22, 2020 Share Posted February 22, 2020 My opencore config works well on an iMac 2011, but when i try to load HiiDatabase.efi the boot process stop before loading the bootpicker. the last line in log file is OC: Driver HiiDatabase.efi at 2 is being loaded... and nothing happen after. any ideas? opencore-2020-02-22-205701.txt config.plist.zip Link to comment Share on other sites More sharing options...
Dazdaz19 Posted February 22, 2020 Share Posted February 22, 2020 Hi guys, I'm having a little trouble booting into mac OS for the first time. I followed snazzy labs video guide and used the opencore vanilla troubleshooting guide he linked in the description for any problems I'm encountering, however I'm now stuck at the opencore boot menu and when I choose macOS base system (external) I get "this verion of mac OS X is not supported on this platform! Reason: Mac-F221BEC8" I am using the same system in his video. I'm new to this so I've attached my config.plist below for anyone to help Thanks! config.plist Link to comment Share on other sites More sharing options...
droples Posted February 23, 2020 Share Posted February 23, 2020 7 hours ago, bayard said: My opencore config works well on an iMac 2011, but when i try to load HiiDatabase.efi the boot process stop before loading the bootpicker. the last line in log file is OC: Driver HiiDatabase.efi at 2 is being loaded... and nothing happen after. any ideas? opencore-2020-02-22-205701.txt config.plist.zip Try to boot with this driver. HiiDatabase.efi.zip Link to comment Share on other sites More sharing options...
Alpha22 Posted February 23, 2020 Share Posted February 23, 2020 Made some corrections, but I have this Quote OC: Your config has improper for kext info Halting on critical error Advice config.plist.zip opencore-2020-02-23-071705.txt Link to comment Share on other sites More sharing options...
atsankov Posted February 23, 2020 Share Posted February 23, 2020 Hi for everyone. Please help me with what exactly this hash means? Quote XhcDriverBindingStart: failed to enable 64-bit DMA on 64-bit capable controller @ B5E65C98 (Unsupported) Halting on critical error opencore-2020-02-23-113652.txt Link to comment Share on other sites More sharing options...
Mike Ranger Posted February 23, 2020 Share Posted February 23, 2020 I have something I cannot explain regarding text-size in the boot-picker. With that current builds, output config have changed. For some reason, the text size in the boot-picker is much larger (seems about 2x original size?). In some previous build, there was also a zoom but that was taken out again. With that larger text, it almost looks like resolution is not right. Can anyone confirm that?.... Regards, Mike Link to comment Share on other sites More sharing options...
vit9696 Posted February 23, 2020 Share Posted February 23, 2020 @btwise, please do refrain from stating your personal opinion as the development team opinion or as common sense. Anyone using tools like "OpenCore Configurator" or similar will be permanently excommunicated by the development team from any kind of support or bug submission upon first notice. 5 Link to comment Share on other sites More sharing options...
Nanorise Posted February 23, 2020 Share Posted February 23, 2020 (edited) hey, I have no audio on Windows If i boot to it through OpenCore High Definition Audio Controller has a yellow ! on it in Device manager, This device cannot find enough free resources that it can use. (Code 12) Adding my EFIusing SMBIOS iMac 19,1 When trying to install latest BootCamp through brigaider I get an error, screenshot below. Thanks for any help. OC.zip Edited February 23, 2020 by Nanorise Link to comment Share on other sites More sharing options...
Nanorise Posted February 23, 2020 Share Posted February 23, 2020 (edited) Quick Update, removing my custom DSDT fixed the Audio issue, I had it since CLOVER days. (Still can't install BootCamp same issue) Is a DSDT really necessary with OpenCore? Edited February 23, 2020 by Nanorise Link to comment Share on other sites More sharing options...
mhkmichaell Posted February 23, 2020 Share Posted February 23, 2020 If anyone wanted a working EFI for Probook 6470b. For me work better than with clover. More responsive. EFI-MHK.zip 1 Link to comment Share on other sites More sharing options...
Erroruser Posted February 23, 2020 Share Posted February 23, 2020 2 hours ago, Nanorise said: Quick Update, removing my custom DSDT fixed the Audio issue, I had it since CLOVER days. (Still can't install BootCamp same issue) Is a DSDT really necessary with OpenCore? DSDT is not really needed but to use a DSDT you have to repatch it as ssdt are better off to be used no need for re patching Link to comment Share on other sites More sharing options...
atsankov Posted February 23, 2020 Share Posted February 23, 2020 If anyone have working EFI for Probook 650 G1 to shear?Sent from my iPhone using Tapatalk Link to comment Share on other sites More sharing options...
Andres ZeroCross Posted February 23, 2020 Share Posted February 23, 2020 IMG_4087.MOV Nice GUI,, Latest Officially OpenCore 0.5.6 with NdkBootPicker.efi Link to comment Share on other sites More sharing options...
Mike Ranger Posted February 23, 2020 Share Posted February 23, 2020 (edited) 5 hours ago, Mike Ranger said: I have something I cannot explain regarding text-size in the boot-picker. With that current builds, output config have changed. For some reason, the text size in the boot-picker is much larger (seems about 2x original size?). In some previous build, there was also a zoom but that was taken out again. With that larger text, it almost looks like resolution is not right. Can anyone confirm that?.... Regards, Mike The key seems UIScale.... changed it to 01 and Text is small again. Edited February 23, 2020 by Mike Ranger Link to comment Share on other sites More sharing options...
bayard Posted February 23, 2020 Share Posted February 23, 2020 16 hours ago, droples said: Try to boot with this driver. HiiDatabase.efi.zip Same Behavior. Boot stops loading HiiDatabase.efi. opencore-2020-02-23-213047.txt Link to comment Share on other sites More sharing options...
MacNB Posted February 23, 2020 Share Posted February 23, 2020 12 minutes ago, bayard said: Same Behavior. Boot stops loading HiiDatabase.efi. opencore-2020-02-23-213047.txt Why do you need/want HiiDatabase.efi ??? Link to comment Share on other sites More sharing options...
bayard Posted February 23, 2020 Share Posted February 23, 2020 4 minutes ago, MacNB said: Why do you need/want HiiDatabase.efi ??? I wanted to try loading HiiDatabase.efi alone to see if it can loads on my iMac Because it's a dependency of NdkBootPicker.efi and NdkBootPicker.efi make boot process stop before reaching bootpicker. It seems that is related to HiiDatabase.efi not loading on my iMac 2011. Other than that, OpenCore works great without HiiDatabase.efi. Link to comment Share on other sites More sharing options...
droples Posted February 24, 2020 Share Posted February 24, 2020 4 hours ago, bayard said: I wanted to try loading HiiDatabase.efi alone to see if it can loads on my iMac Because it's a dependency of NdkBootPicker.efi and NdkBootPicker.efi make boot process stop before reaching bootpicker. It seems that is related to HiiDatabase.efi not loading on my iMac 2011. Other than that, OpenCore works great without HiiDatabase.efi. If you use fork OC then ask questions in the corresponding topic. Link to comment Share on other sites More sharing options...
Andres ZeroCross Posted February 24, 2020 Share Posted February 24, 2020 1 hour ago, droples said: If you use fork OC then ask questions in the corresponding topic. What???? "NdkBootPicker.efi" is driver for OpenCore GUI. It's not about "Fork OC" or not. Yes, NDK make Fork of OC but it's different story, we talk about "NdkBootPicker.efi (GUI Driver for OC)" not about OpenCore itself Link to comment Share on other sites More sharing options...
Recommended Posts