tomnic

Postazione Intel secondaria aggiornata al top... risolto anche il problema di Safari che crashava se mi loggavo su YouTube e similari, molto stabile come beta (dalla 3 a dire il vero)!!!

Perfetto anche con OC 0.7.1 ufficiale ;)

Di già? Maremma melosa!!!!

Aaaaand... it WORKSSSS!!! Very few patches with Clover 5137/5138... Just make sure to have all the kexts updated to the latest release version: BS 11.4, 11.5, MR Beta1/2/3 ...somebody just stops at number 2 😉 config.plist.zip

Padre Maronno salvaci tuuuu 😄

Hi, I use an old Clover since it is in production now and I cannot touch it again 😉

Using official OC 0.7.1 and this config with reduced patches thanks to @fabiosun I successfully booted Monterey beta 3 in my AMD Ryzen 9 rig. Wonderful! config.plist.zip

Concordooooo, vai e usa la fix pat di Shaneee, vedrai che boost!

Per ora con la macchinozza Intel secondaria 😉 Aggiornamento a beta3 lanciato dal treno tramite Anydesk, liscio come l'olioooooo 😛 Ti piace vincere facileeeee, bom xi bom xi bombombommmm, pappapparaaaah

Avevo un hardware similare X58 con cpu singola, nel bios controlla di aver disabilitato il CSM.

Amarioooooooo 😄

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.

Questi sono i miei quirks

It would be nice to find out why the reduced set patches don't work for you, please attach a debug log

Hi, I can boot BigSur 11.4 stable on my Ryzen 9 build with Clover and this reduced patch set sent by @fabiosun, will try with Monterey Beta1 as soon as possible. Using Clover revision: 5137 (master, commit cc561f87d) config.plist.zip P.s.: with the same bootloader I can boot Mojave - Catalina - Big Sur using this configall, some warnings about empty find field but it boots and works fine! configall.plist.zip

Schermata login copiata da centos 7 Barra di avvio centrata copiata da ChromeOS Disposizione app mutuato dal launcher di MacOS Un bel fritto misto!!!!

Usati ancora in produzione qui dove lavoro nel reparto audio... insieme all'immortale Snow Leopard!!!!! Una bella f*ga di os al pari ai miei occhi di Windows NT4 e WinXP 64 bit ahahahahahah

Ad ora con la Insider non ci sto riuscendo... già!

Io sto provando ad installarlo su una Asus P9x79 ma non ci sto riuscendo... sigh

How are the patch location located, via error logs? I think that this is fully automated by the patch engine of the chosen bootloader, the found offset is shown in the debug log. If you use a hex editor and go to that offset you'll find exactly the found pattern. Replaced values are only loaded in memory not actually written to the kernel. P.s.: IMHO the offset piker uses, 0x200000, is related to its specific xcpm patch. Every patch has a different one, as you can see analyzing any debug log in the patch applying section. How is the value to be substituted determined (the replacement value)? This involves both assembly and xnu knowledge: the pattern we choose to replace some code is actually machine language code created by anybody who deeply knows xnu... the goal is to bypass or modify specific functions not suitable for AMD cpus. If you physically apply the patch and disassemble the kernel you'll get perfectly working assembly code, different from the source, but "perfect" to be directly run by AMD cpus. P.s.: IMHO the right procedure would be: analyze the full source xnu kernel once published by Apple here https://opensource.apple.com/source/xnu/, change the functions / values not suitable for AMD cpus in c++ language, compile them and create a find / replace with masks to maintain durability and portability of the binary patches to obtain the same modded code without replacing the actual kernel. Which file is examined for this section, an already installed drive with the new macOS, or the installation app for this new macOS? You can take the kernel from the installation app or an official apple update package, or even from a real booted mac or intel hackintosh, installation kernel and booted kernel usually are the same version.

Seconda postazione Hackintosh Intel aggiornata come un Mac vero alla Beta2. Avanti tutta!!!!

...quello è un disastro per far applicare le patch in fase di studio abbiamo visto @fabiosun

This is what I've understood starting from the debug log of clover, I think it is similar with OC. For example, let's pick the patch algrey - cpuid_set_info - jmp to calculations and set cpuid_cores_per_package - 10.15/10.16 it is complete because we have a hex find, a mask find, a hex replace and a mask replace. It says: Find: 7571E800000000488B050000000048890500000000 Mask: FFFFFF00000000FFFFFF00000000FFFFFF00000000 Replace: 744E000000000090890D00000000E97E0000006690 Replace Mask: FFFF0000000000FFFFFF00000000FFFFFFFFFFFFFF How does the patch engine work? We are searching a hex pattern, the "find" one, but we're using a byte mask: this changes a bit our search criteria: 7571E8 00000000 488B05 00000000 488905 00000000 (find) FFFFFF 00000000 FFFFFF 00000000 FFFFFF 00000000 (mask find) ----------------------------------------------- 7571E8 xxxxxxxx 488B05 xxxxxxxx 488905 xxxxxxxx So we're effectively searching 7571E8 xxxxxxxx 488B05 xxxxxxxx 488905 xxxxxxxx ... where xxxxxxxx is a wildcard! Every hex combination found in place of xxxxxxxx of its exact bytes lenght is good. Looking in the clover debug log we can find some precious info about the patches: 55:733 0:010 OC: Kernel patch [9] algrey - cpuid_set_info - jmp to calculations and set cpuid_cores_per_package - 10.15/10.16 55:749 0:015 Replace 7571E800000000488B050000000048890500000000/FFFFFF00000000FFFFFF00000000FFFFFF00000000(7571E8B6090000488B0577EAED0048890538EBED00) by 744E000000000090890D00000000E97E0000006690/FFFF0000000000FFFFFF00000000FFFFFFFFFFFFFF(744EE8B609000090890D77EAED00E97E0000006690) at ofs:1273 The effective code found in the kernel is: 7571E8B6090000488B0577EAED0048890538EBED00 7571E8 B6090000 488B05 77EAED00 488905 38EBED00 7571E8 xxxxxxxx 488B05 xxxxxxxx 488905 xxxxxxxx ...a nice match with our find mask!!! So now in the replace side we do the same calculations: 744E000000000090890D00000000E97E0000006690 FFFF0000000000FFFFFF00000000FFFFFFFFFFFFFF 744E 0000000000 90890D 00000000 E97E0000006690 FFFF 0000000000 FFFFFF 00000000 FFFFFFFFFFFFFF ---------------------------------------------- 744E xxxxxxxxxx 90890D xxxxxxxx E97E0000006690 We must replace in the actual found hex bytes "string" found with the previous calculations, 7571E8B6090000488B0577EAED0048890538EBED00: 7571E8B6090000488B0577EAED0048890538EBED00 (actual found code) 744E000000000090890D00000000E97E0000006690 (replace data) FFFF0000000000FFFFFF00000000FFFFFFFFFFFFFF (replace mask) 744E 0000000000 90890D 00000000 E97E0000006690 (replace data) FFFF 0000000000 FFFFFF 00000000 FFFFFFFFFFFFFF (replace mask) 7571 E8B6090000 488B05 77EAED00 48890538EBED00 744E xxxxxxxxxx 90890D xxxxxxxx E97E0000006690 ---------------------------------------------- 744E E8B6090000 90890D 77EAED00 E97E0000006690 The xxxxxxxx hex "string" must be left exactly as it has been found, the other bytes must be replaced... so the final actual replace is 744EE8B609000090890D77EAED00E97E0000006690. Offsets are calculated and applied automatically by OC / Clover kernel patch engine.

Eccomi con il mio intellozzo secondario...

Io ho pazienza da stravendere e aspetto anche un anno per avere la 6800xt a prezzo di costo... macOS lo tengo a bada con una rx 460 presa a 80 eur che di questi tempi è stato un miracolo e la voglia di giocare è strasoddisfatta da una 3070 presa a poco più di quanto ho venduto la VII 😉 Attendiamo al varco... 😛