Jump to content

[AMD] Clover Bootloader Monterey Beta (1 ,2,3) installation patches!!


Recommended Posts

  • Supervisor
Posted (edited)

 

1305925552_Screenshot2021-06-30at13_06_23.thumb.png.6688587d640ce4d2dc2442cd747e7bc9.png

 

1536792849_Screenshot2021-06-30at13_48_39.thumb.png.446d375877c55ca62ea44b3ed2ea6602.png

 

14846963_Schermata2021-07-01alle07_52_02.thumb.png.16a3571b5cdfdc9927c7a58155b679e5.png

 

851925477_Schermata2021-06-30alle23_05_01.png.d63e45bd4e3ef95234382673ed8da98c.png

 

1948077380_Screenshot2021-06-30at13_50_58.png.accb3159cf6969e01fbb726046ae8849.png

 

Spoiler

21:049  0:027  GetOSVersion: 
21:067  0:017  Filtering KextPatches:
21:076  0:008   - [00]: com.apple.driver.AppleEthernetAquantiaAqtion (Aquantia BigSur) :: BinPatch :: [OS:  | MatchOS: 11.x,11 | MatchBuild: All] ==> allowed
21:100  0:024   - [01]: com.apple.driver.AppleEthernetAquantiaAqtion (Aquantia Monterey) :: BinPatch :: [OS:  | MatchOS: 12.x12 | MatchBuild: All] ==> allowed
21:118  0:017   - [02]: com.apple.driver.AppleAHCIPort (External icons patch) :: BinPatch :: [OS:  | MatchOS: All | MatchBuild: All] ==> allowed
21:140  0:022   - [03]: com.apple.driver.AppleIntelCPUPowerManagement (NoLabel) :: BinPatch :: [OS:  | MatchOS: All | MatchBuild: All] ==> disabled by user
21:165  0:025   - [04]: com.apple.driver.AppleEthernetAquantiaAqtion (Aquantia BigSur) :: BinPatch :: [OS:  | MatchOS: All | MatchBuild: All] ==> allowed
21:192  0:027  Filtering KernelPatches:
21:206  0:013   - [00]: algrey - _commpage_populate - Remove rdmsr - 10.13/10.14/10.15/11.0/12.0 :: [OS:  | MatchOS: 12.x,12 | MatchBuild: no] ==> allowed by OS
21:238  0:032   - [01]: algrey - _cpuid_set_cache_info - Set cpuid to 0x8000001D instead 4 - 10.13/10.14/10.15/11.0/12.0 :: [OS:  | MatchOS: 12.x,12 | MatchBuild: no] ==> allowed by OS
21:262  0:024   - [02]: algrey - _cpuid_set_cache_info - Don't set cpuid_cores_per_package - 12.0 :: [OS:  | MatchOS: 12.x,12 | MatchBuild: no] ==> allowed by OS
21:279  0:017   - [03]: algrey - _cpuid_set_cache_info - Don't set cpuid_cores_per_package - 10.13/10.14/10.15/11.0 :: [OS:  | MatchOS: 11.x,11 | MatchBuild: no] ==> allowed by OS
21:302  0:022   - [04]: algrey - _cpuid_set_generic_info - Remove wrmsr - 10.13/10.14/10.15/11.0/12.0 :: [OS:  | MatchOS: 12.x,12 | MatchBuild: no] ==> allowed by OS
21:322  0:020   - [05]: algrey - _cpuid_set_generic_info - Set flag=1 - 10.13/10.14/10.15/11.0/12.0 :: [OS:  | MatchOS: 12.x,12 | MatchBuild: no] ==> allowed by OS
21:345  0:022   - [06]: algrey - _cpuid_set_info - GenuineIntel to AuthenticAMD - 10.13/10.14/10.15/11.0/12.0 :: [OS:  | MatchOS: 12.x,12 | MatchBuild: no] ==> allowed by OS
21:362  0:017   - [07]: algrey - _cpuid_set_cpufamily - Force CPUFAMILY_INTEL_PENRYN - 10.13/10.14/10.15/11.3 :: [OS:  | MatchOS: 11.x | MatchBuild: no] ==> allowed by OS
21:388  0:025   - [08]: Goldfish64 - Bypass GenuineIntel check panic - 12.0 :: [OS:  | MatchOS: 12.x,12 | MatchBuild: no] ==> allowed by OS
21:409  0:021   - [09]: DhinakG - _cpuid_set_cpufamily - Force CPUFAMILY_INTEL_PENRYN - 11.3b1 :: [OS:  | MatchOS: 11.x,11 | MatchBuild: no] ==> allowed by OS
21:427  0:017   - [10]: algrey - _cpuid_set_cpufamily - Force CPUFAMILY_INTEL_PENRYN - 12.0 :: [OS:  | MatchOS: 12.x,12 | MatchBuild: no] ==> allowed by OS
21:445  0:018   - [11]: algrey - jmp to calculations and set cpuid_cores_per_package - 10.15/11.0 :: [OS:  | MatchOS: 11.x,11 | MatchBuild: no] ==> allowed by OS
21:471  0:026   - [12]: XLNC - jmp to calculations and set cpuid_cores_per_package - 12.0 :: [OS:  | MatchOS: 12.x,12 | MatchBuild: no] ==> allowed by OS
21:488  0:017   - [13]: algrey - cores and threads calculations - 10.15/10.16 :: [OS:  | MatchOS: 11.x,11 | MatchBuild: no] ==> allowed by OS
21:511  0:022   - [14]: XLNC - cores and threads calculations #1 - 12.0 :: [OS:  | MatchOS: 12.x,12 | MatchBuild: no] ==> allowed by OS
21:541  0:030   - [15]: XLNC - cores and threads calculations #2 - 12.0 :: [OS:  | MatchOS: 12.x,12 | MatchBuild: no] ==> allowed by OS
21:564  0:022   - [16]: algrey - _i386_init - Remove rdmsr (x3) - 10.13/10.14/10.15/11.0/12.0 :: [OS:  | MatchOS: 12.x,12 | MatchBuild: no] ==> allowed by OS
21:585  0:021   - [17]: algrey - Remove Penryn check to execute default case - 10.13/10.15/11.0/12.0 :: [OS:  | MatchOS: 12.x,12 | MatchBuild: no] ==> allowed by OS
21:607  0:021   - [18]: algrey - Get DID and VID from MSR - 10.13/10.14/10.15/11.0/12.0 :: [OS:  | MatchOS: 12.x,12 | MatchBuild: no] ==> allowed by OS
21:629  0:021   - [19]: XLNC - Remove version check and panic - 10.15/11.0/12.0 :: [OS:  | MatchOS: 12.x,12 | MatchBuild: no] ==> allowed by OS
21:651  0:022   - [20]: XLNC - Remove version check and panic - 10.15/11.0/12.0 :: [OS:  | MatchOS: 12.x,12 | MatchBuild: no] ==> allowed by OS
21:679  0:028   - [21]: algrey - Skip checks and prevent panic - 10.15/11.0/12.0 :: [OS:  | MatchOS: 12.x,12 | MatchBuild: no] ==> allowed by OS
 

 

683967443_Screenshot2021-06-30at13_52_01.thumb.png.f59ad224c24ab6319304af365797f5fe.png

 

1421453561_Screenshot2021-06-30at13_52_51.thumb.png.dbeced7e3a3704d1509f84fdca47eb63.png

 

Spoiler

20:265  0:033  GetOSVersion: 12.0 (21A5248p)
20:286  0:021  Filtering KextPatches:
20:299  0:013   - [00]: com.apple.driver.AppleEthernetAquantiaAqtion (Aquantia BigSur) :: BinPatch :: [OS: 12.0 | MatchOS: 11.x,11 | MatchBuild: All] ==> not allowed
20:322  0:023   - [01]: com.apple.driver.AppleEthernetAquantiaAqtion (Aquantia Monterey) :: BinPatch :: [OS: 12.0 | MatchOS: 12.x12 | MatchBuild: All] ==> not allowed
20:345  0:023   - [02]: com.apple.driver.AppleAHCIPort (External icons patch) :: BinPatch :: [OS: 12.0 | MatchOS: All | MatchBuild: All] ==> allowed
20:370  0:025   - [03]: com.apple.driver.AppleIntelCPUPowerManagement (NoLabel) :: BinPatch :: [OS: 12.0 | MatchOS: All | MatchBuild: All] ==> disabled by user
20:393  0:022   - [04]: com.apple.driver.AppleEthernetAquantiaAqtion (Aquantia BigSur) :: BinPatch :: [OS: 12.0 | MatchOS: All | MatchBuild: All] ==> allowed
20:415  0:022  Filtering KernelPatches:
20:425  0:009   - [00]: algrey - _commpage_populate - Remove rdmsr - 10.13/10.14/10.15/11.0/12.0 :: [OS: 12.0 | MatchOS: 12.x,12 | MatchBuild: no] ==> allowed by OS
20:445  0:020   - [01]: algrey - _cpuid_set_cache_info - Set cpuid to 0x8000001D instead 4 - 10.13/10.14/10.15/11.0/12.0 :: [OS: 12.0 | MatchOS: 12.x,12 | MatchBuild: no] ==> allowed by OS
20:463  0:017   - [02]: algrey - _cpuid_set_cache_info - Don't set cpuid_cores_per_package - 12.0 :: [OS: 12.0 | MatchOS: 12.x,12 | MatchBuild: no] ==> allowed by OS
20:486  0:022   - [03]: algrey - _cpuid_set_cache_info - Don't set cpuid_cores_per_package - 10.13/10.14/10.15/11.0 :: [OS: 12.0 | MatchOS: 11.x,11 | MatchBuild: no] ==> not allowed by OS
20:510  0:024   - [04]: algrey - _cpuid_set_generic_info - Remove wrmsr - 10.13/10.14/10.15/11.0/12.0 :: [OS: 12.0 | MatchOS: 12.x,12 | MatchBuild: no] ==> allowed by OS
20:527  0:017   - [05]: algrey - _cpuid_set_generic_info - Set flag=1 - 10.13/10.14/10.15/11.0/12.0 :: [OS: 12.0 | MatchOS: 12.x,12 | MatchBuild: no] ==> allowed by OS
20:550  0:022   - [06]: algrey - _cpuid_set_info - GenuineIntel to AuthenticAMD - 10.13/10.14/10.15/11.0/12.0 :: [OS: 12.0 | MatchOS: 12.x,12 | MatchBuild: no] ==> allowed by OS
20:571  0:020   - [07]: algrey - _cpuid_set_cpufamily - Force CPUFAMILY_INTEL_PENRYN - 10.13/10.14/10.15/11.3 :: [OS: 12.0 | MatchOS: 11.x | MatchBuild: no] ==> not allowed by OS
20:594  0:022   - [08]: Goldfish64 - Bypass GenuineIntel check panic - 12.0 :: [OS: 12.0 | MatchOS: 12.x,12 | MatchBuild: no] ==> allowed by OS
20:611  0:017   - [09]: DhinakG - _cpuid_set_cpufamily - Force CPUFAMILY_INTEL_PENRYN - 11.3b1 :: [OS: 12.0 | MatchOS: 11.x,11 | MatchBuild: no] ==> not allowed by OS
20:637  0:025   - [10]: algrey - _cpuid_set_cpufamily - Force CPUFAMILY_INTEL_PENRYN - 12.0 :: [OS: 12.0 | MatchOS: 12.x,12 | MatchBuild: no] ==> allowed by OS
20:654  0:017   - [11]: algrey - jmp to calculations and set cpuid_cores_per_package - 10.15/11.0 :: [OS: 12.0 | MatchOS: 11.x,11 | MatchBuild: no] ==> not allowed by OS
20:672  0:018   - [12]: XLNC - jmp to calculations and set cpuid_cores_per_package - 12.0 :: [OS: 12.0 | MatchOS: 12.x,12 | MatchBuild: no] ==> allowed by OS
20:701  0:028   - [13]: algrey - cores and threads calculations - 10.15/10.16 :: [OS: 12.0 | MatchOS: 11.x,11 | MatchBuild: no] ==> not allowed by OS
20:724  0:022   - [14]: XLNC - cores and threads calculations #1 - 12.0 :: [OS: 12.0 | MatchOS: 12.x,12 | MatchBuild: no] ==> allowed by OS
20:746  0:022   - [15]: XLNC - cores and threads calculations #2 - 12.0 :: [OS: 12.0 | MatchOS: 12.x,12 | MatchBuild: no] ==> allowed by OS
20:764  0:018   - [16]: algrey - _i386_init - Remove rdmsr (x3) - 10.13/10.14/10.15/11.0/12.0 :: [OS: 12.0 | MatchOS: 12.x,12 | MatchBuild: no] ==> allowed by OS
20:789  0:024   - [17]: algrey - Remove Penryn check to execute default case - 10.13/10.15/11.0/12.0 :: [OS: 12.0 | MatchOS: 12.x,12 | MatchBuild: no] ==> allowed by OS
20:807  0:017   - [18]: algrey - Get DID and VID from MSR - 10.13/10.14/10.15/11.0/12.0 :: [OS: 12.0 | MatchOS: 12.x,12 | MatchBuild: no] ==> allowed by OS
20:824  0:017   - [19]: XLNC - Remove version check and panic - 10.15/11.0/12.0 :: [OS: 12.0 | MatchOS: 12.x,12 | MatchBuild: no] ==> allowed by OS
20:845  0:020   - [20]: XLNC - Remove version check and panic - 10.15/11.0/12.0 :: [OS: 12.0 | MatchOS: 12.x,12 | MatchBuild: no] ==> allowed by OS
20:872  0:027   - [21]: algrey - Skip checks and prevent panic - 10.15/11.0/12.0 :: [OS: 12.0 | MatchOS: 12.x,12 | MatchBuild: no] ==> allowed by OS

 

 

I have converted only patches mandatory for my chipset and cpu..

you can follow the same schema in nomenclature definitions

By the way ,some definitions in clover 5137 are not described well and I think must be update their nomenclature 

 

Also MAtchOs need some check and I hope devs will solve a very annoying bug for AMD users 🙂

MAtchOS is not perfect by now in my definition of this plist..but was useful to boot with a clean and also to update from 11.5 beta 4

 

I used the attached patch plist to install from scratch and then to update

Only GoldFish64 patch has some definition problem in CLoverBootloader due Empty Find value (in verbose it prints out a not destructive error)

I have also attached two debug log to see problem I have said before and also others job to do.

1)installation debug (GetOS Empty all patches applied.....😇

2) after installation is completed....GetOS detection works as it must do

 

Thanks to patches-manager and creator 🙂

 

 

debug_pre inst_inst.zip

 

opencore-2021-07-01-161751.txt.zip

 

for lryzen friend (17h19h)

 

pay attention on patch 43..I commented limit there 😉

 

thanks @iGPUfor Goldfish64 2F tip! 😉

 

------

UPDATE 18-07-2021

https://www.macos86.it/topic/4913-amd-clover-bootloader-monterey-beta-1-installation-patches/?do=findComment&comment=116586

 

Clover-Kernel_Patches_Quirks.plist.zip

Edited by fabiosun
UPDATE 18-07-2021
  • Like 4
  • +1 1
Link to post
Share on other sites
  • Gengik84 changed the title to [AMD] Clover Bootloader Monterey Beta 1 installation patches!!
  • Supervisor
Posted (edited)

 

OP updated with patches for 11.4.x 11.5.x 12 B1 and their debug logs! 😉

 

UPDATE 18-07-2021

https://www.macos86.it/topic/4913-amd-clover-bootloader-monterey-beta-1-installation-patches/?do=findComment&comment=116586

Clover Kernel Patches 10.4.x-10.5.x-12 Beta1_and debugs.zip

Edited by fabiosun
UPDATE 18-07-2021
Link to post
Share on other sites
  • Supervisor

Added a video on OP to show also booting steps in 3 OSX for my rig....

take a look! 😉

 

Link to post
Share on other sites
  • Supervisor


sorry guys I did a sociological experiment to understand how a harmless error propagated in the patches posted ..

I have already seen on insanelymac a positive result for the propagation of the error 🙂 🙂

you can see the error in the image that I am attaching 🙂

Forgive me!

 

----

 

scusatemi ragazzi
ho fatto un esperimento sociologico per capire come si propagasse un innocuo errore nelle patches postate..
Ho visto già su insanelymac un risultato positivo alla propagazione dell'errore 🙂 🙂
potete vedere l'errore nella immagine che vi allego 🙂
Perdonatemi!

 

20366260_Screenshot2021-07-02at9_07_32AM.thumb.png.4cf02cecb0ede0ba64c42ef039f0cd15.png

 

 

  • whahahah 1
Link to post
Share on other sites
  • Supervisor
Posted (edited)

added a complete version for 17h and 19h

take care and pay attention on patch 43..

limit set to 250 and I have commented it because I do not know very well clover 😉

132142012_Screenshot2021-07-02at12_59_35PM.thumb.png.ca8181834cdbd3b1989da93f97c1825b.png

check also if for your rig patches value "Disabled" should be on YES or NO

 

UPDATE 18-07-2021

https://www.macos86.it/topic/4913-amd-clover-bootloader-monterey-beta-1-installation-patches/?do=findComment&comment=116586

 

patches_clover.plist.zip

Edited by fabiosun
check also If for your rig patches value "Disabled" should be on YES or NO
  • Like 1
Link to post
Share on other sites
  • Support Team
2 ore fa, fabiosun ha scritto:

patches_clover.plist.zip 2 kB · 4 download

 

added a complete version for 17h and 19h

take care and pay attention on patch 43..

limit set to 250 and I have commented it because I do not know very well clover 😉

132142012_Screenshot2021-07-02at12_59_35PM.thumb.png.ca8181834cdbd3b1989da93f97c1825b.png

check also if for your rig patches value "Disabled" should be on YES or NO

 

 

beyond social experiments, there are some errors about matchOS

  • Thanks 1
Link to post
Share on other sites
  • Supervisor

Stavolta non e' stato un esperimento sociologico 😉

per sbrigarmi ho sbagliato....

cmq non e' grave per il funzionamento (per modo di dire) del matchOS? o Sbaglio?

 

this time is not been a sociologic experiment..in rush I was wrong..

Not so great for functional? ore not? 

Link to post
Share on other sites
  • Supervisor
1 hour ago, iCanaro said:

OC Limit = Clover RangeFind

 

not works

this one instead is interesting me a lot...

is there some public thread where we can find this?

in a slice post limit is not a value that He translates in a list posted as picture time ago

 

Link to post
Share on other sites
  • Support Team
8 minuti fa, fabiosun ha scritto:

this one instead is interesting me a lot...

is there some public thread where we can find this?

 

1 ora fa, iCanaro ha scritto:

PS: if the clover devs follow the logic used for big sur, monterey in matchOS must be 12.x

 

some details of Slice

https://www.insanelymac.com/forum/topic/284656-clover-general-discussion/?do=findComment&comment=2761981

 

RangeFind you can also omit, enable it even with a value of 10 as Slice says, it changes from a config that works to one that does not start
same thing if you enter 00 00 ff as always indicated by slice, a config that works, stops working even if the validateer from everything OK

Link to post
Share on other sites
  • Supervisor

Non hai risposto alla domanda! 🙂

Dove si trova la conversione limit=rangefind ? come nomenclatura intendo, c'e' un posto pubblico dove se ne parla?

 

Poi se vedi segnalo una patch per 10.13, 10.14 che ha un limit =250...(la numero 43)

e qui ci potrebbe essere un problema per quesi sistemi, ma dall'inizio parte tutto quello che ho provato...e ho anche rinnovato una issue sul GitHub a proposito del GetOS Detection che sta ancora li dalla versione 5124

Ci puo' essere un problema iniziale che clover ti mette tuto ciao' che trova non capendo con che sistema stai partendo

 

Il discorso di quello che ti dice slice e' nato, credo perche' non vi siete capiti

mettere qualcosa dove non c'e' nulla e' da folli....parlo di mask find e replace

il problema si ha solo sulla patch nuova di GoldFish dove clover restituisce un warning e funziona bene ugualmente perche' questa patch non e' come le altre..

se vedi i log che ho messo vedi uno dei miei tentativi dopo che avevo fatto funzionare tre sistemi con il find non a zero..e vedi nel log cosa accade

ma li magari slice non sa cosa fa la patch di Goldfish64

che per inciso e' quella che vi fa bolccare sul +++++++++++

se non  metti corretta

ti rileggo volentieri tra un po'..sto facendo delle prove e credo che non mi parta per un po' OSX 🙂

 

 

-----

You did not answer the question! 🙂 Where is the conversion limit = rangefind? as a nomenclature I mean, is there a public place where we talk about it? Then if you see I report a patch for 10.13, 10.14 which has a limit = 250 ... (number 43) and here there could be a problem for these systems, but everything I tried starts from the beginning ... and I also renewed an issue on GitHub about GetOS Detection which is still there since version 5124 There may be an initial problem that clover gives you all bye he finds not understanding what system you are starting with The speech of what slice tells you was born, I think because you didn't understand each other putting something where there is nothing is crazy .... I'm talking about mask find and replace the problem occurs only on the new GoldFish patch where clover returns a warning and works equally well because this patch is not like the others .. if you see the logs I put you see one of my attempts after I had run three systems with the find not at zero .. and you see what happens in the log but there maybe slice doesn't know what the Goldfish64 patch does which incidentally is the one that makes you stamp on +++++++++++ if you don't put it correct

 

Link to post
Share on other sites
  • Supervisor
Posted (edited)
40 minutes ago, iCanaro said:

si evince tra le righe della discussione, visto che non me l'ha censurata o segnalata come errore; invece per lui il count = 0 non andrebbe bene, ma lelle patch di OC e così e sino all'altro giorno andava bene anche con Clover

 

No I disagree here because he says many not exact things and some very weird he said in this way

 

40 minutes ago, iCanaro said:

secondo me ci siamo capiti, se leggi più indietro con fusione per le kext to patch, li funziona questa cosa, ma non funziona per le kernel to patch, ed è lì che Slice fa orecchie da mercante o gli parlo nell'orecchio gigo

 

No also here I have to disagree, he says find should not be to 0

you and others change also Findmask and replace mask and other...

Replace C3 and count 0 does not need to have fulfilled those arguments...and it is delivery  risky to do 🙂

 

_ (underscore) he says to delete is funny

try to decompile kernel as I said in a thread where I invite people to search for the patches, all AMD Kernel patches you can find as in it an _ (underscore)

and it is an important thing as search pattern and AMD OSX patches manager leave it in the comment..(thank for this)

 

40 minutes ago, iCanaro said:

il punto è che io non stò provando con monterey, la conversione delle ultime patch di OC, non mi avvia nessun macOS, con Clover; OC invece funge bene

other weird assertion is about count 0 and his declaration to put it to 1..

Do you know what count 0 or 1 do?

 

if you have multiple kernel part to replace and you say replace it only one time....

0..should mean all (not sure but it should)

 

 

Edited by fabiosun
risky
Link to post
Share on other sites
  • Supervisor

I have downloaded your converted patches...

I would suggest to delete or comment also Procedure Arguments

in that way patches should do their work also for you if you have used origina GitHub ones

 

Link to post
Share on other sites
Posted (edited)

Actually, the idea was not from reading OC documentation.

 

Instead, I found out about using "2F" as a null entry for editing SSDT files a couple of years ago when working on Find/Replace SSDT patching problems going, ironically, from Clover to OC on the Z390 system. And so I thought it might work here too.

 

 

Edited by iGPU
  • Like 2
Link to post
Share on other sites
31 minutes ago, Gengik84 said:

@iGPU Hi

Do you mean "nop" for 2F in acpi patch?

 

EDIT: this is comment..ok  🙂

Thanks

 

Yes.

Link to post
Share on other sites
  • fabiosun changed the title to [AMD] Clover Bootloader Monterey Beta (1 ,2,3) installation patches!!

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.