Contribute
Register

Stork's Thunderball II Build: ASUS ProArt Z490 Creator (Thunderbolt 3) - i5-10400 - RX 580

Glad to see the build is up!! Congratulations for getting it up and running despite the challenges posed.

This is a very tempting motherboard. I was torn between this and the Gigabyte Z490 Vision D. Both are wonderful choices.
 
The board has its limitations unfortunately, I have been using it since summer and had to deal with several issues, the first BIOS was a mess, couldn't even properly configure CPU clock and other options.

@Stork are you on 0.6.4? I have a strange issue every time I turn on from cold where the BIOS throws a POST error message. With 0.6.1 it didn't happen tho.

The Ethernet issue can be solved adding this SSDT
Code: 
DefinitionBlock ("", "SSDT", 1, "DRENAN", "GIGE", 0x00000000)
{
    External (_SB_.PCI0.RP05, DeviceObj)
    External (PXSX, DeviceObj)
    
    Scope (\_SB.PCI0.RP05)
    {
        Scope (PXSX)
        {
            Method (_STA, 0, NotSerialized){If (_OSI ("Darwin")){Return (0)}Else{Return (0x0F)}}
        }

        Device (GIGE)
        {
            Name (_ADR, Zero)
            Name (_S0W, 0x03)
            Method (_DSW, 3, NotSerialized)
            {
            }
            
            Method (_DSM, 4, NotSerialized)
            {
                If ((Arg2 == Zero)){Return (Buffer (){0x03})}
                
                Return (Package ()
                {
                    "AAPL,slot-name",
                    Buffer ()
                    {
                        "Internal"
                    },

                    "built-in",
                    Buffer ()
                    {
                         0x00
                    },
                    
                    "device-id",
                    Buffer ()
                    {
                         0xf2, 0x15, 0x00, 0x00
                    }, 

                    "model",
                    Buffer ()
                    {
                        "Intel 400 Series 2.5G I225-V Ethernet Chipset"
                    },

                    "name",
                    Buffer ()
                    {
                        "Intel(R) Comet Lake 2.5G Ethernet Controller"
                    }
                })
            }
        }
    }
}
Or by adding the device ID on the SSDT inside the .plist creating an entry with the correct PCI device path.
 

Attachments

  • SSDT-Z490-GIGE-DRENAN.aml
    342 bytes · Views: 151
dolgarrenan said:
The board has its limitations unfortunately, I have been using it since summer and had to deal with several issues, the first BIOS was a mess, couldn't even properly configure CPU clock and other options.

@Stork are you on 0.6.4? I have a strange issue every time I turn on from cold where the BIOS throws a POST error message. With 0.6.1 it didn't happen tho.
Click to expand...
I get that, too. There's a fix in the OV guide for that BIOS Post error. I've got it on my list to find.:D
dolgarrenan said:
The Ethernet issue can be solved adding this SSDT
Code: 
DefinitionBlock ("", "SSDT", 1, "DRENAN", "GIGE", 0x00000000)
{
    External (_SB_.PCI0.RP05, DeviceObj)
    External (PXSX, DeviceObj)
   
    Scope (\_SB.PCI0.RP05)
    {
        Scope (PXSX)
        {
            Method (_STA, 0, NotSerialized){If (_OSI ("Darwin")){Return (0)}Else{Return (0x0F)}}
        }

        Device (GIGE)
        {
            Name (_ADR, Zero)
            Name (_S0W, 0x03)
            Method (_DSW, 3, NotSerialized)
            {
            }
           
            Method (_DSM, 4, NotSerialized)
            {
                If ((Arg2 == Zero)){Return (Buffer (){0x03})}
               
                Return (Package ()
                {
                    "AAPL,slot-name",
                    Buffer ()
                    {
                        "Internal"
                    },

                    "built-in",
                    Buffer ()
                    {
                         0x00
                    },
                   
                    "device-id",
                    Buffer ()
                    {
                         0xf2, 0x15, 0x00, 0x00
                    },

                    "model",
                    Buffer ()
                    {
                        "Intel 400 Series 2.5G I225-V Ethernet Chipset"
                    },

                    "name",
                    Buffer ()
                    {
                        "Intel(R) Comet Lake 2.5G Ethernet Controller"
                    }
                })
            }
        }
    }
}
Or by adding the device ID on the SSDT inside the .plist creating an entry with the correct PCI device path.
Click to expand...
I tried your SSDT. It didn't work. I need to explore more.
 
Stork said:
I get that, too. There's a fix in the OV guide for that BIOS Post error. I've got it on my list to find.:D
Click to expand...
I will have a look and report back
Stork said:
I tried your SSDT. It didn't work. I need to explore more.
Click to expand...
Are you not using the FakePCIID kexts??

EDIT: Activate "DisableRtcChecksum" quirk to get rid of the BIOS post error
 

Attachments

  • FakePCIID.kext.zip
    13.5 KB · Views: 96
  • FakePCIID_Intel_I225-V.kext.zip
    3.5 KB · Views: 89
Last edited:
Stork said:
I get that, too. There's a fix in the OV guide for that BIOS Post error. I've got it on my list to find.:D

I tried your SSDT. It didn't work. I need to explore more.
Click to expand...
same here, not sure what ethernet problem was being solved :)
 
dolgarrenan said:
The board has its limitations unfortunately, I have been using it since summer and had to deal with several issues, the first BIOS was a mess, couldn't even properly configure CPU clock and other options.

@Stork are you on 0.6.4? I have a strange issue every time I turn on from cold where the BIOS throws a POST error message. With 0.6.1 it didn't happen tho.

The Ethernet issue can be solved adding this SSDT
Code: 
DefinitionBlock ("", "SSDT", 1, "DRENAN", "GIGE", 0x00000000)
{
    External (_SB_.PCI0.RP05, DeviceObj)
    External (PXSX, DeviceObj)
   
    Scope (\_SB.PCI0.RP05)
    {
        Scope (PXSX)
        {
            Method (_STA, 0, NotSerialized){If (_OSI ("Darwin")){Return (0)}Else{Return (0x0F)}}
        }

        Device (GIGE)
        {
            Name (_ADR, Zero)
            Name (_S0W, 0x03)
            Method (_DSW, 3, NotSerialized)
            {
            }
           
            Method (_DSM, 4, NotSerialized)
            {
                If ((Arg2 == Zero)){Return (Buffer (){0x03})}
               
                Return (Package ()
                {
                    "AAPL,slot-name",
                    Buffer ()
                    {
                        "Internal"
                    },

                    "built-in",
                    Buffer ()
                    {
                         0x00
                    },
                   
                    "device-id",
                    Buffer ()
                    {
                         0xf2, 0x15, 0x00, 0x00
                    },

                    "model",
                    Buffer ()
                    {
                        "Intel 400 Series 2.5G I225-V Ethernet Chipset"
                    },

                    "name",
                    Buffer ()
                    {
                        "Intel(R) Comet Lake 2.5G Ethernet Controller"
                    }
                })
            }
        }
    }
}
Or by adding the device ID on the SSDT inside the .plist creating an entry with the correct PCI device path.
Click to expand...
care to list the limitations ?
other than it being first gen of a line, inherent i225-v issue.
 
dolgarrenan said:
I will have a look and report back

Are you not using the FakePCIID kexts??
Click to expand...
No. Here's the kexts I'm using:
Stork's Creator kexts.png

BTW, I've been using IntelMausi.kext since OC 0.6.0, and it worked until I created OC 0.6.4 from scratch.

dolgarrenan said:
EDIT: Activate "DisableRtcChecksum" quirk to get rid of the BIOS post error
Click to expand...
Thank you. Now I can enjoy my morning pot of coffee.
 
Last edited:
centraljava said:
care to list the limitations ?
other than it being first gen of a line, inherent i225-v issue.
Click to expand...
Besides first gen:
  • There has been problems with overclocking. You couldn't turn on completely XMP with CPU turbo rates, which for some reason was giving away problems and system just wouldn't boot.
  • RTC is not properly patched thus the boot issue.
  • All PCIs share bandwidth with different devices which limits things a lot.

  • Ethernet port is as is, it needs trickery and using FakePCIID set of kext which are old and not supported by the developer any more (@RehabMan).
  • To achieve audio through integrated HDMI you need to make changes again, the use of AppleALC by itself isn't enough.
  • USB RHUB needs to be deactivated otherwise is almost impossible to map correct USBs, I had this board since almost day 1 and had to work much in order to get all USB working at the right speeds.
  • HDMI port is 1.4.... c'mon, seriously...
That's just my thoughts, I use this board as a daily driver and besides little stuff going on like with updates. (Big Sur proved to be a pain in the butt to install and had to change AWAC to RTC0 to make it boot.) There is also the price tag if you ask me, not the cheapest hardware.

Screenshot 2020-12-30 at 13.17.18.png
 
Stork said:
No. Here's the kexts I'm using:
View attachment 502966
BTW, I've been using IntelMausi.kext since OC 0.6.0, and it worked until I created OC 0.6.4 from scratch.


Thank you. Now I can enjoy my morning pot of coffee.
Click to expand...
Just use the .kext I attached on my previous post with SSDT and remove IntelMausi, not compatible with this board.
 
You must log in or register to reply here.
Copyright © 2010 - 2024 tonymacx86 LLC
Back
Top