Jump to content

fabiosun

Supervisor
  • Posts

    11,147
  • Joined

  • Days Won

    512

Everything posted by fabiosun

  1. daje che sono anche saltate le patches per AMD...che nn si sono viste.per Monterey in pubblico....forse si vedranno per beta 3? 😛
  2. No @tuxy Patches for Monterey are not available... so also on x570 platform is enough a minimal set of patches to boot fine?
  3. you have to analyse your actual config.plist and see if you use Algrey or Shane fix pat in it if so you have to add it then 40 patches are for all system from HighSierra to Big Sur latest beta if you delete the ones for old system, you will have a minimal set of patches useful to boot only Big Sur (ie with it this set high sierra does not boot) then you can cut also a couple of them or more 🙂
  4. If you have a backup you can try.. these are working with Big Sur 11.4, 11.5 b1,b2,b3 and almost all working in Monterey Beta 1 (three of them are not working yet) Pay also attention to fix pat (we ,trx40 users, do not need of it) 😉
  5. Attached are: 1) minimal set of patches to boot and work fine with OSX 11.4 release and 11.5.b3 with Opencore 2) minimal set of patches to boot and work fine with OSX 11.4 release and 11.5.b3 with Clover latest patch is for aquantia ethernet, you can disable it if you do not use (Opencore patches plist) Users that use Topology patch, maybe they have to add again this patch I do not understand well why some users need of it... clover trx40 kernel patches.plist.zip Opencore trx40 kernel patches.plist.zip
  6. Thank you Carlo You have discovered we do not need to boot also of this patch: algrey - cpuid_set_generic_info - disable check to allow leaf7 @iGPUand all users..could you test if it is the same also for you? Great catch @carlo_67 tested on OSX 11.4 release and 11.5.b3
  7. fabiosun

    hp z600

    ciao @evafiste benvenuto Vuoi aggiornare a Monterey? nel caso metti in firma dal tuo profilo (signature o firma) le caratteristiche della tua workstation grazie
  8. @iGPU to be in touch with clover dev you can use this GitHub channel: https://github.com/CloverHackyColor/CloverBootloader/issues/283 Clover has many unsolved problems from time ago..but it useful to debug a kernel patch better than opencosre (with less error reboot and try I mean) We can add many patches we desire and then deactivate on boot menu. but Pay attention if you have multiple system booting on your rig (using clover) OS Detection works sometime in its way 🙂
  9. I am trying to understand from where on of this patch come: lapic_init - remove version check and panic f:25FC0000 0083F813 r:25FC0000 000F1F00 it should be valid also in Monterey and i used it from Catalina OS
  10. about kernel patching: in this thread you will find a link where years ago I have had some help from pikeralpha to understand "how to" For AMD related part no valid documentation is available (in public I mean) For people as me it is difficult to rebuild all the passes from older systems where some informations was available because I didn't live those moments (always had an Intel CPU from p90 age..before I have had an Amiga) new Patches's maintainers do not share their secret...I do not like this way to do..but I have to accept it 🙂 we should try to better understand what happens to you .. but if everything works well for you I don't feel like asking you to do other tests
  11. @wolvherin78ma che hardware stai tentando di sistemate con la 1070ti ? cpu e piastra madre?
  12. ciao ed i driver li hai installati correttamente ora? se si devi installare come upgrade per avere speranze per il dopo devi avere i tuoi monitor funzionanti su Catalina alle loro risoluzioni native e Nvidia web quindii installato regolarmente
  13. Aggiunti nel post iniziale il debug e la EFI di clover 5137 Nessun errore al boot Da risolvere il problema memoria causato da MacPro7.1 che utilizzo che SMBIOS Vorrei risolverlo come si fa in Opencore senza utilizzare kext
  14. if you have patience we will understand better 🙂 patch 13 is only for Big Sur from your min and max kernel Catalina should work disabling it If you have time and I f you like to do for the sake of discovering things try to disable patch number 12 and leave 13 on put also a - v boot-args to see beyond an apple logo 🙂 attached my clover debug log... some useful info on masking and offset stuff for kernel patching (@tomnic is working on this) 2021-06-27_13-13_BOOTX64.EFI.txt 2.zip
  15. I know you do not love clover boot loader...partially I agree with this...but : https://www.macos86.it/applications/core/interface/file/attachment.php?id=33686 if you want to test and to experiment with Kernel patches is the best solution available EFI posted above is working with Big Sur 11.4 release I have to solve in a clean way as @iGPUposted for open core bootloader memory problem with MAcPro 7.1 smbios...without using additional kext I mean
  16. Done @Ploddles could you try to disable patch 13 and see if your system boot fine the same in Big Sur (if you have a backup where you can boot again..just in the worst case) 🙂
  17. I am using this attached set of patches to boot with Big Sur, I think is possible also for all of you to boot and to have a perfect system as I have..Maybe, gigabyte users need also of CPU topology patch as @Arrakistested some time ago. My question is different and above maybe I have explained in a not clearly way. Official patch from AMD OSX github : algrey - lapic_init - remove version check and panic - 10.13/10.14 find 25FC0000 0083F813 replace 25F00000 00EB2390 good for HighSierra and Mojave NoOne - lapic_init - remove version check and panic - 10.16 find 83F8130F 86810000 00 replace 90909090 90909090 90 good for Big Sur patch I use: lapic_init - remove version check and panic find 25FC0000 0083F813 replace 25FC0000 000F1F00 good for Big Sur so in my case same FIND of Mojave but different replace data to patch... I and others two people of good will are trying to understand how to "discover" useful way to create own patches.. but it's hard to understand in my case because I have an AMD CPU only from latest Threadripper as you know..and this was only recently supported from Opencore Bootloader and its clone 🙂 I put in a spoiler the following thoughts (it is a personal opinion and maybe you could not like this): patches.plist.zip Yep the goal was also for me to minimise Patches's number Curious why you have to use both on your system When you have time and if you like I would like to try your patches combination thank you
  18. to be more clear , without that patch my system does not boot it boots fine with this one (NoOne official one and it seems completely different from one I and @Ploddlesand maybe other people are using): It would be useful to understand why 🙂
  19. @Ploddles We are both using this patch, but it is not an official one I think do you remember where it was taken from or have you taken it in the past from my config.plist? I can't find it and strangely it works the same way as the official one ... @iGPU and @Shaneee can you take a look when you have time too? thank you very much
  20. non nel caso..uscirà in autunno come sempre (Fall come dicono loro) 🙂
  21. per tagliare la testa al toro...usa i driver sbloccati che ti sono stati indicati quelli in Catalina si devono installare senza problemi poi lanci dopo l'installazione e se vuoi un riavvio (non necessario) nv_patcher che ti allinea il plist con la stessa versione del sistema che hai su
  22. @rainbowflarenon lo dire a me ..io ne sono riuscito a prendere due da gennaio la prima rivenduta che non c'era il driver Hai usato qualche metodo particolare? se puoi dirlo ovviamente 🙂
  23. Ciao la scheda ti funziona senza problemi anche senza... Pero' siccome sono amico del capo ( @gengik84 😂) Mi ha sistemato alcune cose riguardo la scheda ed altre cose (GFX0,HDAU,PMCR,USBX) che trovi in quel SSDT Va sistemato in ogni caso in base al tuo ioreg nel caso decidessi di usarlo che culo fortuna 🙂 vedi @tomnicci si riesce ancora
×
×
  • 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.