Nyaomi

Per la prima parte, mi illudevo che AirPortOpenBSD potesse avere uno spiraglio di senso per le schede ethernet Intel (sarebbe molto carino); Per la seconda parte, mannaggia, sta AX200 è inutile. Riconosco di aver sparato una baggianata con Ethernet, ma ormai sto cercando ogni spiraglio di speranza dopo la morte di SmallTree (e AppleIGB che non funziona per niente bene). Io purtroppo ho una I211.

Ma le features AirPort funzionano o no su questo kext? Io avrei voglia di switchare dato che non riesco a usare Continuity. Poi, funziona solo per WiFi e BT? Niente Ethernet?

Vi presento AMDFriend, uno strumento per riga di comando che è la perfetta combinazione della guida di @tomnicsul patching delle librerie per farle girare sugli hackintosh AMD e pigrizia e desiderio di semplice automazione. Come scritto sulla pagina GitHub: Istruzioni aggiornate su come installare, aggiornare e usare lo strumento son su GitHub (in inglese): https://github.com/NyaomiDEV/AMDFriend. Questo strumento non rimpiazza in nessun modo il patching manuale (per ora), dato che occhio e cervello umani son sicuramente più capaci di un pattern mat

Parallels (così come altre soluzioni all'infuori di VirtualBox) dipende da AppleHV che correntemente non gira su AMD. Versioni veramente datate di Parallels, come la 13.1.0, possono funzionare ma è un enorme rischio per la sicurezza del sistema.

The discussion thread is available here:

This is the discussion thread that references this post: Feel free to discuss, share excitement, errors and whatnot! Let's bring AMD hackintoshes on par with their Intel counterparts!

I present you with AMDFriend, a command-line tool that is the perfect combination of @tomnic 's guide on patching libraries for AMD hackintoshes and laziness and desire for simple automation. As stated in the GitHub page: Up to date instructions on how to install, update and use it are on GitHub: https://github.com/NyaomiDEV/AMDFriend. This in no way replaces manual patching (for now), as a human's eye and brain are certainly more capable than a pattern matcher; but it already successfully patches some common libraries (found in After Effects, Photos

Reporting in to give some more information about PS library patching: From my research, those framework libraries have intel specific calls and are not patched (by tomnic's guidelines): - libiomp5.dylib (probably shared with AE and PR) - libmkl_avx512.dylib (probably also shared) - libmkl_avx2.dylib - libmkl_mc3.dylib - libippiy8.dylib - libippil9.dylib - libippik0.dylib (what do those three libs offer?) And it seems we're missing the "Shake Reduction" plugin! EDIT: Added my version (remember to codesign it), but sadly I am still

From extensive research, those other two plugins needed patching: - AEFilterLumetri - AEFilterMask Here they are in their patched version. Remember to codesign! PR 22.1.2 AE Filters 2.zip

Patched libraries to make Premiere Pro 22.1.2 work on AMD Hackintoshes. REMEMBER THIS IS NOT A CRACK! Those libraries go to: /Applications/Adobe Premiere Pro 2022/Adobe Premiere Pro 2022.app/Contents/Frameworks Remember to codesign! AE Filters are in the post below! PR 22.1.2 Frameworks.zip Patched AE effects for Premiere Pro 22.1.2 / AMD Hackintoshes. Those plugins go to the respective bundles in: /Applications/Adobe Premiere Pro 2022/Adobe Premiere Pro 2022.app/Contents/Plug-Ins/Common/<AE Filter Name>.bundle/Contents/M

Okay, so, as general thoughts the find pattern for __mkl_serv_intel_cpu_true would be, in a regex, the following: \x53\x48\x83\xEC\x20\x8B\x35[\s\S]{4} and for the others, the masked regex would be: (\xFF{4}|\x90{4})\x56\xE8(?:\x6A|\x5A|\x4A|\x3A)\x00\x00\x00([\s\S]{2}) Now, does anyone love PCRE around here? I sure do. The next step is putting the replace patterns in a regex, so for the first one, essentially, the replace is \x55\x48\x89\xE5\xB8\x01\x00\x00\x00\x5D\xC3 For the second one, things get tricky: \1\

Yeah, I did read that, sadly enough. However, what about writing a routine that finds and patches libraries? I've been wanting to write one, but I need to know if I understood what's explained in the guide correctly enough. For example, you cite this sequence of bytes as the most general one yet for __mkl_serv_intel_cpu_true: 53 48 83 EC 20 8B 35 xx yy zz ww Then you say that bytes xx, yy, zz and ww are different from each other, but different how? Let me give out two example cases and you'll tell me if I am correct on my interpretation. Case 1:

...e scoprì che anche loro, come me, godono del frutto proibito. Salve a tutti! Mi chiamo Naomi e giro un hackintosh da relativamente poco tempo, per motivi legati allo studio in accademia d'arte. La mia build è una improvvisata e imperfetta, che descrivo di seguito: - ASRock X570 Taichi - Ryzen 7 3800XT - Sapphire Nitro+ RX 580 8GB - 32GB RAM - SSD SATA Samsung 870 EVO da 500GB per il boot - MacOS Big Sur (di cui onestamente non sto a citare l'esatta versione, che non ricordo) su OpenCore 0.7.8 Non ho comprato addon cards e roba extra e cerco di usare ciò ch

I am not sure if the method described can be then generalized by pattern matching instead of hard find/replace. If we can match a pattern, then I'd assume someone can also make an userspace library patcher that works without having to disassemble the library code every time. Also, how do you guys patch libraries as of now? Do you decompile each and every library or do you just find and replace in the hex editor?