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

[Ayvan]

​

Big Navi:

• Hardware ray tracing (DirectX Ray Tracing)​

​

It has hardware ray tracing, look at AMD website:

One Ray Accelerator per CU for any Big Navi GPU.

 

[CaseySJ]

It has hardware ray tracing, look at AMD website:
View attachment 493543
One Ray Accelerator per CU for any Big Navi GPU.

There was some confusion about this right after the event, hence the strikeout. But yes it does have hardware ray tracing. Post updated.

 

[Verit9s]

Is anyone having issues with their MSI Radeon Vega 56 fans not spinning?

I've always had this issue since I installed Mojave installation with Clover. I eventually updated to 10.15.1 and recently switched to OpenCore 6.2 (following the mini-guide) with 10.15.17 and there's still no fan spin.

Can someone point me in the right direction?

 

[CaseySJ]

Is anyone having issues with their MSI Radeon Vega 56 fans not spinning?

I've always had this issue since I installed Mojave installation with Clover. I eventually updated to 10.15.1 and recently switched to OpenCore 6.2 (following the mini-guide) with 10.15.17 and there's still no fan spin.

Can someone point me in the right direction?

AMD GPUs have fan stop capability. The fans will start spinning once the GPU temperature reaches 55 to 60 C.

 

[joevt]

Hello everybody,

My question is geared toward Thunderbolt link speed, mainly using Thunderbolt audio interfaces. But anybody having Thunderbolt more in-depth knowledge could chime in... No answer yet from Presonus (ticket created) nor Gearslutz users.

From what I know, there are few of them from:

- RME;
- Zoom;
- Focusrite (Clarett, now discontinued);
- Slate;
- Apogee;
- UAD;
- Lynx;
- Presonus (my case, a Quantum 2626 but they made other Quantum AI's back);
- Resident Audio.

So, I use:

- Gigabyte Z390 Designare BIOS F9g with unflashed TB firmware;
- Mojave 10.14.6 and Windows 10 2004;
- Presonus Quantum 2626 Thunderbolt 3;
- Startech TB3 certified 40 gbps active 2m cable ( https://www.startech.com/en-us/cables/tblt3mm2ma );


Well, I was looking for device enumeration and link speed under MacOS and Windows and this is what I've got and just want to be sure that it is indeed correct.

Windows 10 HWInfo64:

View attachment 493255


Just to compare, main TB bus:

View attachment 493256

On Mojave:

View attachment 493258
View attachment 493264
LSPCI output:

06:00.0 Class 0604: Device 8086:15ea (rev 06)
    Bus: primary=06, secondary=07, subordinate=f5, sec-latency=0
    Capabilities: [c0] Express (v2) Upstream Port, MSI 00
        LnkCap:    Port #0, Speed 8GT/s, Width x4, ASPM L1, Latency L0 <64ns, L1 <2us
        LnkSta:    Speed 8GT/s, Width x4, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-
        LnkCtl2: Target Link Speed: 8GT/s, EnterCompliance- SpeedDis-, Selectable De-emphasis: -6dB

07:00.0 Class 0604: Device 8086:15ea (rev 06)
    Bus: primary=07, secondary=09, subordinate=09, sec-latency=0
    Capabilities: [c0] Express (v2) Downstream Port (Slot+), MSI 00
        LnkCap:    Port #0, Speed 2.5GT/s, Width x4, ASPM L1, Latency L0 <64ns, L1 <1us
        LnkSta:    Speed 2.5GT/s, Width x4, TrErr- Train- SlotClk+ DLActive- BWMgmt+ ABWMgmt-
        LnkCtl2: Target Link Speed: 2.5GT/s, EnterCompliance- SpeedDis-, Selectable De-emphasis: -6dB

07:01.0 Class 0604: Device 8086:15ea (rev 06)
    Bus: primary=07, secondary=7f, subordinate=82, sec-latency=0
    Capabilities: [c0] Express (v2) Downstream Port (Slot+), MSI 00
        LnkCap:    Port #1, Speed 2.5GT/s, Width x4, ASPM L1, Latency L0 <64ns, L1 <1us
        LnkSta:    Speed 2.5GT/s, Width x4, TrErr- Train- SlotClk+ DLActive+ BWMgmt- ABWMgmt-
        LnkCtl2: Target Link Speed: 2.5GT/s, EnterCompliance- SpeedDis-, Selectable De-emphasis: -6dB

07:02.0 Class 0604: Device 8086:15ea (rev 06)
    Bus: primary=07, secondary=08, subordinate=08, sec-latency=0
    Capabilities: [c0] Express (v2) Downstream Port (Slot+), MSI 00
        LnkCap:    Port #2, Speed 2.5GT/s, Width x4, ASPM L1, Latency L0 <64ns, L1 <1us
        LnkSta:    Speed 2.5GT/s, Width x4, TrErr- Train- SlotClk+ DLActive- BWMgmt+ ABWMgmt-
        LnkCtl2: Target Link Speed: 2.5GT/s, EnterCompliance- SpeedDis-, Selectable De-emphasis: -6dB

07:04.0 Class 0604: Device 8086:15ea (rev 06)
    Bus: primary=07, secondary=0a, subordinate=0a, sec-latency=0
    Capabilities: [c0] Express (v2) Downstream Port (Slot+), MSI 00
        LnkCap:    Port #4, Speed 2.5GT/s, Width x4, ASPM L1, Latency L0 <64ns, L1 <1us
        LnkSta:    Speed 2.5GT/s, Width x4, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-
        LnkCtl2: Target Link Speed: 2.5GT/s, EnterCompliance- SpeedDis-, Selectable De-emphasis: -6dB

08:00.0 Class 0c03: Device 8086:15ec (rev 06) (prog-if 30)
    Capabilities: [c0] Express (v2) Endpoint, MSI 00
        LnkCap:    Port #0, Speed 2.5GT/s, Width x4, ASPM L1, Latency L0 <64ns, L1 <1us
        LnkSta:    Speed 2.5GT/s, Width x4, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-
        LnkCtl2: Target Link Speed: 2.5GT/s, EnterCompliance- SpeedDis-, Selectable De-emphasis: -6dB

09:00.0 Class 0880: Device 8086:15eb (rev 06)
    Capabilities: [c0] Express (v2) Endpoint, MSI 00
        LnkCap:    Port #0, Speed 2.5GT/s, Width x4, ASPM L1, Latency L0 <64ns, L1 <1us
        LnkSta:    Speed 2.5GT/s, Width x4, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-
        LnkCtl2: Target Link Speed: 2.5GT/s, EnterCompliance- SpeedDis-, Selectable De-emphasis: -6dB

7f:00.0 Class 0604: Device 8086:15c0 (rev 01)
    Bus: primary=7f, secondary=80, subordinate=82, sec-latency=0
    Capabilities: [c0] Express (v2) Upstream Port, MSI 00
        LnkCap:    Port #0, Speed 2.5GT/s, Width x4, ASPM L0s L1, Latency L0 <2us, L1 <4us
        LnkSta:    Speed 2.5GT/s, Width x4, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-
        LnkCtl2: Target Link Speed: 2.5GT/s, EnterCompliance- SpeedDis-, Selectable De-emphasis: -6dB

80:00.0 Class 0604: Device 8086:15c0 (rev 01)
    Bus: primary=80, secondary=82, subordinate=82, sec-latency=0
    Capabilities: [c0] Express (v2) Downstream Port (Slot+), MSI 00
        LnkCap:    Port #0, Speed 8GT/s, Width x1, ASPM L0s L1, Latency L0 <2us, L1 <4us
        LnkSta:    Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+ DLActive+ BWMgmt- ABWMgmt-
        LnkCtl2: Target Link Speed: 8GT/s, EnterCompliance- SpeedDis-, Selectable De-emphasis: -3.5dB

80:01.0 Class 0604: Device 8086:15c0 (rev 01)
    Bus: primary=80, secondary=81, subordinate=81, sec-latency=0
    Capabilities: [c0] Express (v2) Downstream Port (Slot+), MSI 00
        LnkCap:    Port #1, Speed 8GT/s, Width x1, ASPM L0s L1, Latency L0 <2us, L1 <4us
        LnkSta:    Speed 2.5GT/s, Width x4, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-
        LnkCtl2: Target Link Speed: 8GT/s, EnterCompliance- SpeedDis-, Selectable De-emphasis: -3.5dB

82:00.0 Class 0401: Device 1c67:0104
    Capabilities: [60] Express (v2) Endpoint, MSI 00
        LnkCap:    Port #0, Speed 2.5GT/s, Width x1, ASPM L0s, Latency L0 unlimited, L1 unlimited
        LnkSta:    Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-
        LnkCtl2: Target Link Speed: 2.5GT/s, EnterCompliance- SpeedDis-, Selectable De-emphasis: -6dB

I uderstand that for almost a decade, USB2 with 480 mbits/s bandwidth was sufficient for audio and Thunderbolt use is mainly to reduce the in/out latency (on par with PCIe) but I would guess audio bandwidth was also a part of the effort?

If I understand the above numbers, the in-built Alpine Ridge bridge in the Quantum negotiate at PCIe 1.1 specs, 1x 2.5 GT/s, correct? Is this normal?

Thanks,

Patrice

Thunderbolt NHI and USB and their bridges always report 2.5 GT/s x4 even though they are faster than that (these devices are internal to the Thunderbolt controller so they don't really use PCIe bus).
You should only worry about the upstream Thunderbolt bridge (8 GT/s x4 is normal/max) and your device (the Presonus is set to 2.5 GT/s x1 which is the minimum ~200 MB/s for PCIe but still much faster than USB 2.0 (~50 MB/s) or FireWire 800 (~80 MB/s).

 

[Verit9s]

AMD GPUs have fan stop capability. The fans will start spinning once the GPU temperature reaches 55 to 60 C.

Thanks for the quick reply CaseySJ.

My GPU Temp's are running around 59 C and increasing but no fans are spinning. Is this normal behavior?

 

[AlexComputerWiz]

Okay, I admit it. I screwed up. I installed Linux Mint on another NVMe which I added to the Designare board yesterday. After the install, Clover is gone and I can't select to boot to it in the BIOS. Tried these methods but haven't been able to get Clover working. I installed EasyUEFI in Windows to see everything and try to make some sense of it, but I'm more confused now (see screenshot). The "ubuntu" and "UEFI OS" both highlight the same EFI on the MacOS - OS drive, which is alarming, but the "Clover Boot Manager" is showing as hidden and on the Win10 drive? WTF? During the Linux install, it asked where to install the bootloader, which I selected the same drive as I was installing the OS on. I clearly see that didn't happen.

Question to @CaseySJ. I can't find my Clover USB, I can't make Clover unhidden. Should I just use this opportunity to upgrade my SSDs which I have been meaning to do and just start fresh? Or is there someway to fix this? I also tried booting to my Mojave Clover Install USB to attempt the Clover cmd trick, didn't even see it. I am trying to make a Catalina one too. All my important files are in iCloud so I don't really care, but trying to find the fastest way to get back into MacOS.

EDIT: Running 10.15.4

 

[Verit9s]

AMD GPUs have fan stop capability. The fans will start spinning once the GPU temperature reaches 55 to 60 C.

Currently the temperature is 70 C and rising. No fans are going off. The only time I hear the fans go off are doing POST and/or boot. I'm guessing there is some other issue?

 

[CaseySJ]

Okay, I admit it. I screwed up. I installed Linux Mint on another NVMe which I added to the Designare board yesterday. After the install, Clover is gone and I can't select to boot to it in the BIOS. Tried these methods but haven't been able to get Clover working. I installed EasyUEFI in Windows to see everything and try to make some sense of it, but I'm more confused now (see screenshot). The "ubuntu" and "UEFI OS" both highlight the same EFI on the MacOS - OS drive, which is alarming, but the "Clover Boot Manager" is showing as hidden and on the Win10 drive? WTF? During the Linux install, it asked where to install the bootloader, which I selected the same drive as I was installing the OS on. I clearly see that didn't happen.

Question to @CaseySJ. I can't find my Clover USB, I can't make Clover unhidden. Should I just use this opportunity to upgrade my SSDs which I have been meaning to do and just start fresh? Or is there someway to fix this? I also tried booting to my Mojave Clover Install USB to attempt the Clover cmd trick, didn't even see it. I am trying to make a Catalina one too. All my important files are in iCloud so I don't really care, but trying to find the fastest way to get back into MacOS.

EDIT: Running 10.15.4

This usually happens with Linux and even with Windows. It seems Linux has written its EFI bootloader into the EFI partition of your macOS SSD.

Fortunately, this problem is solvable, but you will need to find a way to mount the EFI partition of the macOS SSD. There are ways to do this in Windows and Linux, but you may have to Google for the answer.

An alternative approach is to connect your Bootable Backup Disk and press F12 at BIOS Splash Screen and boot from that disk. Then mount EFI partition from macOS.

Once the EFI partition is mounted (using either Windows, Linux, or macOS), please expand the EFI folder and post a screenshot or a photo. Based on that we can help you move files around to fix the problem.

Does the Linux SSD contain its own EFI partition?

 

[CaseySJ]

Currently the temperature is 70 C and rising. No fans are going off. The only time I hear the fans go off are doing POST and/or boot. I'm guessing there is some other issue?

At 70 C the fans should be spinning. Have you created a custom fan/power curve for your Vega? There is a complete guide here:

[GUIDE] Injection of AMD Vega Power and Fan Control Properties

Injection of Device Properties for Power and Fan control Last updated 14th May 2019 Update: MacOS Mojave 10.14.5+ includes a major overhaul of the Vega GPU drivers which should resolve all the power and fan control issues with most Vega cards and thus should make the methods outlined in this...

www.tonymacx86.com