Asus Z690 ProArt Creator WiFi (Thunderbolt 4) + i7-12700K + AMD RX 6800 XT

[kenose]

@kenose

The existing SSDT-AQUANTIA-AQC113C.aml is not compatible with Big Sur because it sets device-id to 0x94c0, which is supported in Monterey (left) but not in Big Sur (right).

We could try spoofing the device-id to 0x04c0 instead, but I do not know if it will work. If you want to try it, simply use the new SSDT below and disable the existing one.

Thanks Casey! Yeah, I was looking at the Aquantia driver plist last night and came to the same realization.

I just tried the new SSDT on my external SSD with Big Sur 11.6.1 installed, but no luck. In IORegistryExplorer, the "device-id" and "compatible" fields for RP01 --> IOOP --> D069 still contained the 0x94c0 value— is that what is tripping up the driver?

 

[CaseySJ]

Thanks Casey! Yeah, I was looking at the Aquantia driver plist last night and came to the same realization.

I just tried the new SSDT on my external SSD with Big Sur 11.6.1 installed, but no luck. In IORegistryExplorer, the "device-id" and "compatible" fields for RP01 --> IOOP --> D069 still contained the 0x94c0 value— is that what is tripping up the driver?

Please post screenshot of your OpenCore Configurator --> ACPI page so we can check if the new SSDT was applied.

 

[CaseySJ]

About this issue for new builds.

Today, when I saw blank gray screen, I found that forum members try anything with language string in NVRAM. I fixing my gray screen when I deleted language string at all. no string - no problem. When installer started, it ask me what language I prefer.

Wow — I will test this soon!!

*** CONFIRMED! ***​

The OpenCore config.plist for this build contains an error in the NVRAM section:

The item prev-lang:kbd should be of type DATA. After changing it to the following, the USB install drive starts the macOS installer with no problem on a fresh system (after NVRAM Reset):

I'm about to replace the OpenCore 0.7.8 EFI folder with this change:

 

[CaseySJ]

@starghost1100,

Thank you for helping us find this very important solution. Now new users can easily install fresh copy of macOS. When I first created the EFI folder for this build, I forgot to change type from STRING to DATA. One little mistake with such large consequences!!

 

[etorix]

The item prev-lang:kbd should be of type DATA. After changing it to the following, the USB install drive starts the macOS installer with no problem on a fresh system (after NVRAM Reset):​

Thanks for confirming this nice find by @starghost1100. But is it that prev-lang:kbd cannot be a string, or that prev-lang:kbd cannot be an empty string?
I never experienced any issue, but I do set a non-empty string on my own EFIs.

 

[starghost1100]

@starghost1100,

Thank you for helping us find this very important solution. Now new users can easily install fresh copy of macOS. When I first created the EFI folder for this build, I forgot to change type from STRING to DATA. One little mistake with such large consequences!!

I never thought that I would be a useful member of the forum before, as far as I remember, it didn't matter if it was a string or data. but problems with a white / gray screen during installation can be traced even to a High Sierra.

 

[CaseySJ]

Thanks for confirming this nice find by @starghost1100. But is it that prev-lang:kbd cannot be a string, or that prev-lang:kbd cannot be an empty string?
I never experienced any issue, but I do set a non-empty string on my own EFIs.

The Type field is important. I tested the following conditions:

• prev-lang:kbd --> empty --> Type = DATA
  • Valid and preferred for new installations because empty string forces macOS to open the Language Selection dialog.
• prev-lang:kbd --> empty --> Type = STRING
  • Invalid, macOS installer will boot to gray screen
• prev-lang:kbd --> filled in with hex codes (ASCII) --> Type = DATA
  • Valid, but because language has been selected, macOS will not display the Language Selection dialog.

Not Tested:

• prev-lang:kbd --> filled in with text such as en-US:0 --> Type = STRING
  • Will it work? Left as an exercise for the reader!

 

[starghost1100]

Поле Тип имеет важное значение. Я тестировал следующие условия:

• prev-lang:kbd --> пусто --> Type = DATA
  • Действителен и предпочтителен для новых установок, поскольку пустая строка заставляет macOS открывать диалоговое окно «Выбор языка».
• prev-lang:kbd --> пусто --> Type = STRING
  • Неверно , установщик macOS загрузится с серым экраном
• prev-lang:kbd --> заполняется шестнадцатеричными кодами (ASCII) --> Type = DATA
  • Valid , но поскольку язык был выбран, macOS не будет отображать диалоговое окно выбора языка.

Не испытано:

• prev-lang:kbd --> заполняется текстом, например en-US:0 --> Type = STRING
  • Это будет работать? Оставлено в качестве упражнения для читателя!

Tomorrow I will be doing another installation on the Asus Z590 Maximus Hero. one of the few motherboards for socket 1200 with a working hot-plug Thunderbolt that I managed to find and buy. and I'll check en-us:0

 

[kenose]

Please post screenshot of your OpenCore Configurator --> ACPI page so we can check if the new SSDT was applied.

 

[gandem]

I never thought that I would be a useful member of the forum before, as far as I remember, it didn't matter if it was a string or data. but problems with a white / gray screen during installation can be traced even to a high sierra.

Never say never! The good folks in the Z690 discussion proved "never" not to be the case. Awesome!