Jump to content
30961 posts in this topic

Recommended Posts

33 minutes ago, Matgen84 said:

 I don't find your r5127 EFI folder in your topic.

 

Full problem reporting files (including EFI) for r5127 here.

 

Full problem reporting files (including EFI) for r5122 here.

 

Both my r5122 and r5127 EFIs include the exact same config.plist, exact same kexts and exact same ACPI/patched.  The only difference between my two EFIs is CLOVER r5122 vs. CLOVER r5127.

 

33 minutes ago, Matgen84 said:

Your problem occurs with r5127 on Catalina, right ?

 

The problem specifically is this: When I boot Catalina 10.15.7 with CLOVER r5122, my Energy Saver options are these (5 options):

Spoiler

image.png.0f8cfa4af4263ae28c315ee6ba2b93c4.png

 

When I boot Catalina 10.15.7 with CLOVER r5127, my Energy Saver options are these (only 2 options):

Spoiler

image.png.c986b315774f6dde771a05f17a3ae54f.png

 

Thank you!

 

By the way: I hope I do not seem to be complaining - I am NOT.  My system performance is better with r5127 than it is with r5122 (better Geekbench5 multicore benchmarks with r5127 than with r5122, system seems more responsive and I have a new lower CPU multiplier (10x) with r5127 that I don't have with r5122 (13x).  I am very pleased with r5127.  I am only pointing this out, hoping to help identify an issue to be resolved (since it appears to be affecting @MacKonsti sleep/wake and possibly others).

Edited by tonyx86
  • Like 2
2 minutes ago, tonyx86 said:

 

Full problem reporting files (including EFI) for r5127 here.

 

Full problem reporting files (including EFI) for r5122 here.

 

Both my r5122 and r5127 EFIs include the exact same config.plist, exact same kexts and exact same ACPI/patched.  The only difference between my two EFIs is CLOVER r5122 vs. CLOVER r5127.

 

Thank you!

 

I take a look to you r5122 EFI folder in your topic. 

r5122 use old Clover way and r5127 use new Clover way (injection,...) :) For r5127, you can't use config.plist (5122 version), old openruntime, ocquirks.... So update your config.plist before using r5127 

Since r5124+, Clover use his own openruntime without ocQuirks. There are some new settings. A topic exists on the forum but I don't remember the name.

Sorry for my bad English.

  • Thanks 1

Booting r5128 on HP Prodesk 600 G1 = Slow Boot comparing r5127 (about 30 seconds) System is Big Sur 11.1 (20C69)

Edited by chris1111
  • Thanks 1
  • Sad 1
7 minutes ago, Matgen84 said:

 

I take a look to you r5122 EFI folder in your topic. 

r5122 use old Clover way and r5127 use new Clover way (injection,...) :) For r5127, you can't use config.plist (5122 version), old openruntime, ocquirks.... So update your config.plist before using r5127 

Since r5124+, Clover use his own openruntime without ocQuirks. There are some new settings. A topic exists on the forum but I don't remember the name.

I really do appreciate your help!  I believe I have correctly followed the available suggestions (including this guide) for upgrading CLOVER.

3 minutes ago, tonyx86 said:

I really do appreciate your help!  I believe I have correctly followed the available suggestions (including this guide) for upgrading CLOVER.

 

Do you have the same issue with the new config.plist !

27 minutes ago, Matgen84 said:

 

Do you have the same issue with the new config.plist !

 

I have always been testing with "the new config.plist" and I have always seen the same issue with "the new config.plist."  The issue I reported is with "the new config.plist" in my problem reporting files (which is updated with the additional Quirks as per the guide).  The only change that I made after posting my problem reporting files is that I deleted kexts from /Library/Extensions and rebuilt kextcache (which did not change the issue or fix the problem).  I am using the EXACT SAME UPDATED config.plist for both r5122 and r5127.  My config.plist includes the new Quirks for r5127 (which are ignored by r5122).

 

EDIT: @Matgen84 If I boot Catalina 10.15.7 with OpenCore 0.6.5 (with exact same kexts and exact same patched ACPI that I use for CLOVER r5127), the Energy Saver options are restored.

Edited by tonyx86
  • Sad 1

@tonyx86 The other day I had taken a quick look at your OC and Clover EFI and if I remember correctly, you don't exactly use the same SSDTs. If it was my hack, for starters, I would use SSDT itself and boot-arg myself on OC and Clover.
Another annotation, if you use the plugin type only with Clover 5127/5128 then the Power Management does not work

  • Thanks 2
1 hour ago, chris1111 said:

Booting r5128 on HP Prodesk 600 G1 = Slow Boot comparing r5127 (about 30 seconds) System is Big Sur 11.1 (20C69)

Do you use the quirk XhciPortLimit?

It was not working in 5127 and does work in 5128.

  • Like 1
  • Thanks 1
13 minutes ago, Slice said:

Do you use the quirk XhciPortLimit?

It was not working in 5127 and does work in 5128.

No I did not use it

Alright with the XhciPortLimit the boot is like a JET :plane: 

Perfect thanks

  • Like 2
42 minutes ago, iCanaro said:

@tonyx86 The other day I had taken a quick look at your OC and Clover EFI and if I remember correctly, you don't exactly use the same SSDTs. If it was my hack, for starters, I would use SSDT itself and boot-arg myself on OC and Clover.
Another annotation, if you use the plugin type only with Clover 5127/5128 then the Power Management does not work

Thank you for taking the time to look!  For my current testing of r5122 and r5127, I am using the exact same SSDTs.  Interesting that you mention plugin type - I was just about to disable SSDT>Generate>PluginType in CLOVER config.plist and use my plugin-type SSDT... 

 

Unfortunately, after switching between r5122 and r5127 EFIs, my entire disk is corrupted (I test OC with a separate SSD).  As soon as I figure out what happened and restore (from backup if necessary), I'll try replacing CLOVER's SSDT>Generate>PluginType with SSDT-PLUG.

 

EDIT: All who are testing r5122 and r5127 - this may be purely a coincidence, but my SSD is currupted after switching back and forth between r5122 and r5127 for testing.  Attempts to repair with diskutilty result in the following:

 

Checking the space manager

error: (oid 0x6e1d) cib: found zeroed-out block

error: failed to read spaceman cib 0 at address 0x6e1d

Space manager is invalid

The volume /dev/rdisk3s1 could not be verified completely

 

 

Thank you!

Edited by tonyx86
25 minutes ago, tonyx86 said:

Thank you for taking the time to look!  For my current testing of r5122 and r5127, I am using the exact same SSDTs.  Interesting that you mention plugin type - I was just about to disable SSDT>Generate>PluginType in CLOVER config.plist and use my plugin-type SSDT... 

 

it's no coincidence that I mentioned plugin type, recently on macos86.it they detected that using recent Clover, The Power Management did not work, to get him back to work with Clover without using SSDT X PM you had to set also in the

config >> acpi >> SSDT Plugin Type --> 1

over flagging plugin type in generate options

 

 

  • Like 1
  • Thanks 1

@iCanaro Grazie mille!  Thank you for your quick responses!  Just to be clear, I am (was until my disk corrupted) enabling "SSDT->Generate->PluginType" in my config.plist for both r5122 and r5127.  Are you saying that in addition to enabling "Generate->PluginType", I also need to set PluginType->1 in CLOVER config.plist?  If that is correct, are you saying that this requirement for "Plugin Type -> 1" is new for r5127?

12 minutes ago, tonyx86 said:

Are you saying that in addition to enabling "Generate->PluginType", I also need to set PluginType->1 in CLOVER config.plist?  If that is correct, are you saying that this requirement for "Plugin Type -> 1" is new for r5127?

 

yes it's accurate.
But my advice is to use SSDT x PM that you're using with OC and use the same SSDT for both Clover and OC and let go of plugin types in Clover's config 

  • Like 1
  • Thanks 1
4 minutes ago, iCanaro said:

 

yes it's accurate.
But my advice is to use SSDT x PM that you're using with OC and use the same SSDT for both Clover and OC and let go of plugin types in Clover's config 

Thank you!  I will test soon after I recover.

cc'ing @MacKonsti

 

@iCanaro I would give the same advice about CLOVER's "Fix SBUS."  Disable "Fix SBUS" in CLOVER's config.plist and use an SSDT for my reasons here.

Edited by tonyx86

Thanks for the tagging @tonyx86

 

So wait @iCanaro as it's not clear to me. Sorry to repeat TonyX86:

You say that r5127 and newer, we need on top of this in config.plist

		<key>SSDT</key>
		<dict>
			<key>Generate</key>
			<dict>
				<key>CStates</key>
				<false/>
				<key>PStates</key>
				<false/>
				<key>PluginType</key>
				<true/>
			</dict>
		</dict>

...we need this from SSDT-PLUG as found on Dortania guides?

    Method (PMPM, 4, NotSerialized) {
        If ((Arg2 == Zero)) {
           Return (Buffer (One) { 0x03 })
        }

       Return (Package (0x02) {"plugin-type", One})
    }

so that in IORegistry we see the key "plugin-type" under CPU zero?

So what's the purpose of <key>PluginType</key> then in recent versions of Clover? Is it not taken under consideration at all?

@Slice can you enlighten us please mate?

 

With Clover r5123-1 when I open my IORegistryExplorer (SMBIOS is Macmini8,1) I do see plugin-type as 0x01 just fine, without SSDT-PLUG.AML or whatever the Power Management SSDT AML name...

Edited by MacKonsti

@MacKonsti Lose the SSDT->PluginType in CLOVER config.plist and patch ACPI with your own SSDT (same as you would for OC).

 

I also recommend that you lose CLOVER's "Fix SBUS" and patch SBUS.BUS0 with your own SSDT.  Soon, all CLOVER users will be following @MaLd0n 's ACPI patching guides and we'll be running with patched DSDTs. :)

Edited by tonyx86
5 hours ago, chris1111 said:

No I did not use it

Alright with the XhciPortLimit the boot is like a JET :plane: 

Perfect thanks

do you mean you turn this quirks on true ? if yes for what for? if you  have personal usbkext or usb SSDT. why would we need to turn true this quirk ? 

Edited by odemolay

@iCanaro - I am now running CLOVER r5127 without SSDT->PluginType and with SSDT-PLUG (attached).  You are correct!!!! The Power Saver settings are now working.  It does appear that CLOVER's SSDT-PluginType is not working correctly and needs to be fixed.  @Slice FYI.

 

Spoiler

186629287_ScreenShot2021-01-07at5_28_02PM.png.03d5540d6494f19f7bf87ba5860f6445.png

 

 @MacKonsti - maybe this solves your problem, too.  I have disabled CLOVER r5127's SSDT->PluginType and r5127's "Fix SBUS" and have replaced these CLOVER settings with SSDTs (attached).  All appears to be running perfectly.

 

@MifJpn - this is the solution to the problem.  This IS a CLOVER r5127 bug that needs to be fixed and it is not a configuration problem. Thank you for your help.

 

*** NOTE: The attached SSDT-PLUG.aml is specific to my ACPI (_SB_.PR00).  You will need to make sure that your SSDT-PLUG patch is suitable for your system's ACPI. ***

 

Attached is the SSDT-PLUG.aml (same as what I use for Open Core) that should replace CLOVER r5127's SSDT->PluginType.  Also attached is SSDT-SBUS.aml that should replace CLOVER r5122 and r5127 "Fix SBUS."

 

SSDT-PLUG.zip

 

SSDT-SBUS.zip

Edited by tonyx86
Added note about SSDT-PLUG compatibility with ACPI
  • Like 3
  • Thanks 1

@MacKonsti using translators, my thoughts are not always fully expressed, specified this, we found that the only plugin type flag does not make power management work properly, this in the most recent versions of Clover (5125/5126 etc...) and I reported the thing in this thread. In order for Clover to handle the PM correctly, type 1 plugins must be enabled in addition to the plugin type flag in generate options. That said, since here many like me use OC and Clover at the same time, I think it's more appropriate for the PM to be managed by an identical functional SSDT for both boot loaders

  • Like 1

@iCanaro The table below represents my testing with r5122 and r5127.  After I replaced CLOVER r5127's Generate->PluginType with SSDT-PLUG.aml, my Geekbench 5 multi-core performance dropped back down to what I was observing with r5122 here.  Notice that my i7-8700 CPU performance is better with CLOVER r5127 and CLOVER's Generate->PluginType (without "Plugin Type = 1").  If @Slice or someone can figure out how to fix Energy Saver settings and retain the increased CPU performance, that would be great.

 

EDIT: I updated this table with an additional column to show that @iCanaro is correct about enabling "Plugin Type = 1" in the CLOVER r5127 config.plist.  I may have overstepped a bit by claiming this to be an r5127 "bug."  Maybe all previous versions of CLOVER should have required "Plugin Type = 1" and this "bug" is now fixed in r5127.  Regardless, this is a change from r5122 to r5127.

 

 

CLOVER R5122 with 

Generate->PluginType

CLOVER R5127 with 
Generate->PluginType

CLOVER R5127 with 
SSDT-PLUG.aml

CLOVER R5127 with 
Generate->PluginType and Plugin Type = 1

Energy Saver Preferences

5 settings available

2 settings available

5 settings available

5 settings available

GeekBench 5 multi-core benchmark

5500+

5600+

5500+

5500+

Lowest CPU multiplier

13

10

13

13

Edited by tonyx86
Added table column with "Plugin Type = 1"
  • Like 1
5 minutes ago, MifJpn said:

After that, for historical reasons, the developer will decide if it can be fixed.

 

I wouldn't want it any other way.  May the developer choose wisely.

Is there a reason that OC 0.6.3 and 0C 0.6.5 are able to properly inject FakeSMC_CPUSensors.kext (6.26-357-gceb835ea.1800) but CLOVER r5127 is not?  Details below...

 
I still use FakeSMC.kext and FakeSMU_CPUSensors.kext with HWMonitor.app ( (all three are version 6.26-357-gceb835ea.1800).  I know - they're old, but I've never had a reason to change and they have served me well all the way through Catalina with CLOVER r5122 and CLOVER r5127 (kexts installed in /Library/Extensions).  This same FakeSMC/Sensor/HWMonitor combo works fine with Catalina and Big Sur and OpenCore 0.6.3 and 0.6.5 (where no 3rd-party kexts are installed in /L/E).

 

To prepare my Catalina 10.15.7 for upgrade to Big Sur with CLOVER r5127, I moved all of my 3rd-party kexts to E/C/k/O, deleted my kexts from /L/E and rebuilt kext cache.  With kexts in E/C/k/O, no 3rd-party kexts in /L/E and CLOVER r5127, HWMonitor.app no longer shows CPU temps/clocks. I'm guessing that CLOVER r5127 is not properly injecting my old FakeSMC_CPUSensors.kext.

 

I'm guessing that upgrading to a newer version of FakeSMC/Sensors/HWMonitor fixes this, but since these old versions have served me so well and still work fine with OC and Big Sur, is there a reason that r5127 doesn't work with these?

 

Thank you.

 

 

×
×
  • Create New...