Jump to content

fabiosun

Supervisor
 View Profile  See their activity

  • Posts

    11,289

  • Joined

  • Days Won

    534

 Content Type 

Everything posted by fabiosun

  1. fabiosun
    @1515thank for you config.plist ..I do not know useful for? but thank you have 2 Force cpuid_cores_per_package on the bottom of your list they should be on top Otherwise some problems could happen with other patches
  2. fabiosun
    Yes @iGPUif I have compiled it well😅 UPDATE 17-07-2021: I tried again the EFI deriving from Shaneee's Pull Request and it works. Consequently, I clean up all my posts, putting this post written here as Edit - Update. I update accordingly the first post with the EFI that I use. If there are no contraindications during the further daily use tests, I will use the EFI as my primary. If you do the same with your posts, please notify me or clearly indicate it in the same posts that you are going to modify thank you
  3. fabiosun
    Hello everybody in the attachment I add another variable for you that could cause more confusion .. (ehehehe joking) But in the spirit of always sharing everything that is possible to share ... 🙂 :P attached the EFI of opencore that can be obtained by filling in the Shanee Pull Request posted in this thread: OpenCore-0.7.2-DEBUG-Shanee.zip attached also patches I use with this EFI 🙂 remember now a quirk includes a lot of patches. Patches for PR EFI.plist.zip latest to patches are for Aquantia ethernet card I use) Patches are for BigSur and latest Monterey Beta (1-2-3) Disclaimer: this PR EFI is not yet approved by Opencore Devs team and it is not included in official release or beta from them
  4. fabiosun
    sometimes the difference in language makes talking between us complex :P patches work, you just have to adapt your quirks to the latest news If you want better help Post your EFI which worked with older OSX. And if possible, put your pc specifications in signature! thank you
  5. fabiosun
    @Ploddles i think @iGPUpatches revision is good for you , maybe you can disable a couple if you do not use Mojave and high Sierra and if you use Big Sur >= 11.4 🙂
  6. fabiosun
    there are big changes happening now in the AMD community, hoping for new developments that include in the most used bootloader (OpenCore), some features that will make life easier for many .. I am attaching the config I use today for maximum functionality It Uses the latest patches, some only available in the opencore PULL Request made by Shaneee I hope you find it useful. It works from Big Sur 11.4 to the latest Monterey beta (b3) I recommend ... make good use of it 🙂 config.plist.zip if you use a X570 or lower platform, you may have to use also: Shaneee or Algrey - _mtrr_update_action fix PAT - 10.13/10.14/10.15/11.0/12.0 enjoy it 😉
  7. fabiosun
    new patch algrey - Force cpuid_cores_per_package: Below I hope an useful schema taken from Shaneee Opencore PR COMMENT: algrey - Force cpuid_cores_per_package FIND: c1 e8 1a 00 00 00 MASK : FF FD FF 00 00 00 BASE: _cpuid_set_info COUNT: 1 REPLACE high sierra to mojave: b8 XX 00 00 00 00 REPLACE from catalina to big sur : ba XX 00 00 00 00 REPLACE MASK high sierra to big sur : FF FF FF FF FF 00 REPLACE monterey : ba XX 00 00 00 90 REPLACE MASK monterey : FF FF FF FF FF FF 3970x --->32 cores XX=20 3960x--->24 cores XX=18 3950x--->18 cores XX=10 and so on 🙂 so for all system from high Sierra you have three different patches (common find and mask) different replace and replace mask minKernel and maxKernel do the jobs to enable proper ones for OS you use I am using an old patch posted on @jsl2000config.plist which works in BIG SUR and all Monterey Beta But latest PR uses above patching 😉
  8. fabiosun
    @PloddlesI asked your config because I have to see also used quirk I think you are using a new opencore version and I have to know if you have enabled this quirk: ProvideCurrentCpuInfo
  9. fabiosun
    @Ploddles it's all happening now and I've personally tried to get all the information I could I've also been working from the start to get clover going so I'm sorry if I haven't been clear Now you have everything available the only patch you need to calculate after you add the new ones or update the old ones is the one posted above That allows you to delete several other patches if you want as I did for jsl2000 if you send me your config working with big sur I try to fix it But I don't have any experience with wifi and blurtooth that I don't use 🙂
  10. fabiosun
    @jsl2000I know you use also clover bootloader.. with that bootloader same patches plus 2 more. Obviously converted with right names 😉 by the way you can also refine your 0 patch, but in this moment I couldn't advice to use PR ones because I have not tested it properly. then..with these set of patches you can boot also Big Sur from 11.4 to 11.5 release
  11. fabiosun
    great Thank you @jsl2000 remember proper credit to this forum on "others" 🙂
  12. fabiosun
    @jsl2000if you want try this config-4.plist.zip
  13. fabiosun
    @jsl2000 I see too many patches in your previous config try to reduce and then try to use 0 patch with a value of 07 Now you have 08 in replace then you have also to enable quirk I have said
  14. fabiosun
    jsl2000 sorry only one of this are the same patch only a different revision and both wrong
  15. fabiosun
    no @jsl2000 has your cpu 8 cores? if so with 0 patch you use in your config it is no good now I am solving a problem caused to me from new patch and the experiment but patch you use has no mask so you have to fill better replace if 8 cores 8-1=7=07 then also count should be to 0 in that initial patch @jsl2000you have also to enable quirk: ProvideCurrentCpuInfo
  16. fabiosun
    pay attention in my case and only tested with other bootloader this PR new patch is not working.. I can use the one posted on insanelymac by algrey (useful only for OSX greater than HighSierra) So if you want try @your own risk as usual with a solid backup to recover 😉 post your config.plist only you should also post a debug..just in case 🙂
  17. fabiosun
    and this is my patches list now to boot from Big Sur to Monterey beta 3: Patches_BS_MR_1_2_3.plist.zip You have to add (in initial position this): Force cpuid_cores_per_package from @Shaneee PR or with old one published on insanelyMac by Algrey (with cores number -1) now without -1 for your cores number (not tested by me because i am using a different way) so core count with above patch is: 32 cores - 3970x =2 0 24 cores - 3960x = 18 16 cores - 3950x = 10 10 cores = 0A 8 cores = 08 6 cores = 06 Update: I prefer to use old patch for "Force Cupid_cores_per_package" but for someone could be fine to use it also Update:2 Patches in PR works also in clover bootloader , it was a error of mine (missing Procedure on it)
  18. fabiosun
    hey guys....maybe you have missed something... 😛 b2/b3 patch has been published.... only read me is old.... secret was revealed by Shaneee a day ago or more 🙂 🙂 the secret is gone 🙂 🙂 🙂
  19. fabiosun
    @A23SS4NDROmy was a question not a statement I have seen your link i boot with 960 pro in OS X it seems I have not any delay i will check better maybe ten seconds from boot menu to login page for trim I always used default custom config posted in opencore doc
  20. fabiosun
    @Jaidyi did only davinci candle benchmark for graphic gpu is about 5% slower than latest Big Sur cinebench23 is the same as previous os
  21. fabiosun
    Hi welcome here
  22. fabiosun
    no @iGPUit is a 960 pro 1Tb MVME Mounted on a pciex card as you can see in this bad picture :
  23. fabiosun
    Hi and welcome here. files are there you need a minimal 2 posts to download files from here and also in forum download area!
  24. fabiosun
    thank you @iGPU it works also in M-ß3 😉 with kext: without kext: Nvme in this pictures is on a pciEx card and it is seen by default as Apple SSD Controller Or Samsung 960 pro is more compatible with apple? IDK
  25. fabiosun
    Grazie @Sundrawda una versione di Big Sur in poi va nativamente
×
×
  • 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.