Leaderboard

I propose that Clover package install BootloaderChooser instead, to definitively put an end at this duplication of clover efi file. I'm working on that. VirtualSMC.efi and FakeSMC.kext has nothing to do with each other. One is loaded at EFI time, one is loaded by kernel. We'll do "differential" debugging together, like before and we'll find the problem. Hey everyone : don't go too fast I can't keep up... When a bug is known, no need to test anymore until one dev says it's fixed !

As I said before, commit r5123_641b75e by @Slice is wrong and changes old Clover KernelAndKextPatches behavior. Those who had working config.plist in old Clover with KernelPm=Yes can try adding KernelXCPM=Yes if using Clover r5124_a2ffdf8 . Edit: Bug now fixed in Clover_r5124_086e5682a.pkg Fix for above commit requires you to link Clover function OC function KernelXCPM = AppleXcpmExtraMsrs KernelPm = AppleXcpmCfgLock AppleIntelCPUPM = AppleCpuPmCfgLock

The latest version Clover_r5124_a2ffdf864 Clover_r5124_086e5682a.pkg On my legacy desktop GA-P55aUD3 (System 2 in signature)... Some tips for converting over from old Clover r5122 to new ones with OC 0.6.1 integration in this post. However this commit r5123_641b75e by @Slice changes old Clover KernelAndKextPatches behavior: To get power management for Sandy/IvyBridge CPUs that need patched AppleIntelCPUPowerManagement.kext, now need KernelPm=Yes instead of AppleIntelCPUPM=Yes. To get kernel power management for Haswell and newer CPUs , now need KernelXCPM=Yes instead of KernelPm=Yes. Edit: Above bug was fixed with r5124_086e5682a.

For those interested and do not know Clover now has OpenCore integration and can boot Big Sur and below. Please make sure you check out the sample config and adjust your own accordingly and make a backup USB or test via USB first, also there are EFI folders posted for reference in the clover general discussion thread. Sent from my iPhone using Tapatalk

This is why you should always have a USB backup or test via USB first. Have you tried rolling back clover version then checking your config against the config-sample?

Should be fixed in v3.4.5

I strongly recommend using Clover 5124.PKG instead of replacing *.efi files. As to IvyB's XCPM, I have tested this theory and can confirm it works with ssdtPRGen and CPUFriend. I finally got it working again today after the old patches I applied in 10.15.6 failed after the 10.15.7 update.

I understand now. Fixed. See 086e5682a

@fusion71au Okay so I'm a complete stupid. After reading your quote I remembered that I had KernelPM=Yes and KernelXCPM=No, and I just forgot to edit them to KernelXCPM=Yes and KernelPM=No. Clover v5124 booted just fine after editing them. buhh.. big thanks for you.

Z170 finally I solved! Z170_5124_OK_debug.log now start my hacks Z68, Z97, Z170, Z370 with Clover 5124, Quirks and OpenRuntime if you have a kernel panic, it's easy to be a kext

With Clover_OC Integration, need to delete HS80211Family.kext/Contents/PlugIns/IO80211NetBooter.kext to fix this problem. No such issue when using HS80211Family.kext with OC 0.6.2 and Big Sur (unless you add the plugin kext to config.plist/Kernel/Add and enable its loading). Yes, wifi was still working here after deleting the plugin kext .

@Jief_Machak finally also on the Z97 hack with Clover 5124 I manage to start sierra, high sierra, mojave, catalina, windows 10 even here it happens that the log debugging is created once and then only empty files of zero kb Z97_5124_preboot.log Z97_5124_debug_OK.log

Here is version 2.4.0d5 in which I fixed an issue with EEE support. The archive contains a debug and a release build and was built for Mojave and above. Provided nothing unexpected happens, I think we are pretty close to an official release 2.4.0. I'll continue to support Mojave and, in case there is a demand, High Sierra too. Let's see what users have to say about High Sierra? Mieze RealtekRTL8111-V2.4.0d5.zip

I installed clover r5124 and cannot boot Catalina or Big Sur with my 5123 EFI folder I can boot Catalina but not Big Sur, I am rusty.

Now waiting for version 5125 to come out, I will try. In case of correction for DSDT.aml to work

I'm working on that. let me know when you'll be ready to see you do something about AMD, X570 my T-RyZo for now a huge thank you to you and Slice for the excellent work done so far PS: a mention for Fusion always precise and clarifying interventions

Idem DSDT no charged HP Envy Reline 23-K030ef haswell !!! Clover r5123 = OK Clover r5124 = no charged DSDT !

I already tested Clover v5123 with my build, GA-Z97-HD3 with dGPU RX-580 and I was able to boot in Big Sur beta 9 without major issues. Just made sure that I checked the quirks recommended in Dortania for Hasswell, setting up the device properties for wifi card (Broadcom combo card 4331) in config plist file and uploading the Kexts (compiled latest kext build) and drivers required in my case.

Rigth, BOOTX64.efi is a rename file of CLOVERX64.efi. When you update Clover from PKG, both files are changed to the new version. Post debug.log (Notebook) maybe users can help you. Hi @Jief_Machak I update my IvyBridge config.plist to new standard. I can boot r5124 but my MaLdOn's DSDT failed to display PCI entries in System Info (Mojave). All works fine with r5122. Any ideas ! Please

I don’t know what the “rule” is with Bootx64.efi but if I updated Cloverx64 I always updated Bootx64. Same when I was using OC, if I updated OpenCore.efi I always updated Bootx64.

KernelPm patch is for CFG locked in BIOS. KernelXCPM enables kernel power managements on unsupported CPU: SandyBridge-E LGA2011 IvyBridge, IvyBridge-E Haswell-E Broadwell-E/EP

Actually, KernelXCPM only works for SandyBridge, IvyBridge, Haswell, and Broadwell-E/EP. Newer platforms naturally have XCPM and don't need KernelXCPM to enable XCPM. Yeah, I think Slice need to fix that. The more reasonable correlation should be KernelXCPM = AppleXcpmExtraMsrs, KernelPm = AppleXcpmCfgLock, AppleIntelCPUPM = AppleCpuPmCfgLock

For anyone needing assistance the EFI attached works for me on my laptop (specs in signature). This EFI boots Arch Linux, Windows 10, macOS Catalina and Big Sur. EFI-Laptop-i7-9750H.zip The only oddity is my CPU is displaying incorrectly. I have an i7-9750H not an i9.

Not same. 10.15 assumes 10.15.0 only "All" assumes 11.0 as well.

On my Z68 hack with Clover 5124 I managed to start windows, linux mageia, high sierra, mojave and catalina only a little strange thing, the debug log was generated the first time I started high sierra, and then with all the other macOS, a debug log of zero Kb empty was generated In case it could serve dev, I attach the generated log debugging and the preboot starting with quirks and OpenRuntime Z68-5124-preboot.log Z68_5124-d2bec9ba0_OK_high-sierra-debug.log

Clover_r5124 Upgrade

try changing UIScale to 02

Not yet. On the TODO list.

Ok attach your full catalina efi that you use with the clover

You're right. I have suspected this from reading your text about several EFIs, one for each system. I have Catalina on one SSD and BS on another SSD, each with its own ESP partition and complete EFI folder. After reading your text, I have rebooted but I have cleared NVRAM and rebooted again and SATA hot plug works!!! This was the problem, swapping disks that read NVRAM that has been stored from another disk. Since I use SSDT-PMC, I have native NVRAM and it is no longer saved in the root of each system disk, as before, I think it's stored now in the Board CMOS (I guess it's in this place though I'm not sure but NVRAM values are available for systems other than the one that generated them). Thank you very much for your help, problem solved.

No idea what MaLdOn means but maybe you can try generating a new DSDT? Also, I wonder if we still need VirtualSMC.efi since 5124 includes OC now. Maybe that means we need to remove FakeSMC* kexts?

Try newer version, set medium manually, test different speeds and its a bit off-topic.

"Adding" KernelPm=Yes KernelXCPM=Yes Or you mean: KernelPm=No KernelXCPM=Yes

I see that in your system it works fine. I will review it again. I have Sata hot plug enabled in Bios. I don't use Nvme. On Catalina’s disk the patch works fine. But not in BS. I'll go over everything and tell you.

what are the kexts that give problems, you'll have to locate them, maybe start with the FakeSMC of Slice and a few kexts nullCPU with ivy bridge should not serve you, you need to generate a ssdt for the power management of your CPU

Same for me. Acer Aspire V5-591G i5-6300HQ: Stuck at [EB|#LOG:EXITBS:START] -> reverted back to v5123, booted just fine i7-6700K PC: v5124 booted just fine. I didn't do anything rather than updating CLOVERX64.efi, using the same drivers as my Acer notebook except DataHubDxe. Here is the debug from earlier. I don't see any errors in it, the only thing I noticed is that my AGDP KextPatches aren't loaded because it's missing. I fixed it by renaming AppleGraphicsDevicePolicy to com.apple.driver.AppleGraphicsDevicePolicy. Also on PC I have an older DataHubDxe driver (new one gave me red error msg), on notebook I don't have such efi driver. I'll try to use that one and see if it's okay or not, but I don't think it'll make any differences. EDIT: Just tried with an older DataHubDxe, made no difference.

thank for you effort to try, according the fusion71au said remove IO80211NetBooter can solve the issue, anyway thanks for help that make me clear, I'm editing in download section and removing IO80211NetBooter from plugin

With the Clover the kexts in question ( HS80211Family.kext & AirPortAtheros40.kext ) the startup of Big Sur is blocked. On which version of Opencore have they been tested and which work?

Correct answer is 10.15.x. 10.15=10.15.0 only All=All macOS, including but not limited to 10.15.0-10.15.7. Refer to post by @Micky1979 TBH, not sure if MatchOS will still work in Clover_OC integration, since kext patching is actually done by OC 0.6.1 and that patch engine uses Min & MaxKernel versions to filter the patches AFAIK, all kext injection and patching in new Clover_OC Integration is now done under the hood with OC 0.6.1. The above commit (incorrectly IMHO) links OC AppleCpuPmCfgLock, which patches AppleIntelCPUPowerManagement.kext for Sandy/IvyBridge systems, with Clover setting config.plist/KernelAndKextPatches/KernelPm, instead of AppleIntelCPUPM... line 3058 in rEFIt_UEFI/Platform/Settings.cpp gSettings.KernelAndKextPatches.OcKernelQuirks.AppleCpuPmCfgLock = gSettings.KernelAndKextPatches.KPKernelPm; Similarly, the commit incorrectly links OC AppleXcpmCfgLock (which enables kernel power management for Haswell and newer CPUs with locked msrs) with Clover setting config.plist/KernelAndKextPatches/KernelXCPM instead of KernelPm... line 3062 in rEFIt_UEFI/Platform/Settings.cpp gSettings.KernelAndKextPatches.OcKernelQuirks.AppleXcpmCfgLock = gSettings.KernelAndKextPatches.KPKernelXCPM; Edit: Bug fixed in Clover_r5124_086e5682a.pkg

Hi @SavageAUS You use MacBookPro16,1 (i9) instead of MacBookPro15,1 (i7): so you need CPU patch in your config.plist display the correct processor (cosmetic). I think.

Hi The name is os_bigsur.icns

Hi - This is the Patch in my config.plist also check that the particular Sata Port the Drive is connected to, that Hot Plug is enabled in the BIOS.

@Matgen84 5124 works with 10.15.7 & IvyB here.

Try this MO80211Family.kext.zip based on Mojave, I uploaded full kext n plugin you can choose which what you needed and don't forget inject that in your config.plist, in your case maybe MO80211Family & AirPortBrcm4311

The result is the same. 13 .14 .15 11. edit.. Let's move to oem, the result is the same. This overlap was left with two options. Noteworthy Is there an exception where I have a black circle? Let's update again I got your help mifjpn That gave the code to create a clover until success From .. ~% cd ~% rm -rf CloverBootloader % git clone -b master --recurse-submodules https://github.com/CloverHackyColor/CloverBootloader.git ..................................... ~ % cd CloverBootloader/ % git status % ./buildme --------------------------------------------- buildme, Clover r5124 (SHA: a2ffdf864) TOOLCHAIN: GCC53 (override example: './buildme XCODE8') 1) build Clover 2) build Clover with HFSPlus 3) make pkg 4) make app 5) make app (with Clover) 6) make iso 7) build all 8) test build (no autogen, no boot files) 9) status 10) update Clover 11) show diff 12) open CloverV2/EFI/CLOVER directory 13) update Clover (reset changes) 14) clean BaseTools 15) quit Please enter your choice:(7).. ............................. buildme, Clover r5124 (SHA: a2ffdf864) TOOLCHAIN: GCC53 (override example: './buildme XCODE8') 1) build Clover 2) build Clover with HFSPlus 3) make pkg 4) make app 5) make app (with Clover) 6) make iso 7) build all 8) test build (no autogen, no boot files) 9) status 10) update Clover 11) show diff 12) open CloverV2/EFI/CLOVER directory 13) update Clover (reset changes) 14) clean BaseTools 15) quit Please enter your choice: (15) ~ % cd ~ % cd CloverBootloader % git pull && git fetch % ./buildme buildme, Clover r5124 (SHA: a2ffdf864) TOOLCHAIN: GCC53 (override example: './buildme XCODE8') 1) build Clover 2) build Clover with HFSPlus 3) make pkg 4) make app 5) make app (with Clover) 6) make iso 7) build all 8) test build (no autogen, no boot files) 9) status 10) update Clover 11) show diff 12) open CloverV2/EFI/CLOVER directory 13) update Clover (reset changes) 14) clean BaseTools 15) quit Please enter your choice: (7) ................................................. buildme, Clover r5124 (SHA: a2ffdf864) TOOLCHAIN: GCC53 (override example: './buildme XCODE8') 1) build Clover 2) build Clover with HFSPlus 3) make pkg 4) make app 5) make app (with Clover) 6) make iso 7) build all 8) test build (no autogen, no boot files) 9) status 10) update Clover 11) show diff 12) open CloverV2/EFI/CLOVER directory 13) update Clover (reset changes) 14) clean BaseTools 15) quit Please enter your choice: (15) Again.. This time I knew something was missing (OcQuirks.efi), but I tried installing it over the old one and it still works fine. I didn't feel any difference. But the solved DSDT problem does not load at all.

When you get to the OpenCore bootpicker press the space bar to reveal the option to clear the NVram and then clear it a couple of times before booting into macOS using OC for the first time. also make sure you remove RC scripts if you were using them in clover or your have all sorts of trouble.

I don’t know if you are coming from Audiogod’s Clover EFI or another. If it’s not Audiogod’s then make sure to check the /library/extensions folder for kexts that could or should be (re)moved. (Thinking of fakesmc for one).

I've got one problem i had to use cpufriend.kext in order to get hibernation/wake on a chinese x99 board with a 2678 v3 xeon processor but once it resumes from wake up, the processor wont reach the turbo frecuency