Contribute
Register

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

Thanks for the quick reply!

This setup was working in the confidence / older version of bios & F9 with Clover and Catalina.

The chain is Akitio Thunderbolt 3 Quad mini bay raid, then a Call digit TS3+ TB3 Dock with maybe 10 USB3 HDD's + 2x TB3 -TB2 devices

I haven't tested the Akitio will work for any real length of time by itself yet as I havent linked my AppleID and therefore FCPX with the new SMBIOS just yet. Either way as soon as the other devices are connected the whole thing freezes
I have the Akitio Thunderbolt Quad X (the full-size version). It's been working fine on Big Sur and Monterey. You may need to go to their website and check to see if there is newer firmware for your device. Also, a firmware update came out for the TS3 not that long ago last year. Check the Caldigit site against your device to make sure you have the latest firmware as well. I have used both of these devices with no problem, daisy-chaining a Thunderbolt drive to the Akitio since sometime in 2020, as well as filling up the TS3+ with all sorts of devices and it works great since about August 2021.

Also, try a process of elimination if you haven't already. Try only the Quad Mini to see if that works. Then, with nothing else attached to it, plug in the TS3+. Also, try the TS3 on a Thunderbolt port with the Quad Mini not plugged in and with nothing else attached to the TS3+. That should confirm if it's the dock or the Quad Mini. If they both work then chances are one of the extra devices may be the issue, though I would certainly make sure firmware is up to date on everything in order to work with Big Sur/Monterey.
 
Which version of macOS are you running now? Have you tried enabling or disabling AppleVTD as described in the OpenCore 0.7.5 and 0.7.6 mini-guides in this thread?
Hi CaseySJ

For some reason I might have been doing something wrong. I did exactly whats in the tutorial, but I still can’t get WiFi/Bluetooth. I got AVB working using Tb3 - Tb2 - Ethernet, but no WiFi/Bluetooth.

I am using Fenvi T919.
 
Hi everyone and especially to all of those who make all this possible and help the community. I need help getting my Wifi/Bluetooth working after doing the procedure.
 
Hello @echosat1,

Happy new year to you as well!

Some (obvious) things to try first:
  • Cold start. This means shutting down the system and flipping power switch on PSU to OFF for 10 seconds, then powering up.
  • If problem persists, try Reset NVRAM by pressing space bar at the OpenCore boot picker.
  • If problem still persists, try disabling BrcmPatchRAM3.kext.
Hello again,

I tried Resetting NVRAM, cold start + NVRAM reset, removing BrcmPatchRAM3 kext (+ cold start, NVRAM reset). None of these worked and bluetoothd still works at 220% after waking from a sleep, this stops the moment I disable bluetooth or it never happens if bluetooth + wifi is disabled all together. After I disable and enable the bluetooth, it goes away but the problem happens whenever computer sleeps and wakes.

I'm using BCM94360CS2 card with a PCI adapter. You can see from the screenshot of iStatMenus that there are peaks with bluetooth enabled boot and wake from sleep, and then sudden drop whenever bluetooth is disabled. The highest peak happened with the boot when BrcmPatchRAM3 kext was removed.
 

Attachments

  • istat.png
    istat.png
    133.4 KB · Views: 42
  • istat2.png
    istat2.png
    110.1 KB · Views: 40
@CaseySJ
in OC 0.7.7 there's no more MinimumVolume (Integer) in UEFI->Audio.
Instead there's DisconnectHDA (Boolean).
Both MinimumVolume and DisconnectHDA are present in OCC 2.55.0.0.
 
@CaseySJ
in OC 0.7.7 there's no more MinimumVolume (Integer) in UEFI->Audio.
Instead there's DisconnectHDA (Boolean).
Both MinimumVolume and DisconnectHDA are present in OCC 2.55.0.0.
Yes, those have been replaced with 3 decibel parameters instead. The next release of OpenCore Configurator will fix this part of the schema.

<key>MaximumGain</key>
<integer>-15</integer>
<key>MinimumAssistGain</key>
<integer>-30</integer>
<key>MinimumAudibleGain</key>
<integer>-55</integer>
 
Last edited:
Yes, those have been replaced with 3 decibel parameters instead. The next release of OpenCore Configurator will fix this part of the schema.

<key>MaximumGain</key>
<integer>-15</integer>
<key>MinimumAssistGain</key>
<integer>-30</integer>
<key>MinimumAudibleGain</key>
<integer>-55</integer>
Are those setting the default or your recommendation?
 
Are those setting the default or your recommendation?
Those are default settings. On the new Asus Z690 ProArt Creator, they produce a boot chime that's just about right in volume...
 
@CaseySJ
in OC 0.7.7 there's no more MinimumVolume (Integer) in UEFI->Audio.
Instead there's DisconnectHDA (Boolean).
Both MinimumVolume and DisconnectHDA are present in OCC 2.55.0.0.
Thanks for this. I've never understood the allure of boot-chimes and other app & system beeps and boops.
 

Attachments

  • Screen Shot 2022-01-11 at 11.01.49 AM.png
    Screen Shot 2022-01-11 at 11.01.49 AM.png
    59.7 KB · Views: 59
I’ll take a look soon. Some immediate comments:
  • VT-d should be enabled in BIOS if t you’re dropping the original DMAR table and replacing it with a modified version.
  • BlueToolFixup.kext is necessary in Monterey for any kind of Bluetooth operation (both Broadcom and Intel).
Update:
  • Please try attached EFI folder, but copy serial numbers into PlatformInfo --> DataHub before use.
Hi Casey,

Does this mean FV-T919 also require BlueToolFixup.kext in Monterey for Bluetooth operation? It seemed mine was working without that kext but if for any reason it's needed I might as well install it.
 
Back
Top