Jump to content

fabiosun

Supervisor
  • Posts

    11,397
  • Joined

  • Days Won

    546

Everything posted by fabiosun

  1. hi and welcome here with latest opencore you have a boot menu option to do it otherwise you can do by hand on nvram section of your config.plist I use for my other needs 67000000 you can use others value to achieve this
  2. I am very sorry that this problem has arisen for you, and most likely I have expressed myself badly from the beginning If you have a reduced patch system that starts without difficulty or problems, just adding the patch: Force cpuid_cores_per_package available on insanelymac and published by algrey, it is possible to try to further reduce them by deleting some related to: cpuid_cores_per_package and: cores and logicals count if you use any of them in your small patch set And try to see if you can get any of that type off I am sorry for any inconvenience this may cause you, but I cannot publish the work of others without permission it would be a serious disrespect for the work of others. I hope I have partly clarified the fact that it was created perhaps because of my too much enthusiasm to share things with you on the fly! I will not do it again'!
  3. Clover Patches useful to boot with Big Sur 11.4,11.5 beta 5, 12.x (x=1 and 2) 🙂 Opencore Patches useful to boot with Big Sur 11.4,11.5 beta 5, 12.x (x=1 and 2) list of patches I use in above pictures: new_Algrey Force cpuid_cores_per_package (unreleased in latest form tested today, you can use patch available for now) _cpuid_set_cpufamily - Force CPUFAMILY_INTEL_PENRYN (unreleased) Goldfish64 - Bypass GenuineIntel check panic - 12.0 algrey - _commpage_populate - Remove rdmsr - 10.13/10.14/10.15/11.0/12.0 algrey - _cpuid_set_cache_info - Set cpuid to 0x8000001D instead 4 - 10.13/10.14/10.15/11.0/12.0 algrey - _cpuid_set_generic_info - Remove wrmsr - 10.13/10.14/10.15/11.0/12.0 algrey - _cpuid_set_generic_info - Set flag=1 - 10.13/10.14/10.15/11.0/12.0 algrey - Remove Penryn check to execute default case - 10.13/10.15/11.0/12.0 algrey - Get DID and VID from MSR - 10.13/10.14/10.15/11.0/12.0 algrey - _cpuid_set_info - GenuineIntel to AuthenticAMD - 10.13/10.14/10.15/11.0/12.0 algrey - _i386_init - Remove rdmsr (x3) - 10.13/10.14/10.15/11.0/12.0 XLNC - Remove version check and panic - 10.15/11.0/12.0 this patches: algrey - Remove Penryn check to execute default case - 10.13/10.15/11.0/12.0 algrey - Get DID and VID from MSR - 10.13/10.14/10.15/11.0/12.0 they are not useful if you use a bootloader with ProvideCurrentCpuInfo quirk capability. Personally, my goal was reached by now! always thank to @algrey for his time and skill! 🙂 UPDATE 17-07-2021:
  4. @Ploddles better or no? 🙂 about Monterey but also other system Whatevergreenkext should be disabled or "boot argumetated" well 🙂 if you are using 6900 xt otherwise black screen when login should happen
  5. @Ploddles my full EFI is always the same! now only a patch is not available and Devs decide when publish it I am helping to debug some stuff if algrey needs to test but all is working fine with latest GitHub AMD OSX patches and algrey one posted here and on insanelymac. obviously without unreleased one beta 2 does not boot with patches available for all is it possible to boot fine from 11.4 to 11.5 beta 5 to 12 beta1 I am trying also to create an interest to have more people helping devs to find patches and test well also in different conditions but my thread has had few success! 😉 Maybe @algrey gave me this chance because I was in touch with him from the first days when patches "was borked" PS it is possible to use Clover Bootloader and Opencore bootloader with the same set of patches (declared in proper way for both bootloader) clover needs two more patches , but as I said before all patches are posted here !
  6. @Ploddlesi am not in touch with shanee as I said I have had it from the creator..😂 @algrey I mean to reduce instead number of patches you have all you need unrealease patch is only for Monterey b2
  7. @iGPU https://pikeralpha.wordpress.com/2016/07/26/xcpm-for-unsupported-processor/comment-page-2/#comment-7296
  8. A long time ago some users who had dual CPU systems with the Xeon 2696 V4 22 cores 22 threads for each cpu for a total of 44 cores + 44 threads, we asked pikeralpha to take an interest in this, and he pulled the location where the kernel declared this limit out of the hat. and it was clearly a value of 3F. It was not possible to modify it in any way and it had to be limited as today by bios, limiting the total number to 64 c / t I don't find where we talked about it, if I find the posts I submit them to your attention If my second dose of Pfizer vaccine doesn't make me crazy, I also remember that we had to patch a kext..but no one has ever succeeded unfortunately and pikeralpha was not very interested in for testing I have changed 1F in 07 but I have in this way a kp in early booting steps
  9. Bonasera a te 🙂
  10. For Opencore and Clover bootloders: algrey - new Force set cpuid_cores_per_package (new version of original available @Inasanelymac) algrey _cpuid_set_info (unreleased) Goldfish64 - Bypass GenuineIntel check panic - 12.0 algrey - _commpage_populate - Remove rdmsr - 10.13/10.14/10.15/11.0/12.0 algrey - _cpuid_set_cache_info - Set cpuid to 0x8000001D instead 4 - 10.13/10.14/10.15/11.0/12.0 algrey - _cpuid_set_generic_info - Remove wrmsr - 10.13/10.14/10.15/11.0/12.0 algrey - _cpuid_set_generic_info - Set flag=1 - 10.13/10.14/10.15/11.0/12.0 algrey - Remove Penryn check to execute default case - 10.13/10.15/11.0/12.0 algrey - Get DID and VID from MSR - 10.13/10.14/10.15/11.0/12.0 algrey - _cpuid_set_info - GenuineIntel to AuthenticAMD - 10.13/10.14/10.15/11.0/12.0 algrey - _i386_init - Remove rdmsr (x3) - 10.13/10.14/10.15/11.0/12.0 XLNC - Remove version check and panic - 10.15/11.0/12.0 --- Published a first version on IM - algrey is improving it (refine its search) --- Unpublished (Useful to boot Monterey b1 and b2) --- Useful in Clover Bootloader and in Opencore Bootloader (if you do not use*: ProvideCurrentCpuInfo Kernel quirk) *Clover bootloader misses that quirk in release 5137/38 used by me! Opencore bootloader quirk I use: Opencore bootloader quirk I use: Clover bootloader quirks I use: I hope it could be useful to understand better!
  11. errori del config.plist che fortunatamente per il tuo sistema non sono gravi devi cercare le voci principali nel config e sistemarle come da manuale tra <> ti da una idea in che sezioni cercare l'errore 🙂
  12. [For Hackers] An utility to search a masked string Maybe an useful utility made by @slice
  13. @dreamwhitenon te lo so spiegare con matematica, ma per installare photoshop ed alcune patches per AMD puo' essere utile la sip Specifico patches per Photoshop! 😉
  14. @Ploddlesnew patches are good for 11.4.x, 11.5 b5 .12 b1 with unreleased single b2 patches all the patches are working also in b2 also with clover
  15. ciao, non c'e' un motivo..sto provando cose con clover! comunque in generale non ho problemi con qualsiasi valore di quelli noti
  16. fatto lavorare le nuove Patches anche su beta 5... tutto ok! 🙂 anche le "vecchie" vanno" nessun problema
  17. @iGPUgreat catch,, I think should be good 1F like we do...we miss @meina222he could test this and maybe it could be very useful without lock cores on bios..if 1F works as I think
  18. it seems you have had succes If not contact an admin thank you
  19. Non chiedete come 🙂 ringrazio @algrey che mi ha fatto provare in anteprima la patch per beta 2
  20. Hi @sileshnyou have a minimal of one or two message before it is unlocked automatically welcome here
  21. Always thanks @algrey, thanks especially to the mother of all patches, already posted by algrey on IM and here in our thread Very useful to further reduce the number of kernel patches to be used with AMD CPUs two old patches needed if compared with OpenCore bootloader, and some little problem caused by a very Clover Bootloader old bug, but..here we go!
×
×
  • 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.