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

[Feartech]

OC 0.6.4 Release

your image explains the issues you have

for example the playchime issue, if you check the sample.plist and search for playchime, you see:

<key>Audio</key>
        <dict>
            <key>AudioCodec</key>
            <integer>0</integer>
            <key>AudioDevice</key>
            <string>PciRoot(0x0)/Pci(0x1b,0x0)</string>
            <key>AudioOut</key>
            <integer>0</integer>
            <key>AudioSupport</key>
            <false/>
            <key>MinimumVolume</key>
            <integer>20</integer>
            <key>PlayChime</key>
            <string>Auto</string>
            <key>VolumeAmplifier</key>
            <integer>0</integer>
        </dict>

and you check yours:

<key>Audio</key>
        <dict>
            <key>AudioCodec</key>
            <integer>0</integer>
            <key>AudioDevice</key>
            <string>PciRoot(0x0)/Pci(0x1F,0x3)</string>
            <key>AudioOut</key>
            <integer>0</integer>
            <key>AudioSupport</key>
            <true/>
            <key>MinimumVolume</key>
            <integer>40</integer>
            <key>PlayChime</key>
            <string></string>
            <key>VolumeAmplifier</key>
            <integer>120</integer>
        </dict>

you will need to add in Auto (or Disabled or Enabled)

then you check the other issues from your image and make your amendments

 

[CaseySJ]

OC 0.6.4 Release

Please try attached config.plist.

 

[CaseySJ]

@CaseySJ,
I have GC-Titan ridge v1 flashed with NVM50. When I hot plug my eGPU (Omen Accelerator with RX580), GPU is not fully detected (no frame buffers) and is not operating.

Main difference between onboard controller and GC-Titan-Ridge card is also on BIOS setting for onboard like ressource allocation (MEM, PMEM, IRQ). We don't have those settings for add-on card.

I have tested with onboard controller by setting all data to Zero except for MEM and PMEM with 1MB minimum required. On this configuration, I have same result (eGPU not fully detected).
I noticed that eGPU detection occur with 10MB only on MEM .

By the way, this issue doesn't appear with Thunderbolt 2 Ethernet (with TB3 to TB2 adaptator), probably because this device not require ressource allocation.

To solve this issue on eGPU detection, I have added _CRS method on my Thunderbolt SSDT (under RP21) and have modified two registers (R_20 and R_24) on _INI () initialization step (or PINI for Z390 Designare MB).

...

MMRP() is a native method (included on DSDT) and RPNB data related to Root Port number (here 0x15 = 21) connected to the add-on card (shall be modified).

I don't know if my previous issue is related to @i0ntempest issue but you can test it

@Elias64Fr,

Please check if the various fields and methods below are at the right scope:

• RPSM at RP23 scope
• _CRS method also at RP23 scope

Because the Z490 Vision D calls Method PINI conditionally if it exists, we can simply create a Method PINI instead of applying ACPI patches to rename the existing Method _INI.

This SSDT is parsed without error, but unfortunately Thunderbolt port behavior remains unchanged. Namely, a Thunderbolt-only device will connect, but a dual mode Thunderbolt/USB-C-alt-mode device will attempt to connect via USB-alt-mode and fail.

 

[salvomercadante]

Please try attached config.plist.

i tried to replace your file but on reboot i always get the same messages. honestly I tried to modify the strings as suggested by the other guy, but my skills are still very low

 

[CaseySJ]

i tried to replace your file but on reboot i always get the same messages. honestly I tried to modify the strings as suggested by the other guy, but my skills are still very low

This is the procedure to replace the file:

• Mount EFI partition of the macOS SSD.
• Inside the EFI disk you will see a folder that is also called EFI
• Inside this EFI folder you will find a subfolder called OC
• Copy the new config.plist into the OC folder
• Reboot
• Make sure the USB install disk is removed
• If there are multiple disks in the system, press F12 at the Gigabyte Splash Screen to bring up the BIOS Boot Menu (not OpenCore Picker)
• From this menu, select the internal macOS SSD
• Now OpenCore Picker will appear

Do you still see those OCS Schema warnings?

 

[salvomercadante]

This is the procedure to replace the file:

• Mount EFI partition of the macOS SSD.
• Inside the EFI disk you will see a folder that is also called EFI
• Inside this EFI folder you will find a subfolder called OC
• Copy the new config.plist into the OC folder
• Reboot
• Make sure the USB install disk is removed
• If there are multiple disks in the system, press F12 at the Gigabyte Splash Screen to bring up the BIOS Boot Menu (not OpenCore Picker)
• From this menu, select the internal macOS SSD
• Now OpenCore Picker will appear

Do you still see those OCS Schema warnings?

I had already done so, but when in doubt I tried and I still see these messages on reboot

 

[moodog]

Hey All, Yesterday Decided to take Catalina 10.15.7 build on to OpenCore 0.6.4, this went pretty smoothly. Everything seems to be working great. Today I proceeded to try the update to Big Sur, When it reboots and It tries to boot the Install image I end up with OCB: StartImage failed - Aborted.

I dug around this thread for anything and didn't find anything on this specifically then moved on to various other threads with options but everything that I found resulted in the same error or breaking my OpenCore completely on this hardware. SO, here I am haha, being that the hardware is based on this thread Im hoping someone has seen this and just got it going easily.

Any help is much appreciated... Ill keep searching in the meantime....

 

[CaseySJ]

I had already done so, but when in doubt I tried and I still see these messages on reboot

Please post screenshot of the EFI folder as shown below so we can see Date Modified (no need to expand the ACPI, Kexts, Drivers, Tools, and Resources folders):

 

[CaseySJ]

Hey All, Yesterday Decided to take Catalina 10.15.7 build on to OpenCore 0.6.4, this went pretty smoothly. Everything seems to be working great. Today I proceeded to try the update to Big Sur, When it reboots and It tries to boot the Install image I end up with OCB: StartImage failed - Aborted.

I dug around this thread for anything and didn't find anything on this specifically then moved on to various other threads with options but everything that I found resulted in the same error or breaking my OpenCore completely on this hardware. SO, here I am haha, being that the hardware is based on this thread Im hoping someone has seen this and just got it going easily.

Any help is much appreciated... Ill keep searching in the meantime....

We can usually fix this as follows:

• Go to BIOS Setup
• Then go to the Boot section

Here you will see boot disks listed in priority order. The first boot priority will most likely be OpenCore. Change the first boot priority to the macOS SSD itself. Now the system should boot...

Note that OpenCore will later change first boot priority back to OpenCore, and that is perfectly okay.

 

[salvomercadante]

Pubblica uno screenshot della cartella EFI come mostrato di seguito in modo da poter vedere la data di modifica (non è necessario espandere le cartelle ACPI, Kexts, Drivers, Tools e Resources):

View attachment 503127