Jump to content

fabiosun

Supervisor
 View Profile  See their activity

  • Posts

    11,243

  • Joined

  • Days Won

    529

 Content Type 

Everything posted by fabiosun

  1. fabiosun
    😂😂
  2. fabiosun
  3. fabiosun
    ciao @Ramirez71si stiamo dicendo tutti la stessa cosa! 🙂 nei sistemi moderni con bootloader moderni se si resetta la nvram torna al primo posto quello che alcuni bios chiamano Windows boot
  4. fabiosun
    hi @naiclubit happens to all of us if you have multiple disk in your OS (change booting order) There is no solution Ciao, succede anche a noi se si hanno multipli dischi che fanno partire diversi sistemi (cambia l'ordine dei dischi) Non c'e' soluzione
  5. fabiosun
    yes @iGPUI have said this a couple of hour ago @Shaneee (also for others platform as x370 or x570 are not mandatory) Clover for me was useful to do this kind of testing I do not use them also from older releases I think they will be revisited also other typos in their commit...
  6. fabiosun
    Thanks @carlo_67he noticed I have forgotten a MatchOS for High Sierra in patch 17 so adding in it 10.13.x...bangggg all system start... I am updating above post 🙂
  7. fabiosun
    Tested in a rush Opencore new Patches! Work fine "algrey - _cpuid_set_generic_info - Disable check to allow leaf7 - 10.13/10.14/10.15/11.0/12.0" as before is not needed to boot.. I have asked if there is some unknown reason to maintain it As always thanks to the devs and patches maintainers!
  8. fabiosun
    For Opencore users: I have not tested this new and shining set of patches , I will do later I see they left some not useful patch as the "leaf"one we demonstrated here we can skip (trx40, x570, x370 chipset) Same typo as: For Clover users: for now I will stay with this set: it misses in my case HighSierra boot in clover bootloader, all others newer system from Mojave are fine IT WORKS! 🙂
  9. fabiosun
    and now...... https://github.com/AMD-OSX/AMD_Vanilla Patches for all..... 😛
  10. fabiosun
    Dear Clover's friend 🙂 attached here a minimal set of patches useful to boot these OS: 0) High Sierra 1) Mojave 2) Catalina 3) BigSur (tested 11.4 ,11.5,11.5.1) 4) Monterey(tested Monterey b1,2,3) if you like and you want to try: HS_MOJ_CATA_BS_MR.plist.zip If this set of patches is not working for you and you like to be useful to understand..post a debug specifying your system and if possible attach here your config.plist used! Thank you
  11. fabiosun
    finche' la barca va....
  12. fabiosun
    Hai aggiornato tutti i kext?
  13. fabiosun
  14. fabiosun
    @BIG_MATT potete fare come vi pare..ma attenzione..sarebbe sempre utile per il forum avere le discussioni pubbliche Spero tu capisca! 😉
  15. fabiosun
    I see an error in your config-OC-FX6300.plist: if you see this: 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 REPLACE high sierra to mojave: b8 XX 00 00 00 00 REPLACE from catalina to big sur : ba XX 00 00 00 00 for macOS HighSierra, Mojave, Catalina, BigSur 0090 should be 0000 in this way OCValidate passes with 0 error masking section
  16. fabiosun
    @Giaccaztu l'hai trovata a 240 euro? io quelle che vedo sono in asta... e spesso salgono anche sopra i 300...
  17. fabiosun
    @jsl2000 thank you so much for the tests you are doing and sharing with the forum I compiled the latest version of opencore taken from the official github and added the two useful patches for my operating systems (Big Sur 11.4, 11.5 and Monterey 12.b3 The patch for big sur works perfectly even if it does not pass the verification with OC Validate Tried the same thing with the High Sierra and Mojave patch too They do not pass the OC Validate validation, but then they work perfectly, allowing you to eliminate many of the patches related to the core logical processor and the core count. By the way, I allow myself to ask you very humbly, how come you still use all those patches if you use the new ones (0,1)?
  18. fabiosun
    @jsl2000old ones work for you (with FX cpu I mean)?
  19. fabiosun
    @jsl2000 old one: patch 0 that algrey posted on Insanely Mac is made for my processor in this example it is very easy to recreate it for other types of cpu (search on this forum new patch, below is the old one😞 PatchProvideCurrentCpuInfo set cpuid_cores_per_package f:4489EAC1 EA1A r:BA1F0000 0090 PAY ATTENTION Value 1F means 31, 3970 x has 32 cores so as stated by @algrey on IM 32 -1=31=1F IE for a 8 cores CPU : 8-1=7=07 for 3950x or 5950x 16: 16-1=15=0F and so on newer (not latest because it is not public for now...but a good one) 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
  20. fabiosun
    yes.. you can try to use old patch for it or try to verify better the schema proposed here (I will find for you if you do not find it) two kind of patches were proposed from the start one core number -1 (count 0 and other stuff) two a more articulated ones with mask and replace masking (count 1) remember..if they have not published in a clear way..a reason could be there 😉
  21. fabiosun
    OC PR Patches.plist.zip to explain better (I hope in a better way I mean) attached here patches I use withOpenCore PR 072 No, only in 072 PR Patches 0,1,2 are included in that quirk
  22. fabiosun
    @jsl2000OC PR does not need of any of them...they are included in OpenCore
  23. fabiosun
    @Arrakis this one is not a patches problem: "An error occurred while preparing for installation….." I would try to download again the installer
  24. fabiosun
    @jsl2000 Lightening the number of patches in the config.plist, leaving only those that are really useful for the systems you have installed, certainly does not solve your "cosmetic" problem on the CPU name .. but it helps, maybe, to better understand any others problems imho you should do this with both clover and OpenCore
  25. fabiosun
    @jsl2000 if you use this quirk as I see in your config: ProvideCurrentCpuInfo you can disable these 2 patches: then if you have how I see first two patches you can try to disable all patches you see with core logical string in comment section... if you use also clover you can test easily with it this my latter assertion
×
×
  • 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.