Jump to content

fabiosun

Supervisor
 View Profile  See their activity

  • Posts

    11,148

  • Joined

  • Days Won

    512

 Content Type 

Everything posted by fabiosun

  1. fabiosun
    could you see if you do a step more with this? config-3-Arrakis.plist.zip
  2. fabiosun
    @Arrakis I was seeing your EFI posted in the first post of this thread. Opencore 070 and use of the patch: algrey - cpu_topology_sort -disable _x86_validate_topology this patch later included in the ProvideCurrentCpuInfo quirk It allows you to start without having that patch in the config.plist just by activating the mentioned quirk The patch in that form is no longer available, there is another one instead: XLNC - Disable _x86_validate_topology - 10.13/10.14/10.15/11.0/12.0 It is completely different and, in my opinion, much more invasive Now, it seems that you are unable to use neither this patch nor the quirk to go through the second phase of the installation .. I would not want the patch in this form to be invalid for your cpu. Although, in case it could be a big problem even for users of platforms lower than ours have to try asking other x570 platform users if they use this patch on their working rigs In case, can you post the config.plist you are trying to start Monterey with? thank you
  3. fabiosun
    @Arrakis i cant see on your image first KP part.. dummypowermanagemt is in my opinion the last thing to understand well togheter topology patch you need (included now in ProvideCpuInfo quirk)
  4. fabiosun
    With the publication of the updated kernel patches, now available for everyone, it is possible to clean up the thread, also thanks to the patch present in the PR published by Shaneee in the Opencore github, also applicable to Clover. So I'll clean up some of my posts by referencing this post (UPDATED 18-07-2021) AMD OSX Patches Shaneee Pull Request I provide quirks and patches useful for my system (and as regards the kernel patches also for different platforms such as x570, x370 and some FX AMD user) if you want or need to try your system with clover bootloader in OSX like Big Sur or Monterey Beta (1,2,3) For the moment I close here my experience with Clover bootloader, resuming it later if there will be any news! Clover-Kernel_Patches_Quirks.plist.zip
  5. fabiosun
    Just to explain that that EFI is not mine, but it is the same one you can get by downloading from here: https://github.com/Shaneee/OpenCorePkg later to compile it yourself. you can run the command found in the downloaded folder from the terminal : build_oc.tool you will find after some minutes in binaries folder two zip:
  6. fabiosun
    I agree with all above written @iGPU and, He remarked well about our TRX40 chipset @jsl2000has a different chipset and I think MMIO is not important for him I add an option to the comprehensive methodological list explained by iGPU The Clover Bootloader option 🙂 If you win the right dislikes as it is not as clear as it can work today .. It is a great option to try the patches without having to re-edit your config Months ago I reduced the number of patches I used thanks to one of the first clover(512x) who copied the way of working of opencore. Not completely reliable but it helps a lot to understand some relationships for example between patches,quirks (not all quirks are present) a bit OT below: now that we have all the same tools to start with the "new" patches .. As soon as you solve the problems you have with the updates and kext in use useful for you .. I would like to "attack" another controversial topic .. Relationship between: A) Quirk B) Patches Not in the conventional way or based only on configuration.pdf or on very famous guides that have often copied things from us (and pass me the joke, even in a wrong way) 🙂 so I would like to understand with you when you have your system fully functional the relationship between for example: 0) patches 1) DummyPowerManagement 2) RebuildAppleMemoryMap 3) SetupVirtualMap 4) ProvideCurrentCpuInfo in particular, because 1) not all trx40 users need it, but all Gigabyte users for example and x570 users Because 2) it can be circumvented in some cases 4) why an important patch like Disable _x86_validate_topology some need it and others don't and if it is not needed, what happens by activating the superquirk 4)? These are just thoughts of a midsummer morning 😉 but I wanted to share them with you!
  7. fabiosun
    No need of it if you use PR EFI edition it is included in quirk you use👍 I mean you don’t need of those 3 patches core count is inside provide cpu info quirk
  8. fabiosun
    @jsl2000with 072 debug of shaneee have you disabled patch 0?
  9. fabiosun
    I use Aquantia card of MSI trx40 pro same b1 patch you can find in my Efi i think I used yours posted time ago no problem there
  10. fabiosun
    I have installed from an USB installer to do a "clean" test With MacPro7.1 ,no WEG, only -v as bootarg a SSDT for GPU pM and other few stuff I have a pciex card for my 960 pro nvme and also Aquantia card as pciex card... two NVME on M2 slots and a bunch of mechanical disks and bd writer.. tb not inserted from a bit of time..so I can't say @iGPUif you have installed beta 3 and if you have time to test try to change MaxKernel of algrey - _cpuid_set_info - GenuineIntel to AuthenticAMD - 10.13/10.14/10.15/11.0/12.0 to 20.99.99 It seems not mandatory for Monterey I have also said @Shaneeeto verify it in his testing steps.. we verified it also on lower platform as x570 or x370 so it should be fine for all platform
  11. fabiosun
    thunderbolt card could be deactivated?
  12. fabiosun
    @Arrakisare you updating from Big Sur 11.4 or 11.5.x? you could also try to put all original kernel patches from AMD OSX Github and use a opencore EFI released official.. but your problem is weird I do not think is ImacPro1.1 SMBIOS you use...
  13. fabiosun
    maybe we could refine also this patch: algrey - _cpuid_set_info - GenuineIntel to AuthenticAMD - 10.13/10.14/10.15/11.0/12.0 maybe on this MaxKernel should be 20.99.99 it seems not mandatory for Monterey B3
  14. fabiosun
    @Arrakisi have put my EFi on OP maybe you can try to adapt your posted there and see Limit only kext in use because could need some update for some of it
  15. fabiosun
    @Arrakis kernel and quirks part seem fine I only will try to reduce your kext in this installation part (no experience for it in my case) IE I do not use SMCAMDProcessor.kext but only this AMDRyzenCPUPowerManagement.kext I think also this AirportItlwm.kext should be calibrated better..but I think @iGPUknows more 🙂
  16. fabiosun
    @all-trx40 users 🙂 the road we are following with the use of patches automatically through the "super powerfull Quirk" Personally I don't like it, and I told it to the right people I would not like to retrace a problem from years ago that happened with Clover with opencore .. Out of the blue the XCPM patches were applied through a cpu detect ... there was a popular uprising 🙂 Even today if you think about it, a patch is also applied to those who do not need it ... talk about the CPU topology ... Let's hope it doesn't automate too much My aim was to reduce unnecessary patches, but to leave the user complete freedom to understand what he is doing and to make mistakes on his own 🙂
  17. fabiosun
    Pero' se non ci fossero le persone come te o me e ad altri che provano subito e sistemano o danno log a chi sa sistemare...forse anche tuo marito ora installerebbe HighSierra 🙂
  18. 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
  19. 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
  20. 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
  21. 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
  22. 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 🙂
  23. 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 😉
  24. 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 😉
  25. 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
×
×
  • 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.