Clover General discussion

[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! 😉

[iCanaro]

after various tests, I had only item 10 left that I could not solve, filling the fields with 00 and FF from the debuglog all a success, too bad you keep not starting anything.
It happens the same with kerneltopatchs that start RIG AMD, if you fill in the fields as indicated by the developers, everything is fine on paper, basically the hack no longer starts. 
It will be a problem with translators that you find it difficult to understand.

 

 

2021-07-07_21-10_CLOVERX64.efi.log2021-07-07_21-27_CLOVERX64.efi.log

 

[Slice]

MaskFind should be FFFFFFFFFFFFF

[deeveedee]

I'm reading these latest CLOVER Discussion posts with a big smile as I remember September 7, 2020 when folks were advising Slice to abandon CLOVER to allow developers to focus on a single boot loader.  Well done, CLOVER Team!

Edited July 8, 2021 by tonyx86

[SavageAUS]

I for one have never given up on clover, I’ve switched to OC a few times and then back just purely because of the way clover handles other operating systems…..it doesn’t and that’s the way I like it.


Sent from my iPhone using Tapatalk

[iCanaro]

On 7/8/2021 at 7:13 AM, Slice said:

MaskFind should be FFFFFFFFFFFFF

 

it is funny to observe that an obvious error then in the log does not generate any kerneltopatch borked

but how many F's should there be? Here I count 13, but then once entered and saved, PlistEDPlus reduces them to 12

[Matgen84]

Hi @Slice @Jief_Machak @MifJpn and @all

I want to change this setting in config.plist: replace LastBootedVolume to MY_VOLUME_NAME, for Monterey. What is the correct way to do that ! Because, Clover boot Monterey or Big Sur via Preboot Volume.

Should I use Preboot or Monterey (the name of the main volume and my hard drive). Let me know, please.

[iCanaro]

29 minutes ago, MifJpn said:

The developers of PlistEDPlus have changed </true> to </ true> and </false> to </ false>.
When I asked why, he replied, "It's a cosmetic problem."
So I said, "Everyone will use it if you don't put spaces in true and false."

This editor is very easy to use, but you might want to talk to the developers.

I think the developers will be flexible.

 

For FindMask all zeros, I think it's appropriate to have a "warning" in the log message, since all bits are arbitrary.

 

Thank you.

 

the developer seems to me very careful 

https://www.insanelymac.com/forum/topic/345512-open-source-cross-platform-plist-file-editor-plistedplus/?do=findComment&comment=2762425

 

 

[Slice]

I prefer LastBootedVolume. It works for Monterey as well.

[Matgen84]

38 minutes ago, MifJpn said:

It is OK if you specify this "Disk / Partition UUID" in Boot → Default Volume of Clover as shown below.

 

 

 

Thanks a lot 🙂 If In understand well, you're using physical group volume container !

 

30 minutes ago, Slice said:

I prefer LastBootedVolume. It works for Monterey as well.

 

You are right. But for some reason, I've got problems with LastBootedVolume when I switch between HDD and USB test stick. Or Boot Windows (separate hard drive).

 

Edited July 9, 2021 by Matgen84

[iCanaro]

@Slice would you be so kind as to complete the item (PlistEDPlus) 10, 22, 26, 40 for how it must be done with CLOVER regarding find, maskfind maskreplace, where they are now commented on

 

 

 

CLOVER_patches_17H19H.plist

[Slice]

6 hours ago, Matgen84 said:

Hi @Slice @Jief_Machak @MifJpn and @all

I want to change this setting in config.plist: replace LastBootedVolume to MY_VOLUME_NAME, for Monterey. What is the correct way to do that ! Because, Clover boot Monterey or Big Sur via Preboot Volume.

Should I use Preboot or Monterey (the name of the main volume and my hard drive). Let me know, please.

This is a very complex question. You want non-standard solution if possible.

First priority is users choice during boot. It will be remembered if "LastBootedVolume" is set.

Second priority is NVRAM variable. Not config. Why?

1. Because Startup Preference setting should work no matter what is written in config.

2. Because OS update may and want to change this setting. First reboot into "Install..." and second reboot into "Preboot".

See, I updated Monterey beta 1 to beta 2 by one click in Sofware Update. Clover performs correct reboot first, second and third times during update installation. While OC failed.

If NVRAM is empty and user choose nothing then there will be config setting to be taken into account: UUID of the partition containing boot.efi. For Mojave it will be system partition Fot BigSur and Monterey it must be corresponding Preboot partition. See Clover.log.

Quote

4:999  0:000  - [18]: 'Preboot'
4:999  0:000      ApfsContainerUUID=1EF63EAA-F2D7-4601-ADFC-9979491D69D5
4:999  0:000      ApfsFileSystemUUID=A844613B-12ED-49BF-B559-D72145442E84
4:999  0:000      APFSTargetUUID=0C483552-CAC3-4E72-B7DD-94F16C44C394
5:054  0:054        contentDetails name:Monterey
5:068  0:013        AddLoaderEntry for Volume Name=Preboot, idx=5
5:079  0:010        OSVersion=12.0 
 

5:624  0:000      - found entry 3. 'Boot Mac OS from Monterey via Preboot', Volume 'Preboot', '\0C483552-CAC3-4E72-B7DD-94F16C44C394\System\Library\CoreServices\boot.efi'

diskutil info disk2s2 

   Volume Name:               Preboot
   Mounted:                   Yes
   Mount Point:               /System/Volumes/Preboot

   Disk / Partition UUID:     A844613B-12ED-49BF-B559-D72145442E84

 

[Slice]

7 hours ago, MifJpn said:

It is uncertain whether the following are relevant:

From some previous versions, or in H370 + i7 8700, when updating the OS, I feel that the next candidate to be started indicated by NVRAM is not applied.

In the middle of the update, I think that a boot candidate with "Install" in the name should be selected, but since it is not selected, I manually select it at the time of update.

I apologize for not knowing why and failing to report because it cannot be reproduced without an update.

I can't reproduce because it works for me. May be it depends on my setting "LastBootedVolume"?

[Matgen84]

11 hours ago, Slice said:

This is a very complex question. You want non-standard solution if possible.

First priority is users choice during boot. It will be remembered if "LastBootedVolume" is set.

Second priority is NVRAM variable. Not config. Why?

1. Because Startup Preference setting should work no matter what is written in config.

2. Because OS update may and want to change this setting. First reboot into "Install..." and second reboot into "Preboot".

See, I updated Monterey beta 1 to beta 2 by one click in Sofware Update. Clover performs correct reboot first, second and third times during update installation. While OC failed.

If NVRAM is empty and user choose nothing then there will be config setting to be taken into account: UUID of the partition containing boot.efi. For Mojave it will be system partition Fot BigSur and Monterey it must be corresponding Preboot partition. See Clover.log.

diskutil info disk2s2 

   Volume Name:               Preboot
   Mounted:                   Yes
   Mount Point:               /System/Volumes/Preboot

   Disk / Partition UUID:     A844613B-12ED-49BF-B559-D72145442E84

 

 

@Slice Thanks for these detailed explanations. Since few years, I only use "LatestBootedVolume" for my HDD.

Now, I've another issue: my USB Install Monterey (set to "LatestBootedVolume) with the same EFI folder (5137 (master, commit e12aefe81)) as my HDD, don't boot macOS Monterey HD named Monterey. Or Install macOS 12 Beta.
Stuck at : 

 

[EB LOG:EXITBS:START]
*************************
		-

Debug.log attached. Two tries.
Let me know if you have an idea. I try to found a solution since few days, without success.

 

2021-07-09_16-03_BOOTX64.EFI.log

2021-07-09_16-03_BOOTX64.EFI.log

 

EDIT: Opencore USB stick boot  fine macOS or Installer 

Edited July 10, 2021 by Matgen84

[iCanaro]

17 hours ago, MifJpn said:

Excuse me.

Which version are you using?
With V1.0.59, the number of F in Item10 seems to be maintained.

CLOVER_patches_17H19H.item10.plist 52.24 kB · 1 download

Thank you

I'm sorry if I misunderstand the meaning.

 

with version 1.060 the number of F is brought back to 12, which should be the maximum value that can be inserted, since propertree also warns of the excess number of characters and returns it to 12 in case you enter 13