[SUCCESS] Gigabyte Designare Z390 (Thunderbolt 3) + i7-9700K + AMD RX 580

[smashdownbabylon]

Holy COW IT WORKS!! It works perfectly! UAD Apollo 16 mkii x2 daisy chained and 99.999% functional, WooHoo!!!!!!!

Can switch sample rates on the fly without total audio destruction, everything configurable and recognized like it would be on a real Mac!

I am floored. Thought it was still broken earlier, but just needed a hardware reset on the UAD side and a clean boot(no audio apps open on startup, to “grab” core audio or the drivers attention) and BAM, full on thunderbolty latency free hidef audio awesomeness on 32 physical channels!

Thanks again @CaseySJ for your technical prowess, and thorough instruction methods, you are an absolute sage. I owe you like so many beers....

 

[CaseySJ]

@CaseySJ Here is the IORegistryExplorer screenshot--I don't see HS11 or HS12

You must be using USBInjectAll 0.7.5 instead of 0.7.3. Please type this in Terminal:

kextstat | grep -v apple

 

[CaseySJ]

Holy COW IT WORKS!! It works perfectly! UAD Apollo 16 mkii x2 daisy chained and 100% functional, WooHoo!!!!!!!

Can switch sample rates on the fly without total audio destruction, everything configurable and recognized like it would be on a real Mac!

I am floored. Thought it was still broken earlier, but just needed a hardware reset on the UAD side and a clean boot and BAM, full on thunderbolty latency free hidef audio awesomeness on 32 physical channels!

Thanks again @CaseySJ for your technical prowess, and thorough instruction methods, you are an absolute sage. I owe you like so many beers....

Awesome -- really glad to hear it!!

If you tested the same device before flashing the Thunderbolt firmware, can you say which features did not work before (or did not work properly before), but are working only after flashing the modified firmware?

 

[CaseySJ]

@CaseySJ thanks for your immediate response and thanks for making my professional life 1000x less of a hustle with the workflow and efficiency boost I gained through your guide.

The Apps where tested solely via WIFI Connection. Is there any problem/ solution you could think of regarding that ?
Im using the "fenvi fv-t919" WIFI Card as suggested in your build.

Best regards
Jack

Were those apps (Radio Silence, IPVanish) working before? When did the problem begin -- after any software or OS update on the Hackintosh?

 

[mdog474]

You must be using USBInjectAll 0.7.5 instead of 0.7.3. Please type this in Terminal:

kextstat | grep -v apple

Hi @CaseySJ GetInfo on USBInjectAll.kext says Version: 0.7.1 => here is the kextstat output:

Index Refs Address            Size       Wired      Name (Version) UUID <Linked Against>
   16    0 0xffffff7f80d1a000 0x12000    0x12000    org.netkas.driver.FakeSMC (1800) FC7031CC-C949-35D1-AC1A-CA8DB349793E <12 8 6 5 3 1>
   17    2 0xffffff7f80ec5000 0x22000    0x22000    as.vit9696.Lilu (1.2.8) 54014689-C8DA-318B-84F4-944BBA7AD2AC <8 6 5 3 2 1>
   18    0 0xffffff7f80ee7000 0x60000    0x60000    as.vit9696.WhateverGreen (1.2.4) 25D369F5-0FD8-3264-9060-3FDB014904BC <17 13 8 6 5 3 2 1>
   19    0 0xffffff7f80fa3000 0x110000   0x110000   as.vit9696.AppleALC (1.3.8) 27CB586F-8863-3720-8EB4-A76EDF07E6D3 <17 13 8 6 5 3 2 1>
   61    0 0xffffff7f80f80000 0x23000    0x23000    com.insanelymac.IntelMausiEthernet (2.4.0) F99BECF1-A2CE-3C72-A66F-FCFBD5395306 <20 13 6 5 3 1>
   68    0 0xffffff7f80d30000 0x8000     0x8000     org.rehabman.driver.FakePCIID (1.3.15) B185B092-1FC9-308E-B093-32FD88E5822D <13 8 6 5 3 1>
  106    0 0xffffff7f8119e000 0x22000    0x22000    com.smalltree.driver.SmallTreeIntel82576 (1.2.5) 0E5F5CDA-75BD-3359-8426-E494578D6491 <20 13 6 5 3 1>
  118    0 0xffffff7f83db0000 0x95000    0x95000    com.uaudio.driver.UAD2System (9.11.0) no UUID <117 89 13 6 5 3 1>
  125    0 0xffffff7f82ec2000 0x3b000    0x3b000    com.uaudio.driver.UAFWAudio (4.3.1 47542) 7768A827-9D44-3C93-9B59-9224F4F8C9CE <117 89 6 5 3 1>

Update: I tried updating the USBInjectAll.kext in EFI/Clover/kext/Other to V0.7.3 and the Bluetooth is still not showing up.

 

[smashdownbabylon]

Awesome -- really glad to hear it!!

If you tested the same device before flashing the Thunderbolt firmware, can you say which features did not work before (or did not work properly before), but are working only after flashing the modified firmware?

Yes, system audio was spotty, and only worked at low sample rates. Daisy chaining was also spotty and while hot plug seemed to work in terms of connecting the interface to the comp, audio wouldn’t work properly. On the fly sample rate changing worked but resulted in massive audio distortion. The only sample rate that did work was 44.1khz, I think because thats sort of the default rate that most things would use anyway. Occasionally channel mapping was screwy and generally unusable. The IO tree before the update had the UAD driver on a completely different section than the TB controller, and the TB controller was not recognized in System Info. It was like the computer could see the device and the driver knew what to do, but they weren’t speaking the same language in terms of syntax, ie bussing.

With the firmware update, all of these aforementioned issues seem to have been solved. Of note, turning on the device on the end of the chain, waiting for it to initialize, and so on down to booting the computer seems to be the way to go, although hot plugging does also seem to be functional once everything has been booted properly once (see note at bottom). The UAD hardware reset was necessary, having the TB cables unplugged while doing it. I did not have to do the whole “unplug all power, disconnect all cables, let it sit for ten minutes” thing described elsewhere, which frankly i think is a load of hooey,lol. Just make sure the TB cables are unplugged when resetting and turn the devices on from last to first, and then the comp PSU (because the TB controller is powered without the comp being booted). I can’t think of anything else, but if anyone has any questions with regard to getting a UAD device working I’d be happy to help!

Note: HotPlugging seems to advance the ch count in Console by 2 every time, ie 1-2 becomes 3-4 and so on with each hotplug reinstatement of the audio session.

 

[hitch21]

@CaseySJ My mother board is gigabyte z390m gaming.
Where would I found instruction to unlock MSR 0xE2? Or would it be same as yours?

UPDATE: I found the below guide so will give it a try.

Gigabyte Z390 M Gaming build with working NVRAM

Gigabyte Z390 M Gaming Build Components Gigabyte Z390 M Gaming Motherboard > Amazon, Newegg Intel i9-9900K Processor > Amazon, Newegg Noctua NH-D15S CPU Cooler > Amazon, Newegg Oloy DDR4 3200MHz 4x16GB RAM > Amazon, Newegg PowerColor Radeon VII > Amacon, Newegg BCM94360CS2 on PCI-e Adaptor >...

www.tonymacx86.com

UPDATE2: I have unlocked MSR as per your and the above instructions but still same issue

Hi @CaseySJ, I tried resetting and upgrading BIOS to latest and setting it as per your guide r other working guides that use same motherboard. I tried disconnecting external devices to see if this helps. I tried Plan C with 16GB USB 2 and with 128GB USB 3, and no luck with either.
I'm out of ideas. Would you be able to recommend next things to try?

 

[CaseySJ]

Hi @CaseySJ GetInfo on USBInjectAll.kext says Version: 0.7.1 => here is the kextstat output:

Index Refs Address            Size       Wired      Name (Version) UUID <Linked Against>
   16    0 0xffffff7f80d1a000 0x12000    0x12000    org.netkas.driver.FakeSMC (1800) FC7031CC-C949-35D1-AC1A-CA8DB349793E <12 8 6 5 3 1>
   17    2 0xffffff7f80ec5000 0x22000    0x22000    as.vit9696.Lilu (1.2.8) 54014689-C8DA-318B-84F4-944BBA7AD2AC <8 6 5 3 2 1>
   18    0 0xffffff7f80ee7000 0x60000    0x60000    as.vit9696.WhateverGreen (1.2.4) 25D369F5-0FD8-3264-9060-3FDB014904BC <17 13 8 6 5 3 2 1>
   19    0 0xffffff7f80fa3000 0x110000   0x110000   as.vit9696.AppleALC (1.3.8) 27CB586F-8863-3720-8EB4-A76EDF07E6D3 <17 13 8 6 5 3 2 1>
   61    0 0xffffff7f80f80000 0x23000    0x23000    com.insanelymac.IntelMausiEthernet (2.4.0) F99BECF1-A2CE-3C72-A66F-FCFBD5395306 <20 13 6 5 3 1>
   68    0 0xffffff7f80d30000 0x8000     0x8000     org.rehabman.driver.FakePCIID (1.3.15) B185B092-1FC9-308E-B093-32FD88E5822D <13 8 6 5 3 1>
  106    0 0xffffff7f8119e000 0x22000    0x22000    com.smalltree.driver.SmallTreeIntel82576 (1.2.5) 0E5F5CDA-75BD-3359-8426-E494578D6491 <20 13 6 5 3 1>
  118    0 0xffffff7f83db0000 0x95000    0x95000    com.uaudio.driver.UAD2System (9.11.0) no UUID <117 89 13 6 5 3 1>
  125    0 0xffffff7f82ec2000 0x3b000    0x3b000    com.uaudio.driver.UAFWAudio (4.3.1 47542) 7768A827-9D44-3C93-9B59-9224F4F8C9CE <117 89 6 5 3 1>

Update: I tried updating the USBInjectAll.kext in EFI/Clover/kext/Other to V0.7.3 and the Bluetooth is still not showing up.

In this case, please post the SSDT-UIAC-DESIGNARE... file from the CLOVER/ACPI/patched folder. I wonder if it's the wrong one.

 

[CaseySJ]

Yes, system audio was spotty, and only worked at low sample rates. Daisy chaining was also spotty and while hot plug seemed to work in terms of connecting the interface to the comp, audio wouldn’t work properly. On the fly sample rate changing worked but resulted in massive audio distortion. The only sample rate that did work was 44.1khz, I think because thats sort of the default rate that most things would use anyway. Occasionally channel mapping was screwy and generally unusable. The IO tree before the update had the UAD driver on a completely different section than the TB controller, and the TB controller was not recognized in System Info. It was like the computer could see the device and the driver knew what to do, but they weren’t speaking the same language in terms of syntax, ie bussing.

With the firmware update, all of these aforementioned issues seem to have been solved. Of note, turning on the device on the end of the chain, waiting for it to initialize, and so on down to booting the computer seems to be the way to go, although hot plugging does also seem to be functional once everything has been booted properly once (see note at bottom). The UAD hardware reset was necessary, having the TB cables unplugged while doing it. I did not have to do the whole “unplug all power, disconnect all cables, let it sit for ten minutes” thing described elsewhere, which frankly i think is a load of hooey,lol. Just make sure the TB cables are unplugged when resetting and turn the devices on from last to first, and then the comp PSU (because the TB controller is powered without the comp being booted). I can’t think of anything else, but if anyone has any questions with regard to getting a UAD device working I’d be happy to help!

Note: HotPlugging seems to advance the ch count in Console by 2 every time, ie 1-2 becomes 3-4 and so on with each hotplug reinstatement of the audio session.

Thank you -- this is very helpful. I've added it to the ongoing list here:

[SUCCESS] Gigabyte Designare Z390 (Thunderbolt 3) + i7-9700K + AMD RX 580

Thanks for your reply. I’ve tried pretty much everything up to now. over the weekend I swapped out the power supply for a new one, some issues. things I’ve tried but still get freezing: unplugging all USB devices except for mouse (and used a different mouse/keyboard) changed power supply for...

www.tonymacx86.com

 

[mdog474]

In this case, please post the SSDT-UIAC-DESIGNARE... file from the CLOVER/ACPI/patched folder. I wonder if it's the wrong one.

Hi @CaseySJ it is version V7 (I uploaded a copy)--I didn't change any of these files when I updated the BIOS. The system had been working for months on the older BIOS. Very strange.