OpenCore General Discussion

Tiem · February 18, 2020

19 minutes ago, telepati said:

Failed to parse real field of type 1

It means you have a problem with an entry in your config file. Either it's in the wrong place, or has an invalid field.

6 hours ago, Logician said:

Thanks, that worked. Used the "CleanNvram.efi" tool to do it.

NP. OC does support proper Apple shortcuts for cleaning it (OPT + CMD + P + R). Another way is using Hackintool (NVRAM tab). Yet another way is using Terminal (nvram -c for a total wipe or you can use nvram -d x and delete specific entries, where 'x' is the specific variable).

Andrey1970 · February 18, 2020

1 hour ago, telepati said:

is there any timeout option for error seeing? For example, I am getting this error 'Failed to parse real field of type 1' before the boot picker, but it is passing extremely fast there is no time to read.

I set up this way but still fast cant read anything;

Under Debug;

DisableWatchDog YES

DisplayDelay 100

But I am not sure these are the correct option for my needs.

100 microseconds are very small time.

Slice · February 18, 2020

8 hours ago, telepati said:

You are right and that's why I chose Xcode for editing first in place but lately, when I use Xcode it starts to convert <integer> to <real> and giving this error while boot "Failed to parse real field of type 1". I create a new config.plist and still giving the same error. And I don't know how to fix this problem on Xcode. But I create the same config files with the same settings on ProperTree "Failed to parse real field of type 1" error gone. Why Xcode doing that I don't get it?

5 hours ago, Erroruser said:

xcode is fine yes but there has been an issue with saving in the ESP a few others have encountered this issue as well so we found that plist editor pro a better option

3 hours ago, bronxteck said:

try saving a DATA entry with latest Xcode. it will not allow you to save and sometimes removes that part of the code tree. a simple edit like changing your layout id becomes an issue.

Really? All you tell about Catalina? Or there are cases of initially bad plists?

I worked with Xcode since v2.4 and never encountered such problems.

telepati · February 18, 2020

27 minutes ago, Andrey1970 said:

100 microseconds are very small time.

DisplayDelay is the correct option then. Increase the value will fulfill my needs. Thank you, Andrey.

Tiem · February 18, 2020

48 minutes ago, Slice said:

Really? All you tell about Catalina? Or there are cases of initially bad plists?

I worked with Xcode since v2.4 and never encountered such problems.

They are talking about the way Xcode handles some fields (like the data field).

Xcode:

Plist Editor Pro:

Pretty trivial to change the value on PED. Not so much in Xcode. So yeah, for the majority of people, PED is a much better way to handle Hack plists. Not like they are anything special (binary plists). Just a basic text file. Notepad works just as well and you can use Hackintool to convert between Hex, Binary, etc.

telepati · February 18, 2020

2 hours ago, Slice said:

Really? All you tell about Catalina? Or there are cases of initially bad plists?

I worked with Xcode since v2.4 and never encountered such problems.

Yes really. Catalina and latest Xcode. It is not a bad plists problem. Cause I test it in multiple ways. Xcode eventually at some point converts <integer></integer> to as a <real></real>

1 hour ago, Tiem said:

They are talking about the way Xcode handles some fields (like the data field).

Xcode:

Plist Editor Pro:

Pretty trivial to change the value on PED. Not so much in Xcode. So yeah, for the majority of people, PED is a much better way to handle Hack plists. Not like they are anything special (binary plists). Just a basic text file. Notepad works just as well and you can use Hackintool to convert between Hex, Binary, etc.

I am not talking about that.

mhaeuser · February 18, 2020

18 minutes ago, telepati said:

Yes really. Catalina and latest Xcode. It is not a bad plists problem. Cause I test it in multiple ways. Xcode eventually at some point converts <integer></integer> to as a <real></real>

You probably just accidentially type or copy a period/dot

Erroruser · February 19, 2020

1 hour ago, Download-Fritz said:

You probably just accidentially type or copy a period/dot

4 hours ago, Slice said:

Really? All you tell about Catalina? Or there are cases of initially bad plists?

I worked with Xcode since v2.4 and never encountered such problems.

i made one lil change for boot arg an wouldnt save had to drag out the config to save then put back so i found plist editor pro the best to use never had any issues after that

Tiem · February 19, 2020

TFW the second your system reboots you realize you forgot to run vault

grimacing-face_1f62c.png.c9d6b62231b04d2230073e4ad22952e1.png

Slice · February 19, 2020

12 hours ago, Tiem said:

They are talking about the way Xcode handles some fields (like the data field).

Xcode:

Plist Editor Pro:

Pretty trivial to change the value on PED. Not so much in Xcode. So yeah, for the majority of people, PED is a much better way to handle Hack plists. Not like they are anything special (binary plists). Just a basic text file. Notepad works just as well and you can use Hackintool to convert between Hex, Binary, etc.

Data 0300983E is not the same as 0x0300983E because of endianness. It is 0x3E980003.

Sure you use right value.

Tiem · February 19, 2020

1 hour ago, Slice said:

Data 0300983E is not the same as 0x0300983E because of endianness. It is 0x3E980003.

Sure you use right value.

Same plist friend :hysterical:

Edited February 19, 2020 by Tiem

hardcorehenry · February 19, 2020

35 minutes ago, Tiem said:

Same plist friend

AAPL,ig-platform-id Data <3E980003>

EDIT: Sorry, should be:

AAPL,ig-platform-id Data <0300983E>

Edited February 19, 2020 by hardcorehenry

Kynyo · February 19, 2020

@Andrey1970 Please attach your OC EFI folder without sensitive data. Im willing to test because I have a similar motherboard.

Thank you.

Andrey1970 · February 19, 2020

28 minutes ago, Kynyo said:

@Andrey1970 Please attach your OC EFI folder without sensitive data. Im willing to test because I have a similar motherboard.

Thank you.

https://www.insanelymac.com/forum/topic/338516-opencore-discussion/?do=findComment&comment=2704639

Flyinace2000 · February 19, 2020

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 ~ %

Edited February 20, 2020 by Flyinace2000
Added config file

nmano · February 20, 2020

Hi All

Can you make mini guide for How to update OpenCore-0.5.6-DEBUG

I try to update but stack in Gigabyte logo.

Thank you.

telepati · February 20, 2020

35 minutes ago, nmano said:

Hi All

Can you make mini guide for How to update OpenCore-0.5.6-DEBUG

I try to update but stack in Gigabyte logo.

Thank you.

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

Edited February 20, 2020 by telepati

Icaro82 · February 20, 2020

On 5/25/2019 at 2:53 PM, Rodion2010 said:

for ICH7/8/9/10 and some other we need to patch

AppleAHCIPort 40600200 to 00000000

or change SATA device-id to ICH6 8126

Helpful is reading about "the things you need", not using my EFI folder, because DSDT, SSDT, network , graphics and audio codec are completely different - if you do not use exactly the same configuration

Hello,

My HDDs don’t work in Catalina, only SSDs. I have a Westmere system (Xeon x5675) and Intel IHC10. That hardware gives problems with AppleAHCIPort.kext in new OSX versions. I’ve tried the patch (40600200 -> 00000000) on Clover and Opencore and no luck. My Hdds disks don’t initialize. My other option was to install the AppleAHCIPort.kext v.328 in the Library/Extensions folder but the result was a Catalina dead with boot error (Clover and Opencore).

How can I change the SATA device-id? I will lost performance because of the change?

Other solutions are welcome! Thanks all!!!

Edited February 20, 2020 by Icaro82

Rodion2010 · February 20, 2020

3 hours ago, Icaro82 said:

How can I change the SATA device-id? I will lost performance because of the change?

Other solutions are welcome! Thanks all!!!

I use this for a very long time and it works OK with any Mac OS from Leopard to Catalina

Erroruser · February 21, 2020

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

nmano · 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

vandroiy2012 · 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:

Vault
Type: plist string
Failsafe: Secure
Description: 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.

nmano · February 21, 2020

25 minutes ago, vandroiy2012 said:

Read manual:

Vault
Type: plist string
Failsafe: Secure
Description: 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 807498209_ScreenShot2020-02-21at3_54_46AM.png.7c07f9de56821af7a704905dbab16c55.png

Flyinace2000 · 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

Alpha22 · February 22, 2020

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

OpenCore General Discussion

Recommended Posts

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites