trx40 [Discussion] - TRX40 Bare Metal - Vanilla Patches

[luchina]

@fabiosun,

 

Got an Asus Prime TRX40 Pro with a 3970X, got it installed and everything but I noticed some weird things.

1. When trying to use 'built-in | Data | 01000000' on SATA controllers, the disk disappears even from Disk Utility. I'm not a big fan, but I even tried with Innie.kext, and although the disc didn't disappear, it remained orange (External);
2. I also noticed that trying to use RestrictEvents the CPU name is not corrected, it remains Unknown in About This Mac. I also used the corp's cpuname, but even setting revpatch=cpuname, the name is not accepted in About This Mac;
3. Audio does not work with any layout-id, and it is a Realtek ALC1220. It already includes HPET (SSDT + ACPI> Patches) and nothing.

Have you noticed these behaviors in the TRX40?

 

Thanks 😉

 

[fabiosun]

Hi Luchina

never had that problem:

1) i used Hackcheck app to "check" path and declare device as internal

2) also there no problem (put 0 in processor type or 3841 (i do not remeber)

3) are you sure about it could be an USB Audio?

In this case you have to map your USB port well

My MSI had USB audio

[luchina]

On 5/25/2025 at 4:42 AM, fabiosun said:

Hi Luchina

never had that problem:

1) i used Hackcheck app to "check" path and declare device as internal

2) also there no problem (put 0 in processor type or 3841 (i do not remeber)

3) are you sure about it could be an USB Audio?

In this case you have to map your USB port well

My MSI had USB audio

 

Audio OK now, it's USB too, before it didn't appear on the USBs.

One thing I noticed is that the BIOS had an option turned on by default which was:

Advanced > SATA Configuration > NVMe RAID mode

And after turning this off the audio started to work/detect correctly.

 

Now the correct name of the processor doesn't work at all, nor does the built-in for the SATA controller (there are two) to show the disk as internal. When I configure it as internal, the disk simply disappears.

 

I'll keep testing some things, I'll bring news if it works

 

[edit]

 

- Nothing done, the processor name simply remains as 'Unknown'. I have already configured the items:

Added RestrictEvents.kext

NVRAM > Add > 4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102 > revcpu | Number | 1

NVRAM > Add > 4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102 > revcpuname | String | AMD Ryzen Threadripper 3970X 32-Core

NVRAM > Add > 4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102 > revpatch | String | cpuname,sbvmm

NVRAM > Delete > 4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102 > revcpu

NVRAM > Delete > 4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102 > revcpuname

NVRAM > Delete > 4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102 > revpatch

ProcessorType = 3841

 

- SATA Controllers

When I add the built-in property | Data | 010000 to its DeviceProperties, it simply disappears, I've never seen this happen.

InnieKext don't work too.

 

 

 

Edited May 26 by luchina

[luchina]

@fabiosun,

 

I noticed something strange, when opening Cinebench 2024, it shows 50 Cores, 64 Threads.

 

 

[edit]

 

I'm going to force myself into an onion stalk LOL

I had put 32 and not 20 in the core mapping inside Kernel > Patch.

Now the CPU name and the number of cores are working correctly.

 

Edited May 26 by luchina

[fabiosun]

16 hours ago, luchina said:

NVRAM > Add > 4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102 > revcpu | Number | 1

NVRAM > Add > 4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102 > revcpuname | String | AMD Ryzen Threadripper 3970X 32-Core

NVRAM > Add > 4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102 > revpatch | String | cpuname,sbvmm

NVRAM > Delete > 4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102 > revcpu

NVRAM > Delete > 4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102 > revcpuname

NVRAM > Delete > 4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102 > revpatch

this part is not mandatory..only the bootarg could work

[luchina]

5 hours ago, fabiosun said:

this part is not mandatory..only the bootarg could work

 

You can also use all these parameters via boot-args, but in my opinion it is very cluttered, but both work.

 

The problem was that I actually put the core mapping in decimal and not hexadecimal, which is why the name correction failed.

 

Oh, and the corp cpuname script uses the configs in NVRAM too, it no longer uses them in boot-args.

 

But both work without any problems.

[fabiosun]

22 hours ago, luchina said:

revpatch | String | cpuname,sbvmm

i used only this as bootarg..also now  with my new AM5 platform

 

[Driftwood]

Sonoma 14.8 all good on TRX Creator 3970X Still 🙂
Basics to help you guys.
Aquantia 107 working etc...

 

 

Driftwood Sonoma 14.8 beta EFI.zip

Edited 21 minutes ago by Driftwood

[Driftwood]

TRX40 - Installing Sequoia Watchouts:
 

1. Boot Hangs or Kernel Panics Before Installer

• Cause: Missing or mis-scoped new leaf 7 allowance patch for Darwin 24.x.

• Without it, _cpuid_set_generic_info blocks CPUID leaf 7 and early kernel init fails.

• Fix: Ensure the MinKernel=24.0.0 leaf 7 patch is present and enabled (we did this in your Sequoia/Tahoe array).

---

2. PAT (Page Attribute Table) Changes

• Cause: Apple tweaked PAT handling in Sequoia → breaks older Ventura/Sonoma PAT patches.

• Symptom: Black screen after the Apple logo, or login window never appears.

• Fix: Use only the Algrey/Zormeister 15+ PAT variant. The Shaneee version can still work but tends to cause subtle GPU framebuffer quirks on TRX40.

---

3. Non-Monotonic Time Panics

• Cause: The scheduler trips over AMD’s TSC drift.

• Symptom: Panic messages mentioning non-monotonic or Quantum::invoke.

• Fix: Keep both “Visual” time patches covering 24.0.0–24.99.99. Without them, uptime-related panics are common after sleep or heavy load.

---

4. PCI Enumeration Oddities

• Cause: Newer IOPCIFamily builds in Sequoia can misread certain Threadripper bridges.

• Symptom: NVMe or certain USB controllers missing, or devices showing in System Profiler but not functioning.

• Fix: Keep “Disable 10-bit tags” patch active; avoid AM5-specific PCI patches, which can hang TRX40 entirely.

---

5. Aquantia 10GbE Driver Allocations

• Cause: Slight API change in AppleEthernetAquantiaAqtion in 24.x.

• Symptom: Network interface exists but won’t get DHCP / stalls under load.

• Fix: The alloc_dma_buffer and withOptions patches still work — keep them extended to 24.x.

---

6. Core Count Hardcoding

• Cause: Darwin 24+ scheduler changes can misdetect AMD core counts above 16 without patches.

• Symptom: System boots but shows wrong core/thread count; performance tanks.

• Fix: Use the 13.3+ cpuid_cores_per_package patch with 0x20 for 3970X.

---

7. Quirks and Kext Expectations

• Lilu & WhateverGreen need to be latest — older ones break in Sequoia with certain AMD GPUs.

• ProvideCurrentCpuInfo must be enabled or CPU info patching won’t apply.

• DisableIoMapper is still needed if VT-d is off in BIOS — but if you enable IOMMU + AMD patches, some TRX40 boards crash at boot.

 

Sequoia Survival Checklist tailored for TRX40 + Threadripper on AMD Hackintosh, so you can pre-flight your EFI before booting Darwin 24.x.

---

EFI / OpenCore Settings

1. OpenCore Version

   • Use latest release or debug build (as of now, OC 1.0.3+ recommended for Sequoia).

   • Older OC builds don’t handle Sequoia’s new kext linking behavior.

2. NVRAM Reset

   • Always Reset NVRAM after changing patches, kexts, or upgrading macOS.

   • Prevents stale CPU data or boot-arg conflicts.

3. Kernel → Quirks

   • ProvideCurrentCpuInfo = true

   • DisableIoMapper = true (unless you’ve verified working IOMMU on TRX40)

   • CustomSMBIOSGuid = true

   • PanicNoKextDump = true

   • AppleCpuPmCfgLock = true (avoid CPU power mgmt panic on some BIOS)

   • AppleXcpmExtraMsrs = true

   • CustomCPUID = only if running extra vendor masking (most don’t need)

4. Boot Args

   • Always keep:

     keepsyms=1 debug=0x100 alcid=1

     Add npci=0x2000 only if PCI enumeration hangs — remove if boot OK.

---

Kext Requirements

1. Always Latest:

   • Lilu

   • VirtualSMC

   • WhateverGreen

   • AppleALC

   • NVMeFix

   • SMCAMDProcessor (latest build for Sequoia, not older Ventura/Sonoma one)

2. Networking

   • Aquantia: latest AquantiaAqtion.kext with Sequoia support.

   • Intel: latest IntelMausi.

3. USB Mapping

   • Must be done with custom SSDT or USBMap.kext — Sequoia breaks some XHCI defaults.

---

Kernel Patches

1. CPUID Core Count (13.3+)

   • MinKernel=22.4.0 MaxKernel=25.99.99 → 0x20 for 3970X.

2. Leaf 7 Allowance (Sequoia)

   • MinKernel=24.0.0 MaxKernel=25.99.99

3. PAT Fix (15+)

   • Use Algrey/Zormeister 15+ only.

   • Shaneee 15+ is optional but not recommended for TRX40.

4. Non-Monotonic Time Fixes (Visual)

   • Two standard patches for Darwin 21–25.

5. PCI Fix

   • Disable 10-bit tags patch.

   • Do not enable AM5 PCI hotplug fix.

6. GenuineIntel Bypass

   • Goldfish64/algrey patch MinKernel=21.0.0–25.99.99.

---

BIOS Settings (TRX40)

1. Disable:

   • CSM

   • Secure Boot

   • Serial Port

   • Above 4G decoding (enable only if needed for GPUs with >4GB VRAM and your EFI supports it)

2. Enable:

   • XMP / DOCP for RAM

   • SVM (if running virtual machines)

   • HPET (High Precision Event Timer)

---

Before Booting Sequoia

• Test EFI first on Sonoma (Darwin 23) to confirm baseline stability.

• Update all kexts to the latest release from July 2025 or newer.

• Keep USB keyboard connected — wireless HID devices can fail during installer prelinkedkernel load.

Edited 16 minutes ago by Driftwood

[Driftwood]

Boot Sequoia (Darwin 24) and Tahoe (Darwin 25) without changing EFICombo TRX40 Patch set - Sequoia (Darwin 24) and Tahoe (Darwin 25) Patches to paste into your config.plist.zip

Tahoe TRX40 INSTALL - Pitfalls Checklist

1. Kernel & ACPI Compatibility

• Patches must be Darwin 25–aware — Sequoia-only EFI won’t boot without extending MaxKernel to 25.99.99.

• Watch for ACPI quirks:

  • Some TRX40 boards drop _CRS IRQ routing differently in newer macOS; keep SSDT-EC-USBX and SSDT-PLUG up-to-date.

  • Ensure SSDT-CPUR or SSDT-CPUR-ZEN matches your CPU topology (especially if you edited _SB.PR00).

• Keep Kernel → Quirks → ProvideCurrentCpuInfo enabled — Tahoe’s CPUID checks are slightly stricter.

---

2. PCI & IOPCIFamily Changes

• Tahoe has a rewritten PCI enumeration path:

  • The Disable 10-bit tags patch is still needed.

  • Don’t enable IOPCIIsHotplugPort AM5 patch — TRX40 doesn’t like it.

• If devices vanish after boot (especially NVMe on chipset lanes), double-check:

  • Above4GDecoding enabled in BIOS.

  • Resize BAR disabled.

---

3. GPU Drivers

• AMD Navi / RDNA2 GPUs:

  • Works if already working in Sequoia.

  • Check that agdpmod=pikera boot-arg is still set if you’re bypassing board-ID checks.

• RDNA3 (RX 7xxx):

  • Still experimental; some kext names changed in Tahoe — might require spoofing Device ID.

---

4. Audio (RME / PCIe Cards)

• If Fireface works in Sequoia, it should work in Tahoe — but:

  • Gatekeeper reset in upgrade will block unsigned RME extensions until re-authorized.

  • After install, run: 

    Terminal bash

    sudo spctl --master-disable
    sudo kextcache -i /

  • Then re-plug your device.

---

5. Networking

• Intel i210/i225 NICs:

  • Update IntelMausi or LucyRTL8125Ethernet to the latest before upgrade.

• If using Aquantia AQC107:

  • The Apple driver (AppleEthernetAquantiaAqtion) in Tahoe is fussier about PCI config space; may require device property injection.

---

6. Sleep / Wake

• Tahoe tightens non-monotonic time checks again.

  • Both Visual time patches must extend to Darwin 25 or you’ll kernel panic on wake.

• Disable Power Nap in System Settings; TRX40 firmware doesn’t play nice with it.

---

7. Security Changes

• amfi_get_out_of_my_way=1 is even more necessary for unsigned kexts in Tahoe.

• Some OC users needed csr-active-config set to 03080000 for post-install patches to load without SIP interference.

---

8. Installer Quirks

• When installing from USB:

  • Use Kernel → Quirks → DisableIoMapper = YES for first boot stage (workaround for TRX40 IOMMU mapping issue).

  • Re-enable after install if you need VT-d for virtual machines.

• Avoid hot-plugging USB during install — Tahoe is fussier about re-enumeration.

---

If you get stuck in the second boot stage (Apple logo ~50% then reboot), it’s almost always:

1. Missing or mis-ranged CPUID patch for Darwin 25.

2. PAT patch not applied for 15+ kernel.

3. GenuineIntel bypass missing.

Edited 18 minutes ago by Driftwood

[Driftwood]

Here’s a table showing recommended Secure Boot model + SIP (csr-active-config) combos for TRX40 AMD on Sonoma, Sequoia, and Tahoe — along with why each combo works best for stability and patch compatibility.

---

See Excel  xls Table attached.
 

  

---

Why not full SIP disable?

• Setting csr-active-config to FF0F0000 (full SIP off) will allow anything, but:

  • Breaks some macOS security preference panes.

  • Can trigger security audits in some DRM apps.

  • Not needed for standard AMD kernel patches.

---

Why not keep Secure Boot enabled in Tahoe?

• Tahoe’s new boot policy re-verifies some kernel signatures even after OpenCore patch injection.

• With SecureBootModel set to a real Mac, these checks can fail mid-boot on AMD and cause kernel panics or “Unable to verify kernel” messages.

• Disabling it bypasses that policy, making installs/upgrades smoother on TRX40.

 

SecureBoot_TRX40_Sonoma_Sequoia_Tahoe.xlsx.zip