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

[Inqnuam]

192khz holy wow.

Any idea how we can check the sample rate of a .movpkg "file" ?

(of course I checked every file from the screenshot)

 

[NorthAmTransAm]

Any idea how we can check the sample rate of a .movpkg "file" ?
View attachment 521334View attachment 521335

(of course I checked every file from the screenshot)

If you have Pro Tools you can try to import it (create a new session, file-->import...) and the next steps should inform you if theres a conversion from the files native sample rate to what the session is.

 

[luvlastcall]

You might be booting from the wrong drive. Please check BIOS --> BOOT order or press F12 at Gigabyte splash screen to select the correct boot drive.

I checked it and it's booting from correct drive as it was previously should I go ahead and reinstall the OS one more time

 

[luvlastcall]

Try clearing NVRAM from the boot menu.

Already tried that

 

[Elias64Fr]

Bonjour @Casey and all,
After long search on UEFI firmwares (Z390 Designare ans Apple), I finally found how to have ThunderboltNhi, ThunderboltXDomain and PciThunderbolt Dxe drivers operating on Z390 BIOS firmware .
Now, with OpenShell command DH, I can see them :

After removing all properties added on OpenCore (ThunderboltDROM, ThunderboltConfig...), all theses properties automatically appears on NHI0 device (IOReg) with new data for Thunderbolt DROM, ThunderboltConfig, ThunderboltUUID and TBTFlags :

ThunderConfig: <00 02 1c 00 02 00 05 03 01 00 04 00 05 03 02 00 03 00 05 03 01 00 00 00 03 03 02 00 01 00 02 00>

and TBTFlags: <0b 00 00 00>

I have flashed Thunderbolt firmware with light DROM (like apple firmware) and ThunderboltDROM fully appears :

For long time, I was blocked on missed protocol AC5E4829-A8FD-440B-AF33-9FFE013B12D8, I finally found that it is generated by ApplePlatformInfoDatabaseDxe driver ... and ... 2 paired PEI modules added at the end of PEI modules volume (A3C7A8BA-094A-47C6-9F66-F6DE5E42A6E7 and ApplePlatformInfoDatabaseDxe, both extracted from Apple firmware):

 

[Elias64Fr]

This is a beta version that was posted some time ago. Some folks have already tried it and, I think, reported some issues with USB-C devices on Thunderbolt ports.

And this last F9k Gigabyte firmware does not include last Microcodes from January 2021 ...

 

[CaseySJ]

Bonjour @Casey and all,
After long search on UEFI firmwares (Z390 Designare ans Apple), I finally found how to have ThunderboltNhi, ThunderboltXDomain and PciThunderbolt Dxe drivers operating on Z390 BIOS firmware .
Now, with OpenShell command DH, I can see them :
View attachment 521341
View attachment 521342

After removing all properties added on OpenCore (ThunderboltDROM, ThunderboltConfig...), all theses properties automatically appears on NHI0 device (IOReg) with new data for Thunderbolt DROM, ThunderboltConfig, ThunderboltUUID and TBTFlags :

ThunderConfig: <00 02 1c 00 02 00 05 03 01 00 04 00 05 03 02 00 03 00 05 03 01 00 00 00 03 03 02 00 01 00 02 00>

and TBTFlags: <0b 00 00 00>

I have flashed Thunderbolt firmware with light DROM (like apple firmware) and ThunderboltDROM fully appears :

View attachment 521348
View attachment 521351

For long time, I was blocked on missed protocol AC5E4829-A8FD-440B-AF33-9FFE013B12D8, I finally found that it is generated by ApplePlatformInfoDatabaseDxe driver ... and ... 2 paired PEI modules added at the end of PEI modules volume (A3C7A8BA-094A-47C6-9F66-F6DE5E42A6E7 and ApplePlatformInfoDatabaseDxe, both extracted from Apple firmware):

View attachment 521354

@Elias64Fr,

This is amazing!! Wow.

Before posting the new BIOS, could you please send me a copy via private message so I can run some tests?

In IOReg, do you also see pathcr?

 

[CaseySJ]

I checked it and it's booting from correct drive as it was previously should I go ahead and reinstall the OS one more time

Not necessary to reinstall the OS because the OS is completely independent of the OpenCore boot loader. OS is installed in APFS partition and OpenCore is installed in EFI partition.

Please mount the EFI partition, expand the following folders, and post a screenshot:

• EFI/BOOT
• EFI/OC

 

[P1LGRIM]

Already tried that

Then it appears that your OpenCore version is being accurately reported.
Your current version will not prevent the installation of a newer version.
There was an issue with the OpenCore version being incorrectly reported and this was cured by clearing NVRAM, you do not seem to be suffering from this problem.

 

[Elias64Fr]

@Elias64Fr,

This is amazing!! Wow.

Before posting the new BIOS, could you please send me a copy via private message so I can run some tests?

In IOReg, do you also see pathcr?

I can see also pathcr

All these firmware modifications are on a customised firmware (DSDT and SSDT modified by including all patches like GFX0 to IGPU, IMEI, DTPG ... and some Firmware structure modifications ), I haven't made an original F9i based firmware yet.