SATA drives not detected on macOS Tahoe (AMD B550 chipset + ASMedia) | worked fine on Sequoia with same EFI

[rxtsel]

Hardware​

• Motherboard: MSI PRO B550-VC
• CPU: AMD Ryzen 7 5800X
• GPU: AMD Radeon RX 6600 (Navi 23)
• Storage: 2x ADATA SU650 2.5" SATA SSD
• OpenCore: 1.0.7
• SMBIOS: MacPro7,1

Problem​

Two SATA controllers on this board:

• PCI 1022:43EB — AMD B550 chipset SATA controller (motherboard SATA1-6)
• PCI 1B21:0612 — ASMedia ASM1061/1062 controller (motherboard SATA7-8)

Neither is detected by macOS Tahoe (currently on 26.5.2). Disk Utility / diskutil list show nothing SATA — only the USB installer. This is a regression: the exact same EFI (OpenCore 1.0.7, same kexts, no changes) boots macOS Sequoia fine and detects both SATA SSDs without any special kext. The problem only appears when booting the Tahoe installer.

What we ruled out (with evidence, not just "tried it")​

1. AMDSata.kext (aka SATA-unsupported.kext, also re-hosted as AlfCraft07/AMDSata)
Verified via Info.plist inspection: IOClass = AppleIntelPchSeriesAHCI. This class was removed from AppleAHCIPort.kext since Big Sur (confirmed via multiple sources including the archived eason329/AMD-SATA-unsupported repo's own README). This kext cannot functionally match anything on any post-Big Sur macOS, regardless of what any README claims about "known working through Tahoe."

2. CtlnaAHCIPort.kext (both HeaDragon's original and Dortania's hosted copy in OpenCore-Install-Guide/extra-files/)
Downloaded and disassembled the actual binary's IOKitPersonalities. It contains only Intel PCH device IDs (pci8086,... — 10 personalities, all Intel 5-Series through 200-Series). Zero AMD (1022) or ASMedia (1b21) entries. This kext is commonly recommended across guides as "the Big Sur+ fix for third-party SATA" but it is Intel-only and cannot help AMD/ASMedia hardware at all.

3. BIOS SATA Hot Plug
Per-port Hot Plug was disabled for SATA1-6 (chipset). Enabled it — no change. SATA7-8 (ASMedia) doesn't expose a Hot Plug toggle in BIOS at all.

4. ACPI-level fixes

• Built an SSDT to disable (_STA=0) the AMD chipset SATA ACPI device (\_SB.PCI0.GPP1.PT01) to isolate/avoid a kernel hang we hit earlier when the SATA controller was touched (see below) — confirmed via acpidump/iasl decompile that this is the correct ACPI path for 02:00.1.
• Built an SSDT-Bridge.aml (via CorpNewt's SSDTTime) to declare the missing leaf PCI device for the ASMedia controller (\_SB.PCI0.GPP1.PT02.PT26, target path PciRoot(0x0)/Pci(0x1,0x2)/Pci(0x0,0x2)/Pci(0x6,0x0)/Pci(0x0,0x0)).
• Neither changed the outcome for detection, though the SSDT hiding the AMD controller did stop an earlier kernel hang (see below).

Diagnostic evidence collected​

With AppleDebug/ApplePanic enabled and a DEBUG build of OpenCore:

• Before hiding the AMD chipset SATA controller via ACPI: boot would hang hard after AppleAHCI::start appears in verbose (no panic ever written to disk — genuine hang, not a crash. Confirmed no panic log ever generated across 5+ attempts).
• Blocking com.apple.driver.AppleAHCIPort entirely (Kernel -> Block) let the installer reach the GUI — confirming the AMD chipset controller was the source of the hang.
• After that, in the installer's Terminal:

  kextstat | grep -i ahci
  84  1  ...  com.apple.iokit.IOAHCIFamily
  85  0  ...  com.apple.driver.AppleAHCIPort

AppleAHCIPort loaded but 0 active clients — it never attached to either SATA controller (AMD chipset or ASMedia). dmesg | grep -iE "ahci|sata" returns nothing at all — not even a failed-match log line.

Question for the community​

Has anyone gotten SATA (not NVMe) drives working under Tahoe on an AMD B550/X570 FCH controller or an ASMedia SATA controller? Is this a known Tahoe-specific regression in AppleAHCIPort/IOAHCIFamily generic AHCI class-code matching, separate from the old Big Sur AppleIntelPchSeriesAHCI removal? Happy to share the full EFI, logs, or test anything.