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).
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).
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!
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:
Weird... Can you make a backup of your EFI folder and then try with WhateverGreen.kext removed? WhateverGreen.kext can be found in /EFI/CLOVER/kexts/Other/. Can I just disable it in Clover (spacebar -> options, block kext) without removing the kext itself? Should be pretty easy to roll-back...www.tonymacx86.com
excited to try out your thunderbolt3 ssdt after that @rj510 !
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.