Jump to content
30960 posts in this topic

Recommended Posts

I found peace :angelo_non: with this KernelToPatch for AMD 17H 19H:

No waring at boot and the same using validator
I can boot mojave, catalina, big sur 11.4 e 11.5 and maybe can boot high sierra, but i have no way to test it there anymore

 

CLOVER_AMD_17_19_H_35Patch_HS_MOJ_CAT_BSg.plist.zip

 

It also starts BigSur by deleting the 3 patches that caused the warnings :isterico:

  • Like 4
14 hours ago, Matgen84 said:

Maybe we need some explanation on this point and Clover's ability to convert OC patches.

 

I would also be interested in this.

 

More specifically, I am trying to convert OpenCore's IOHIDFamily patch to work in Clover (fixes broken USB Mouse and Keyboard function in Big Sur on certain legacy machines)...

 


Код:

<dict>
                <key>Base</key>
                <string>_isSingleUser</string>
                <key>Count</key>
                <integer>1</integer>
                <key>Enabled</key>
                <true/>
                <key>Find</key>
                <data></data>
                <key>Identifier</key>
                <string>com.apple.iokit.IOHIDFamily</string>
                <key>Limit</key>
                <integer>0</integer>
                <key>Mask</key>
                <data></data>
                <key>MaxKernel</key>
                <string></string>
                <key>MinKernel</key>
                <string>20.0.0</string>
                <key>Replace</key>
                <data>uAEAAADD</data>
                <key>ReplaceMask</key>
                <data></data>
                <key>Skip</key>
                <integer>0</integer>
            </dict>

As you can see, the Find entry for the above patch is left empty so Clover is not happy 😔.

  • Thanks 2
12 hours ago, fusion71au said:

 

I would also be interested in this.

 

More specifically, I am trying to convert OpenCore's IOHIDFamily patch to work in Clover (fixes broken USB Mouse and Keyboard function in Big Sur on certain legacy machines)...

 



Код:

<dict>
                <key>Base</key>
                <string>_isSingleUser</string>
                <key>Count</key>
                <integer>1</integer>
                <key>Enabled</key>
                <true/>
                <key>Find</key>
                <data></data>
                <key>Identifier</key>
                <string>com.apple.iokit.IOHIDFamily</string>
                <key>Limit</key>
                <integer>0</integer>
                <key>Mask</key>
                <data></data>
                <key>MaxKernel</key>
                <string></string>
                <key>MinKernel</key>
                <string>20.0.0</string>
                <key>Replace</key>
                <data>uAEAAADD</data>
                <key>ReplaceMask</key>
                <data></data>
                <key>Skip</key>
                <integer>0</integer>
            </dict>

As you can see, the Find entry for the above patch is left empty so Clover is not happy 😔.

I think for Clover it will be

               <dict>
                    <key>Procedure</key>
                    <string>_isSingleUser</string>
                    <key>Count</key>
                    <integer>1</integer>
                    <key>Disabled</key>
                    <false/>
                    <key>RangeFind</key>
                    <integer>10</integer>
                    <key>Find</key>
                    <data>AAAAAAAA</data>
                    <key>Name</key>
                    <string>com.apple.iokit.IOHIDFamily</string>
                    <key>Mask</key>
                    <data>AAAAAAAA</data>
                    <key>MinKernel</key>
                    <string>20.0.0</string>
                    <key>Replace</key>
                    <data>uAEAAADD</data>
                    <key>ReplaceMask</key>
                    <data>////////</data>
                    <key>Skip</key>
                    <data>AAA=</data>
                </dict>

 

  • Like 1
  • Thanks 2
1 hour ago, Slice said:

I think for Clover it will be

 

Thanks Slice.

 

The following IOHIDFamily Clover patch worked for me in Big Sur (after also checking your other post in the Clover Changes thread and verifying my config.plist with CloverConfigPlistValidator0.7)...

			<dict>
				<key>Comment</key>
				<string>Enable USB HID in Big Sur</string>
				<key>Procedure</key>
				<string>_isSingleUser</string>
				<key>Count</key>
				<integer>1</integer>
				<key>Disabled</key>
				<false/>
				<key>RangeFind</key>
				<integer>10</integer>
				<key>Find</key>
				<data>AAAAAAAA</data>
				<key>Name</key>
				<string>com.apple.iokit.IOHIDFamily</string>
				<key>MaskFind</key>
				<data>AAAAAAAA</data>
				<key>MatchOS</key>
				<string>11.x.x</string>
				<key>Replace</key>
				<data>uAEAAADD</data>
				<key>MaskReplace</key>
				<data>////////</data>
				<key>Skip</key>
				<integer>0</integer>
			</dict>

Note:  I changed from MinKernel=20.0.0 (OC config) to MatchOS=11.x.x (Clover config) and Mask-->MaskFind, ReplaceMask==>MaskReplace.

  • Like 4
On 6/21/2021 at 8:34 PM, fusion71au said:

 

Thanks Slice.

 

The following IOHIDFamily Clover patch worked for me in Big Sur (after also checking your other post in the Clover Changes thread and verifying my config.plist with CloverConfigPlistValidator0.7)...


			<dict>
				<key>Comment</key>
				<string>Enable USB HID in Big Sur</string>
				<key>Procedure</key>
				<string>_isSingleUser</string>
				<key>Count</key>
				<integer>1</integer>
				<key>Disabled</key>
				<false/>
				<key>RangeFind</key>
				<integer>10</integer>
				<key>Find</key>
				<data>AAAAAAAA</data>
				<key>Name</key>
				<string>com.apple.iokit.IOHIDFamily</string>
				<key>MaskFind</key>
				<data>AAAAAAAA</data>
				<key>MatchOS</key>
				<string>11.x.x</string>
				<key>Replace</key>
				<data>uAEAAADD</data>
				<key>MaskReplace</key>
				<data>////////</data>
				<key>Skip</key>
				<integer>0</integer>
			</dict>

Note:  I changed from MinKernel=20.0.0 (OC config) to MatchOS=11.x.x (Clover config) and Mask-->MaskFind, ReplaceMask==>MaskReplace.

I want to know what this code is for, thank you very much.

  • Like 1
7 hours ago, naiclub said:

I want to know what this code is for, thank you very much.

 

You can try the patch if your attached USB mouse or keyboard stop working when you try to update your system to Big Sur/Monterey (Apple removed legacy USB support on old hardware and someone noticed it still worked if macOS was booted in single user mode.  The patch forces single user mode so your USB HID devices still work).  From Dortania's troubleshooting guide for Big Sur...

 

"For certain legacy systems, you may notice that while the USB ports work your HID-based devices such as the keyboard and mouse may be broken".

 

 

  • Like 3
7 hours ago, MifJpn said:

Hello everyone.
I hope it's because of my mind ...
With this commit (f424a77c25027e4a5395fdb57287affae51f4ac5), I feel like Monterey has taken a long time to start. (I feel that the seek bar under the Apple mark does not stretch easily after the characters of Verbose boot are displayed.)
I don't use C3 Latency at all, and Big Sur is the same time as before, so shouldn't I care too much?

Thank you.

 

 

try the new commit

https://github.com/CloverHackyColor/CloverBootloader/commit/e12aefe81663d9dcfd2d91ec530010b4c61bf1ba

Edited by iCanaro
  • Like 1
  • Thanks 1

Hi @Slice and everyone, thanks again for your continuing efforts.

 

WIth a well-working Lenovo S145-14iWL configuration and Clover r5136 used for some time with Catalina, I decided to update to Big Sur. I thus downloaded the installer and let the system update like a real Mac, since my boot process was now smooth.

 

However, I noticed that after updating to 11.3.1 and then to 11.4.0 that Clover r5136 did not show the correct boot icon, or detect the correct partition or container (or whatever it is the name) and I was forced to press F3 to reveal drives and use the "Boot Mac OS from Preboot" entry.

 

So I decided to do a clean installation, erased NVMe via Ubuntu and with Big Sur USB installer and same Clover configuration + r5136 I did the installation effort. I had hopes this would be fixed, but no; I am still forced to use F3 and select Preboot entry.

 

As I do want to remain with Clover because I finally managed to make this a working hack, what kind of logs may you need to help me debug this problem?

 

Does it have to do with Scan key setting? Do I need a Custom Entry for Preboot, then?


For Big Sur, is it expected this Preboot to be used? It may have been replied many pages ago, so I apologise if I missed it, but your help is appreciated. Thank you.

config-lenovo.plist

Edited by MacKonsti
2 hours ago, Hervé said:

Guys, please do not pollute this Clover dev thread with TPM2.0/Win11 matters. It's totally unrelated, nothing to do with Clover really. If need be, please open up a dedicated thread on the matter where existing or future workarounds, alternatives and solutions may be discussed.

@PG7 and @Matgen84 your post talking about Win11 was moved to the Windows 11 Discussion thread.

 

😃

  • Thanks 1
Hi [mention=112217]Slice[/mention] and everyone, thanks again for your continuing efforts.
 
WIth a well-working Lenovo S145-14iWL configuration and Clover r5136 used for some time with Catalina, I decided to update to Big Sur. I thus downloaded the installer and let the system update like a real Mac, since my boot process was now smooth.
 
However, I noticed that after updating to 11.3.1 and then to 11.4.0 that Clover r5136 did not show the correct boot icon, or detect the correct partition or container (or whatever it is the name) and I was forced to press F3 to reveal drives and use the "Boot Mac OS from Preboot" entry.
 
So I decided to do a clean installation, erased NVMe via Ubuntu and with Big Sur USB installer and same Clover configuration + r5136 I did the installation effort. I had hopes this would be fixed, but no; I am still forced to use F3 and select Preboot entry.
 
As I do want to remain with Clover because I finally managed to make this a working hack, what kind of logs may you need to help me debug this problem?
 
Does it have to do with Scan key setting? Do I need a Custom Entry for Preboot, then?

For Big Sur, is it expected this Preboot to be used? It may have been replied many pages ago, so I apologise if I missed it, but your help is appreciated. Thank you.
config-lenovo.plist

You will need to create a custom entry for the preboot entry and rename it to what you want.


Sent from my iPhone using Tapatalk
  • Like 1
1 hour ago, SavageAUS said:

You will need to create a custom entry for the preboot entry and rename it to what you want.

I agree @SavageAUS but I have a hard time making the Custom entry appear... this method quoted by many places (reported in Clover's Git Hub issues) does not seem to work on my hack.

Has anyone managed to successfully create a Custom Entry with latest Clover e.g. r5136? Please can you either point me to your message or share your method? When looking for "Preboot" information in the log, it does produce results for ApfsContainerUUID, ApfsFileSystemUUID and APFSTargetUUID but using the 2 latter onces for a custom entry does not display the custom icon :( Thanks in advance.

long time no see. clover team.

i want to report this part.

here is result from ccpv

sherlocks@SherloccBookPro ~ % ccpv /Volumes/EFI/EFI/CLOVER/config.plist

Warning: Custom has to be defined if Inject is defined in dict '/Graphics/EDID:810'.

sherlocks@SherloccBookPro ~ %

 

Custom has to be defined

-> not correct.

 

clover support productid and vendorid without custom edid.

i'm using this for long time.

        <key>EDID</key>
        <dict>
            <key>Inject</key>
            <true/>
            <key>ProductID</key>
            <string>0x9a3b</string>
            <key>VendorID</key>
            <string>0x1006</string>

Spoiler

here is clover log

0:106  0:006  === [ Starting Clover ] =========================
0:106  0:000  Now is 29.06.2021,  12:07:40 (GMT)
0:106  0:000  Starting Clover revision: 5137 (master, commit cc561f87d) on Phoenix Technologies Ltd. EFI
0:106  0:000  Build id: 20210616212122-cc561f8-5137-dirty
0:106  0:000  Build with: [Args: -D NO_GRUB_DRIVERS_EMBEDDED -D LESS_DEBUG -t GCC53 | --cmd-len=50000 -D NO_GRUB_DRIVERS_EMBEDDED -D LESS_DEBUG --conf=/Users/sergey/src/CloverBootloader/Conf -D USE_LOW_EBDA -a X64 -b RELEASE -t GCC53 -n 5 | OS: 12]
0:106  0:000  SimpleTextEx Status=Success

~~~

9:389  0:000  === [ RestSetup macOS ] =========================
9:389  0:000  EdidDiscovered size=128
9:389  0:000  --- Discovered EDID Table size:128
9:389  0:000  000  |  00  FF  FF  FF  FF  FF  FF  00  30  E4
9:389  0:000  010  |  76  04  00  00  00  00  00  18  01  04
9:389  0:000  020  |  A5  1F  11  78  02  07  B5  A0  5B  53
9:389  0:000  030  |  90  26  0C  50  54  00  00  00  01  01
9:389  0:000  040  |  01  01  01  01  01  01  01  01  01  01
9:389  0:000  050  |  01  01  01  01  29  36  80  A0  70  38
9:389  0:000  060  |  1F  40  30  20  55  00  35  AE  10  00
9:389  0:000  070  |  00  19  00  00  00  00  00  00  00  00
9:389  0:000  080  |  00  00  00  00  00  00  00  00  00  00
9:389  0:000  090  |  00  00  00  FE  00  4C  47  20  44  69
9:389  0:000  100  |  73  70  6C  61  79  0A  20  20  00  00
9:389  0:000  110  |  00  FE  00  4C  50  31  34  30  57  46
9:389  0:000  120  |  34  2D  53  50  41  31  00  42
9:389  0:000      VendorID = 0xe430 changed to 0x1006
9:389  0:000      ProductID = 0x0476 changed to 0x9a3b
9:389  0:000  --- Patched EDID Table size:128
9:389  0:000  000  |  00  FF  FF  FF  FF  FF  FF  00  06  10
9:389  0:000  010  |  3B  9A  00  00  00  00  00  18  01  04
9:389  0:000  020  |  A5  1F  11  78  02  07  B5  A0  5B  53
9:389  0:000  030  |  90  26  0C  50  54  00  00  00  01  01
9:389  0:000  040  |  01  01  01  01  01  01  01  01  01  01
9:389  0:000  050  |  01  01  01  01  29  36  80  A0  70  38
9:389  0:000  060  |  1F  40  30  20  55  00  35  AE  10  00
9:389  0:000  070  |  00  19  00  00  00  00  00  00  00  00
9:389  0:000  080  |  00  00  00  00  00  00  00  00  00  00
9:389  0:000  090  |  00  00  00  FE  00  4C  47  20  44  69
9:389  0:000  100  |  73  70  6C  61  79  0A  20  20  00  00
9:389  0:000  110  |  00  FE  00  4C  50  31  34  30  57  46
9:389  0:000  120  |  34  2D  53  50  41  31  00  14

 

 

but show message when enter clover bootloader.

can you consider this case?

 

https://github.com/CloverHackyColor/CloverBootloader/blob/master/rEFIt_UEFI/Settings/ConfigPlist/Config_Graphics.h#L96

Edited by Sherlocks
  • Like 2
  • Thanks 1

@Slice if you kindly check the conversion of the patches from OC to Clover, I did it from scratch a couple of times, checked and double-checked but no macOS starts on my AMD, it seems that the patches are not loaded

 

CLOVER_patches_17H19H_Monterey_beta1.plistOC_patches_17H_19H.plist

 

this should be the correct table for the conversion

1753293274_CLOVEROCTabellaConversione.thumb.png.48329b615749de5555ecde4cd7bd7d7f.png

 

so I hope I did something wrong; otherwise it needs some tweaking of the patches, or something to fix in Clover to load / activate the patches :thanks_speechbubble:

  • Like 1
4 hours ago, iCanaro said:

@Slice if you kindly check the conversion of the patches from OC to Clover, I did it from scratch a couple of times, checked and double-checked but no macOS starts on my AMD, it seems that the patches are not loaded

 

CLOVER_patches_17H19H_Monterey_beta1.plist 36.01 kB · 2 downloads OC_patches_17H_19H.plist 36.86 kB · 1 download

 

this should be the correct table for the conversion

1753293274_CLOVEROCTabellaConversione.thumb.png.48329b615749de5555ecde4cd7bd7d7f.png

 

so I hope I did something wrong; otherwise it needs some tweaking of the patches, or something to fix in Clover to load / activate the patches :thanks_speechbubble:

There is common mistake as I already mentioned.

For Clover Find string can't be zero length. It length must be the same as  Replace length.

If you are not going to search something other then the procedure start then use Find = <00 > and MaskFind = <00 >. See length of Replace. And MaskReplace=<FF> if you want to replace.

You also may restrict RangeFind  as 10 to speedup the search.

And sure that Enabled=Yes is converted to Disabled=NO, and the line can be omitted as default.

  • Like 2
  • Thanks 1
5 hours ago, Slice said:

You also may restrict RangeFind  as 10 to speedup the search.

in a working plist for mojave, catalina and big sur with commented RangeFind # if I activate it, even setting 10 then no macOS starts

5 hours ago, Slice said:

And sure that Enabled=Yes is converted to Disabled=NO, and the line can be omitted as default.

this obviously must be done, but I didn't understand what is meant by:

and the line can be omitted as default

 

5 hours ago, Slice said:

There is common mistake as I already mentioned.

For Clover Find string can't be zero length. It length must be the same as  Replace length.

If you are not going to search something other then the procedure start then use Find = <00 > and MaskFind = <00 >. See length of Replace. And MaskReplace=<FF> if you want to replace.

this was something I had already tried when it was explained, and in fact there are no more warnings, but then as I said earlier, no macOS starts. They start leaving the fields empty and consequently you get the warning at boot, or in my system, by eliminating these KernelToPatch everything works regularly, no warnings, regular start of mojave, catalina and big sur

 

if anyone wants to take a look here

https://www.macos86.it/topic/4913-amd-clover-bootloader-monterey-beta-1-installation-patches/?tab=comments#comment-115745

2 hours ago, Slice said:

Don't leave these fields empty. It will not work.

 

this is my last modified kerneltopatch, some "Procedure" fields are left empty if you kindly check it, indicate any errors and possibly an example base to work on :thanks_speechbubble:

 

CLOVER_patches_17H19H_Monterey_beta1 2.plist

PS: not works

  • Like 1
3 hours ago, iCanaro said:

 

this is my last modified kerneltopatch, some "Procedure" fields are left empty if you kindly check it, indicate any errors and possibly an example base to work on :thanks_speechbubble:

 

CLOVER_patches_17H19H_Monterey_beta1 2.plist 36.6 kB · 3 downloads

PS: not works

Although I have tried to fix the length of MaskFind & MaskReplace it still not bootable at all !

CLOVER_patches_17H19H_Monterey_beta1-jslai.plist

  • Thanks 1

Hi guys,

 

here‘s a question about having to mess around with a working dual boot setup (Windows 10 and macOS) on separate drives:

 

Initially, I installed Windows on a SATA drive, checked if everything works, did some undervolting etc. and then installed macOS on a NVME drive. 

 

So far, so good.

 

Unfortunately my Windows Installation is kind of broken by now which means I cannot install the 2021 update through the regular windows update mechanism. Instead, I would need to use Windows Media Creation Tool from inside Windows. My SATA drive will get wiped during the update process which means I will have to install apps, drivers etc. again.

 

Question:

do I have to follow a certain protocol (i.e. disabling the ports/drives macOS is installed onto in BIOS) so that Windows Boot Manager doesn‘t break Clover as the preferable bootloader during the update process?


If would need to install Windows from scratch, what protocol/steps should I follow?

 

Thanks in advance! 😊

Edited by rramon
7 hours ago, iCanaro said:

 

this is my last modified kerneltopatch, some "Procedure" fields are left empty if you kindly check it, indicate any errors and possibly an example base to work on :thanks_speechbubble:

 

CLOVER_patches_17H19H_Monterey_beta1 2.plist 36.6 kB · 4 downloads

PS: not works

Why Count=0?

I have also propose to use more human name for procedures:

instead of "_i386_switch_lbrs" you'd better write "i386_switch_lbrs".

  • Like 1
  • Thanks 1
3 hours ago, Slice said:

Why Count=0?

I have also propose to use more human name for procedures:

instead of "_i386_switch_lbrs" you'd better write "i386_switch_lbrs".

 

OK then I take off the front underscores
Count = 0 is what I find in the OC kernel patch plist, with what value could you change?

removed the initial underscores in proceedings
count = 0 changed to count = 1
count = 1 changed to count = 2

I try to start big sur, but it's not going; if you need here's the log and kerneltopatch tried

 

2021-07-01_20-50_CLOVERX64-5137-d2e652bd4.efi.logCLOVER_patches_17H19H_Monterey_beta1 3.plist

4 hours ago, rramon said:

Hi guys,

 

here‘s a question about having to mess around with a working dual boot setup (Windows 10 and macOS) on separate drives:

 

Initially, I installed Windows on a SATA drive, checked if everything works, did some undervolting etc. and then installed macOS on a NVME drive. 

 

So far, so good.

 

Unfortunately my Windows Installation is kind of broken by now which means I cannot install the 2021 update through the regular windows update mechanism. Instead, I would need to use Windows Media Creation Tool from inside Windows. My SATA drive will get wiped during the update process which means I will have to install apps, drivers etc. again.

 

Question:

do I have to follow a certain protocol (i.e. disabling the ports/drives macOS is installed onto in BIOS) so that Windows Boot Manager doesn‘t break Clover as the preferable bootloader during the update process?


If would need to install Windows from scratch, what protocol/steps should I follow?

 

Thanks in advance! 😊

Question:

do I have to follow a certain protocol (i.e. disabling the ports/drives macOS is installed onto in BIOS) so that Windows Boot Manager doesn‘t break Clover as the preferable bootloader during the update process?

me. yes..

×
×
  • Create New...