Leaderboard

Read this summary along with fabiosun's post preceding that post to understand what is going on with the new Quirk and patches. RestrictEvents has nothing to do with booting; it's more cosmetic. (You might also read this link too to get an idea of the EFI structure.) The basic factors affecting booting are: Booter/MmioWhitelist Booter/Quirks Kernel/kexts (mostly Lilu and VirtualSMC) Kernel/Patches Kernel/Quirks fabiosun in his uploaded OCv072-Shanee EFI has it all laid out. Change very little or you will make things difficult for yourself. Don't be creative at this stage. You only need to adjust your mobo MmioWhitelist as most everything else will work for all of our TRX40 mobos. For some reason, many people keep changing the Quirks around and this is a guaranteed way of getting a boot failure. fabiosun and I have kept the Quirks the same for several days now. *** To avoid trouble when experimenting with your EFI, I would suggest doing the following. To keep testing simple, my BIOS is set to boot from a known, working EFI (call it #1). I have the same, working EFI on another drive (call it #2 that I do not change; this is my backup EFI) that I can access by pressing F11 during boot (may be a different key for your mobo). EFI #2 is my backup guaranteeing that I can gain access to my computer (yes, I also have external USB EFI serving as even more backups). At this stage, what ever EFI works (boots) is okay; don't worry about minimal patch lists, etc. EFI #1 will then become my experimental EFI that I change. In addition to different EFIs, one of these two drives contains a known working macOS (such as Big Sur). The other drive contains the new, to-be-tested macOS (such as Monterey). During the automatic boot, EFI #1 is selected and once the OC menu appears, I then select which OS to enter. Again, I test on the EFI #1, making any changes only to it (not EFI #2). If I break it, such as by using a bad patch, and it won't boot, I re-start computer, hold down the F11 key, select EFI #2. Once booted through EFI #2, I can then make changes on EFI #1 and test it again, repeating this cycle as desired. If you only use one internal EFI and drive, your backup EFI could be an external USB. I tend to use internal drives and their EFIs for testing, since USB drives are slower to boot and prolong the test cycles.

Grazie per averlo poster Questo strumento fa risparmiare molto tempo

Ok I would have liked to prepare an Efi for you i respect your decision👍

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!

Nuova app da @chris1111 fresca fresca per ridimensionare un immagine da usare come background senza l ausilio di photoshop o altro https://github.com/chris1111/Background-Resizer L immaggine verra ridimensionata in: 3840x2160.png-5120x2880.png-2560x1600.png-3840x2400.png-3360x2100.png-3200x2400.png-3200x1800.png-2880x2160.png-2880x1800.png-2732x1536.png-2880x1800.png-2048x1536.png basta scegliere poi la nostra risoluzione e convertirla in .icns con https://github.com/chris1111/OpenCanopy-Generator

@fabiosunno, i don't prefer to test with clover i don't know anything about it. I prefer to stay on opencore because at least I am on familiar ground. even though I don't have your knowledge levels.😀

A few comments regarding your config file. But first, are you trying to boot into BS or new Monterey; if latter, then do a fresh install (as I mentioned in a recent post above). When systems behave strangely, remove un-necessary items. In your case, remove the TB AIC (and note Spoiler below) and any USB devices if possible. Kext adjustment (also, if not necessary, since you had so many problems with I225, maybe disable those kexts and unplug your ethernet cables until system booting reliably): I'd use change these Kernel/Quirks (Boot/Quirks look ok): And you might try a MmioWhitelist variation: Your Patches look ok, but the following are not needed for BS onwards and could be removed: Finally, the UEFI section: a few changes to try:

@fabiosun As you can see, I have the exact same quirks as yours. This means that it is starting to have uniformity between motherboards. (MSI TRX40 Creator, Gigabyte TRX40 Aorus Xtreme, MSI Trx40 Pro 10G, Gigabyte TRX40 Designare) I have to keep the DummyPowerManagement activated otherwise I get this error (Screen capture) I'm still on your version of Open Core 0.7.2. I will try to remake a Monterey B3 instal today if I have time. @PloddlesDo you also have to activate Dummy Power Management?

devi estrarre le api e ioreg e provare controlla il disco non sia formattato con mbr deve essere in GPT io te la riallego ma solo per provare per quello sempre da USB tutto Materiale dal sito https://www.macos86.it/ niente di mio Archivio.zip comunque prova poi allega ioreg e il Config eventualmente posta la foto del blocco i dottori faranno la diagnosi 👍

Bingo 😄😄 GRAZIE mille @antuneddu

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

Come mai hai Windows fra i volumi nascosti ? prova a toglierlo la cartella Bootstrap in CLOVER e' un residuo di OC ? penso la puoi eliminare uso solo 3 driver per avviare Clover ; ApfsDriverLoader.efi,OpenRuntime.efi,VBoxHfs.efi fine ti servono tutti quei driver ?

😂 Neanche io, non quel tipo di hardware quindi non ho provato, ma credo dovrebbe essere un pò come quella di Chris1111 con installazione guidata https://dortania.github.io/OpenCore-Legacy-Patcher/

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:

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

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

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

Ciao antuneddu e marco, scusate ma non ho avuto tempo. Questa sera finalmente in 3 secondi netti ho risolto il problema con bootice. Grazie mille, problema risolto. 😀

Those very duplicate boot entries is why OpenCore has this (red box) to eliminate those duplicate entries. It sounds like you should enable this Quirk.

I'm just like you, no one can help me. I used to follow fabiosun's style but never had success. but there was one time that ever succeeded A long time ago 4-5 years ago, before replacing the boot system with UEFI clover, it was a lackacy boot. I'm sorry, no one will help us. Risolto di nuovo Ora avvia tutti i sistemi usando Clover//** tranne OC. apparirà immediatamente sullo schermo blu