Leaderboard

@ckrueger99in my opinion your is the best available motherboard I like it as I like gigabyte designare ex.. for ASMedia I think you can try some kext but not tested by me

Okayish... This is Big Sur beta 6 (Prox to come) Im running on standard BIOS RAM setups not Performance if that matters...!? Plus I had a few apps running inc safari 🙂

Here are C15 results for both bare metal and VM on AMD. Both are lower than Intel side. Based on what I'm seeing, I don't think C15 uses both Radeon VIIs. Meanwhile, MarkLux does, as the scores below are consistent with Intel side where I have one Radeon VII on that system and it gets 54,000 on LuxMark. Also, LuxMark gives same scores for dual Radeon VII in VM and bare metal. Big Sur ß6 bare metal, dual Radeon VII (XMP was on, 4G enabled and only 13 kernel patches--sourced from Pavo) : C15 Test using Proxmox VM, dual Radeon VII (Mojave): SMBIOS Comparison (LuxMark): dual Radeon VII, BS ß5 (iMacPro1,1 vs MacPro7,1):

Here is my Cinebench 15 on Asrock TRX40 Creator, Vega 64.

@ckrueger99 thanks if you see we have a thread about Titan ridge I have also put some pictures to explain how I have achieved 3,3v with most used eprom programmer I have no skill in this subject and I have tested volt in both setup

Ok, I will try SSDT generation using this method (taken from a tonymac thread I'm reading, to be honest I have no idea what this does besides the promise to generate unique ID for the network ROM). I need to modify PCI path too from the template. I'll report the results later when I get a chance to test. https://hackindrom.zapto.org

This is the more up-to-date link, which uses 3.3V natively.

Yes, but I did not use the white wires he soldered on the board. Technically, you should use a volt meter and check voltage, but I got lazy and did it anyways. Flashed twice, no problem using https://www.amazon.com/gp/product/B07SHSL9X9/ref=ppx_yo_dt_b_asin_title_o00_s00?ie=UTF8&psc=1 and the clip + the 25XXX green PCB oriented correctly ('1' on the PCB facing the lever on the lever side and red wire routed from 1 to the BLUE dot on the chip). I would 1st watch this video and then check the video from the German gentleman.

You basically program the stand alone mode by copying your input/ouput setup into firmware of the RME FF800. Then you detach it from computer and use it live on the road or studio and it will retain those settings for Input/Output path as standalone. See manual. If you are switching it between computers all settings are retained. The RME FF800 drivers which work both in Catalina and Big Sur are here: driver_fw_mac_339.zip The same driver works under Proxmox with non-abridged firewire card like mine! Though, it is not as 'reliable' as bare metal. I use two RMEFF800s. They're stilll top quality! However, I am about to buy the newly announced AIO Pro (RMEs new AIO card version which is clean (no headphone noise) and better pathways in the digital process. For me (who uses predominantly plugins inside Logic and Avid Pro Tools) the AIO card is just as good as an MADI FX card which is a little bit more expensive but if you require a ton of inputs /outputs would be better option. The AIO Pro card is released within the next two weeks Synthax tell me - Price around 560 - 650 EUs/dollars/GBPs

flash worked like a charm from 1st try, no modifications. Will try it in the hack later.

BS Beta 6 Firewire Audio Tip: So firewire/fireface seemed broke (crackly). But you just have to reinstall drivers. Anyone using Firewire cards plus something like a Decklink capture card. Install Decklink first followed by a reinstall of fireface drivers from RME will get firewire audio working again. The Apple firewire driver works as good as old times!

@Gengik84 e @iCanaro Installato... ✌🏻 Riconosciuto come: iMac Pro 3,4 GHz intel Core i5 6 core 16gb 3200 MHz DDR4 Radeon RX 5700 XT 8 GB come numero di serie mi da “???” Le usb funzionano tutte (non benissimo, noto con il mouse che lagga, come se l’imput arrivasse ad intermittenza) tranne due nel retro 2.0. Lo stop funziona solo se ripreso dopo pochi secondi, poi non si riesce più ad attivare. Audio funzionante. Per tutto il resto mi sembra vada bene, domani lo spulcio con calma...prossima tappa, mappatura delle porte usb? Per concludere vorrei ringraziarvi tantissimo ragazzi, mi avete aiutato tanto e la mia vittoria è anche la vostra

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

Oggi un Rivenditore mi ha mandato un Video su un computer assemblato da un altro Rivenditore (non si dice chi), il video spiega bene a che livelli si può arrivare... - HDD.mp4

Intel® Core™ i7-9750H https://ark.intel.com/content/www/it/it/ark/products/191045/intel-core-i7-9750h-processor-12m-cache-up-to-4-50-ghz.html

@nick0k si vero, era presente, ma ora in questo config l'ho iniettata da properties, prova config.plist.zip

posta la EFI che usi ora si potrebbe aggiungere in device properties EDID del monitor sul percorso PCI della 570 inoltre la HD630 è configurata con o senza uscita video? se serve solo per la codifica, si usa senza uscita video Empty Framebuffer 0x59120003 (default)