Contribute
Register

Gigabyte Z690 Aero G + i5-12600K + AMD RX 6800 XT

Fix - Sleep/Wake on BIOS F22
Although sleep/wake worked after reverting back to BIOS F8, version F22 seems to support my RAM better (4x8GB Patriot Viper Steel DDR4 4400); especially when overclocking.

I decided to try jumping back to BIOS F22 and see if it would fail again after setting all the BIOS options in order to boot; and it did. Before doing so, I thought I had enabled Re-size BAR support since I'm running a 6900 XT and my config is set for Re-size BAR support, but I was not able to boot. That is because I forgot that in version F8, Re-size BAR Support is visible but hidden in F22 until you set Above 4GB MMIO BIOS assignment. After testing sleep/wake and it failing once again after jumping to F22, i went back into BIOS and looked at the description text when selecting Above 4GB MMIO BIOS assignment. That setting seems to have a dependency on Aperture Size in that according to the description it is enabled automatically when Aperture Size is set to 2048MB. I decided to check what my max value is for Aperture Size and saw that the default value was 256MB. I bumped it up to the max value to 1024MB, saved the changes and booted up.

Increasing Aperture Size from the default of 256MB seems to have done the trick and I'm no longer experience the sleep/wake issue that I was having earlier on BIOS F22 and that made a difference.

I've attached some screenshots of the BIOS settings for reference.

BIOS Version F22
230225014915.jpg


Aperture Size default 256MB
230225014800.jpg


230225014815.jpg


230225014828.jpg


230225014842.jpg


Change Aperture Size to max value.
230225014856.jpg


You can see the total number of Sleep/Wakes (3) that I did sequentially:
Screenshot 2023-02-24 at 9.21.48 PM.png
 
Last edited:
Fix - Sleep/Wake on BIOS F22
Although sleep/wake worked after reverting back to BIOS F8, version F22 seems to support my RAM better (4x8GB Patriot Viper Steel DDR4 4400); especially when overclocking.

I decided to try jumping back to BIOS F22 and see if it would fail again after setting all the BIOS options in order to boot; and it did. Before doing so, I thought I had enabled Re-size BAR support since I'm running a 6900 XT and my config is set for Re-size BAR support, but I was not able to boot. That is because I forgot that in version F8, Re-size BAR Support is visible but hidden in F22 until you set Above 4GB MMIO BIOS assignment. After testing sleep/wake and it failing once again after jumping to F22, i went back into BIOS and looked at the description text when selecting Above 4GB MMIO BIOS assignment. That setting seems to have a dependency on Aperture Size in that according to the description it is enabled automatically when Aperture Size is set to 2048MB. I decided to check what my max value is for Aperture Size and saw that the default value was 256MB. I bumped it up to the max value to 1024MB, saved the changes and booted up.

Increasing Aperture Size from the default of 256MB seems to have done the trick and I'm no longer experience the sleep/wake issue that I was having earlier on BIOS F22 and that made a difference.

Thank you for this. I am using Raptor Lake and have to use BIOS F20 and above. I will try this and report back.
 
Hi @CaseySJ !

I recently changed my Titan Ridge, for a Maple Ridge, which works flawlessly on Windows 11 (the Titan didn't) and I followed carefully your post about setting up SSDT's for this new card :


I followed the instructions and I'm using the Maple Ridge SSDT you provided, changed the card slot, 5 pin header, etc. I just changed the PCIe card, the rest of the config is a copy of yours.

I wanted to share my experience :

I use the 2 TB4 ports of the cards (1 for Apollo Twin X, 1 for a THB3 SSD external enclosure)

- Cold boot won't work at all
- Hot plug neither

I always need to cold boot first, then restart and only at this second time, the Apollo connects.

I tried with the 2 AML's your provided (Titan and Maple), no change.

View attachment 543012

View attachment 543013

I remember you had changed something in my SSDT for my Titan Ridge and the cold boot problem had disappeared. Isn't it possible with Maple ?

I'm using the config in the EFI attached.
Hi,
I am experiencing exact the same problems!
I have an UAD Apollo Twin.
Did you get to solve this?
 
Yes those are both good.
Thank you Casey! Just want to say an IMMENSE THANK YOU For all your contribution in this thread and elsewhere across the forum. If it wasn't for your tutorials here, I would have never built my Alder Lake hack and had as awesome of a computer as I do; everything is working perfectly in my setup (took a while for my dumbass to figure it all out, but it's super smooth).

You're the real MVP.
 
Hi,
I am experiencing exact the same problems!
I have an UAD Apollo Twin.
Did you get to solve this?
Have you read UA's knowledge base surrounding Thunderbolt 2/3 devices and compatibility with Thunderbolt 4? They won't hot plug according to them, and, for example, it doesn't in Windows 11. So a Maple Ridge add-on card won't help with that; only a cold boot will make it connect.

You will need to use a GC-Titan Ridge card and flash it most likely.

I have an Apollo Twin, the Thunderbolt 2 version and that has been my experience.
 
Last edited:
Have you read UA's knowledge base surrounding Thunderbolt 2/3 devices and compatibility with Thunderbolt 4? They won't hot plug according to them and for example, doesn't in Windows 11, so a Maple Ridge add-on card won't help with that; only a cold boot will make it connect.

You will need to use a GC-Titan Ridge card and flash it most likely.

I have an Apollo Twin, the Thunderbolt 2 version and that has been my experience.
Thanks for your comments!
It is weird now for me because I move the Maple Ridge to the bottom slot, with the headers out, and the Apollo started to work on every single boot, even after a restart. I was making use of the SSDT-TITAN-RIDGE-V1.aml and the SSDT-DTbtSsdt.aml, from CaseySJ's post (#1,159) and the picker enabled was elementary.
But then I started to test with some changings, and I got back to the cold boot only. I cannot have it work smoothly as when I just put it back to the bottom slot.
And it is not just that a cold boot is needed, it needs a restart after the cold boot to have it working... Really annoying.
How do you have your setup working?
It will be enough for me if I can have the UAD connected every time I turn on the computer.
 
Thanks for your comments!
It is weird now for me because I move the Maple Ridge to the bottom slot, with the headers out, and the Apollo started to work on every single boot, even after a restart. I was making use of the SSDT-TITAN-RIDGE-V1.aml and the SSDT-DTbtSsdt.aml, from CaseySJ's post (#1,159) and the picker enabled was elementary.
But then I started to test with some changings, and I got back to the cold boot only. I cannot have it work smoothly as when I just put it back to the bottom slot.
And it is not just that a cold boot is needed, it needs a restart after the cold boot to have it working... Really annoying.
How do you have your setup working?
It will be enough for me if I can have the UAD connected every time I turn on the computer.
You didn't have hot-plug working right with the GC-Maple Ridge card?

The only TB device that I have is the Apollo Twin and I was able to cold boot and have it connect.

Didn't need any additional SSDT enabled in the ACPI folder as you can see.

Screenshot 2023-03-03 at 3.21.14 PM.png


Screenshot 2023-03-03 at 3.37.00 PM.png
 
Last edited:
You didn't have hot-plug working right with the GC-Maple Ridge card?

The only TB device that I have is the Apollo Twin and I was able to cold boot and have it connect.

Didn't need any additional SSDT enabled in the ACPI folder as you can see.

View attachment 564182

View attachment 564183
Thanks, I can see. So you don't need to restart the system to have it detected after a cold boot?

What PCI Slot are you using for the Maple Ridge?
 
Back
Top