Jump to content

OpenCore General Discussion

dgsga

By dgsga,
in OpenCore

 Share
8,887 posts in this topic

Recommended Posts

Matgen84
Matgen84
Posted
Posted
2 minutes ago, Logician said:

Anyone know why I cannot enable SIP?  I have  


<key>csr-active-config</key>
<data>AAAAAA==</data>

and I see 


> nvram -p
csr-active-config	g%00%00%00

but when I check, I get 


>csrutil status
System Integrity Protection status: disabled.

I don't know what else to check/try.

 

Maybe, You've to reset NVRAM after this change. Just my opinion.

  • Like 1
Link to comment
Share on other sites
telepati
telepati
Posted
Posted
3 hours ago, Slice said:

Xcode remains the best option to edit plist files because this is Apple's used files. 

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?

  • Like 1
Link to comment
Share on other sites
Erroruser
Erroruser
Posted
Posted
6 hours ago, Slice said:

Xcode remains the best option to edit plist files because this is Apple's used files.

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

  • Like 1
Link to comment
Share on other sites
telepati
telepati
Posted
Posted

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.

Link to comment
Share on other sites
Tiem
Tiem
Posted
Posted
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).

  • Thanks 1
Link to comment
Share on other sites
Andrey1970
Andrey1970
Posted
Posted
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.

  • Thanks 1
Link to comment
Share on other sites
Slice
Slice
Posted
Posted
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.

Link to comment
Share on other sites
Tiem
Tiem
Posted
Posted
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:

169488044_ScreenShot2020-02-18at12_48_51PM.thumb.png.5c167912ff0e27b42d259246a351bc0d.png

 

Plist Editor Pro:

1555958102_ScreenShot2020-02-18at12_49_25PM.thumb.png.b9d89a64ce8ed9e25096f66284cb1111.png

 

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.

  • Like 1
Link to comment
Share on other sites
telepati
telepati
Posted
Posted
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:

169488044_ScreenShot2020-02-18at12_48_51PM.thumb.png.5c167912ff0e27b42d259246a351bc0d.png

 

Plist Editor Pro:

1555958102_ScreenShot2020-02-18at12_49_25PM.thumb.png.b9d89a64ce8ed9e25096f66284cb1111.png

 

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.

Link to comment
Share on other sites
mhaeuser
mhaeuser
Posted
Posted
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

  • Like 2
Link to comment
Share on other sites
Erroruser
Erroruser
Posted
Posted
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

Link to comment
Share on other sites
Slice
Slice
Posted
Posted
12 hours ago, Tiem said:

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

 

Xcode:

169488044_ScreenShot2020-02-18at12_48_51PM.thumb.png.5c167912ff0e27b42d259246a351bc0d.png

 

Plist Editor Pro:

1555958102_ScreenShot2020-02-18at12_49_25PM.thumb.png.b9d89a64ce8ed9e25096f66284cb1111.png

 

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.

  • Like 1
  • Haha 1
Link to comment
Share on other sites
Tiem
Tiem
Posted
Posted (edited)
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 by Tiem
Link to comment
Share on other sites
Flyinace2000
Flyinace2000
Posted
Posted (edited)

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 by Flyinace2000
Added config file
Link to comment
Share on other sites
nmano
nmano
Posted
Posted

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.

Link to comment
Share on other sites
telepati
telepati
Posted
Posted (edited)
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 by telepati
  • Like 1
Link to comment
Share on other sites
Icaro82
Icaro82
Posted
Posted (edited)
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 by Icaro82
Link to comment
Share on other sites
 Share
Go to topic listing
×
×
  • Create New...