Clover General discussion

[Matgen84]

Hi @Jief_Machak @Slice

I build latest r5137 commit  a634a82. Using USB drive,  I test a new config.plist called config-wifi.plist. Strange behavior appears: what is ':4'

 

• Clover detected an error from Clover GUI

Spoiler

 

• The same tool from local repo: no error

Spoiler

 

 

Clover GUI shows up 'Boot macOS Big Sur via Preboot' instead of 'Boot macOS Monterey via Preboot'

 

Spoiler

 

2021-07-05_14-15_BOOTX64.EFI.log

Edited July 5, 2021 by Matgen84

[kushwavez]

It says "Boot Mac OS BigSur via Preboot" because your drive's name is "BigSur"

 

The already defined tag means that it is added by the first config.plist, then the new one with new values are overwriting the defined value. It is a cosmetic bug.

[Matgen84]

53 minutes ago, kushwavez said:

It says "Boot Mac OS BigSur via Preboot" because your drive's name is "BigSur"

 

The already defined tag means that it is added by the first config.plist, then the new one with new values are overwriting the defined value. It is a cosmetic bug.

 

My drive is named 'Monterey' not BigSur. I have rename it since Beta 1   Strange indeed. Clover Keep the old name ! Right  Tag ':4' is a bug, but not cosmetic. I think there is a problem in configmanager, see commits on July, 1 @Jief_Machak or @Slice will find a solution.

 

Spoiler

 

Edited July 5, 2021 by Matgen84

[chris1111]

34 minutes ago, Matgen84 said:

 

My drive is named 'Monterey' not BigSur  Strange indeed ! Right  Tag ':4' is a bug, but not cosmetic. I think there is a problem in configmanager, see commits on July, will find a solution.

 

  Reveal hidden contents

 

No issue latest Compile Clover here

My drive is SSD Monterey 

 

[Guest 5T33Z0]

I have a question about csr-active config. For Monterey I use EF0F0000 in OpenCore. Would that be 0xFEF in Clover or what is the correct value to disable SIP?

[Matgen84]

13 hours ago, chris1111 said:

No issue latest Compile Clover here

My drive is SSD Monterey 

 

 

 

Thanks  After some investigations, I think the problem is occured when I rename my BigSur'HDD to Monterey via Disk Utility (Finder). Maybe System/Preference/Start Up disk keep the old name  I don't know what is the correct way, to rename internal macOS drive, correctly o avoid this kind of issue. Now, my two USB key (Clover and Opencore) can't boot macOS Monterey 

 

EDIT: I upgrade from Big Sur 11.5 Beta to Monterey Beta 2. Not a clean install

Edited July 6, 2021 by Matgen84

[LockDown]

4 hours ago, 5T33Z0 said:

Would that be 0xFEF in Clover

Yes

[Matgen84]

Hi @Slice @Jief_Machak

I've got few problem to boot macOS Monterey Beta via my USB stick (Z390 Config). Clover r5137 commit e12aefe81

Either the USB installation pen drive or the hard drive via the USB stick.

672:606  0:015  OCOS: OS set: <null> macOS 11.0
672:620  0:013  OCOS: OS set: Apple Inc. macOS 11.0

Let me know if there is a solution. Please

2021-07-06_08-57_BOOTX64.EFI.log

Edited July 6, 2021 by Matgen84

[iCanaro]

@Jief_Machak @Slice currently that version of opencore is in use in the clover engine?

[Slice]

12 hours ago, 5T33Z0 said:

I have a question about csr-active config. For Monterey I use EF0F0000 in OpenCore. Would that be 0xFEF in Clover or what is the correct value to disable SIP?

I updated Monterey beta 1 to Monterey beta 2 with Clover 5137 having csr-active-config=0x285. Other bits are surplus.

 

2 hours ago, iCanaro said:

@Jief_Machak @Slice currently that version of opencore is in use in the clover engine?

If you carefully see changes in OpenCore then you may notice there are nothing essencial since 0.6.0 which is partially used in modern Clover.

We are tracing OpenCore changes to apply significant events.

Again, Clover uses 10% of OpenCore. 

[Allan]

4 minutes ago, naiclub said:

I tried the latest OC version 0.7.1 but I'm not as happy as beta 0.7.1 before that, the latest version, booting into the icon selection page is very slow with slow.

Problems with OC has nothing to do with Clover right? Or am I wrong? 🤔

[Guest 5T33Z0]

4 hours ago, Slice said:

If you carefully see changes in OpenCore then you may notice there are nothing essencial since 0.6.0 which is partially used in modern Clover.

We are tracing OpenCore changes to apply significant events.

Again, Clover uses 10% of OpenCore. 

 

"10 per cent" which provide all the memory fixes in the form of OpenRuntime.efi which make up 90 % of what makes Hackintoshes work.

[jsl2000]

On 7/5/2021 at 5:10 PM, iCanaro said:

@SavageAUS if you want to try these kerneltopatches, they should be the exact translation of those of OC.
NB: anyone can check them if there are errors or forgetfulness

 

CLOVER_17H_19H_patches_All 3.plist 26.9 kB · 6 downloads

I double-checked the quirks in my AMD hack and they are identical between Clover and OC
With MONTEREY Boot OC, Clover doesn't start anything with the translation of the latest kerneltopatch

Eventually my Ryzen 1700X can boot by Clover 5137 at Monterey beta1 now.

Please try my clover-config.plist

 

config.plist.zip

Edited July 7, 2021 by jsl2000

[iCanaro]

from me does not work, the debug log with monterey signals me 2 kerneltopatch borked, while with big sur borked they become 3

 

PS: use Clover 5138

Edited July 7, 2021 by iCanaro

[iCanaro]

8 hours ago, Slice said:

If you carefully see changes in OpenCore then you may notice there are nothing essencial since 0.6.0 which is partially used in modern Clover.

We are tracing OpenCore changes to apply significant events.

Again, Clover uses 10% of OpenCore. 

my question was to try to figure out what doesn't work with kerneltopatches for AMD; since with OC 0.6.5 monterey starts correctly on my signature rig ryzen, I would not want it to be related to the OC engine that is currently used with Clover.
I hypotise that with intel there are no problems, in fact I installed monterey with Clover on my hacks Z170 and Z370, while with AMD and the current 46 patches you have problems

[Slice]

7 hours ago, 5T33Z0 said:

 

"10 per cent" which provide all the memory fixes in the form of OpenRuntime.efi which make up 90 % of what makes Hackintoshes work.

Remember that OpenRuntime.efi is improved OsxAptioFix. Thanks vit9696 for the improvements.

 

Legacy boot (through boot6) can do fine working macOS without OpenRuntime and AptioFixes at all.

[iCanaro]

As a plist editor I normally use PlistEdit Pro, I tried to change and used PlistEdPlus, I retranslated OC kerneltopatches for Clover, but in the end the result is always identical, from the debuglog of the patches are borked

 

 

take, for example, the one highlighted in yellow, which is the 10 in the last kerneltopatch and turns out to be borked

 

 

while the same patches in the previous version of kerneltopatchs work regularly

 

 

I hope the developers can help, I leave debug log and config with inside commented on the previous kerneltopatch that work for mojave, catalina and big sur 2021-07-07_09-40_CLOVERX64.efi_OK.log

 

2021-07-07_09-55_CLOVERX64.efi_NOK.log

config-TEST6 noSMBIOS.plist

[jsl2000]

52 minutes ago, iCanaro said:

As a plist editor I normally use PlistEdit Pro, I tried to change and used PlistEdPlus, I retranslated OC kerneltopatches for Clover, but in the end the result is always identical, from the debuglog of the patches are borked

 

 

take, for example, the one highlighted in yellow, which is the 10 in the last kerneltopatch and turns out to be borked

 

 

while the same patches in the previous version of kerneltopatchs work regularly

 

 

I hope the developers can help, I leave debug log and config with inside commented on the previous kerneltopatch that work for mojave, catalina and big sur 2021-07-07_09-40_CLOVERX64.efi_OK.log

 

2021-07-07_09-55_CLOVERX64.efi_NOK.log

config-TEST6 noSMBIOS.plist

In the past I had the similar problem in which only by Clover booting Big Sur & Monterey partitions always showing 10.13.6 instead of 11.x & 12.0.

After edit /Preboot/......../System/Library/CoreServices/SystemVersion.plist to respective correct versions no more such an issue occured again.

Please double check whether your system versions are totally correct or not.

Just one of the solution which worked for me.

[Slice]

2 hours ago, iCanaro said:

As a plist editor I normally use PlistEdit Pro, I tried to change and used PlistEdPlus, I retranslated OC kerneltopatches for Clover, but in the end the result is always identical, from the debuglog of the patches are borked

 

 

take, for example, the one highlighted in yellow, which is the 10 in the last kerneltopatch and turns out to be borked

 

 

while the same patches in the previous version of kerneltopatchs work regularly

 

 

I hope the developers can help, I leave debug log and config with inside commented on the previous kerneltopatch that work for mojave, catalina and big sur 2021-07-07_09-40_CLOVERX64.efi_OK.log

 

2021-07-07_09-55_CLOVERX64.efi_NOK.log

config-TEST6 noSMBIOS.plist

As I said a page ago MaskFind must not be an empty array. It length must be same as Find length.

If you not care then remove the line from config. As well as MaskReplace.

[iCanaro]

1 hour ago, jsl2000 said:

In the past I had the similar problem in which only by Clover booting Big Sur & Monterey partitions always showing 10.13.6 instead of 11.x & 12.0.

After edit /Preboot/......../System/Library/CoreServices/SystemVersion.plist to respective correct versions no more such an issue occured again.

Please double check whether your system versions are totally correct or not.

Just one of the solution which worked for me.

it's not my case now, systemversion in preboot is OK

41 minutes ago, Slice said:

As I said a page ago MaskFind must not be an empty array. It length must be same as Find length.

If you not care then remove the line from config. As well as MaskReplace.

it was something I had already done in past attempts, but I can still try again now 

[Slice]

2 hours ago, MifJpn said:

like this?

If this like IP Mask,FFFFF…?
 

If you want exact coincidence then FFFFFFF

If you want first byte exactly and second arbitrary then FF00

If you want all bites arbitrary then 00000000

In the case FEFFFF there will be arbitrary bit 0 in the first byte. And so on.

Note that OC offers only byte comparing while Clover offers comparing bit by bit.

[Slice]

Instruction here

https://www.insanelymac.com/forum/topic/304530-clover-change-explanations/?do=findComment&comment=2692774

https://www.insanelymac.com/forum/topic/304530-clover-change-explanations/?do=findComment&comment=2719026

 

and next posts

[Allan]

Hey @Slice, how are you? I have a doubt.

 

It is possible to install Clover only copying/paste the files for the EFI partition, I mean doing this like "OC style".

And, we lose something if we don't use the .pkg? Is obligatory to use it?

 

So, we can use Clover without this? 👇

/Volumes/EFI/EFI/CLOVER/drivers64UEFI/EmuVariableUefi-64.efi
/Volumes/EFI/nvram.plist
/etc/rc.clover.lib
/etc/rc.boot.d/10.save_and_rotate_boot_log.local
/etc/rc.boot.d/20.mount_ESP.local
/etc/rc.boot.d/70.disable_sleep_proxy_client.local.disabled
/etc/rc.shutdown.d/80.save_nvram_plist.local

/etc/rc.boot.d
/etc/rc.shutdown.d

Thank you 😃

 

[Slice]

1 hour ago, Allan said:

Hey @Slice, how are you? I have a doubt.

 

It is possible to install Clover only copying/paste the files for the EFI partition, I mean doing this like "OC style".

And, we lose something if we don't use the .pkg? Is obligatory to use it?

 

So, we can use Clover without this? 👇

/Volumes/EFI/EFI/CLOVER/drivers64UEFI/EmuVariableUefi-64.efi
/Volumes/EFI/nvram.plist
/etc/rc.clover.lib
/etc/rc.boot.d/10.save_and_rotate_boot_log.local
/etc/rc.boot.d/20.mount_ESP.local
/etc/rc.boot.d/70.disable_sleep_proxy_client.local.disabled
/etc/rc.shutdown.d/80.save_nvram_plist.local

/etc/rc.boot.d
/etc/rc.shutdown.d

Thank you 😃

 

It depends on UEFI or legacy BIOS.

If you have modern UEFI BIOS (since SandyBridge) then you can install Clover by just copy/paste EFI folder  or if you already have it then just replacing CLOVERX64.EFI.

EmuVariableUefi driver will works with UEFI BIOS having no NVRAM support. But I propose new OpenRuntime.efi already cured this and so EmuVariableUefi is deprecated on most computers.

/etc/rc.* are used only on legacy computers.

[Allan]

1 hour ago, Slice said:

It depends on UEFI or legacy BIOS.

If you have modern UEFI BIOS (since SandyBridge) then you can install Clover by just copy/paste EFI folder  or if you already have it then just replacing CLOVERX64.EFI.

EmuVariableUefi driver will works with UEFI BIOS having no NVRAM support. But I propose new OpenRuntime.efi already cured this and so EmuVariableUefi is deprecated on most computers.

/etc/rc.* are used only on legacy computers.

 

Nice good to know!
Thank you so much! 😉