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

[zirkaiva]

Attached SSDT removes device US00 before creating the rest of the device tree.

Now it reboots in OC, but still does not attach. In SSDT-5 those devices are already defined isn't that an issue?
Also, it is strange that the path in Windows is:

ACPI(_SB_)#ACPI(PC03)#ACPI(BR3A)#PCI(0000)#PCI(0000)#PCI(0000)

Whereas Vega's II path MPX in slot one is:

\_SB.PC01.BR1A.EGP0.EGP1.GFX0

Also it is strange that both devices do not load Windows drivers simultaneously. It is either/or.
What do you think about this:

DefinitionBlock ("", "SSDT", 2, "Apple", "AMD6950", 0x00000000)
{
    External (_SB_.PC03, DeviceObj)
    External (_SB_.PC03.BR3A, DeviceObj)
    External (_SB_.PC03.BR3A.US00, DeviceObj)
    External (DTGP, MethodObj)    // 5 Arguments

    Scope (\_SB.PC03.BR3A)
    {
        Scope (US00)
        {
            Name (_STA, Zero)  // _STA: Status
        }

        
                Device (GFX1)
                {
                    Name (_ADR, Zero)  // _ADR: Address
                    Method (_DSM, 4, NotSerialized)  // _DSM: Device-Specific Method
                    {
                        If (!Arg2)
                        {
                            Return (Buffer (One)
                            {
                                 0x03                                             // .
                            })
                        }

                        Return (Package (0x02)
                        {
                            "device-id",
                            Buffer (0x04)
                            {
                                 0xBF, 0x73, 0x00, 0x00                           // .s..
                            }
                        })                       
                    }
                    DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0))
                        Return (Local0)
                }

                Device (HDAU)
                {
                    Name (_ADR, One)  // _ADR: Address
                }
            }     
  
}

 

[cliffDeane]

Hi Guys,

Has anyone found a solution to the slow boot when Thunderbolt is enabled? I have a z490 Vision D and flashed the firmware via the guide mentioned on this thread.

All working great but a 30 sec delay before post when Thunderbolt is enabled. If disabled, I get an almost instant post.

I have also booted with no drives attached, cleared the CMOS and still the same issue.

Has anyone else experienced this?

Cliff

 

[CaseySJ]

Hi Guys,

Has anyone found a solution to the slow boot when Thunderbolt is enabled? I have a z490 Vision D and flashed the firmware via the guide mentioned on this thread.

All working great but a 30 sec delay before post when Thunderbolt is enabled. If disabled, I get an almost instant post.

I have also booted with no drives attached, cleared the CMOS and still the same issue.

Has anyone else experienced this?

Cliff

One quick suggestion:

• Try different settings of BIOS --> Thunderbolt Boot Support. Try "Boot Once" and others one by one.

 

[cliffDeane]

One quick suggestion:

• Try different settings of BIOS --> Thunderbolt Boot Support. Try "Boot Once" and others one by one.

Okay, just tried both settings.

Boot once and Pre-boot ACL

No joy with either.

Wonder is it the firmware causing it an issue?

Does anyone else have this issue?

 

[CaseySJ]

Okay, just tried both settings.

Boot once and Pre-boot ACL

No joy with either.

Wonder is it the firmware causing it an issue?

Does anyone else have this issue?

Please try the following ACPI patch:

• OpenCore Configurator --> ACPI --> Patch section
• Table Signature: Select DSDT from pop-up menu
• Find: 5C2E5F47 50455449 4E490052 50533052 50543000 5B
• Replace: A3A3A3A3 A3A3A3A3 A3A3A3A3 A3A3A3A3 A3A3A3A3 5B
• Count: 1
• Enabled: Check On

Save config.plist back to EFI partition and reboot. Does it help?

 

[cliffDeane]

No joy unfortunately, I really feel this could be an issue with this firmware and the z490 Vision D board. Could that be possible?

I have tired that suggestion above, reset NVRAM Multiple times and no joy.

Also tired removing GPU, all SSD's, HDD's & NVME drives. Reset Nvram and also reset CMOS - Still the very same issue once thunderbolt is enabled. With Thunderbolt disabled I get almost instant post.

I don't have the original firmware for this board, has anyone got it here? I would like to flash back to the stock TB firmware and see if this issue persists.

 

[cliffDeane]

I had the original TB firmware backed up for this board (Z490 Vision D) but did a reinstall on my MacBook so no longer have it

 

[zirkaiva]

Attached SSDT removes device US00 before creating the rest of the device tree.

@CaseySJ Tried removing the VegaII and only 6950xt is installed. Still does not attach with the provided SSDT.

 

[slickdawg]

Hi everyone, I'm hoping that one of you may be able to help me out. I've got a Gigabyte Vision G Z490 with the @#$@#$ Intel I225-V (rev 2) chip in it. I cannot get it to work in Monterey.

I've tried flashing the I225-V with I225MOD. It changed a two of the values (subsystem ID and subsystem vendor ID) however it does NOT keep the values in green, as noted by 5T33Z0 here (his github instructions)

If someone has a Z490 Vision G and has done the I225MOD, would you please check and see if the values in green are what they are shown in the image, or did they revert back? All of mine reverted back except the subsystem ID and subsystem vendor ID. I'll make another post about what I'm seeing in ioregistryexplorer.

 

[slickdawg]

This was after the I225MOD attempt, and the boot flag e1000=0. I can boot, plug in the cable, no freezes, no crashes. There's no network link. I can change it to 1000 full duplex and assign an IP manually, and it becomes green in preferences/network. It can ping its own IP, and cannot ping anything on the network. It will show connected even if I remove the cable.