Is it necessary to use ACPI patch in config if equipped with whatevergreen?

[a361445613]

According to https://www.tonymacx86.com/threads/an-idiots-guide-to-lilu-and-its-plug-ins.260063/, when using Whatevergreen as GPU solution, following clover ACPI patches should be disabled or removed:

• Change/Rename GFX0 to IGPU
• Change/Rename PEG0 to GFX0
• Change/Rename HECI to IMEI

But in Rehabman's Clover config repository on Github, the existence of such patches really confuses me. Anybody could help or give more precise answer? Better if answered by Rehabman himself.

 

[phrozenpenguin]

Did you get to the bottom of this?

 

[KruxConcept]

Bump. Really want to know that too

 

[UtterDisbelief]

Hi all.

@jaymonkey 's guide is correct and your best resource. Read his Chapter 4 where he explains what you need to know very clearly and succinctly. The renames listed are now unnecessary.

Whatevergreen has been upgraded considerably since @RehabMan 's last involvement (check the dates), and as is explained in the guide does so much more nowadays.

 

[FreeJHack]

The renames listed are now unnecessary.

Not always true...

The SSDTs are loaded before kexts, hence, if you have an SSDT which is referring to IGPU (for example) you'll get an ACPI error. In other words, it depends also how you patch your system...

 

[UtterDisbelief]

Not always true...

The SSDTs are loaded before kexts, hence, if you have an SSDT which is referring to IGPU (for example) you'll get an ACPI error. In other words, it depends also how you patch your system...

Okay ...

But renames aren't kexts.

Or are you saying that Clover loads SSDTs before it performs renames in ACPI ?

 

[FreeJHack]

loads SSDTs before it performs renames

That's the point. The clover renaming is done before ACPI tables are loaded, the kext renaming is performed after.

At the very beginning, OSX loads the security policies & ACPI tables and then all kexts. If you have an SSDT with references to IGPU (or other devices/methods), you (might) need the clover's renaming patch otherwise after ACPI Tables loading you get an error and the correspondent table is completely discarded.
It could be the case where an SSDT is expecting the device IGPU already existent in ACPI and, if not found, an ACPI error is reported.