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
    Confermata la versione di RC2
  2. fabiosun
    @Arrakisfrom this EFi and its related config.plist you can disable patch n.6: algrey - cpuid_set_generic_info - disable check to allow leaf7 then I see also this enabled: ProvideCurrentCpuInfo if you enable this you can disable: 13 and 14: algrey - tsc_init - remove Penryn check to execute default case algrey - tsc_init - grab DID and VID from MSR with ProvideCurrentCpuInfo is also included this patch as you know: algrey - cpu_topology_sort -disable _x86_validate_topology I still haven't been able to figure out who wins if the quirk and patch topology are activated at the same time I asked for clarifications but at the moment I have not received them 😉
  3. fabiosun
    sorry, I see now you are in Big Sur OS and so it could be unrelated your CPU panic . For many problems are with new patches for Monterey, overall for beta 2 an 3.. I am lucky, with my MSI and 3970x I have had no panic if I do not experiment too much Proxmox way is different story and there many AMD cpu instruction are bypassed by virtualisation
  4. fabiosun
    ciao @Allubzit seems (it is a my only opinion not confirmed by facts) that many users with 3960x have some problem, do you use Dummypowermanagement quirk? maybe that problem I see also in @Arrakisrig could be topology related... I will stay with regular Opencore and use old way to patch core count
  5. fabiosun
    ciao @Nestorse l'hack che usi e' quello in firma e' anche sovradimensionata!
  6. fabiosun
    @Driftwood i can’t be an example because in this task I did many experimental test with also unreleased patches or Efi, also with clover bootloader. now I am also using an unreleased count core patch included in a opencore debug release(I can’t see the difference in hex because it is yet compiled). all this to say that in my case I have had zero problems to update from 11.4.11.5 12b1 or greater i am using a simple configuration as usual and only aquantia Ethernet and a pciex4 adapter for my third NVME drive. Motherboard nvme are fulfilled like 7sata ports with mechanical disks Listening on the net some people have different problems to update overall on beta 3 i can’t say it because I hadn’t this problem at all. by the way happy filming👍
  7. fabiosun
  8. fabiosun
    RC2
  9. fabiosun
    CINEBENCH R15.038 I use this version , I hope it works also for you
  10. fabiosun
    I did in this way (sip disabled) otherwise I have this:
  11. fabiosun
    Ciao Carlo above 4g i can use also off on 4g try by now 🙂 edit: no differences here
  12. fabiosun
    Benchmarking Monterey B3 and new PR EFI: in Cinebench 23 84° (4* more than Big Sur ) and a bit less of multicore benchmark
  13. fabiosun
    After the countless tests done in this period, which still continue, I got to enjoy a little beta 3 with the programs I use Adobe suite works perfectly with the apps I use (Photoshop, After Effects, Media encoder and Premiere Pro) Blackmagic Davinci Resolve also seems to have no obvious problems Another positive note is also that the sleep / wake continues to work perfectly well!
  14. fabiosun
    Ok I would have liked to prepare an Efi for you i respect your decision👍
  15. fabiosun
    @Arrakiswould you like to try a different approach? clover bootloader I mean let me know if you like
  16. fabiosun
    It seems many people have some problems to update to beta 3 from Big sur I have had no problem in update from beta 1 and from 11.5 rc also all is fine from a clean installation from usb pen
  17. fabiosun
    could you see if you do a step more with this? config-3-Arrakis.plist.zip
  18. 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
  19. 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)
  20. 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
  21. 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:
  22. 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!
  23. 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
  24. fabiosun
    @jsl2000with 072 debug of shaneee have you disabled patch 0?
  25. 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
×
×
  • 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.