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

[Snoots]

I wonder if this is related to the 10 Gbps Ethernet port. Because Clover is still working, please do this:

• Compare Clover and OpenCore settings:
  • Kernel patches
  • ACPI (SSDT) files
  • Kexts
  • UEFI drivers
• Or compress and upload both the CLOVER and OC folders, but remove serial numbers from both.

Hope to check on this later today thanks for helping out

 

[Bobby22]

According to the Razer website, the mouse supports 3 modes of connection:

• Razer™ HyperSpeed Wireless
• Wired - Speedflex Cable
• Bluetooth

Bluetooth connection may not work in BIOS, but these two might. If the SpeedFlex Cable is USB, then it should most likely work.

• Razer™ HyperSpeed Wireless
• Wired - Speedflex Cable

Thank you as always to answer.

But my question was more pointed out ; how can we know if the Bluetooth Mouse/Keyboard will work into the CloverBoot loader ?
Does it need Kext or other things to work ?
Thats my main concern because I've got A Logitech Bluetooth Keyboard that does not work during CloverBootloader so I can't swap Windows/Mac OS with it (only with keyboard).

Thank you

 

[CaseySJ]

Thank you as always to answer.

But my question was more pointed out ; how can we know if the Bluetooth Mouse/Keyboard will work into the CloverBoot loader ?
Does it need Kext or other things to work ?
Thats my main concern because I've got A Logitech Bluetooth Keyboard that does not work during CloverBootloader so I can't swap Windows/Mac OS with it (only with keyboard).

Thank you

In most cases we don't know the answer until we try. In general terms, however, what I mentioned previously still holds: USB keyboards and mice tend to work in BIOS and Clover. This includes Logitech wireless keyboards and mice that use the Logitech USB wireless receiver (hence these are also USB devices even through they are wireless).

 

[dithaack]

I just realized that my TB3 seems capped. I tested a RAID on it and get about 900MB/s vs using a real Macbook Pro at 1600MB/s.
(The Titan Ridge was flashed to NVM50 and configured DROM; all cables are plugged into the card).

Hopefully I didn't miss it, but I haven't found this topic by searching. This is a huge thread but has been hugelyy helpful. Thanks so much @CaseySJ

Anyone experienced this?

 

[joevt]

I just realized that my TB3 seems capped. I tested a RAID on it and get about 900MB/s vs using a real Macbook Pro at 1600MB/s.
(The Titan Ridge was flashed to NVM50 and configured DROM; all cables are plugged into the card).

Hopefully I didn't miss it, but I haven't found this topic by searching. This is a huge thread but has been hugelyy helpful. Thanks so much @CaseySJ

Anyone experienced this?

What kind of RAID (is it RAID 0)? What kind of drives are in the RAID? What is the Thunderbolt device containing the drives?

What model of MacBook Pro? 1600 MB/s is Thunderbolt 2 speed.

Did you check the PCIe link rate and link width of the PCIe controllers used for the drives (try pcitree.sh)?

 

[dithaack]

What kind of RAID (is it RAID 0)? What kind of drives are in the RAID? What is the Thunderbolt device containing the drives?

What model of MacBook Pro? 1600 MB/s is Thunderbolt 2 speed.

Did you check the PCIe link rate and link width of the PCIe controllers used for the drives (try pcitree.sh)?

Yes RAID-0 and a 4-bay M.2 enclosure (https://eshop.macsales.com/item/OWC/TB3EX4M2SL/), They're Samsung SSD 970 EVO's (only250GB each, 4 sticks).

Macbook Pro is 2019 running Catalina (2.3 GHz 8-core Intel Core i9). Actually I just tested with the laptop again and depending on which speed test I use (Blackmagic or AJA), I get between 1800-2100 MB/s--about twice what I'm getting on the hackintosh.

IO REG has my hackintosh Link speed at: 2.5 GT/s ; Link width: x4

Thanks!!

 

[Lukey1979]

Glad to hear it!

SSDT-SBUS-MCHC is not strictly necessary on either platform. Doesn't hurt to try it, though.

Yes, this disables wake-from-USB (hence it disables wake from Bluetooth as well because Bluetooth is connected via USB). Only power button will wake the system. This is not necessary unless the system is experiencing chronic insomnia.

Ha! The sanity checker is wrong. But more specifically, the sanity checker is a generic checker that does not necessarily produce the right results for a specific motherboard. It's a very nice tool, but the output should not be taken as gospel.

Same as last comment -- these warnings from the sanity checker should not be taken as gospel. The settings in OpenCore 0.6.0 Mini-Guide are correct. There is always wiggle room for individuals to individualize their settings, but the standard settings in that guide are fine.

Hi Casey,

Thank you for all your help
Any ideas as to why that SSDT-RX 5700 XT-version 1.0.aml didn’t work (caused the blue screen) even after modifying it for me? I would have thought that if a SSDT is not being injected it should have no impact on the windows boot.

 

[joevt]

Yes RAID-0 and a 4-bay M.2 enclosure (https://eshop.macsales.com/item/OWC/TB3EX4M2SL/), They're Samsung SSD 970 EVO's (only250GB each, 4 sticks).

Macbook Pro is 2019 running Catalina (2.3 GHz 8-core Intel Core i9). Actually I just tested with the laptop again and depending on which speed test I use (Blackmagic or AJA), I get between 1800-2100 MB/s--about twice what I'm getting on the hackintosh.

IO REG has my hackintosh Link speed at: 2.5 GT/s ; Link width: x4

What is IO REG? Do you mean IORegistryExplorer.app or ioreg or System Information.app? They are not sufficient for getting current link rate and link speed for PCIe devices. Plus, you need the link rate and link width of all the parent devices as well to get the full picture.

I don't know what device you are getting that 2.5 GT/s from - probably an embedded Thunderbolt device of the Thunderbolt controller which is always reported at 2.5 GT/s even though the embedded Thunderbolt devices (NHI, XHC, downstream bridges) are faster than that - in this case you want the link rate and link width of the upstream Thunderbolt bridge of the Thunderbolt controller which is not shown in System Information.app.

I believe the OWC Express 4M2 uses PCIe 3.0 x1 for each NVMe device.

 

[jiffyslot]

Dante is not AVB. Dante is great, works fine on Hacks. It only needs a working ethernet port and standard switches, unlike AVB. There's a slight(1-2 mS) overhead compared to the fastest of TB/PCIe interfaces.

But Dante is overkill in my situation, as a bedroom composer with a provisional voice-over booth(I sold my studio a long time ago)

UAD stuff is great for small/personal setups. UAD is also quite reliable. But i chose Metric Halo 15 years ago, and I am basically still happy with my ULN-2 and ULN-8, and Metric Halo as a company.

For bigger systems, Dante rules. No need for miles of expensive analog cables(that will generate noise nevertheless) Very flexible. Reliable. Clean.

So you are always listening through your Mackie mixer? Hm. I would connect my monitors straight to the Apollo.

Maybe I should do a null-test between two setups.

Yeah, I know people laugh about my 20-year old US-made analog Mackie 1202 VLZ Pro from ~2000. It is a fine little bus mixer monitor (plus headphones) that handles various outs from the patchbay. I don't want any latency from the Fractal unit. It's got a lot of headroom. I've never attached a DAW interface to monitors or headphones without the option of putting a hardware limiter between the DAW interface mains and the headphone or monitor bus. My stuff is clean, probably because I invested in great power management gear and balanced cables for my fridge. I don't monitor or track much above 78-88 dB. I don't trust any digital gear –no matter the marketing not to eventually emit a white noise blast at 0dBFS. I hope to one day shrink the footprint down to an API lunchbox.

 

[zipb]

Maybe I should do a null-test between two setups.

Yeah, I know people laugh about my 20-year old US-made analog Mackie 1202 VLZ Pro from ~2000. It is a fine little bus mixer monitor (plus headphones) that handles various outs from the patchbay. I don't want any latency from the Fractal unit. It's got a lot of headroom. I've never attached a DAW interface to monitors or headphones without the option of putting a hardware limiter between the DAW interface mains and the headphone or monitor bus. My stuff is clean, probably because I invested in great power management gear and balanced cables for my fridge. I don't monitor or track much above 78-88 dB. I don't trust any digital gear –no matter the marketing not to eventually emit a white noise blast at 0dBFS. I hope to one day shrink the footprint down to an API lunchbox.

I've been going straight from interface to speakers for 20 years now. No problems, better sound.

Soundwise your Mackie is probably the weakest link in your chain. I would definitely test with and without the Mackie, and see if you can hear a difference. Also depends on your monitors of course, if you have something like $200 KRK's then don't bother.
IMO, the whole audio chain should be balanced quality wise, eg getting a Benchmark DAC to drive your Apple earbuds is not a smart idea.