Jump to content

Clover General discussion


ErmaC
30,167 posts in this topic

Recommended Posts

 

34 minutes ago, Matgen84 said:


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

 

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?-_-

 

Edited by Henry2010
  • Like 1
Link to comment
Share on other sites

29 minutes ago, Matgen84 said:


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

 

Still, nothing of my DSDT is recognized, I missed some corrections
My processor appears in "on this mac" as unknown, it is an ivy bridge (i5-3570K). Should it be some information conflict inserted from my CPU in the system? Does Clover identify a way and OpenCore inside it other information?
I can't even send the debug log, because it is blank "zero bytes"

Link to comment
Share on other sites

2 hours ago, Matgen84 said:

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.

I propose that Clover package install BootloaderChooser :thumbsup_anim:instead, to definitively put an end at this duplication of clover efi file.

 

2 hours ago, JorgeMax said:

I can't even send the debug log, because it is blank "zero bytes"

I'm working on that.

2 hours ago, Henry2010 said:

VirtualSMC.efi since 5124 includes OC now. Maybe that means we need to remove FakeSMC* kexts?

VirtualSMC.efi and FakeSMC.kext has nothing to do with each other. One is loaded at EFI time, one is loaded by kernel.

2 hours ago, Matgen84 said:

I can boot r5124 but my MaLdOn's DSDT failed to display PCI entries in System Info (Mojave). All works fine with r5122.

We'll do "differential" debugging together, like before and we'll find the problem.

 

Hey everyone : don't go too fast :w00t: I can't keep up... When a bug is known, no need to test anymore until one dev says it's fixed !

  • Like 6
  • Haha 1
Link to comment
Share on other sites

2 hours ago, Matgen84 said:


Rigth, BOOTX64.efi est un fichier renommé de CLOVERX64.efi. Lorsque vous mettez à jour Clover à partir de PKG, les deux fichiers sont modifiés vers la nouvelle version. Post debug.log (Notebook) peut-être que les utilisateurs peuvent vous aider.

salut @Jief_Machak

Je mets à jour mon IvyBridge config.plist au nouveau standard. Je peux démarrer r5124 mais le DSDT de mon MaLdOn n'a pas pu afficher les entrées PCI dans System Info (Mojave). Tout fonctionne bien avec r5122.

Des idées ! S'il vous plaît

 

Idem 

 

DSDT no charged

 

HP Envy Reline 23-K030ef 

haswell !!!

 

Clover r5123 = OK

Clover r5124 = no charged DSDT ! 

  • Like 1
  • Haha 1
Link to comment
Share on other sites

28 minutes ago, Jief_Machak said:

I propose that Clover package install BootloaderChooser :thumbsup_anim:instead, to definitively put an end at this duplication of clover efi file.

Spoiler

approved-1.jpg

 

28 minutes ago, Jief_Machak said:
2 hours ago, JorgeMax said:

I can't even send the debug log, because it is blank "zero bytes"

I'm working on that.

:thumbsup_anim:

 

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

:yoji:

PS: a mention for Fusion always precise and clarifying interventions

Edited by iCanaro
  • Like 1
  • Thanks 1
Link to comment
Share on other sites

Im having an issue with 5123 and 5124 loading voodooi2c kexts in the correct order. No matter what my laptop will not boot Catalina with these new versions of Clover. 5122 and all before work normal. Is there a way to set the order of kext loading with the new clover? 

20201004_095702.jpg

Link to comment
Share on other sites

20 hours ago, fusion71au said:

 

The latest version Clover_r5124_a2ffdf864

                          Clover_r5124_086e5682a.pkg

 

On my legacy desktop GA-P55aUD3 (System 2 in signature)...

  Hide contents

screenshot0.thumb.png.e64a04783019f5f02a8537e53593d9fb.pngscreenshot1.thumb.png.6ecfbbd1df692ab043a6ed3b3bbe12b8.png328950681_GAP55aUd3_Clover_r5124_a2ffdf864bootingLion.thumb.png.37f52667116409b459ff84761e09fd56.png

 

Some tips for converting over from old Clover r5122 to new ones with OC 0.6.1 integration in this post.

wow, thank you, fusion71au , for all the great information, screenshots and your edits! Who would've thought.. I was mislead by Clover stopping at 10.11 in kexts/Other.

 

I'll be back at that Laptop in a few days and can report back then. First then need to convert from ole dinosaur Chameleon (remember ^_^?) to Clover. Should be fun.

Edited by BuXb
  • Haha 1
Link to comment
Share on other sites

9 hours ago, Matgen84 said:

@Vampirexx First, a lot of Quirks necessary to new Clover are missing in your config.plist. Have a look to sample.plist :) What is quirks.efi ? you mean Openruntime.efi, I suppose.

And try again.
 

Hi buddy after last clover and setting demo config from https://www.insanelymac.com/applications/core/interface/file/attachment.php?id=358633

 

now i got this kernel panic

083444A2-05D4-4BB1-9C3C-2121925DE371.jpeg

Link to comment
Share on other sites

1 hour ago, SavageAUS said:

PKG does not install on Big Sur. 

 

I meant that for 10.15 and earlier.

But maybe we can make some changes to Clover for 10.16?

 

/usr/local/bin/bdmesg, espfinder, partutil

~/.local/bin/bdmesg, espfinder. partutil

 

/EFI-Backup(s?)

~/.EFI-Backup(s)

Edited by Henry2010
  • Like 2
Link to comment
Share on other sites

@fusion71au

Im a little bit confuse of the changes of your previous posts. can you enlighten me mate :D

 

You said:

Quote

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.

 

@Slice replied:

Quote

I understand now. Fixed. See 086e5682a

 

You edited your post with:

Quote

Edit:  Bug fixed in Clover_r5124_086e5682a.pkg
Edited 5 hours ago by fusion71au 
KernelAndKextPatches behavior restored with r5124_086e5682a.

 

Now my question is...

Which settings is correct now starting at Clover_r5124_086e5682a

Sandy/Ivy > KernelPm=Yes
Haswell+ > KernelXCPM=Yes

OR

 

Sandy/Ivy > AppleIntelCPUPM=Yes
Haswell+ > KernelPm=Yes

 

Link to comment
Share on other sites

20 hours ago, Matgen84 said:

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.

Fixed.

I updated smbios to 16,4 which did not change it so i just set cpu-type in clover to 0x0705

Screen Shot 2020-10-14 at 1.25.59 pm.png

  • Thanks 2
Link to comment
Share on other sites

32 minutes ago, ellaosx said:

@fusion71au

Im a little bit confuse of the changes of your previous posts. can you enlighten me mate :D

 

You said:

 

@Slice replied:

 

You edited your post with:

 

Now my question is...

Which settings is correct now starting at Clover_r5124_086e5682a


Sandy/Ivy > KernelPm=Yes
Haswell+ > KernelXCPM=Yes

OR

 


Sandy/Ivy > AppleIntelCPUPM=Yes
Haswell+ > KernelPm=Yes

 

 

Old (correct) behavior was restored with Clover_r5124_086e5682a

 

ie

Sandy/Ivy > AppleIntelCPUPM=Yes
Haswell+ > KernelPm=Yes

 

The first scenario was applicable only to r5123_641b75e to r5124_a2ffdf8, due to the bug introduced in r5123_641b75e.

  • Like 1
  • Thanks 2
Link to comment
Share on other sites

5 hours ago, mifjpn said:

Sorry for the late reply.
I'm glad that the build is working well on your computer.
For added accuracy, it is recommended to check the build number with the following command.
% cd
% cd CloverBootloader
% git rev-parse --short HEAD

Thanks, I will try

Link to comment
Share on other sites

15 hours ago, Henry2010 said:

 

 

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?-_-

 

I have to explain.

There are two main roads leading to purpose.

One, older way supporting by me and still working:

1. FakeSMC.kext+its plugins (IntelCpuMonitor.kext, RadeonMonitor.kext, ITEIT87x.kext, ACPIMonitor.kext, VoodooBatterySMC.kext, SMIMonitor.kext)

2. SMCHelper.efi driver

Second way, developed by vit9696 and Acidanthera group:

1. VirtualSMC.kext+its plugins (.....). It required Lilu.kext to be also installed.

2. VirtualSMC.efi driver.

 

Don't mix these different ways! Don't jump from one road to another on full speed!

  • Like 7
Link to comment
Share on other sites

12 hours ago, Mirone said:

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.:hysterical:

 
Hello my dear friend, all right?
Tell me what you use your desktop or notebook, let's see if I can help you this time .. :)
What is the problem ...?
I have no problem with the clover 5123 and 5124 all perfect Big Sur and Catalina both on the desktop PC and on the Acer e1 notebook in signature.
 
Link to comment
Share on other sites

3 hours ago, fusion71au said:

 

Old (correct) behavior was restored with Clover_r5124_086e5682a

 

ie

Sandy/Ivy > AppleIntelCPUPM=Yes
Haswell+ > KernelPm=Yes

 

The first scenario was applicable only to r5123_641b75e to r5124_a2ffdf8, due to the bug introduced in r5123_641b75e.

Thank you for clarification.

That said, , what does kernelXCPM now for?

  • Like 1
  • Haha 1
Link to comment
Share on other sites

2 hours ago, ellaosx said:

Thank you for clarification.

That said, , what does kernelXCPM now for?

 

AFAIK, Clover's original KernelXCPM setting works as before to enable Xnu kernel CPU Power Management for unsupported  SandyBridge, IvyBridge, Haswell, and Broadwell-E/EP processors - refer to @stevezheng's post and @Pike R. Alpha's blog for detailed background.

 

Check with @Slice and @Jief_Machak whether they intend to remove the above setting in future, given overlap with OC AppleXcpmExtraMsrs function.

 

 

Edited by fusion71au
correct links
  • Thanks 1
  • Confused 1
Link to comment
Share on other sites

2 minutes ago, fusion71au said:

 

AFAIK, Clover's original kernelXCPM setting works as before for for SandyBridge, IvyBridge, Haswell, and Broadwell-E/EP - refer to @stevezheng's post.

 

Check with @Slice and @Jief_Machak whether they intend to remove the above setting in future, given overlap with OC AppleXcpmExtraMsrs function.

 

 

 

@fusion71au the link to @stevezheng's post don't work: error 404.

Link to comment
Share on other sites

Spoiler

455131537_ScreenShot2563-10-14at18_01_58.thumb.png.97f265eb259ef7ba5681e80ae90c3140.png

That's really what I think.
Left latest version master, commit 086e5682a.
Right version 5122-ocint-3009.3
Apparently There are 2 overlapping lines. It will load the BIOS file instead of the modified file.
The next question is, what will you do next?

  • Confused 1
  • Sad 1
Link to comment
Share on other sites

×
×
  • Create New...