Leaderboard

Grosse novità per gli utenti AMD. A breve sarà rilasciata una versione di Opencore che consentirà attraverso un quirk di avere un numero molto ridotto di patches, per Clover per il momento non e' possibile usufruire di questa riduzione, fino al completamento della "clonazione" del sistema kernel patches e quirks Ho avuto la fortuna di provare una versione in anteprima di Opencore 072 DBG e con poco piu' di 1x patches (x >1 ,x <7 ) 😛 e' possibile far partire ed usare proficuamente i sistemi che ho in questo momento! macOS High Sierra 10.13.6 Big Sur 11.4 Big Sur 11.5 beta 5 Big Sur 11.5. (20G701) Monterey 12 beta 1 Monterey 12 Beta 2 Monterey 12 Beta 3 Ho fornito i log dei seguenti sistemi e speriamo che venga pubblicato il tutto al piu' presto! Grazie ai devs! 😉 ------ Big news for AMD users. Soon a version of Opencore will be released that will allow through a quirk to have a very small number of patches, for Clover for the moment it is not possible to take advantage of this reduction, until the completion of the "cloning" of the system kernel patches and quirks I was lucky enough to try a preview version of Opencore 072 DBG and with little more than 1x patches (x> 1, x <7) 😛 it is possible to successfully start and use the systems I have right now! macOS High Sierra 10.13.6 Big Sur 11.4 Big Sur 11.5 beta 5 Big Sur 11.5. (20G701) Monterey 12 beta 1 Monterey 12 Beta 2 Monterey 12 Beta 3 I have provided the logs of the following systems and we hope that everything will be published soon! Thanks to the devs! 😉

Link to a news for AMD user :)

bene funziona tutto 🙂

Start from a clean Photoshop install, don't use zii or you'll break Photoshop. Disable SIP and put libfakeintel.dylib in your Application folder, don't replace anything. Then put environment.plist in your Library/LaunchAgents folder starting from your user's home, reboot. You are now ready to fully work with Photoshop without problems with your Ryzentosh. If you want even AE CC 2021 fully working you need to enter After Effects.app/Contents/Frameworks and REPLACE libiomp5.dylib there. Let me know if now the procedure is clearer.

Aggiornata cartella Resources, ora funziona tutto perfettamente con le nuove versioni di OpenCanopy! 🙂

il tuo motorino di avviamento😔😀 andato 😇

Rilasciata la RC build 20G70

lo vedi palesemente nella tua immagine 🙂 ora le SS sono usb3 mentre le HS sono usb2 tranne quella interna

potrebbe, metti Disabled

a questo punto puoi rimuovere quel SSDT e le due patch dal config il tutto è gestito al livello si sistema

rimappata la luminosità e funziona !!! Intanto ho richiesto a CHUWI l'aggiornamento dell'EC per il corretto funzionamento degli FN

Ho fatto così e sta continuando l'installazione, speriamo bene 😀😀😀 ho ricontrollato il config e questi numeri 11 22 ecc ecc sono alla voce ROM non nel SystemSerialNumber Per quanto riguarda l'id della patch grafica me l'ha suggerito un utente sulla chat di telegram e funziona, se dovesse andare a buon fine l'installazione rimetto 12040000 come id e vediamo che succede

il Sample.plist va rinominato config.plist non hai SSDT nella cartella ACPI

Find: 5F 51 30 38 00 Replace: 58 51 30 38 00 5F 51 31 30 00 58 51 31 30 00

Aggiungi i rename _Q09 -> XQ09 _Q10 -> XQ10 aggiungi SSDT e prova SSDT-Fn.aml.zip

se ti funzionano tutte sei ok hai fatto un buon lavoro 🙂 si se vuoi allega ioreg

scusami non ci avevo pensato, vado a inserirli nel readme!

Amarioooooooo 😄

Ciao prova a mettere usbinjectall ...dichiaralo USBInjectAll.kext.zip

Grazie! No issues found Perfetto

Without making any kind of controversy, let me tell you to take a look at this plist and if you want, try to adapt it to the bootloader you use and remember also patch 0 has a value (1F) for my 3970x, you must adapt to your cores cpu number. all patches used are public and available patch 0 later had some adjustments, in particular on the masks and on the count brought to 1 these adjustments are not yet published by the author, but are not necessary to make various modern systems work the patch published by algrey on insanely mac, allows you to remove several "XLNC" patches In the usual spirit that has always distinguished us, if you want to try them, if they don't work for you post a debug ... you will not believe it .. but this thread is also read by people who then solve the problems in the bootloaders 🙂 @carlo_67it should work also on your platform 😉 Mario* thanks you for trying the previous solution * UPDATE 17-07-2021:

good morning guys 🙂 Italy won a beautiful football match with England and my second dose of Pfizer vaccine is fortunately also losing intensity tighter small problems it has produced in me. So I'll hopefully clarify it definitively. I understand that it is very frustrating to see "solutions" and to be told I cannot provide them. But, do you also know how much I spent for example to get out the patches for Monterey beta 1 stimulating, at times, perhaps, even in a heavy way, the managers of the same. having said that, in this space I will try to make myself better understood by talking exclusively about what is available at the moment. That is the official patches downloadable from the official AMD OSX Github. The patches are those valid up to Monterey Beta1 I will do a further reduction of the field and will think exclusively on systems ranging from Big Sur 11.4 to big Sur 11.5.beta 5 This discourse can be carried on up to Monterey beta 1 and, having an unreleased patch available also in Monterey beta 2. But let's stay with the facts. The schemes that I will propose are for clover bootloader. Patches used are the same for both bootloaders, obviously with the respective names useful for the two bootloaders that have different nomenclature for their patches entries. With the Opencore bootloader, it is possible to use two patches less, because the developers of Opencore have added a quirk not present in Clover. Let's begin 0) algrey - Force cpuid_cores_per_package This patch was first posted by algrey on insanelymac: https://www.insanelymac.com/forum/topic/338516-opencore-discussion/?do=findComment&comment=2762290 https://www.insanelymac.com/forum/topic/338516-opencore-discussion/?do=findComment&comment=2762342 links have been edited few times I think so data could differ a bit. then it was converted by me for Clover and also explained on our forum in several places: this above is the patch that, most likely, is preventing the release of new patches for everyone. Unfortunately it still doesn't work on macOS HighSierra in tests done in private thanks to algrey. 1) algrey - commpage_populate -remove rdmsr 2) algrey - cpuid_set_cache_info - cpuid 0x8000001D instead 4 3) algrey - cpuid_set_cache_info - don't set cpuid_cores_per_package 4) algrey - cpuid_set_generic_info - remove wrmsr 5) algrey - cpuid_set_generic_info - set flag=1 6) algrey - cpuid_set_info - GenuineIntel to AuthenticAMD 7) algrey - cpuid_set_info - jmp to calculations and set cpuid_cores_per_package - 10.15/10.16 😎 algrey - cpuid_set_info - cores and threads calculations - 10.15/10.16 9) algrey - i386_init - remove rdmsr (x3) 10) tsc_init - remove Penryn check to execute default case 11) algrey - tsc_init - grab DID and VID from MSR 12) NoOne - lapic_init - remove version check and panic - 10.16 13) DhinakG - cpuid_set_cpufamily - force CPUFAMILY_INTEL_PENRYN - 11.3b1 now let's go a little deeper. If I activate patch 0 I can deactivate the yellow patches (this is also valid for osx like Monterey beta 1beta 1 (not in macOSHighSierra). If I used opencore bootloader I can also do without the red patches (10,11), this activating a quirk that is unfortunately not present in clover at the moment. quirk is: ProvideCurrentCpuInfo If you have followed this far, it is now possible for you to better understand what Patch 0 does. Its work is done in the same way also in Beta 1, so if you update the present patches and the new ones available for beta 1 accordingly, activating or not the patches 0 you can reduce the number of patches of the family of those marked here in yellow .. and there are also in the latest release of the patches if you proceed to this type of test, refer to find and replace and not to the names of the patches (they often take different names depending on who writes them in their config), it's a bad habit that I have too). I usually try to download the latest official ones, and grab the ones that have the same find and replace that I use in my current working config.plist in use if you have any questions, I will be happy to answer based on my knowledge on this topic good day everyone

all ps 2021 22.4.2 functions work, thank you, first thing you shoudl do is to disable SIP in Mac recovery tools

adesso definisci i connettori delle usb 😄 applica la mia patch e per ogni usb attiva va a definirla manualmente esempio SS01 cambi da (GUPC(One)) a (GENG(One,0x03)) etc..

I've gone through this thread several times, followed everything to the letter, but I still cannot even get Photoshop's object selection tool to work without crashing Ps, let alone warp stabilizer in Ae. Is there some step I'm missing or misunderstanding? FYI, it took me a while to figure out what filepath you meant in regards to Contents>Framework. And now that I'm looking again, I also replaced the Photoshop with the libiomp5.dylib file. You probably only meant to have the user replace AE? That might be better stated... I am going to attempt to uninstall Ps and reinstall now to get the original libiomp5.dylib back.

Clover 12 Patch, Opencore, 9 Patch start Bigsur e thanks to Mario 😇 indeed in Clover it does not even serve to enable Quirk