fabiosun
-
Posts
11,397 -
Joined
-
Days Won
546
Content Type
Profiles
Forums
Events
Downloads
Everything posted by fabiosun
-
Thanks @iGPUfor a tip given.. It is possible to use his sets of minimal patches to boot 11.4 and 11.5 b4, in my case I have had problems due AMDRyzenCPUPowerManagement.kext which caused without those two patches a reboot in early stage now patches are 11 to boot in 11.4 and 11.5 b4 with trx40 system
- 3,994 replies
-
- 1
-
-
- amd vanilla patches
- amd kernel patches
- (and 3 more)
-
attached a minimal set pf patches booting with 11.4,11.5 b4 and 12 b1 🙂 🙂 🙂 PS Poropopo edition 🙂 UPDATE 18-07-2021 https://www.macos86.it/topic/4913-amd-clover-bootloader-monterey-beta-1-installation-patches/?do=findComment&comment=116586 EURO2020_Poropopo_edition-11.4-11.5-12.plist.zip
-
ok and the winner is....... He solved this warning problem reading some OC documentation (see iGPU answer below) 2021-07-02_16-24_BOOTX64.EFI.log.zip
-
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
-
No I disagree here because he says many not exact things and some very weird he said in this way 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) 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)
-
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
-
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
-
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?
-
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 😉 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
-
scusa visto solo ora come upgrade lo fai da 1ui:
-
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!
-
@valmeidaAre you sure then you are installing Beta 1...
-
@valmeida maybe you have to update opencore and all your kext then if you use bt or Wi-Fi kext maybe you have to do some work on those
-
@all I know, you do not love clover bootloader...but to try patches job..is a fast way 🙂
- 3,994 replies
-
- 1
-
-
- amd vanilla patches
- amd kernel patches
- (and 3 more)
-
Added a video on OP to show also booting steps in 3 OSX for my rig.... take a look! 😉
-
@SemanticAsono piaceri che si riscontrano in "altra vita" Ps grazie per il tuo lavoro! 😉 -
thank you to clarify this my doubt was about the two patches below (system works well we both or one of them) different pattern same job?
-
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
-
Glad you're happy :D
-
Yes Carlo Also sleep ad wake works fine 😃
-
a bit OFF Topic (I will ban my self later) we are happy to say that also with clover boot loader is possible to install from scratch and also update from a previous OSX version I do not advise Clover boot loader because many problem could happen during installation steps and not solved by now: 1)GetOS Detection 2)MatchOS but with patches you can find in thread below I have had success!
-
per gli amanti di Clover con CPU AMD..una bella novità la trovate qui: credo sia una prima assoluta che macos86.it da alla sua comunità (utenti AMD) 🙂
-
Added on 01-08-2021 AMD Clover Vanilla patches Github: https://github.com/AMD-OSX/AMD_Vanilla/tree/clover 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
