Jump to content

OpenCore General Discussion

dgsga

By dgsga,
in OpenCore

 Share
8755 posts in this topic

Recommended Posts

miliuco
miliuco
Posted
Posted

@Anto65

Your proposal is another method to do it. Indeed it doesn't need SIP disable. I'll add it to my local guides store.

For novice or less Terminal-savvy users, the easiest method is to install or reinstall Intel Power Gadget, since this installation rebuilds Preboot volume and updates .disk_label.contentDetails file.

 

  • Like 5
cankiulascmnfye
cankiulascmnfye
Posted
Posted (edited)
On 9/1/2024 at 9:19 PM, obus said:

My system is booting perfect on 1.0.0 up to latest version of Sonoma with this quirk enabled. Must be something with my Asus C422 Pro SE motherboard. I will report to developers.

 

The quirk has been fiixed: https://github.com/acidanthera/OpenCorePkg/commit/94ec1dc375eaec0ff3a5746a10c6716bfd639dd3

 

Try the latest nightly build (94ec1dc) from Dortania's Github repo to test: https://dortania.github.io/builds/?product=OpenCorePkg&viewall=true

Edited by cankiulascmnfye
  • Like 3
obus
obus
Posted
Posted
10 hours ago, cankiulascmnfye said:

 

The quirk has been fiixed: https://github.com/acidanthera/OpenCorePkg/commit/94ec1dc375eaec0ff3a5746a10c6716bfd639dd3

 

Try the latest nightly build (94ec1dc) from Dortania's Github repo to test: https://dortania.github.io/builds/?product=OpenCorePkg&viewall=true

Yea it was solved after my report to @PMheart so I'm well aware of this. Thanks anyway for the information😉

  • Like 1
miliuco
miliuco
Posted
Posted (edited)

Hello to all.

OpenCore 1.0.2 (not released yet) has this text in Configuration.pdf:

 

Quote

Docs: Update Booter >> Quirks >> FixupAppleEfiImages wording. Mac OS X boot.efi images contain WˆX permissions errors (in all versions) and in very old versions additionally contain illegal overlapping sections (affects 10.4 and 10.5 32-bit versions only). Modern, strict PE loaders will refuse to load these images unless additional mitigations are applied. Image loaders which enforce these stricter rules include the loader provided with current versions of OpenDuet, the loader in OVMF if compiled from Acidanthera and possibly the image loaders of some very recent 3rd party firmware (e.g. Microsoft).
This quirk detects these issues and pre-processes such images in memory so that a strict loader will accept them. On a system with such a modern, stricter loader this quirk is required to load Mac OS X 10.4 to macOS 10.12, and is required for all newer macOS when SecureBootModel is set to Disabled because pre-processing in memory is incompatible with UEFI Secure Boot, as the image loaded is not the image on disk, so you cannot sign files which are loaded in this way based on their original disk image contents.
This quirk is never applied during Apple Secure Boot for newer macOS. The Apple Secure Boot path in OpenCore includes its own separate mitigations for boot.efi WˆX issues.

 

Question: Does this mean we have to enable always this quirk when we set SecureBootModel to Disabled on newer macOS? What do you think about it?

Edited by miliuco
OCLP text new build (minor changes)
  • Like 2
Stefanalmare
Stefanalmare
Posted
Posted
13 minutes ago, miliuco said:

Hello to all.

OpenCore 1.0.2 (not released yet) has this text in Configuration.pdf:

 

 

Question: Does this mean we have to enable this quirk when we set SecureBootModel to Disabled on newer macOS? How do you understand it?

I use this quirk only with the new duet loader for legacy, given by "LegacyBoot" utility.

  • Like 4
Matgen84
Matgen84
Posted
Posted (edited)
18 hours ago, Stefanalmare said:

Hey @cankiulascmnfye! With latest OC I have in OCAT: "OCS: missing key Unload, context <UEFI>!

 

Hi @Stefanalmare Add <key>Unload</key> to the end of config.plist with <array/> (see sample config.plist)

Most important things: have a look to changelog file before update Opencore. Same for sample.plist and config doc. Plist editor, BBEddit or Sublime Text are good tools.

Edited by Matgen84
complement
  • Like 2
MacNB
MacNB
Posted
Posted
17 hours ago, Stefanalmare said:

Hey @cankiulascmnfye! With latest OC I have in OCAT: "OCS: missing key Unload, context <UEFI>!

 

That's one of the problems with bespoke configurators. The Devs of those tools need to keep up OC changes.

I personally use PlistEditPro .plist editor ...so easy to use....of course you need to know what you are editing.

  • Like 2
cankiulascmnfye
cankiulascmnfye
Posted
Posted (edited)
1 hour ago, eSaF said:

Yes, OCAT needs Updating to include that line.

I don't know if the developer is continuing to Update the app.

 

I put in a bug report on his GitHub page hoping he correct the omission.

As it stands, even after physically adding the line to the config.plist, it is removed by OCAT whenever you update Opencore.

 

It will then throw up the error as the line is not included in the UEFI section of the app.

This is because it does not correspond with the Sample Config.plist in its Data Base which includes the line.

 

1 hour ago, MacNB said:

 

That's one of the problems with bespoke configurators. The Devs of those tools need to keep up OC changes.

I personally use PlistEditPro .plist editor ...so easy to use....of course you need to know what you are editing.

 

18 hours ago, Stefanalmare said:

Hey @cankiulascmnfye! With latest OC I have in OCAT: "OCS: missing key Unload, context <UEFI>!

 

AFAIK, OCAT can add strings to the GUI on it's own (which no other configurator tool can do), but since "Unload" is an Array, my guess is that the app needs to be updated (which hasn't been necessary in a long time). In the past, the turnaround forfor fixing reported issues was pretty fast, though.

 

For now, just open the sample.plist in propertree, copy the array and paste it in your config.plist.

 

I had to look up what "Unload" is actually for:

 

Bildschirmfoto2024-10-08um16_56_40.png.6d3c355da1c3b638202f2ff8ff48a4dc.png

 

Edited by cankiulascmnfye
  • Like 2
  • Thanks 1
Stefanalmare
Stefanalmare
Posted
Posted
3 hours ago, Matgen84 said:

 

Hi @Stefanalmare Add <key>Unload</key> to the end of config.plist with <array/> (see sample config.plist)

Most important things: have a look to changelog file before update Opencore. Same for sample.plist and config doc. Plist editor, BBEddit or Sublime Text are good tools.

 

2 hours ago, MacNB said:

 

That's one of the problems with bespoke configurators. The Devs of those tools need to keep up OC changes.

I personally use PlistEditPro .plist editor ...so easy to use....of course you need to know what you are editing.

 

2 hours ago, eSaF said:

Yes, OCAT needs Updating to include that line.

I don't know if the developer is continuing to Update the app.

 

I put in a bug report on his GitHub page hoping he correct the omission.

As it stands, even after physically adding the line to the config.plist, it is removed by OCAT whenever you update Opencore.

 

It will then throw up the error as the line is not included in the UEFI section of the app.

This is because it does not correspond with the Sample Config.plist in its Data Base which includes the line.

 

I'm using PlistEdit Pro.app, ProperTree.app, OpenCore Configurator.app and OCAT daily and from many years.  For me, OCAT is the best tool for OC. All I wanted with my message to @cankiulascmnfye was to give him a feedback about this situation. I have fixed this with PlistEdit Pro.app at the moment. Thank you all for your help!

  • Like 4
ANTIKO
ANTIKO
Posted
Posted
1 hour ago, cankiulascmnfye said:

 

Of course there will be an error, if the "Unload" entry is deleted from the config upon saving it!

Maybe it's translation difficulties - but if there is "Unload" in PlistEdit Pro, then should it be in OCAT?

Spoiler

 

image.thumb.png.9da5dbee28c4f9e535400f1ae32e602b.png

  • Like 2
fabiosun
fabiosun
Posted
Posted
5 hours ago, eSaF said:

Tested and all is well again.

Thanks for your effort in getting the amendment done. :thumbsup_anim:

thanks for the link and the issue opened

i think it is a working progress because for now it is not possible to add unload parameter in OCAT

However error is gone :)

 

  • Like 1
cankiulascmnfye
cankiulascmnfye
Posted
Posted (edited)
12 minutes ago, fabiosun said:

thanks for the link and the issue opened

i think it is a working progress because for now it is not possible to add unload parameter in OCAT

However error is gone :)

 

 

Noticed this as well. If you have a look at the logs of the compilation process on the "action" tab on github, you can see a bunch of errors due to outdated tools.

 

So, for now: the unload option is added when pressing save, but the Array is not added to the GUI.

 

I think the main issue is that the UEFI section now need a LIST in the GUI to represent entries, just like in the "Add" section of "Kernel" and "ACPI". So this can only be a temporary fix until the GUI is overhauled.

Edited by cankiulascmnfye
  • Like 2
 Share
Go to topic listing
×
×
  • Create New...