Jump to content

Clover General discussion

ErmaC

By ErmaC,
in Clover

 Share
30,171 posts in this topic

Recommended Posts

Sherlocks
Sherlocks
Posted
Posted (edited)

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
Link to comment
Share on other sites
iCanaro
iCanaro
Posted
Posted

@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
Link to comment
Share on other sites
Slice
Slice
Posted
Posted
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
Link to comment
Share on other sites
iCanaro
iCanaro
Posted
Posted
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

Link to comment
Share on other sites
jsl2000
jsl2000
Posted
Posted
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
Link to comment
Share on other sites
rramon
rramon
Posted
Posted (edited)

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
Link to comment
Share on other sites
Slice
Slice
Posted
Posted
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
Link to comment
Share on other sites
iCanaro
iCanaro
Posted
Posted
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?

Link to comment
Share on other sites
naiclub
naiclub
Posted
Posted
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..

Link to comment
Share on other sites
naiclub
naiclub
Posted
Posted
1 hour ago, rramon said:

So I do have to disable all other drives except the one I want to install Windows onto in BIOS?

All you have said is correct. After the installation is complete, then come to activate again.

  • Like 1
  • Thanks 1
Link to comment
Share on other sites
jsl2000
jsl2000
Posted
Posted (edited)
5 hours ago, iCanaro said:

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

Good news !

After add Monterey specific patches to my original working config.plist it can boot both Big Sur and Monterey now to desktop smoothly.

But my Ryzen hackintosh had the issues of VoodooTSCSyncAMD-8-Core.kext and SmallTreeIntel82576.kext at Monterey only.

[Edit]

I found that Clover boots Monterey (system partition) while OpenCore boots Monterey (Data partition) by their respective names in Preboot.

config-Monterey beta1-jslai.plist

Edited by jsl2000
  • Like 3
  • Thanks 1
Link to comment
Share on other sites
SavageAUS
SavageAUS
Posted
Posted
Good news !
After add Monterey specific patches to my original working config.plist it can boot both Big Sur and Monterey now to desktop smoothly.
But my Ryzen hackintosh had the issues of VoodooTSCSyncAMD-8-Core.kext and SmallTreeIntel82576.kext at Monterey only.
[Edit]
I found that Clover boots Monterey (system partition) while OpenCore boots Monterey (Data partition) by their respective names in Preboot.
config-Monterey beta1-jslai.plist

I’ll give your patches a crack when I get a chance on my AMD rig.


Sent from my iPhone using Tapatalk
Link to comment
Share on other sites
iCanaro
iCanaro
Posted
Posted (edited)
9 hours ago, jsl2000 said:

Good news !

After add Monterey specific patches to my original working config.plist it can boot both Big Sur and Monterey now to desktop smoothly.

But my Ryzen hackintosh had the issues of VoodooTSCSyncAMD-8-Core.kext and SmallTreeIntel82576.kext at Monterey only.

[Edit]

I found that Clover boots Monterey (system partition) while OpenCore boots Monterey (Data partition) by their respective names in Preboot.

config-Monterey beta1-jslai.plist 23.65 kB · 6 downloads

 

unfortunately it doesn't work for me, it doesn't start any macOS.... I can't understand why the complete translation of the OC patches (which from me work on mojave, catalina and big sur, I have not yet installed monterey on AMD) with Clover instead does not work and does not start anything.
I did an experiment, in my patches I added yours, all you need to monterey and in mactOS I put 12 12.x and big sur starts, I just have to install monterey betya 1 and see what happens
if you try them too and tell me if they go to you

 

 

 

Edited by iCanaro
  • Like 1
Link to comment
Share on other sites
jsl2000
jsl2000
Posted
Posted (edited)
4 hours ago, iCanaro said:

your i don't think

It's from fabiosun:

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

I have modified his config.plist plus my original one.

Did your hackintosh stop after completetion of kernel patching (+++++++++++++++ appears) ?

After update Clover to 5137 version mine can boot to desktop, but whole system was not so stable.

Quite frequent frozen at desktop.

Edited by jsl2000
Link to comment
Share on other sites
SavageAUS
SavageAUS
Posted
Posted
 
unfortunately it doesn't work for me, it doesn't start any macOS.... I can't understand why the complete translation of the OC patches (which from me work on mojave, catalina and big sur, I have not yet installed monterey on AMD) with Clover instead does not work and does not start anything.
I did an experiment, in my patches I added yours, all you need to monterey and in mactOS I put 12 12.x and big sur starts, I just have to install monterey betya 1 and see what happens
if you try them too and tell me if they go to you
 
 
CLOVER_17H_19H_TEST-iCan.plist

Have you managed to install Monterey yet?


Sent from my iPhone using Tapatalk
Link to comment
Share on other sites
 Share
Go to topic listing
×
×
  • Create New...