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

[rolotrealanis]

Hello @rolotrealanis,

Which version of macOS are you running?

We are seeing improved hot plug behavior in macOS Ventura public beta. One experiment to try would be to install the public beta on a spare SSD, then installing UAD drivers and testing hot plug. In particular, please see this post:

Z490 & Z590 - Will Z590 ever have macOS Support ?

That is still 100% correct: The Buffalo drive uses a Thunderbolt connection, hence it's attached to RP05.UPSB.DSB3 (Thunderbolt port #2). This confirms that the Buffalo enclosure is connected via Thunderbolt. The Buffalo enclosure uses an internal SATA controller for the SATA hard drives...

www.tonymacx86.com

I'm on Monterey 12.5. I actually just deleted my Ventura Drive. I should try that again. I can't move to it yet since some of my software is still unsupported specifically from Rogue Amoeba.

 

[rolotrealanis]

Hello @rolotrealanis,

Which version of macOS are you running?

We are seeing improved hot plug behavior in macOS Ventura public beta. One experiment to try would be to install the public beta on a spare SSD, then installing UAD drivers and testing hot plug. In particular, please see this post:

Z490 & Z590 - Will Z590 ever have macOS Support ?

That is still 100% correct: The Buffalo drive uses a Thunderbolt connection, hence it's attached to RP05.UPSB.DSB3 (Thunderbolt port #2). This confirms that the Buffalo enclosure is connected via Thunderbolt. The Buffalo enclosure uses an internal SATA controller for the SATA hard drives...

www.tonymacx86.com

I installed the latest Public Beta from Apple, and everything is set up correctly. I installed the latest UAD drivers, and they work just like in Monterey. But I am experiencing the same hot plug behavior. So, sadly no luck in that department.

 

[rolotrealanis]

Hello @rolotrealanis,

Which version of macOS are you running?

We are seeing improved hot plug behavior in macOS Ventura public beta. One experiment to try would be to install the public beta on a spare SSD, then installing UAD drivers and testing hot plug. In particular, please see this post:

Z490 & Z590 - Will Z590 ever have macOS Support ?

That is still 100% correct: The Buffalo drive uses a Thunderbolt connection, hence it's attached to RP05.UPSB.DSB3 (Thunderbolt port #2). This confirms that the Buffalo enclosure is connected via Thunderbolt. The Buffalo enclosure uses an internal SATA controller for the SATA hard drives...

www.tonymacx86.com

One of my other questions about this Build is why the GPU had to be "spoofed" I doubt this reduces functionality but why did we have to declare it as a pci device in Device properties. Geekbench detects my 6900xt as AMD Radeon Unknown Prototype Compute Engine for Open CL and AMD Radeon HD GFX10 Family Unknown for Metal.

In Istatistica Pro, the Audio Controler is showing up as a graphics device.

It doesnt bother me but I wanted to know if this is regular and I haven't encountered this behavior in my other builds.

 

[CaseySJ]

One of my other questions about this Build is why the GPU had to be "spoofed" I doubt this reduces functionality but why did we have to declare it as a pci device in Device properties. Geekbench detects my 6900xt as AMD Radeon Unknown Prototype Compute Engine for Open CL and AMD Radeon HD GFX10 Family Unknown for Metal.

Spoofing refers to substituting the native DeviceID of an unsupported device with the DeviceID of a similar, but supported device. For some AMD 6900XTs this is necessary, but not for all.

Adding DeviceProperties such as model and name is purely cosmetic and optional.

In Istatistica Pro, the Audio Controler is showing up as a graphics device.

This is a common problem with iStatistica. On a Z690 system with a Radeon RX 580, for example, it picks up the real GPU. But on most other systems it gets confused

 

[CaseySJ]

I'm on Monterey 12.5. I actually just deleted my Ventura Drive. I should try that again. I can't move to it yet since some of my software is still unsupported specifically from Rogue Amoeba.

Does Thunderbolt hot plug work if you perform one sleep/wake cycle, then try to hot plug the device?

 

[rolotrealanis]

Does Thunderbolt hot plug work if you perform one sleep/wake cycle, then try to hot plug the device?

It Does not. Even though the Apollo is technically Thunderbolt 3, I wonder if the controller for it is Alpine Ridge or something, and that's why it may not be picking it up. I cant find those type of specs from Universal Audios product Manual. I know this is usually incorrect but system info shows the Apollo as a 2.5 Gt/s device which i believe is TB2 bandwidth.

 

[rolotrealanis]

Spoofing refers to substituting the native DeviceID of an unsupported device with the DeviceID of a similar, but supported device. For some AMD 6900XTs this is necessary, but not for all.

Adding DeviceProperties such as model and name is purely cosmetic and optional.


This is a common problem with iStatistica. On a Z690 system with a Radeon RX 580, for example, it picks up the real GPU. But on most other systems it gets confused

Oh Cool. I didn't have any issues without this in my previous build with this PowerColor Red Devil 6900XT. I'm gonna experiment with removing those device properties and just booting normally.

 

[rolotrealanis]

Oh Cool. I didn't have any issues without this in my previous build with this PowerColor Red Devil 6900XT. I'm gonna experiment with removing those device properties and just booting normally.

Removed those device properties, and, now, GeekBench shows the correct label for the compute engines and stuff. Everything seems fine without it. Thanks for the info.

 

[nmask]

Please try attached SSDT in combination with USBInjectAll 0.77

Thanks for support @CaseySJ !
Unfortunately, with provided SSDT the port limit didn't apply at all for some reason.
I can live without ASMedia ports, but only thing that bothers me is BT high CPU usage after sleep. BT falls in loop Searching new devices. I think it could be beta bug or something else.

 

[CaseySJ]

Thanks for support @CaseySJ !
Unfortunately with provided SSDT port limit didn't apply at all for some reason.
I can live without ASMedia ports, but only thing that bothers me is BT high CPU usage after sleep. BT falls in loop Searching new devices. I think it could be beta bug or something else.

The new SSDT contains some significant changes to the port map. Let's take another look. Feel free to post:

• IOReg file (IORegistryExplorer --> File --> Save As...)
• config.plist with serial numbers removed from PlatformInfo --> DataHub

Are you using USBInjectAll 0.7.7 from the link provided in previous post?