Gigabyte Z490 Vision D (Thunderbolt 3) + i5-10400 + AMD RX 580

[inapis.crazy]

If I remove the WD SSD, I can install the EVO+ drive in any M2 slots on the MB, no issue. But I have only 2 EVO+ SSDs. If I had a third one I am not sure if that would cause the pb.
I think the pb is the combination of EVO+ and WD. Even if I have only 1 EVO+ installed, as soon as I add the WD (regardless of the solt), I can't post or boot.

Regarding the card, thisnis what I bought:

Orico M.2 NVME to PCI-E 3.0 X4 Expansion Card | Motherboard Accessories | ORICO-PDM2

Upgrade your PC with the Orico M.2 NVME to PCI-E 3.0 X4 Expansion Card, compatible with 2230/2242/2260/2280 SSDs. This reliable motherboard accessory supports NVME/SATA protocol M.2 SSDs, providing fast 32Gbps (NVME) and 6Gbps (SATA) transmission speeds. Compatible with IOS, Windows 7/8/10, and...

www.centrecom.com.au

I initially thought that it was 2 x M2 NVMe M key but in fact it is only 1 X NVMe M2 M key and one B key.

The WD is installed on that card and I have left the slot #3 empty so that the full bandwidth is allocated to the WD.

This feels like faulty hardware. Have you tested the combination in another motherboard? If the same issue happens, then one of the two ssds are faulty. If not, then the motherboard is faulty.

 

[xtreem.p]

Anyone here tried the Gigabyte Z490 Vision G with ver.1 of the Alpine Ridge TB3 AIC?

 

[CaseySJ]

Anyone here tried the Gigabyte Z490 Vision G with ver.1 of the Alpine Ridge TB3 AIC?

I moved your post to the Z490 Vision D thread where we have a number of people with Vision G.

Please note that there is one version of GC-Alpine Ridge, but two versions of GC-Titan Ridge. I believe the GC-Alpine Ridge should work on Vision G.

I'm using a GC-Titan Ridge (version 1) in my Z490 Vision D. Because Vision D lacks a Thunderbolt header, I simply jumper pins 1 and 3 on the GC-Titan Ridge. It works just fine.

Edit: Correction pointed out by @scottkendall -- there are two versions of GC-Alpine Ridge as well.

 

[crossmoid]

Hello @crossmoid,

Can you please post the subsection of log messages that points to IONVMeFamily.

Hi Casey,

This is strange, looking at the system log in hackintool today, the event has changed but the time (and length) of that occurrence is exactly the same! The stall happens 20s in and lasts for 23s.....

 

[CaseySJ]

Hi Casey,

This is strange, looking at the system log in hackintool today, the event has changed but the time (and length) of that occurrence is exactly the same! The stall happens 20s in and lasts for 23s.....


View attachment 484484

Are any Thunderbolt devices attached?

 

[RentColours]

Forgot to post but complete success

10.15.6 Catalina on a EVO Plus 2TB
i9-10900K, 64GB 3000 Dominator RAM, Sapphire 5700 XT SE, Fractual S36+ celcuis, Broadcom BCM943602CDP with adapter for complete WiFi and Bluetooth functionality

RGB for the board, RAM, GPU and Fractal pump header are all remembered on hardware (set in windows)

Windows 10 running on a 2.5" SSD
Different BIOS profiles saved for switching OS's

No random temp jumping with CPU, just sweet sailing

 

[crossmoid]

Are any Thunderbolt devices attached?

Yes, but not switched on.

 

[jimbojingle]

I have started to get a regular hang at the Gigabyte Splash screen since I installed Big Sur on a separate SSD. This never happened originally with just my Windows and Catalina NVMe’s.

This is still happening even though I have completely removed the Big Sur SSD.

Any ideas why and is anyone else experiencing this problem?

 

[CaseySJ]

Yes, but not switched on.

In your screenshot...

...we see that bsd_autoconf called kminit, which took 23 seconds. However, and this is important, messages in the log file are asynchronous. Several threads and processes are simultaneously sending information to the logs.

Question:

• Every time you reboot the computer, do you see the same delay at the same place?
• If not, then the rest of this reply can be ignored.

If we look at the macOS source code, we find that a function called bsd_autoconf exists in the xnu kernel code (bsd_init.c) and logs the message you see in your screenshot. It then calls kminit.

The function kminit is also part of the xnu kernel code and is shown below. It's located inside a file called km.c, which is the kernel keyboard/monitor module.

​

​

Based on this alone, we can ask some questions:

• What is the make and model of your keyboard?
• Is it powered on and connected during boot?

 

[CaseySJ]

I have started to get a regular hang at the Gigabyte Splash screen since I installed Big Sur on a separate SSD. This never happened originally with just my Windows and Catalina NVMe’s.

This is still happening even though I have completely removed the Big Sur SSD.

Any ideas why and is anyone else experiencing this problem?

If we switch back and forth between Big Sur and Catalina, we might see some issues like this. This is one of several issues I've seen with the first public beta. Whenever this occurs, I do the following:

• Turn off the system and flip power switch on PSU for 10-20 seconds. Sometimes longer to let the machine cool down (but that's because we're experiencing a short-term heat wave in Silicon Valley at the moment).
• If that alone does not work, then CMOS Reset should be performed (which resets BIOS parameters to factory defaults, so always re-configure BIOS afterwards).