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

[whiskeynipple0088]

mine doesnt show it
fyi - Im booted from a USB drive, as I was making sure everything worked

 

[CaseySJ]

mine doesnt show it
fyi - Im booted from a USB drive, as I was making sure everything worked

Kudos for booting from a USB drive. Always a good idea to test new EFI folders this way.

Please try the suggestion in screenshot #2 of my previous reply.

 

[whiskeynipple0088]

sorry just saw the bottom screen shot.
Just made that change going to reboot. Hopefully I will be back.

 

[whiskeynipple0088]

lmfao .... are you serious.... that was it.
It works. You are awesome, thank you so much.

 

[CaseySJ]

lmfao .... are you serious.... that was it.
It works. You are awesome, thank you so much.

Glad to hear it. However this reveals a problem for Catalina users because of the following:

• If we set device ID to 0x15F2 we will invoke the 1GbE driver instead of the 2.5GbE driver.
• On Catalina this is fine because Catalina does not support 2.5GbE.
• But Big Sur and Monterey users will complain because those versions of macOS do support 2.5GbE speeds.
• So Big Sur and Monterey users need to use #device-id, but Catalina users need to use device-id.
• Not sure if there's a way to automatically handle both cases with a single config.plist.
• For the time being I'll add a note asking Catalina users to manually change it to device-id.

 

[CODYQX4]

Glad to hear it. However this reveals a problem for Catalina users because of the following:

• If we set device ID to 0x15F2 we will invoke the 1GbE driver instead of the 2.5GbE driver.
• On Catalina this is fine because Catalina does not support 2.5GbE.
• But Big Sur and Monterey users will complain because those versions of macOS do support 2.5GbE speeds.
• So Big Sur and Monterey users need to use #device-id, but Catalina users need to use device-id.
• Not sure if there's a way to automatically handle both cases with a single config.plist.
• For the time being I'll add a note asking Catalina users to manually change it to device-id.

Is #device-id just a comment or does it have a special function?

 

[MacArthur]

Hi @CaseySJ , it's me again, no NFO, no aliens around still the same hack I got thanks to your hard work for around one year now !
I don't know how you manage HackinDROM apps, when there are changes in your original EFI but I just discover that:
- If I create EFI with the one you posted in your monthly update for OC 0.71 AMD IntelWIFI 2 or 3 days ago (can't really remember) everything is alright.
- If I create the same EFI from scratch with HackinDROM apps (selecting motherboard, AMD GPU and IntelWIFI and then importing my SN), the EFI created gives me... no mouse again .
By checking the config.list generated I see that the culprit ( USBInjectAll.kext) is still not activated.
Just wanted to let you know...

EDIT: And I just discover now that today if we download the EFI from your post related to updated OC 0.71, USBInjectAll.kext is again disabled...

 

[Feartech]

Is #device-id just a comment or does it have a special function?

no, it just means it will be ignored on bootup

 

[bomburt]

Hi CaseySJ, I just wanted to say a big thank you for your excellent guide. Everything worked from first install for me, much much easier than my previous few years running Clover on my Asus Z170 Pro Gaming.

 

[CaseySJ]

Hi CaseySJ, I just wanted to say a big thank you for your excellent guide. Everything worked from first install for me, much much easier than my previous few years running Clover on my Asus Z170 Pro Gaming.

Welcome to the forum and to the Society of Problem Free Builders. This is a distinction reserved for those who get it right the first time!