Jump to content

tomnic

Moderators
  • Posts

    1,071
  • Joined

  • Last visited

  • Days Won

    45

Everything posted by tomnic

  1. Il blocco su quelle righe c'è quando non parte l'accelerazione grafica... a me capitava quando avevo la fix pat patch di Shaneee attiva, incompatibile con le nVidia, e/o qualche settaggio nel bios non gradito a macOS, come quelli segnalati da Carlo: il CSM dovrebbe stare su off purché la tua gpu abbia un bios uefi ready (e semmai potresti flasharcelo, dovrebbe esistere per la 760). Se i kext che hai nel bootloader sono tutti aggiornati dovrebbe partire il tutto, almeno con nv_disable=1 e forzando per scrupolo lilubetaall=1. Il problema è far digerire in qualche modo l'accelerazione della tua GPU a Monterey. La 780ti che ho io sta su Intel e ha bios UEFI, forse flashandola risolvi.
  2. Strano io ho una 780ti con Monterey beta6 che va tranquillamente, i driver accelerati ci sono ancora. Controlla la fix pat patch semmai rimetti quella vecchia di Algrey se l'hai cambiata.
  3. These specific fixes apply only to Adobe Premiere Pro CC 2021 15.4 In this program all the effects / transitions are actually macOS bundles. In macOS bundles my dylib injection doesn't work so we need to manually patch the problematic bundles one by one. Let's start with AEFilterStabilizer.bundle: we open it in Hopper Disassembler and search for the same function we need to make always return TRUE as in libfakeintel.dylib, which is mkl_serv_intel_cpu_true. Once found (very easy with hopper as it retrieves the most of original symbols and function names), we just replace its very beginning with a RET (return), which in x86_64 machine language is C3. Simple as ABC! And IT WORKS! Fun fact: Adobe embedded all its dynamic library mkl code DIRECTLY into every bundle routine... that's a TERRIBLE programming habit! The same libraries are present again and again in the same Premiere application and we can find a different mkl lib version in each application too... shame on you Adobe!!! Then we need to patch the other crashing bundle with AMD cpus: AEFilterMorphCut.bundle. Because of the "fun fact" I explained earlier, the code for the same function mkl_serv_intel_cpu_true in this bundle is DIFFERENT than the one in AEFilterStabilizer and just replacing the whole function with a trivial C3 doesn't work. We need to decompile libfakeintel.dylib with hopper and we find out that our simple program: int mkl_serv_intel_cpu_true() { return 1; } ...equals to this assembly code: 0000000000003fa0 push rbp 0000000000003fa1 mov rbp, rsp 0000000000003fa4 mov eax, 0x1 0000000000003fa9 pop rbp 0000000000003faa ret ; endp ...which is, translated in ML code thanks (again) to Hopper: ...so putting this sequence in AEFilterMorphCut's binary replacing the bytes in the offset where its actual function mkl_serv_intel_cpu_true begins makes everything working like a charm. For simplicity I'll attach both the patched bundles in the top post. I'll try to generate as soon as possible a perl script to automate this procedure for all the future and past releases post 14.3.1, help is appreciated. Right now, enjoy Premiere pro cc 2021 15.4 on AMD bare metal 😉
  4. Some updates for After Effects CC 2021 18.4.0 and up: Camera tracking works as usual with my method but Stabilization stopped working because of a missing symbol in the replaced libiomp5.dylib: Dyld Error Message: Symbol not found: ___kmpc_critical_with_hint Referenced from: /Applications/Adobe After Effects 2021/Adobe After Effects 2021.app/Contents/MacOS/../Frameworks/libmkl_intel_thread.1.dylib So I replaced libmkl_intel_thread.1.dylib with libmkl_intel_thread.dylib (obviously renamed) taken from Adobe Media Encoder 15.2 and Stabilization started working again. I'll attach the file here, just overwrite it in Frameworks folder inside AE app just like libiomp5.dylib. Premiere still need fixes, working on it! libmkl_intel_thread.1.dylib.zip
  5. ...banalità, ma non puoi formattarlo in HFS+ visto che è un disco esterno non di sistema presumo?
  6. tomnic

    Avvio Opencore

    In alternativa c'è da adattare questo paragrafetto tratto da questo link: https://phil-li.gitbook.io/hackintosh/i5-3470-asus-p8p67 "The early UEFI BIOS from ASUS and ASRock is incomplete so there is some trouble for *Clover (Opencore nel nostro caso) to add itself to UEFI boot list, but we can do that manually." To do this, boot into the USB clover stick, and open the UEFI shell. In it, follow the general instructions: Find bootx64.efi on HDD EFI partition with the combination of the following commands: Shell> map fs* ➝ Show all partitions Shell> fs0: (or fs1: or fs2: ...)➝ Switch to fs0, fs1, fs2,... partitions Shell> ls ➝ List the contents of current partition / directory Shell> cd \efi\boot ➝ Change the directory to \efi\boot Shell> ls Then: Shell> help bcfg -b -v ➝ Get help on bcfg command Shell> bcfg boot dump ➝ List current boot options Shell> bcfg boot add N bootx64.efi "Opencore" ➝ Add bootx64.efi from the current dir (\efi\boot) as a boot option labeled "Opencore" (You will see this name also in the UEFI BIOS Boot menu boot items). N is the boot option number: 0 if you want it to be the first, 1 to be the second, etc. Shell> bcfg boot dump ➝ Check if Opencore is added Shell> reset ➝ Restart the system
  7. tomnic

    Avvio Opencore

    Vuol dire che la Asus P8H67 non supporta direttamente il boot UEFI se non da penne USB, così come alcune ASRock più vecchiotte. Qui cosa non riesci a seguire? https://macos86.gitbook.io/guida-opencore/requisiti/legacyusers
  8. tomnic

    Avvio Opencore

    La tua mobo ha un'implementazione UEFI incompleta quindi la cosa più semplice è far partire OC in legacy, o tenere la uefi in una pennetta usb sempre attaccata con la attuale cartella EFI che usi. Segui la guida di Dortania per la creazione della EFI di OC in legacy Evita di postare la stessa richiesta più volte sotto mentite spoglie, ti si aiuta ma non esagerare con le richieste.
  9. For a MSI Carbon Gaming Pro X399 it seems to work but with folders with tons of files it hangs the system just browsing the LAN... at least with this particular Mainboard.
  10. AppleIGB.kext is one of the worst coded kext I've ever seen... panics a lot and works slowly if it works...
  11. Dovrebbero già vedersi dei kernel + kext acpi sperimentali in giro con le prime point release beta di Monterey... incrociamo l'incrociabile!
  12. Per come sono fatto io i lati negativi hanno più peso per me... quindi il termosifone sta dove sta 😉 Proverò il noctua rispetto al mio darkrock appena possibile e sto!
  13. Ma sei soddisfatto? Leggo tra le righe che avresti desiderato qualcosa di più 😉
  14. 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)!!!
  15. 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
  16. Padre Maronno salvaci tuuuu 😄
  17. Hi, I use an old Clover since it is in production now and I cannot touch it again 😉
  18. 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
  19. tomnic

    rx580

    Concordooooo, vai e usa la fix pat di Shaneee, vedrai che boost!
  20. 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
  21. tomnic

    hp z600

    Avevo un hardware similare X58 con cpu singola, nel bios controlla di aver disabilitato il CSM.
×
×
  • 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.