Nice work.As for the USB section, I provided an image to show that I chose not to use the USB ports beneath the Ethernet port: HS09/SS06. On the boot page of the Clover config file, I further eliminated via uia_exclude the following: HS07;HS08;HS09;HS10;HS11;HS12;HS13;SS05;SS06;USR1;USR2. The WiFi/BT unit uses HS14. My active USB list is thus: HS01, HS02, HS03, HS04, HS05, HS06, HS14, SS01, SS02, SS03, SS04, SS07, SS08, SS09, SS10. SSP1 and SSP2 are not include in the 15 USB limit and are associated with TB3. SS10 seems to be a USB-C for the case front (labelling on mobo to follow).
I have not yet placed the board into a case, so I've not yet tested the internal USB 3 header, but I have used the internal USB 2 header and marked it in an attached image (HS01/HS02).
Thanks for the USB3 header info; I updated the mobo image. I'll upload the *.dsl files soon, but only the USB-UIAC file will have any comments.Regarding USB, to complete your list, on a USB3 header:
HS10,SS10 is the first one
HS11,SS08 is the second one.
It would be nice if you could post also the respective .dsl files (the .aml can of course be decompiled, but its always nice to have the source).
In the Aorus build, I used a FireWire board (Vantec FW 800/400; model UGT-FW210) and it integrated just fine in either of the PCIe-x1 slots, requiring no special drivers (I sourced locally, but I've seen them at Amazon).
If you have installed a Firewire PCIe card and find that your computer does not shutdown, then you can try this fix:
- In the ACPI section of Clover Configurator, enable the checkbox for FixFirewire.
- Save the file and reboot.
Thanks to @victor.vhv for this tip!
I did not mention, but as you found out, EmuVariableUEFI is useful to get past the panics and once iCloud and FaceTime are working, this file can be removed. As for the iGPU, I use it leaving the PCIe slot empty. Also the BIOS needs to show that the iGPU is being used, not the PCIe slot and need to bottom of the same window, that the iGPU is 'enabled' (see the BIOS uploads in my post). Also, I only used the i9 9900K chip and don't know what frame buffer changes you might need for the Clover config file. If you can get the iGPU going, try using Hackingtool to create the proper frame buffer for your i5.thanks for the detailed writeup @rj510 !
I just installed 10.14.5 on this board + i5 9400 + pulse RX580
had kernel panics on shutdown, adding EmuVariableUEFI and 'slide=0' seems to have fixed it.
my igpu is not recognized, going to try this solution:
Thank you! Now I'm still on iMac 18,3 too under 10.14.5 (updated MacOS just fine!). Can I safely modify the sysdef to 19,1 now? But I put 0x1009 in CloverConfigurator: ->CPU->Type ... but I read also of 0x1005 for i9-9900K , which one is correct or the best? Now in CloverConfigurator...www.tonymacx86.com
excited to try out your thunderbolt3 ssdt after that @rj510 !
I've been routinely running with the following (see image), without EmuVariableUefi-64.efi and I've had no panics, at least with Mojave 14.5. (I did run Clover_v2.4k_r4920.pkg on my boot drive to install RC scripts.)EmuVariable is required for this (and most other Z390 boards), as the BIOSes for these boards (which are based on a newer version of AMI Aptio) are not (yet) compatible with Aptio*MemoryFix in regards to nvram writing - so native nvram does not work under OSX.
When OSX reboots or shuts down the NVRAM content is being written. Without EmuVariable, the board's native nvram is trying to be accessed for writing, which results in a panic.
What do you mean that it can be removed? It will be possible to remove EmuVariable only when AptioMemoryFix will add nvram write support for the newer boards, which, as far as I know, is not yet being done.