Leaderboard

BIG SUR INSTALLATION EFI I'm posting here an EFI that not only boots the TRX40 bare metal into Catalina or Big Sur, but also allows a Big Sur Install from either a USB Installer, or, having the installer app within the Applications folder. I tested both methods of Big Sur install with destination drives that are internal and external USB. [ Debug Version added at bottom ] There are a few important details that I'll point out below. In a subsequent post, I'll show how removing Snapshots can allow proper read/write of the disk (and this may allow you fabiosun to get your kexts loaded, but I cannot check, so I don't know for certain). That post was divided into 2 parts here and here. Besides booting Catalina and Big Sur, this EFI also seems to have a consistent, properly functioning Shutdown in Big Sur (but not so regularly in Catalina). Shutdown also works from Big Sur Recovery. However, while Shutdown works from the Apple menu, it does not seem to work when using the log-in screen Shutdown button, but gives the usual panic re-boot. I would recommend not changing anything in this EFI (except perhaps for very select items like Ethernet discussed towards the bottom). This EFI uses OC v061 commit from 25 Aug. This commit allow proper booting of Big Sur Recovery without resorting to ScanPolicy 0 or the need to Enable/Yes JumpstartHotPlug (ScanPolicy discussed more below). There are no re-name SSDTs nor any fancy stuff: this is basic, functional EFI. First off, there are 3 config.plist files as shown below. The active one is simply a duplicate of config-basic-genPI-BSinstall.plist as a backup. The other config file, config-basic-genPI, is the same but without boot args (-v, -no_compat_check, and amfi_get_out_of_my_way=1), Those boot arguments will be discussed in the subsequent post, but they're really only useful during a Big Sur install and are otherwise not necessary. Notice that the Slide boot argument is removed. It seems not necessary and avoids conflict with other mobo builds. Config files: Boot Arguments: The other thing to point out is the csr-active-config value of 77080000. This value was gleaned from user "fusion71au" on the InsanelyMac forum and disables both csrutil and csrutil authenticated-root. Disabling these two allows for working with Snapshot files (that will be discussed in the subsequent). This 77080000 value can be used for both Catalina and Big Sur. Some may need to remove npci=0x2000; it is required for me as I leave "Above 4G decoding" disabled in BIOS. Moving onto ScanPolicy shown below. With this latest v061 commit, a proper ScanPolicy (rather than 0) can be used that limits filling the boot menu with useless EFI folders. This scan policy allows for the following drives to appear in the OC boot menu: APFS, HFS, SATA, SASEX, NVME, USB and PCI devices (the latter includes virtual disks, so this is a good ScanPolicy for a Proxmox VM config file). The Auxillary items (like Reset NVRAM) are accessed by pressing the spacebar on the keyboard while viewing the OC boot menu. (Another item that can be activated while viewing the OC boot menu is turning on verbose mode by pressing <Cmd><v>; p 33 of included Docs.) An important new OC setting is changing SecureBootModel to Disabled. The Default value, recommended by the OC Docs, will prevent many things from working, such as the Aquantia kext patch. Don't change this unless you have a good reason. The next issue to discuss is MmioWhitelist. There are references on the Dortania OC Guide for AMD (which has been discussed earlier on this thread) that are incorrect for the TRX40 build. I've tested these values and they don't work; but I've included for illustrative purposes. The MmioWhilelist array that is active (shown below) is actually empty. The other inactive one contains the MmioWhiltelist for my mobo (MSI Creator, which I posted earlier in this thread). I do not know, nor can I test, whether this will work for any other mobo. I would encourage deriving your own for your mobo. Finally, as far as ACPI, kexts and drivers, only a minimum are included. As mentioned earlier, the only other section you might adjust is if you need a different Ethernet driver from what is included in this EFI: SmallTree82576 and Aquantia AQC107. The AQC107 is activated by a kext patch which is Enabled/Yes (and was discussed by Pavo on the InsanelyMac forum). These two cover a majority of our builds and allow at least one Ethernet port to work. BT/Wifi kexts are included and presently Enabled/Yes; these will work with swapped cards as well as PCIe AICs. WEG is Enabled/Yes but partially disabled thru the -wegbeta boot argument. If WEG is left fully Enabled, Big Sur will not boot in bare metal. Lilu, VirtualSMC and AppleALC are Enabled/Yes as is AppleMCEReporterDisabler. Since this EFI is more inclusive and robust, I will delete the EFI folder presented on page 1 of this thread and replace it with a link to this post. As usual, you need to supply SN and SystemUUID values in the PlatformInfo/Generic section before using. EFI-v061-8e2755f-BareMetal-USB-installer-Public.zip Debug version (this is same as above, but does not contain the Install boot-args). The config file is different, adjusted to give more reports, so do not swap between release and debug versions. EFI-v061-8e2755f-BareMetal-USB-installer-Public-Debug.zip

What I will write below is a bit OffTopic. I remind everyone, in particular those who read us but do not actively participate in the forum, that it is very important to respect some rules dictated mostly by common sense: 1) give due credit to people who share their experiences for free 2) not to steal, clone users' github without their direct permission The spirit that I would like to create and that in part I think is already in place is to share with all the people with a minimum of salt in the pumpkin (pumpkin is an acronym for head in Italian :)) our experiences on this new and fascinating possibilities we have with the TRX40 I hope you understand. I also take advantage of this OffTopic to remind you that any EFI posted is used at your own risk ... just a simple advice is valid ... do all your necessary checks before using the EFIs provided (kindly and free of charge) by the most 'willing 🙂 users

@iGPU Good work. I used your config and EFI changing only UUID stuff as usual. Result. This seems a better candidate of EFI than my previous one. For some reasons audio is much improved with choppiness so far. Davinci works better and is pretty good with a lot of Studio edition noise reduction which would barely play before on the old .60 OC EFI - which was a bastardised version of Pavo's & Fabiosun. Havent got round to analysing MMIO yet but will do shortly. Shutdown didnt work for me on my first attempt... Ill give it another go. MMIO Asrock Creator DEBUG from OpenCore xxxxx.txt Driftwood's Asrock TRX40 Creator Hex to Decimal PDF: MMIO ASROCK TRX40 CREATOR - Driftwood.pdf.zip

@iCanaro, Grazie di tutto l'aiuto fornito, per il momento ho riconsegnato il pc a mio figlio, lasciando il tuo Config.plist dove funziona bene la grafica, rinunciando allo stop, gli ho aumentato il tempo di spegnimento. Ciao

Will be very helpful, saves a lot of time, thanks for the work :)

@meina222 our MMIO are pretty similar they diverge in the latest 4, these ones are also problematic to skip in my case

Ok..good news playing with MMIO and with opencore 061 i have solved reboot/shutdown problem... now it is working as it must work

Forse perché Ntfs è un file system di Windows? ))

Windows 10 20H2 pronto per i test finali in attesa del rilascio ufficiale: - L'installazione, quando disponibile, avverrà in pochi minuti come per un normale Aggiornamento Mensile :)...

@Ploddles update: BIOS reflash did the trick. Probably could have done it without reflash, and just a restore defaults followed by the recommended settings. Got my audio jack working again. Thanks to you and @iGPU and @fabiosun for the support and patience. 🙂

Thank you. Yes, I want to retry to whole thing - need to find some time, busy week for me. I will rebuild the EFI from scratch and redo MMIO and might try to guess an initial pattern similar to your file.

Ok..cosi va bene?sto provando di nuovo tutti i layout ma prima vorrei sapere se non ho sbagliato..ovviamente in Devices ho tolto i layout 😛