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 yesterday at 03:25 PM 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 yesterday at 05:56 PM 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